ticket summary component version milestone type severity owner status reporter created _changetime _description 291 Mondo restore process automatically deletes all files on NFS share mondo 2.2.7 defect critical Bruno Cornec reopened univ 2008-11-13T13:50:10+01:00 2013-12-19T18:26:54+01:00 "This is probably more related to mindi but I'm hoping to catch more attention if I select ""mondo"" instead. This should be fixed asap. There is a crucial issue: when booting from a mindi CD in order to restore from an ISO image which is sitting on a remote NFS server, mindi/mondo will, after completing the restore process (really just the last thing it does before dropping you to the shell after a successful restore and telling you to reboot via ""exit""), delete (!) all files on the mounted NFS share! (Of course this only works if you have write permission to the mounted NFS share) Using: - mondo-2.2.7-1.rhel5.x86_64.rpm - mindi-2.0.4-1.rhel5.x86_64.rpm - mindi-busybox-1.7.3-1.rhel5.x86_64.rpm On CentOS 5.2 64bit (x86_64) How to repeat: - Create an image using mondo with e.g. mondoarchive -On 192.168.0.1:/export/backup -d /testserver -E '/mnt /mnt/cdrom /tmp /proc /mnt/floppy' -T /tmp -s 700m -N -l GRUB -f /dev/cciss/c0d0 - Take the mindi ISO and burn it to a CD. This one: /var/cache/mindi/mondorescue.iso - Boot from the mindi CD and restore from the above mentioned NFS share (this will be mounted under /tmp/mondo[something]/nfsdir or /tmp.old/mondo... or similar to that). - At the very end of the successful restore process it will drop you to a shell and offer something like: enter ""exit"" to reboot. A couple of lines before that you will see that the restore script executed two ""rm"" commands on /tmp and/or /tmp.old (not sure, info comes from from memory, sorry.). You will notice this because it will report some errors like ""file or directory busy"" (something like that) when trying to delete. The rm commands seem to be recursive and since the NFS share is mounted there as well this probably results in all data on the mounted NFS share being deleted. I grep'ed through the scripts and it appears to be something about this file: /usr/lib64/mindi/rootfs/sbin/init Possibly somewhere around here where some rm's are being executed (the following can be found at around line 488 in /usr/lib64/mindi/rootfs/sbin/init): LogIt ""Great. Pivot succeeded w/ size=$size"" 1 echo -en ""Pivoting /tmp..."" umount /tmp/tmpfs mkdir -p /tmp.old mv /tmp/* /tmp.old/ # Try to Deal with a busybox bug on inexistant links cp /tmp/* /tmp.old/ rm -f /tmp/* $mount_cmd /tmp mv /tmp.old/* /tmp/ # Try to Deal with a busybox bug on inexistant links cp /tmp.old/* /tmp/ rm -rf /tmp.old mkdir -p /tmp/tmpfs mkdir -p $GROOVY If you need more info write me at ms2 at lightupnet dot de. " 627 Mondorestore CTL+ALT+DEL Fails to Cancel Repartitioning mondo 3.0.2 3.0.5 defect critical Bruno Cornec assigned SamK 2012-06-14T18:54:29+02:00 2014-12-17T19:57:33+01:00 "Ticket raised at the request of Bruno following a report in the mailing list. Fortunately this happened on a test rig. When mondorestore enters the countdown phase prior to repartitioning a disk it instructs the user that the process may be cancelled by the combination keystroke CTL-ALT-DEL. This does not work. This process continues and destroys the partition structure, then recreates it and applies a file system. I think it is important that this feature should work as stated on the screen advice. " 667 issue at restore time with cLVM mondo 3.0.2 3.0.5 defect critical Bruno Cornec new Bruno Cornec 2013-02-21T21:06:48+01:00 2013-03-04T18:11:23+01:00 "at restore time, when using cLVM, mondorestore doesn't seem to be able to access the LVs created correctly, format and then mount them. Part of logs relevant: {{{ running: lvm pvscan > //mondo.tmp.OD94fk/mondo-run-prog-thing.tmp 2> //mondo.tmp.OD94fk/mondo-run-prog-thing.err --------------------------------start of output----------------------------- PV /dev/sda2 VG systemvg lvm2 [598.91 GiB / 598.91 GiB free] Total: 1 [598.91 GiB] / in use: 1 [598.91 GiB] / in no VG: 0 [0 ] File descriptor 3 (/tmp/prep.sh) leaked on lvm invocation. Parent PID 7869: sh File descriptor 4 (/proc/mdstat) leaked on lvm invocation. Parent PID 7869: sh File descriptor 5 (/proc/mdstat) leaked on lvm invocation. Parent PID 7869: sh File descriptor 6 (/proc/mdstat) leaked on lvm invocation. Parent PID 7869: sh File descriptor 7 (/proc/mdstat) leaked on lvm invocation. Parent PID 7869: sh File descriptor 8 (/tmp/i-want-my-lvm) leaked on lvm invocation. Parent PID 7869: sh connect() failed on local socket: No such file or directory Internal cluster locking initialisation failed. WARNING: Falling back to local file-based locking. Volume Groups with the clustered attribute will be inaccessible. --------------------------------end of output------------------------------ ...ran just fine. :-) lvm vgchange -a y systemvg --> 0 lvm lvcreate -L 4096m -r auto -n root_lv systemvg --> 0 lvm lvcreate -L 16384m -r auto -n swap_lv systemvg --> 0 lvm lvcreate -L 2048m -r auto -n tmp_lv systemvg --> 0 lvm lvcreate -L 8192m -r auto -n var_lv systemvg --> 0 lvm lvcreate -L 4096m -r auto -n usr_lv systemvg --> 0 lvm lvcreate -L 4096m -r auto -n opt_lv systemvg --> 0 lvm vgscan --> 0 }}} After that point no LV FS is used by mondorestore." 870 Mondo Backup failed with error --> *** buffer overflow detected ***: mondoarchive terminated mondo 3.2.2 3.3.0 defect critical Bruno Cornec assigned Darshit Doshi 2020-11-28T14:28:13+01:00 2020-12-01T01:08:02+01:00 "{{{ [root@frdatlxstadm jcl]# ./Mondo-BCK.sh Validation du point de montage mondorescue:/data/col1/unixadmin/mondo_image. Affichage du point de montage Filesystem 1024-blocks Used Available Capacity Mounted on mondorescue:/data/col1/unixadmin/mondo_image 586882068480 462095400960 124786667520 79% /mnt/mondo_image Validation des repertoire de travail /mnt/mondo_image/scratch/frdatlxstadm & /mnt/mondo_image/tmp/frdatlxstadm Creation de /mnt/mondo_image/scratch/frdatlxstadm Creation de /mnt/mondo_image/tmp/frdatlxstadm Determination de la version de mondorescue (choix du separateur des excludes FS. SEPARATOR=| Exclusion AUTO = /dev|/dev/shm|/run|/sys/fs/cgroup|/fs03/PRO/commun|/fs01/appl/PRO/aguila|/tmp|/opt|/fs01/appl/PRO/ctmagent|/run/user/0|/mnt/mondo_image Debut de la sauvegarde mondorescue. See /var/log/mondoarchive.log for details of backup run. Checking sanity of your Linux distribution Done. Excluding the following file systems on /dev/shm: ==> | Making catalog of files to be backed up ---evalcall---1--- Making catalog of / ---evalcall---2--- TASK: [*...................] 3% done; 0:32 to go ---evalcall---E--- ---evalcall---1--- Making catalog of / ---evalcall---2--- TASK: [**..................] 9% done; 0:20 to go ---evalcall---E--- ---evalcall---1--- Making catalog of / ---evalcall---2--- TASK: [****................] 16% done; 0:15 to go ---evalcall---E--- ---evalcall---1--- Making catalog of / ---evalcall---2--- TASK: [****................] 20% done; 0:16 to go ---evalcall---E--- ---evalcall---1--- Making catalog of / ---evalcall---2--- TASK: [******..............] 26% done; 0:14 to go ---evalcall---E--- ---evalcall---1--- Making catalog of / ---evalcall---2--- TASK: [*******.............] 32% done; 0:12 to go ---evalcall---E--- ---evalcall---1--- Making catalog of / ---evalcall---2--- TASK: [********............] 37% done; 0:11 to go ---evalcall---E--- ---evalcall---1--- Making catalog of / ---evalcall---2--- TASK: [*********...........] 43% done; 0:10 to go ---evalcall---E--- ---evalcall---1--- Making catalog of / ---evalcall---2--- TASK: [**********..........] 49% done; 0:09 to go ---evalcall---E--- ---evalcall---1--- Making catalog of / ---evalcall---2--- TASK: [***********.........] 55% done; 0:08 to go ---evalcall---E--- ---evalcall---1--- Making catalog of / ---evalcall---2--- TASK: [************........] 56% done; 0:08 to go ---evalcall---E--- ---evalcall---1--- Making catalog of / ---evalcall---2--- TASK: [************........] 59% done; 0:09 to go ---evalcall---E--- ---evalcall---1--- Making catalog of / ---evalcall---2--- TASK: [*************.......] 62% done; 0:08 to go ---evalcall---E--- ---evalcall---1--- Making catalog of / ---evalcall---2--- TASK: [**************......] 70% done; 0:06 to go ---evalcall---E--- ---evalcall---1--- Making catalog of / ---evalcall---2--- TASK: [****************....] 77% done; 0:04 to go ---evalcall---E--- ---evalcall---1--- Making catalog of / ---evalcall---2--- TASK: [*****************...] 84% done; 0:03 to go ---evalcall---E--- ---evalcall---1--- Making catalog of / ---evalcall---2--- TASK: [******************..] 87% done; 0:02 to go ---evalcall---E--- ---evalcall---1--- Making catalog of / ---evalcall---2--- TASK: [*******************.] 91% done; 0:01 to go ---evalcall---E--- ---evalcall---1--- Making catalog of / ---evalcall---2--- TASK: [*******************.] 94% done; 0:01 to go ---evalcall---E--- ---evalcall---1--- Making catalog of / ---evalcall---2--- TASK: [********************] 96% done; 0:00 to go ---evalcall---E--- ---evalcall---1--- Making catalog of / ---evalcall---2--- TASK: [********************] 97% done; 0:00 to go ---evalcall---E--- Done. Dividing filelist into sets Dividing filelist into sets. Please wait. ---evalcall---1--- Dividing filelist into sets ---evalcall---2--- TASK: [*...................] 3% done; 0:32 to go ---evalcall---E--- ---evalcall---1--- Dividing filelist into sets ---evalcall---2--- TASK: [*...................] 4% done; 0:24 to go ---evalcall---E--- ---evalcall---1--- Dividing filelist into sets ---evalcall---2--- TASK: [*...................] 5% done; 0:19 to go ---evalcall---E--- ---evalcall---1--- Dividing filelist into sets ---evalcall---2--- TASK: [**..................] 6% done; 0:15 to go ---evalcall---E--- ---evalcall---1--- Dividing filelist into sets ---evalcall---2--- TASK: [**..................] 7% done; 0:13 to go ---evalcall---E--- ---evalcall---1--- Dividing filelist into sets ---evalcall---2--- TASK: [**..................] 8% done; 0:11 to go ---evalcall---E--- ---evalcall---1--- Dividing filelist into sets ---evalcall---2--- TASK: [**..................] 9% done; 0:20 to go ---evalcall---E--- ---evalcall---1--- Dividing filelist into sets ---evalcall---2--- TASK: [**..................] 10% done; 0:18 to go ---evalcall---E--- ---evalcall---1--- Dividing filelist into sets ---evalcall---2--- TASK: [***.................] 11% done; 0:16 to go ---evalcall---E--- ---evalcall---1--- Dividing filelist into sets ---evalcall---2--- TASK: [***.................] 12% done; 0:14 to go ---evalcall---E--- ---evalcall---1--- Dividing filelist into sets ---evalcall---2--- TASK: [***.................] 13% done; 0:13 to go ---evalcall---E--- ---evalcall---1--- Dividing filelist into sets ---evalcall---2--- TASK: [***.................] 14% done; 0:12 to go ---evalcall---E--- ---evalcall---1--- Dividing filelist into sets ---evalcall---2--- TASK: [***.................] 15% done; 0:11 to go ---evalcall---E--- ---evalcall---1--- Dividing filelist into sets ---evalcall---2--- TASK: [****................] 16% done; 0:15 to go ---evalcall---E--- ---evalcall---1--- Dividing filelist into sets ---evalcall---2--- TASK: [****................] 17% done; 0:14 to go ---evalcall---E--- ---evalcall---1--- Dividing filelist into sets ---evalcall---2--- TASK: [****................] 18% done; 0:13 to go ---evalcall---E--- ---evalcall---1--- Dividing filelist into sets ---evalcall---2--- TASK: [****................] 19% done; 0:12 to go ---evalcall---E--- ---evalcall---1--- Dividing filelist into sets ---evalcall---2--- TASK: [****................] 20% done; 0:16 to go ---evalcall---E--- ---evalcall---1--- Dividing filelist into sets ---evalcall---2--- TASK: [*****...............] 21% done; 0:15 to go ---evalcall---E--- ---evalcall---1--- Dividing filelist into sets ---evalcall---2--- TASK: [*****...............] 22% done; 0:14 to go ---evalcall---E--- ---evalcall---1--- Dividing filelist into sets ---evalcall---2--- TASK: [*****...............] 23% done; 0:13 to go ---evalcall---E--- ---evalcall---1--- Dividing filelist into sets ---evalcall---2--- TASK: [*****...............] 24% done; 0:12 to go ---evalcall---E--- ---evalcall---1--- Dividing filelist into sets ---evalcall---2--- TASK: [******..............] 26% done; 0:11 to go ---evalcall---E--- ---evalcall---1--- Dividing filelist into sets ---evalcall---2--- TASK: [******..............] 27% done; 0:10 to go ---evalcall---E--- ---evalcall---1--- Dividing filelist into sets ---evalcall---2--- TASK: [******..............] 28% done; 0:10 to go ---evalcall---E--- ---evalcall---1--- Dividing filelist into sets ---evalcall---2--- TASK: [******..............] 29% done; 0:09 to go ---evalcall---E--- ---evalcall---1--- Dividing filelist into sets ---evalcall---2--- TASK: [******..............] 30% done; 0:09 to go ---evalcall---E--- ---evalcall---1--- Dividing filelist into sets ---evalcall---2--- TASK: [*******.............] 31% done; 0:08 to go ---evalcall---E--- ---evalcall---1--- Dividing filelist into sets ---evalcall---2--- TASK: [*******.............] 34% done; 0:07 to go ---evalcall---E--- ---evalcall---1--- Dividing filelist into sets ---evalcall---2--- TASK: [*******.............] 35% done; 0:09 to go ---evalcall---E--- ---evalcall---1--- Dividing filelist into sets ---evalcall---2--- TASK: [********............] 36% done; 0:08 to go ---evalcall---E--- ---evalcall---1--- Dividing filelist into sets ---evalcall---2--- TASK: [********............] 37% done; 0:08 to go ---evalcall---E--- ---evalcall---1--- Dividing filelist into sets ---evalcall---2--- TASK: [********............] 38% done; 0:08 to go ---evalcall---E--- ---evalcall---1--- Dividing filelist into sets ---evalcall---2--- TASK: [********............] 40% done; 0:07 to go ---evalcall---E--- ---evalcall---1--- Dividing filelist into sets ---evalcall---2--- TASK: [*********...........] 41% done; 0:07 to go ---evalcall---E--- ---evalcall---1--- Dividing filelist into sets ---evalcall---2--- TASK: [*********...........] 42% done; 0:06 to go ---evalcall---E--- ---evalcall---1--- Dividing filelist into sets ---evalcall---2--- TASK: [*********...........] 44% done; 0:06 to go ---evalcall---E--- ---evalcall---1--- Dividing filelist into sets ---evalcall---2--- TASK: [**********..........] 50% done; 0:06 to go ---evalcall---E--- ---evalcall---1--- Dividing filelist into sets ---evalcall---2--- TASK: [***********.........] 51% done; 0:05 to go ---evalcall---E--- ---evalcall---1--- Dividing filelist into sets ---evalcall---2--- TASK: [***********.........] 53% done; 0:05 to go ---evalcall---E--- ---evalcall---1--- Dividing filelist into sets ---evalcall---2--- TASK: [************........] 60% done; 0:04 to go ---evalcall---E--- ---evalcall---1--- Dividing filelist into sets ---evalcall---2--- TASK: [*************.......] 61% done; 0:03 to go ---evalcall---E--- ---evalcall---1--- Dividing filelist into sets ---evalcall---2--- TASK: [*************.......] 62% done; 0:03 to go ---evalcall---E--- ---evalcall---1--- Dividing filelist into sets ---evalcall---2--- TASK: [*************.......] 64% done; 0:03 to go ---evalcall---E--- ---evalcall---1--- Dividing filelist into sets ---evalcall---2--- TASK: [***************.....] 71% done; 0:02 to go ---evalcall---E--- ---evalcall---1--- Dividing filelist into sets ---evalcall---2--- TASK: [***************.....] 72% done; 0:02 to go ---evalcall---E--- ---evalcall---1--- Dividing filelist into sets ---evalcall---2--- TASK: [***************.....] 74% done; 0:02 to go ---evalcall---E--- ---evalcall---1--- Dividing filelist into sets ---evalcall---2--- TASK: [****************....] 76% done; 0:02 to go ---evalcall---E--- ---evalcall---1--- Dividing filelist into sets ---evalcall---2--- TASK: [****************....] 79% done; 0:01 to go ---evalcall---E--- ---evalcall---1--- Dividing filelist into sets ---evalcall---2--- TASK: [****************....] 80% done; 0:01 to go ---evalcall---E--- ---evalcall---1--- Dividing filelist into sets ---evalcall---2--- TASK: [*****************...] 81% done; 0:02 to go ---evalcall---E--- ---evalcall---1--- Dividing filelist into sets ---evalcall---2--- TASK: [*****************...] 82% done; 0:01 to go ---evalcall---E--- ---evalcall---1--- Dividing filelist into sets ---evalcall---2--- TASK: [*****************...] 83% done; 0:01 to go ---evalcall---E--- ---evalcall---1--- Dividing filelist into sets ---evalcall---2--- TASK: [*****************...] 84% done; 0:01 to go ---evalcall---E--- ---evalcall---1--- Dividing filelist into sets ---evalcall---2--- TASK: [******************..] 86% done; 0:01 to go ---evalcall---E--- ---evalcall---1--- Dividing filelist into sets ---evalcall---2--- TASK: [******************..] 87% done; 0:01 to go ---evalcall---E--- ---evalcall---1--- Dividing filelist into sets ---evalcall---2--- TASK: [******************..] 88% done; 0:01 to go ---evalcall---E--- ---evalcall---1--- Dividing filelist into sets ---evalcall---2--- TASK: [******************..] 89% done; 0:01 to go ---evalcall---E--- ---evalcall---1--- Dividing filelist into sets ---evalcall---2--- TASK: [*******************.] 91% done; 0:00 to go ---evalcall---E--- ---evalcall---1--- Dividing filelist into sets ---evalcall---2--- TASK: [*******************.] 92% done; 0:00 to go ---evalcall---E--- ---evalcall---1--- Dividing filelist into sets ---evalcall---2--- TASK: [*******************.] 93% done; 0:00 to go ---evalcall---E--- ---evalcall---1--- Dividing filelist into sets ---evalcall---2--- TASK: [*******************.] 94% done; 0:00 to go ---evalcall---E--- ---evalcall---1--- Dividing filelist into sets ---evalcall---2--- TASK: [********************] 96% done; 0:00 to go ---evalcall---E--- ---evalcall---1--- Dividing filelist into sets ---evalcall---2--- TASK: [********************] 97% done; 0:00 to go ---evalcall---E--- ---evalcall---1--- Dividing filelist into sets ---evalcall---2--- TASK: [********************] 98% done; 0:00 to go ---evalcall---E--- ---evalcall---1--- Dividing filelist into sets ---evalcall---2--- TASK: [********************] 99% done; 0:00 to go ---evalcall---E--- Your backup will probably occupy a single nfs. Maybe two. Done. Copying Mondo's core files to the scratch directory Done. Calling MINDI to create boot+data disks Your boot loader is GRUB and it boots from /dev/sda Boot loader version string: grub2-install (GRUB) 2.02~beta2 ---evalcall---1--- Calling MINDI to create boot+data disk ---evalcall---2--- TASK: [*...................] 3% done; 0:00 to go ---evalcall---E--- ---evalcall---1--- Calling MINDI for boot disk ---evalcall---2--- TASK: [***.................] 15% done; 0:11 to go ---evalcall---E--- ---evalcall---1--- Calling MINDI for boot disk ---evalcall---2--- TASK: [******..............] 29% done; 0:07 to go ---evalcall---E--- ---evalcall---1--- Calling MINDI for boot disk ---evalcall---2--- TASK: [********............] 39% done; 0:06 to go ---evalcall---E--- ---evalcall---1--- Calling MINDI for boot disk ---evalcall---2--- TASK: [*********...........] 44% done; 0:06 to go ---evalcall---E--- ---evalcall---1--- Calling MINDI for boot disk ---evalcall---2--- TASK: [**********..........] 48% done; 0:06 to go ---evalcall---E--- ---evalcall---1--- Calling MINDI for boot disk ---evalcall---2--- TASK: [***********.........] 52% done; 0:06 to go ---evalcall---E--- ---evalcall---1--- Calling MINDI for boot disk ---evalcall---2--- TASK: [************........] 56% done; 0:06 to go ---evalcall---E--- ---evalcall---1--- Calling MINDI for boot disk ---evalcall---2--- TASK: [*************.......] 65% done; 0:04 to go ---evalcall---E--- ---evalcall---1--- Calling MINDI for boot disk ---evalcall---2--- TASK: [*****************...] 82% done; 0:02 to go ---evalcall---E--- ---evalcall---1--- Calling MINDI for boot disk ---evalcall---2--- TASK: [*****************...] 83% done; 0:07 to go ---evalcall---E--- ---evalcall---1--- Calling MINDI for boot disk ---evalcall---2--- TASK: [*****************...] 85% done; 0:07 to go ---evalcall---E--- ---evalcall---1--- Calling MINDI for boot disk ---evalcall---2--- TASK: [******************..] 86% done; 0:06 to go ---evalcall---E--- ---evalcall---1--- Calling MINDI for boot disk ---evalcall---2--- TASK: [******************..] 88% done; 0:05 to go ---evalcall---E--- ---evalcall---1--- Calling MINDI for boot disk ---evalcall---2--- TASK: [*******************.] 91% done; 0:04 to go ---evalcall---E--- ---evalcall---1--- Calling MINDI for boot disk ---evalcall---2--- TASK: [*******************.] 95% done; 0:02 to go ---evalcall---E--- ---evalcall---1--- Calling MINDI for boot disk ---evalcall---2--- TASK: [********************] 100% done; 0:00 to go ---evalcall---E--- Boot+data disks were created OK Done. Preparing to archive your data Done. Archiving regular files to media Archiving regular files ---progress-form---1--- I am backing up your live filesystem now. ---progress-form---2--- Please wait. This may take a couple of hours. ---progress-form---3--- Working... ---progress-form---E--- ---progress-form---4--- TASK: [*...................] 1% done; 0:00 to go ---progress-form---1--- I am backing up your live filesystem now. ---progress-form---2--- nfs 1: [**..................] 9% used ---progress-form---3--- Please wait. This may take a couple of hours. ---progress-form---E--- ---progress-form---4--- TASK: [*...................] 1% done; 30:18 to go ---progress-form---1--- I am backing up your live filesystem now. ---progress-form---2--- nfs 1: [**..................] 10% used ---progress-form---3--- Please wait. This may take a couple of hours. ---progress-form---E--- ---progress-form---4--- TASK: [*...................] 1% done; 16:45 to go ---progress-form---1--- I am backing up your live filesystem now. ---progress-form---2--- nfs 1: [**..................] 10% used ---progress-form---3--- Please wait. This may take a couple of hours. ---progress-form---E--- ---progress-form---4--- TASK: [*...................] 1% done; 11:06 to go ---progress-form---1--- I am backing up your live filesystem now. ---progress-form---2--- nfs 1: [***.................] 11% used ---progress-form---3--- Please wait. This may take a couple of hours. ---progress-form---E--- ---progress-form---4--- TASK: [*...................] 1% done; 10:46 to go ---progress-form---1--- I am backing up your live filesystem now. ---progress-form---2--- nfs 1: [***.................] 11% used ---progress-form---3--- Please wait. This may take a couple of hours. ---progress-form---E--- ---progress-form---4--- TASK: [*...................] 2% done; 8:34 to go ---progress-form---1--- I am backing up your live filesystem now. ---progress-form---2--- nfs 1: [***.................] 12% used ---progress-form---3--- Please wait. This may take a couple of hours. ---progress-form---E--- ---progress-form---4--- TASK: [*...................] 2% done; 8:45 to go ---progress-form---1--- I am backing up your live filesystem now. ---progress-form---2--- nfs 1: [***.................] 12% used ---progress-form---3--- Please wait. This may take a couple of hours. ---progress-form---E--- ---progress-form---4--- TASK: [*...................] 3% done; 7:28 to go ---progress-form---1--- I am backing up your live filesystem now. ---progress-form---2--- nfs 1: [***.................] 12% used ---progress-form---3--- Please wait. This may take a couple of hours. ---progress-form---E--- ---progress-form---4--- TASK: [*...................] 3% done; 6:30 to go ---progress-form---1--- I am backing up your live filesystem now. ---progress-form---2--- nfs 1: [***.................] 13% used ---progress-form---3--- Please wait. This may take a couple of hours. ---progress-form---E--- ---progress-form---4--- TASK: [*...................] 4% done; 5:44 to go ---progress-form---1--- I am backing up your live filesystem now. ---progress-form---2--- nfs 1: [***.................] 13% used ---progress-form---3--- Please wait. This may take a couple of hours. ---progress-form---E--- ---progress-form---4--- TASK: [*...................] 4% done; 5:08 to go ---progress-form---1--- I am backing up your live filesystem now. ---progress-form---2--- nfs 1: [***.................] 14% used ---progress-form---3--- Please wait. This may take a couple of hours. ---progress-form---E--- ---progress-form---4--- TASK: [*...................] 5% done; 4:39 to go ---progress-form---1--- I am backing up your live filesystem now. ---progress-form---2--- nfs 1: [***.................] 14% used ---progress-form---3--- Please wait. This may take a couple of hours. ---progress-form---E--- ---progress-form---4--- TASK: [*...................] 5% done; 4:14 to go ---progress-form---1--- I am backing up your live filesystem now. ---progress-form---2--- nfs 1: [***.................] 14% used ---progress-form---3--- Please wait. This may take a couple of hours. ---progress-form---E--- ---progress-form---4--- TASK: [**..................] 6% done; 4:52 to go ---progress-form---1--- I am backing up your live filesystem now. ---progress-form---2--- nfs 1: [***.................] 15% used ---progress-form---3--- Please wait. This may take a couple of hours. ---progress-form---E--- ---progress-form---4--- TASK: [**..................] 6% done; 4:30 to go ---progress-form---1--- I am backing up your live filesystem now. ---progress-form---2--- nfs 1: [***.................] 15% used ---progress-form---3--- Please wait. This may take a couple of hours. ---progress-form---E--- ---progress-form---4--- TASK: [**..................] 7% done; 4:23 to go ---progress-form---1--- I am backing up your live filesystem now. ---progress-form---2--- nfs 1: [***.................] 15% used ---progress-form---3--- Please wait. This may take a couple of hours. ---progress-form---E--- ---progress-form---4--- TASK: [**..................] 7% done; 4:17 to go ---progress-form---1--- I am backing up your live filesystem now. ---progress-form---2--- nfs 1: [***.................] 15% used ---progress-form---3--- Please wait. This may take a couple of hours. ---progress-form---E--- ---progress-form---4--- TASK: [**..................] 8% done; 4:11 to go ---progress-form---1--- I am backing up your live filesystem now. ---progress-form---2--- nfs 1: [***.................] 15% used ---progress-form---3--- Please wait. This may take a couple of hours. ---progress-form---E--- ---progress-form---4--- TASK: [**..................] 8% done; 4:16 to go ---progress-form---1--- I am backing up your live filesystem now. ---progress-form---2--- nfs 1: [***.................] 15% used ---progress-form---3--- Please wait. This may take a couple of hours. ---progress-form---E--- ---progress-form---4--- TASK: [**..................] 9% done; 4:11 to go ---progress-form---1--- I am backing up your live filesystem now. ---progress-form---2--- nfs 1: [****................] 16% used ---progress-form---3--- Please wait. This may take a couple of hours. ---progress-form---E--- ---progress-form---4--- TASK: [**..................] 9% done; 3:57 to go ---progress-form---1--- I am backing up your live filesystem now. ---progress-form---2--- nfs 1: [****................] 16% used ---progress-form---3--- Please wait. This may take a couple of hours. ---progress-form---E--- ---progress-form---4--- TASK: [**..................] 10% done; 4:11 to go ---progress-form---1--- I am backing up your live filesystem now. ---progress-form---2--- nfs 1: [****................] 16% used ---progress-form---3--- Please wait. This may take a couple of hours. ---progress-form---E--- ---progress-form---4--- TASK: [**..................] 10% done; 3:58 to go ---progress-form---1--- I am backing up your live filesystem now. ---progress-form---2--- nfs 1: [****................] 16% used ---progress-form---3--- Please wait. This may take a couple of hours. ---progress-form---E--- ---progress-form---4--- TASK: [***.................] 11% done; 4:02 to go ---progress-form---1--- I am backing up your live filesystem now. ---progress-form---2--- nfs 1: [****................] 16% used ---progress-form---3--- Please wait. This may take a couple of hours. ---progress-form---E--- ---progress-form---4--- TASK: [***.................] 11% done; 3:51 to go ---progress-form---1--- I am backing up your live filesystem now. ---progress-form---2--- nfs 1: [****................] 17% used ---progress-form---3--- Please wait. This may take a couple of hours. ---progress-form---E--- ---progress-form---4--- TASK: [***.................] 12% done; 3:54 to go ---progress-form---1--- I am backing up your live filesystem now. ---progress-form---2--- nfs 1: [****................] 17% used ---progress-form---3--- Please wait. This may take a couple of hours. ---progress-form---E--- ---progress-form---4--- TASK: [***.................] 12% done; 3:51 to go ---progress-form---1--- I am backing up your live filesystem now. ---progress-form---2--- nfs 1: [****................] 17% used ---progress-form---3--- Please wait. This may take a couple of hours. ---progress-form---E--- ---progress-form---4--- TASK: [***.................] 13% done; 3:48 to go ---progress-form---1--- I am backing up your live filesystem now. ---progress-form---2--- nfs 1: [****................] 17% used ---progress-form---3--- Please wait. This may take a couple of hours. ---progress-form---E--- ---progress-form---4--- TASK: [***.................] 13% done; 3:45 to go ---progress-form---1--- I am backing up your live filesystem now. ---progress-form---2--- nfs 1: [****................] 18% used ---progress-form---3--- Please wait. This may take a couple of hours. ---progress-form---E--- ---progress-form---4--- TASK: [***.................] 14% done; 3:42 to go ---progress-form---1--- I am backing up your live filesystem now. ---progress-form---2--- nfs 1: [****................] 18% used ---progress-form---3--- Please wait. This may take a couple of hours. ---progress-form---E--- ---progress-form---4--- TASK: [***.................] 14% done; 3:44 to go ---progress-form---1--- I am backing up your live filesystem now. ---progress-form---2--- nfs 1: [****................] 18% used ---progress-form---3--- Please wait. This may take a couple of hours. ---progress-form---E--- ---progress-form---4--- TASK: [***.................] 15% done; 3:41 to go ---progress-form---1--- I am backing up your live filesystem now. ---progress-form---2--- nfs 1: [****................] 18% used ---progress-form---3--- Please wait. This may take a couple of hours. ---progress-form---E--- ---progress-form---4--- TASK: [***.................] 15% done; 3:39 to go ---progress-form---1--- I am backing up your live filesystem now. ---progress-form---2--- nfs 1: [****................] 18% used ---progress-form---3--- Please wait. This may take a couple of hours. ---progress-form---E--- ---progress-form---4--- TASK: [****................] 16% done; 3:36 to go ---progress-form---1--- I am backing up your live filesystem now. ---progress-form---2--- nfs 1: [****................] 18% used ---progress-form---3--- Please wait. This may take a couple of hours. ---progress-form---E--- ---progress-form---4--- TASK: [****................] 16% done; 3:33 to go ---progress-form---1--- I am backing up your live filesystem now. ---progress-form---2--- nfs 1: [****................] 18% used ---progress-form---3--- Please wait. This may take a couple of hours. ---progress-form---E--- ---progress-form---4--- TASK: [****................] 17% done; 3:31 to go ---progress-form---1--- I am backing up your live filesystem now. ---progress-form---2--- nfs 1: [****................] 19% used ---progress-form---3--- Please wait. This may take a couple of hours. ---progress-form---E--- ---progress-form---4--- TASK: [****................] 17% done; 3:33 to go ---progress-form---1--- I am backing up your live filesystem now. ---progress-form---2--- nfs 1: [****................] 19% used ---progress-form---3--- Please wait. This may take a couple of hours. ---progress-form---E--- ---progress-form---4--- TASK: [****................] 18% done; 3:26 to go ---progress-form---1--- I am backing up your live filesystem now. ---progress-form---2--- nfs 1: [****................] 19% used ---progress-form---3--- Please wait. This may take a couple of hours. ---progress-form---E--- ---progress-form---4--- TASK: [****................] 18% done; 3:32 to go ---progress-form---1--- I am backing up your live filesystem now. ---progress-form---2--- nfs 1: [****................] 19% used ---progress-form---3--- Please wait. This may take a couple of hours. ---progress-form---E--- ---progress-form---4--- TASK: [****................] 19% done; 3:34 to go ---progress-form---1--- I am backing up your live filesystem now. ---progress-form---2--- nfs 1: [****................] 20% used ---progress-form---3--- Please wait. This may take a couple of hours. ---progress-form---E--- ---progress-form---4--- TASK: [****................] 19% done; 3:35 to go ---progress-form---1--- I am backing up your live filesystem now. ---progress-form---2--- nfs 1: [****................] 20% used ---progress-form---3--- Please wait. This may take a couple of hours. ---progress-form---E--- ---progress-form---4--- TASK: [****................] 20% done; 3:37 to go ---progress-form---1--- I am backing up your live filesystem now. ---progress-form---2--- nfs 1: [****................] 20% used ---progress-form---3--- Please wait. This may take a couple of hours. ---progress-form---E--- ---progress-form---4--- TASK: [****................] 20% done; 3:42 to go ---progress-form---1--- I am backing up your live filesystem now. ---progress-form---2--- nfs 1: [*****...............] 21% used ---progress-form---3--- Please wait. This may take a couple of hours. ---progress-form---E--- ---progress-form---4--- TASK: [*****...............] 21% done; 3:46 to go ---progress-form---1--- I am backing up your live filesystem now. ---progress-form---2--- nfs 1: [*****...............] 21% used ---progress-form---3--- Please wait. This may take a couple of hours. ---progress-form---E--- ---progress-form---4--- TASK: [*****...............] 21% done; 3:51 to go ---progress-form---1--- I am backing up your live filesystem now. ---progress-form---2--- nfs 1: [*****...............] 21% used ---progress-form---3--- Please wait. This may take a couple of hours. ---progress-form---E--- ---progress-form---4--- TASK: [*****...............] 22% done; 3:48 to go ---progress-form---1--- I am backing up your live filesystem now. ---progress-form---2--- nfs 1: [*****...............] 21% used ---progress-form---3--- Please wait. This may take a couple of hours. ---progress-form---E--- ---progress-form---4--- TASK: [*****...............] 22% done; 3:45 to go ---progress-form---1--- I am backing up your live filesystem now. ---progress-form---2--- nfs 1: [*****...............] 22% used ---progress-form---3--- Please wait. This may take a couple of hours. ---progress-form---E--- ---progress-form---4--- TASK: [*****...............] 23% done; 3:49 to go ---progress-form---1--- I am backing up your live filesystem now. ---progress-form---2--- nfs 1: [*****...............] 22% used ---progress-form---3--- Please wait. This may take a couple of hours. ---progress-form---E--- ---progress-form---4--- TASK: [*****...............] 23% done; 3:42 to go ---progress-form---1--- I am backing up your live filesystem now. ---progress-form---2--- nfs 1: [*****...............] 22% used ---progress-form---3--- Please wait. This may take a couple of hours. ---progress-form---E--- ---progress-form---4--- TASK: [*****...............] 24% done; 3:40 to go ---progress-form---1--- I am backing up your live filesystem now. ---progress-form---2--- nfs 1: [*****...............] 22% used ---progress-form---3--- Please wait. This may take a couple of hours. ---progress-form---E--- ---progress-form---4--- TASK: [*****...............] 24% done; 3:37 to go ---progress-form---1--- I am backing up your live filesystem now. ---progress-form---2--- nfs 1: [*****...............] 22% used ---progress-form---3--- Please wait. This may take a couple of hours. ---progress-form---E--- ---progress-form---4--- TASK: [*****...............] 25% done; 3:34 to go ---progress-form---1--- I am backing up your live filesystem now. ---progress-form---2--- nfs 1: [*****...............] 22% used ---progress-form---3--- Please wait. This may take a couple of hours. ---progress-form---E--- ---progress-form---4--- TASK: [*****...............] 25% done; 3:34 to go ---progress-form---1--- I am backing up your live filesystem now. ---progress-form---2--- nfs 1: [*****...............] 22% used ---progress-form---3--- Please wait. This may take a couple of hours. ---progress-form---E--- ---progress-form---4--- TASK: [******..............] 26% done; 3:32 to go ---progress-form---1--- I am backing up your live filesystem now. ---progress-form---2--- nfs 1: [*****...............] 23% used ---progress-form---3--- Please wait. This may take a couple of hours. ---progress-form---E--- ---progress-form---4--- TASK: [******..............] 26% done; 3:32 to go ---progress-form---1--- I am backing up your live filesystem now. ---progress-form---2--- nfs 1: [*****...............] 23% used ---progress-form---3--- Please wait. This may take a couple of hours. ---progress-form---E--- ---progress-form---4--- TASK: [******..............] 27% done; 3:29 to go ---progress-form---1--- I am backing up your live filesystem now. ---progress-form---2--- nfs 1: [*****...............] 23% used ---progress-form---3--- Please wait. This may take a couple of hours. ---progress-form---E--- ---progress-form---4--- TASK: [******..............] 27% done; 3:27 to go ---progress-form---1--- I am backing up your live filesystem now. ---progress-form---2--- nfs 1: [*****...............] 23% used ---progress-form---3--- Please wait. This may take a couple of hours. ---progress-form---E--- ---progress-form---4--- TASK: [******..............] 28% done; 3:24 to go ---progress-form---1--- I am backing up your live filesystem now. ---progress-form---2--- nfs 1: [*****...............] 23% used ---progress-form---3--- Please wait. This may take a couple of hours. ---progress-form---E--- ---progress-form---4--- TASK: [******..............] 28% done; 3:20 to go ---progress-form---1--- I am backing up your live filesystem now. ---progress-form---2--- nfs 1: [*****...............] 23% used ---progress-form---3--- Please wait. This may take a couple of hours. ---progress-form---E--- ---progress-form---4--- TASK: [******..............] 29% done; 3:20 to go ---progress-form---1--- I am backing up your live filesystem now. ---progress-form---2--- nfs 1: [*****...............] 23% used ---progress-form---3--- Please wait. This may take a couple of hours. ---progress-form---E--- ---progress-form---4--- TASK: [******..............] 29% done; 3:17 to go ---progress-form---1--- I am backing up your live filesystem now. ---progress-form---2--- nfs 1: [*****...............] 24% used ---progress-form---3--- Please wait. This may take a couple of hours. ---progress-form---E--- ---progress-form---4--- TASK: [******..............] 30% done; 3:15 to go ---progress-form---1--- I am backing up your live filesystem now. ---progress-form---2--- nfs 1: [*****...............] 24% used ---progress-form---3--- Please wait. This may take a couple of hours. ---progress-form---E--- ---progress-form---4--- TASK: [******..............] 30% done; 3:11 to go ---progress-form---1--- I am backing up your live filesystem now. ---progress-form---2--- nfs 1: [*****...............] 24% used ---progress-form---3--- Please wait. This may take a couple of hours. ---progress-form---E--- ---progress-form---4--- TASK: [*******.............] 31% done; 3:08 to go ---progress-form---1--- I am backing up your live filesystem now. ---progress-form---2--- nfs 1: [*****...............] 24% used ---progress-form---3--- Please wait. This may take a couple of hours. ---progress-form---E--- ---progress-form---4--- TASK: [*******.............] 31% done; 3:04 to go ---progress-form---1--- I am backing up your live filesystem now. ---progress-form---2--- nfs 1: [*****...............] 24% used ---progress-form---3--- Please wait. This may take a couple of hours. ---progress-form---E--- ---progress-form---4--- TASK: [*******.............] 32% done; 3:00 to go ---progress-form---1--- I am backing up your live filesystem now. ---progress-form---2--- nfs 1: [*****...............] 24% used ---progress-form---3--- Please wait. This may take a couple of hours. ---progress-form---E--- ---progress-form---4--- TASK: [*******.............] 32% done; 2:58 to go ---progress-form---1--- I am backing up your live filesystem now. ---progress-form---2--- nfs 1: [*****...............] 24% used ---progress-form---3--- Please wait. This may take a couple of hours. ---progress-form---E--- ---progress-form---4--- TASK: [*******.............] 33% done; 2:54 to go ---progress-form---1--- I am backing up your live filesystem now. ---progress-form---2--- nfs 1: [*****...............] 24% used ---progress-form---3--- Please wait. This may take a couple of hours. ---progress-form---E--- ---progress-form---4--- TASK: [*******.............] 33% done; 2:54 to go ---progress-form---1--- I am backing up your live filesystem now. ---progress-form---2--- nfs 1: [*****...............] 24% used ---progress-form---3--- Please wait. This may take a couple of hours. ---progress-form---E--- ---progress-form---4--- TASK: [*******.............] 33% done; 2:52 to go ---progress-form---1--- I am backing up your live filesystem now. ---progress-form---2--- nfs 1: [*****...............] 24% used ---progress-form---3--- Please wait. This may take a couple of hours. ---progress-form---E--- ---progress-form---4--- TASK: [*******.............] 34% done; 2:51 to go ---progress-form---1--- I am backing up your live filesystem now. ---progress-form---2--- nfs 1: [*****...............] 24% used ---progress-form---3--- Please wait. This may take a couple of hours. ---progress-form---E--- ---progress-form---4--- TASK: [*******.............] 34% done; 2:47 to go ---progress-form---1--- I am backing up your live filesystem now. ---progress-form---2--- nfs 1: [*****...............] 25% used ---progress-form---3--- Please wait. This may take a couple of hours. ---progress-form---E--- ---progress-form---4--- TASK: [*******.............] 35% done; 2:49 to go ---progress-form---1--- I am backing up your live filesystem now. ---progress-form---2--- nfs 1: [*****...............] 25% used ---progress-form---3--- Please wait. This may take a couple of hours. ---progress-form---E--- ---progress-form---4--- TASK: [*******.............] 35% done; 2:50 to go ---progress-form---1--- I am backing up your live filesystem now. ---progress-form---2--- nfs 1: [*****...............] 25% used ---progress-form---3--- Please wait. This may take a couple of hours. ---progress-form---E--- ---progress-form---4--- TASK: [********............] 36% done; 2:47 to go ---progress-form---1--- I am backing up your live filesystem now. ---progress-form---2--- nfs 1: [*****...............] 25% used ---progress-form---3--- Please wait. This may take a couple of hours. ---progress-form---E--- ---progress-form---4--- TASK: [********............] 36% done; 2:47 to go ---progress-form---1--- I am backing up your live filesystem now. ---progress-form---2--- nfs 1: [******..............] 26% used ---progress-form---3--- Please wait. This may take a couple of hours. ---progress-form---E--- ---progress-form---4--- TASK: [********............] 37% done; 2:45 to go ---progress-form---1--- I am backing up your live filesystem now. ---progress-form---2--- nfs 1: [******..............] 26% used ---progress-form---3--- Please wait. This may take a couple of hours. ---progress-form---E--- ---progress-form---4--- TASK: [********............] 37% done; 2:45 to go ---progress-form---1--- I am backing up your live filesystem now. ---progress-form---2--- nfs 1: [******..............] 26% used ---progress-form---3--- Please wait. This may take a couple of hours. ---progress-form---E--- ---progress-form---4--- TASK: [********............] 38% done; 2:45 to go ---progress-form---1--- I am backing up your live filesystem now. ---progress-form---2--- nfs 1: [******..............] 27% used ---progress-form---3--- Please wait. This may take a couple of hours. ---progress-form---E--- ---progress-form---4--- TASK: [********............] 38% done; 2:43 to go ---progress-form---1--- I am backing up your live filesystem now. ---progress-form---2--- nfs 1: [******..............] 27% used ---progress-form---3--- Please wait. This may take a couple of hours. ---progress-form---E--- ---progress-form---4--- TASK: [********............] 39% done; 2:39 to go ---progress-form---1--- I am backing up your live filesystem now. ---progress-form---2--- nfs 1: [******..............] 27% used ---progress-form---3--- Please wait. This may take a couple of hours. ---progress-form---E--- ---progress-form---4--- TASK: [********............] 39% done; 2:39 to go ---progress-form---1--- I am backing up your live filesystem now. ---progress-form---2--- nfs 1: [******..............] 27% used ---progress-form---3--- Please wait. This may take a couple of hours. ---progress-form---E--- ---progress-form---4--- TASK: [********............] 40% done; 2:36 to go ---progress-form---1--- I am backing up your live filesystem now. ---progress-form---2--- nfs 1: [******..............] 27% used ---progress-form---3--- Please wait. This may take a couple of hours. ---progress-form---E--- ---progress-form---4--- TASK: [********............] 40% done; 2:37 to go ---progress-form---1--- I am backing up your live filesystem now. ---progress-form---2--- nfs 1: [******..............] 27% used ---progress-form---3--- Please wait. This may take a couple of hours. ---progress-form---E--- ---progress-form---4--- TASK: [*********...........] 41% done; 2:34 to go ---progress-form---1--- I am backing up your live filesystem now. ---progress-form---2--- nfs 1: [******..............] 27% used ---progress-form---3--- Please wait. This may take a couple of hours. ---progress-form---E--- ---progress-form---4--- TASK: [*********...........] 41% done; 2:32 to go ---progress-form---1--- I am backing up your live filesystem now. ---progress-form---2--- nfs 1: [******..............] 28% used ---progress-form---3--- Please wait. This may take a couple of hours. ---progress-form---E--- ---progress-form---4--- TASK: [*********...........] 42% done; 2:32 to go ---progress-form---1--- I am backing up your live filesystem now. ---progress-form---2--- nfs 1: [******..............] 28% used ---progress-form---3--- Please wait. This may take a couple of hours. ---progress-form---E--- ---progress-form---4--- TASK: [*********...........] 42% done; 2:29 to go ---progress-form---1--- I am backing up your live filesystem now. ---progress-form---2--- nfs 1: [******..............] 28% used ---progress-form---3--- Please wait. This may take a couple of hours. ---progress-form---E--- ---progress-form---4--- TASK: [*********...........] 43% done; 2:26 to go ---progress-form---1--- I am backing up your live filesystem now. ---progress-form---2--- nfs 1: [******..............] 28% used ---progress-form---3--- Please wait. This may take a couple of hours. ---progress-form---E--- ---progress-form---4--- TASK: [*********...........] 43% done; 2:24 to go ---progress-form---1--- I am backing up your live filesystem now. ---progress-form---2--- nfs 1: [******..............] 28% used ---progress-form---3--- Please wait. This may take a couple of hours. ---progress-form---E--- ---progress-form---4--- TASK: [*********...........] 44% done; 2:24 to go ---progress-form---1--- I am backing up your live filesystem now. ---progress-form---2--- nfs 1: [******..............] 28% used ---progress-form---3--- Please wait. This may take a couple of hours. ---progress-form---E--- ---progress-form---4--- TASK: [*********...........] 44% done; 2:21 to go ---progress-form---1--- I am backing up your live filesystem now. ---progress-form---2--- nfs 1: [******..............] 29% used ---progress-form---3--- Please wait. This may take a couple of hours. ---progress-form---E--- ---progress-form---4--- TASK: [*********...........] 45% done; 2:21 to go ---progress-form---1--- I am backing up your live filesystem now. ---progress-form---2--- nfs 1: [******..............] 29% used ---progress-form---3--- Please wait. This may take a couple of hours. ---progress-form---E--- ---progress-form---4--- TASK: [*********...........] 45% done; 2:18 to go ---progress-form---1--- I am backing up your live filesystem now. ---progress-form---2--- nfs 1: [******..............] 29% used ---progress-form---3--- Please wait. This may take a couple of hours. ---progress-form---E--- ---progress-form---4--- TASK: [**********..........] 46% done; 2:16 to go ---progress-form---1--- I am backing up your live filesystem now. ---progress-form---2--- nfs 1: [******..............] 29% used ---progress-form---3--- Please wait. This may take a couple of hours. ---progress-form---E--- ---progress-form---4--- TASK: [**********..........] 46% done; 2:16 to go ---progress-form---1--- I am backing up your live filesystem now. ---progress-form---2--- nfs 1: [******..............] 29% used ---progress-form---3--- Please wait. This may take a couple of hours. ---progress-form---E--- ---progress-form---4--- TASK: [**********..........] 47% done; 2:14 to go ---progress-form---1--- I am backing up your live filesystem now. ---progress-form---2--- nfs 1: [******..............] 29% used ---progress-form---3--- Please wait. This may take a couple of hours. ---progress-form---E--- ---progress-form---4--- TASK: [**********..........] 47% done; 2:13 to go ---progress-form---1--- I am backing up your live filesystem now. ---progress-form---2--- nfs 1: [******..............] 29% used ---progress-form---3--- Please wait. This may take a couple of hours. ---progress-form---E--- ---progress-form---4--- TASK: [**********..........] 48% done; 2:11 to go ---progress-form---1--- I am backing up your live filesystem now. ---progress-form---2--- nfs 1: [******..............] 30% used ---progress-form---3--- Please wait. This may take a couple of hours. ---progress-form---E--- ---progress-form---4--- TASK: [**********..........] 48% done; 2:09 to go ---progress-form---1--- I am backing up your live filesystem now. ---progress-form---2--- nfs 1: [******..............] 30% used ---progress-form---3--- Please wait. This may take a couple of hours. ---progress-form---E--- ---progress-form---4--- TASK: [**********..........] 49% done; 2:06 to go ---progress-form---1--- I am backing up your live filesystem now. ---progress-form---2--- nfs 1: [******..............] 30% used ---progress-form---3--- Please wait. This may take a couple of hours. ---progress-form---E--- ---progress-form---4--- TASK: [**********..........] 49% done; 2:08 to go ---progress-form---1--- I am backing up your live filesystem now. ---progress-form---2--- nfs 1: [******..............] 30% used ---progress-form---3--- Please wait. This may take a couple of hours. ---progress-form---E--- ---progress-form---4--- TASK: [**********..........] 50% done; 2:06 to go ---progress-form---1--- I am backing up your live filesystem now. ---progress-form---2--- nfs 1: [******..............] 30% used ---progress-form---3--- Please wait. This may take a couple of hours. ---progress-form---E--- ---progress-form---4--- TASK: [**********..........] 50% done; 2:05 to go ---progress-form---1--- I am backing up your live filesystem now. ---progress-form---2--- nfs 1: [******..............] 30% used ---progress-form---3--- Please wait. This may take a couple of hours. ---progress-form---E--- ---progress-form---4--- TASK: [***********.........] 51% done; 2:04 to go ---progress-form---1--- I am backing up your live filesystem now. ---progress-form---2--- nfs 1: [******..............] 30% used ---progress-form---3--- Please wait. This may take a couple of hours. ---progress-form---E--- ---progress-form---4--- TASK: [***********.........] 51% done; 2:03 to go ---progress-form---1--- I am backing up your live filesystem now. ---progress-form---2--- nfs 1: [*******.............] 31% used ---progress-form---3--- Please wait. This may take a couple of hours. ---progress-form---E--- ---progress-form---4--- TASK: [***********.........] 52% done; 2:01 to go ---progress-form---1--- I am backing up your live filesystem now. ---progress-form---2--- nfs 1: [*******.............] 31% used ---progress-form---3--- Please wait. This may take a couple of hours. ---progress-form---E--- ---progress-form---4--- TASK: [***********.........] 52% done; 1:59 to go ---progress-form---1--- I am backing up your live filesystem now. ---progress-form---2--- nfs 1: [*******.............] 31% used ---progress-form---3--- Please wait. This may take a couple of hours. ---progress-form---E--- ---progress-form---4--- TASK: [***********.........] 53% done; 1:57 to go ---progress-form---1--- I am backing up your live filesystem now. ---progress-form---2--- nfs 1: [*******.............] 31% used ---progress-form---3--- Please wait. This may take a couple of hours. ---progress-form---E--- ---progress-form---4--- TASK: [***********.........] 53% done; 1:56 to go ---progress-form---1--- I am backing up your live filesystem now. ---progress-form---2--- nfs 1: [*******.............] 31% used ---progress-form---3--- Please wait. This may take a couple of hours. ---progress-form---E--- ---progress-form---4--- TASK: [***********.........] 54% done; 1:55 to go ---progress-form---1--- I am backing up your live filesystem now. ---progress-form---2--- nfs 1: [*******.............] 31% used ---progress-form---3--- Please wait. This may take a couple of hours. ---progress-form---E--- ---progress-form---4--- TASK: [***********.........] 54% done; 1:54 to go ---progress-form---1--- I am backing up your live filesystem now. ---progress-form---2--- nfs 1: [*******.............] 32% used ---progress-form---3--- Please wait. This may take a couple of hours. ---progress-form---E--- ---progress-form---4--- TASK: [***********.........] 55% done; 1:52 to go ---progress-form---1--- I am backing up your live filesystem now. ---progress-form---2--- nfs 1: [*******.............] 32% used ---progress-form---3--- Please wait. This may take a couple of hours. ---progress-form---E--- ---progress-form---4--- TASK: [***********.........] 55% done; 1:51 to go ---progress-form---1--- I am backing up your live filesystem now. ---progress-form---2--- nfs 1: [*******.............] 32% used ---progress-form---3--- Please wait. This may take a couple of hours. ---progress-form---E--- ---progress-form---4--- TASK: [************........] 56% done; 1:49 to go ---progress-form---1--- I am backing up your live filesystem now. ---progress-form---2--- nfs 1: [*******.............] 32% used ---progress-form---3--- Please wait. This may take a couple of hours. ---progress-form---E--- ---progress-form---4--- TASK: [************........] 56% done; 1:49 to go ---progress-form---1--- I am backing up your live filesystem now. ---progress-form---2--- nfs 1: [*******.............] 32% used ---progress-form---3--- Please wait. This may take a couple of hours. ---progress-form---E--- ---progress-form---4--- TASK: [************........] 57% done; 1:48 to go ---progress-form---1--- I am backing up your live filesystem now. ---progress-form---2--- nfs 1: [*******.............] 32% used ---progress-form---3--- Please wait. This may take a couple of hours. ---progress-form---E--- ---progress-form---4--- TASK: [************........] 57% done; 1:45 to go ---progress-form---1--- I am backing up your live filesystem now. ---progress-form---2--- nfs 1: [*******.............] 33% used ---progress-form---3--- Please wait. This may take a couple of hours. ---progress-form---E--- ---progress-form---4--- TASK: [************........] 58% done; 1:44 to go ---progress-form---1--- I am backing up your live filesystem now. ---progress-form---2--- nfs 1: [*******.............] 33% used ---progress-form---3--- Please wait. This may take a couple of hours. ---progress-form---E--- ---progress-form---4--- TASK: [************........] 58% done; 1:42 to go ---progress-form---1--- I am backing up your live filesystem now. ---progress-form---2--- nfs 1: [*******.............] 33% used ---progress-form---3--- Please wait. This may take a couple of hours. ---progress-form---E--- ---progress-form---4--- TASK: [************........] 59% done; 1:40 to go ---progress-form---1--- I am backing up your live filesystem now. ---progress-form---2--- nfs 1: [*******.............] 33% used ---progress-form---3--- Please wait. This may take a couple of hours. ---progress-form---E--- ---progress-form---4--- TASK: [************........] 59% done; 1:38 to go ---progress-form---1--- I am backing up your live filesystem now. ---progress-form---2--- nfs 1: [*******.............] 34% used ---progress-form---3--- Please wait. This may take a couple of hours. ---progress-form---E--- ---progress-form---4--- TASK: [************........] 60% done; 1:36 to go ---progress-form---1--- I am backing up your live filesystem now. ---progress-form---2--- nfs 1: [*******.............] 34% used ---progress-form---3--- Please wait. This may take a couple of hours. ---progress-form---E--- ---progress-form---4--- TASK: [************........] 60% done; 1:34 to go ---progress-form---1--- I am backing up your live filesystem now. ---progress-form---2--- nfs 1: [*******.............] 34% used ---progress-form---3--- Please wait. This may take a couple of hours. ---progress-form---E--- ---progress-form---4--- TASK: [*************.......] 61% done; 1:32 to go ---progress-form---1--- I am backing up your live filesystem now. ---progress-form---2--- nfs 1: [*******.............] 34% used ---progress-form---3--- Please wait. This may take a couple of hours. ---progress-form---E--- ---progress-form---4--- TASK: [*************.......] 61% done; 1:30 to go ---progress-form---1--- I am backing up your live filesystem now. ---progress-form---2--- nfs 1: [*******.............] 34% used ---progress-form---3--- Please wait. This may take a couple of hours. ---progress-form---E--- ---progress-form---4--- TASK: [*************.......] 62% done; 1:29 to go ---progress-form---1--- I am backing up your live filesystem now. ---progress-form---2--- nfs 1: [*******.............] 34% used ---progress-form---3--- Please wait. This may take a couple of hours. ---progress-form---E--- ---progress-form---4--- TASK: [*************.......] 62% done; 1:27 to go ---progress-form---1--- I am backing up your live filesystem now. ---progress-form---2--- nfs 1: [*******.............] 34% used ---progress-form---3--- Please wait. This may take a couple of hours. ---progress-form---E--- ---progress-form---4--- TASK: [*************.......] 63% done; 1:27 to go ---progress-form---1--- I am backing up your live filesystem now. ---progress-form---2--- nfs 1: [*******.............] 34% used ---progress-form---3--- Please wait. This may take a couple of hours. ---progress-form---E--- ---progress-form---4--- TASK: [*************.......] 63% done; 1:25 to go ---progress-form---1--- I am backing up your live filesystem now. ---progress-form---2--- nfs 1: [*******.............] 34% used ---progress-form---3--- Please wait. This may take a couple of hours. ---progress-form---E--- ---progress-form---4--- TASK: [*************.......] 64% done; 1:24 to go Please be patient. Do not be alarmed by on-screen inactivity. ---evalcall---1--- Running mkisofs to make nfs #1 ---evalcall---2--- TASK: [***************.....] 73% done; 0:00 to go ---evalcall---E--- ---evalcall---1--- Running mkisofs to make nfs #1 ---evalcall---2--- TASK: [******************..] 86% done; 0:00 to go ---evalcall---E--- ---evalcall---1--- Running mkisofs to make nfs #1 ---evalcall---2--- TASK: [*******************.] 95% done; 0:00 to go ---evalcall---E--- ---evalcall---1--- Running mkisofs to make nfs #1 ---evalcall---2--- TASK: [********************] 99% done; 0:00 to go ---evalcall---E--- Call to mkisofs to make ISO (nfs #1) ...OK *** buffer overflow detected ***: mondoarchive terminated ======= Backtrace: ========= /lib64/libc.so.6(__fortify_fail+0x37)[0x7fe2dbbe6b67] /lib64/libc.so.6(+0x115ce2)[0x7fe2dbbe4ce2] mondoarchive[0x433263] mondoarchive[0x406c15] mondoarchive[0x407d82] mondoarchive[0x40d158] mondoarchive[0x403335] /lib64/libc.so.6(__libc_start_main+0xf5)[0x7fe2dbaf1495] mondoarchive[0x4039e5] ======= Memory map: ======== 00400000-00453000 r-xp 00000000 fd:01 4201113 /usr/sbin/mondoarchive 00652000-00653000 r--p 00052000 fd:01 4201113 /usr/sbin/mondoarchive 00653000-00654000 rw-p 00053000 fd:01 4201113 /usr/sbin/mondoarchive 00654000-00659000 rw-p 00000000 00:00 0 01e46000-01e6d000 rw-p 00000000 00:00 0 [heap] 7fe2cc000000-7fe2cc021000 rw-p 00000000 00:00 0 7fe2cc021000-7fe2d0000000 ---p 00000000 00:00 0 7fe2d0000000-7fe2d0021000 rw-p 00000000 00:00 0 7fe2d0021000-7fe2d4000000 ---p 00000000 00:00 0 7fe2d4000000-7fe2d4021000 rw-p 00000000 00:00 0 7fe2d4021000-7fe2d8000000 ---p 00000000 00:00 0 7fe2d9838000-7fe2d9839000 ---p 00000000 00:00 0 7fe2d9839000-7fe2da039000 rw-p 00000000 00:00 0 7fe2da039000-7fe2da03a000 ---p 00000000 00:00 0 7fe2da03a000-7fe2da83a000 rw-p 00000000 00:00 0 7fe2da83a000-7fe2da84f000 r-xp 00000000 fd:01 4212339 /usr/lib64/libgcc_s-4.8.5-20150702.so.1 7fe2da84f000-7fe2daa4e000 ---p 00015000 fd:01 4212339 /usr/lib64/libgcc_s-4.8.5-20150702.so.1 7fe2daa4e000-7fe2daa4f000 r--p 00014000 fd:01 4212339 /usr/lib64/libgcc_s-4.8.5-20150702.so.1 7fe2daa4f000-7fe2daa50000 rw-p 00015000 fd:01 4212339 /usr/lib64/libgcc_s-4.8.5-20150702.so.1 7fe2daa50000-7fe2daa51000 ---p 00000000 00:00 0 7fe2daa51000-7fe2db251000 rw-p 00000000 00:00 0 7fe2db251000-7fe2db352000 r-xp 00000000 fd:01 4358714 /usr/lib64/libm-2.17.so 7fe2db352000-7fe2db551000 ---p 00101000 fd:01 4358714 /usr/lib64/libm-2.17.so 7fe2db551000-7fe2db552000 r--p 00100000 fd:01 4358714 /usr/lib64/libm-2.17.so 7fe2db552000-7fe2db553000 rw-p 00101000 fd:01 4358714 /usr/lib64/libm-2.17.so 7fe2db553000-7fe2db555000 r-xp 00000000 fd:01 4358712 /usr/lib64/libdl-2.17.so 7fe2db555000-7fe2db755000 ---p 00002000 fd:01 4358712 /usr/lib64/libdl-2.17.so 7fe2db755000-7fe2db756000 r--p 00002000 fd:01 4358712 /usr/lib64/libdl-2.17.so 7fe2db756000-7fe2db757000 rw-p 00003000 fd:01 4358712 /usr/lib64/libdl-2.17.so 7fe2db757000-7fe2db84e000 r-xp 00000000 fd:01 4201118 /usr/lib64/libslang.so.2.2.4 7fe2db84e000-7fe2dba4e000 ---p 000f7000 fd:01 4201118 /usr/lib64/libslang.so.2.2.4 7fe2dba4e000-7fe2dba52000 r--p 000f7000 fd:01 4201118 /usr/lib64/libslang.so.2.2.4 7fe2dba52000-7fe2dba6b000 rw-p 000fb000 fd:01 4201118 /usr/lib64/libslang.so.2.2.4 7fe2dba6b000-7fe2dbacf000 rw-p 00000000 00:00 0 7fe2dbacf000-7fe2dbc91000 r-xp 00000000 fd:01 4212187 /usr/lib64/libc-2.17.so 7fe2dbc91000-7fe2dbe91000 ---p 001c2000 fd:01 4212187 /usr/lib64/libc-2.17.so 7fe2dbe91000-7fe2dbe95000 r--p 001c2000 fd:01 4212187 /usr/lib64/libc-2.17.so 7fe2dbe95000-7fe2dbe97000 rw-p 001c6000 fd:01 4212187 /usr/lib64/libc-2.17.so 7fe2dbe97000-7fe2dbe9c000 rw-p 00000000 00:00 0 7fe2dbe9c000-7fe2dbeb3000 r-xp 00000000 fd:01 4358925 /usr/lib64/libpthread-2.17.so 7fe2dbeb3000-7fe2dc0b2000 ---p 00017000 fd:01 4358925 /usr/lib64/libpthread-2.17.so 7fe2dc0b2000-7fe2dc0b3000 r--p 00016000 fd:01 4358925 /usr/lib64/libpthread-2.17.so 7fe2dc0b3000-7fe2dc0b4000 rw-p 00017000 fd:01 4358925 /usr/lib64/libpthread-2.17.so 7fe2dc0b4000-7fe2dc0b8000 rw-p 00000000 00:00 0 7fe2dc0b8000-7fe2dc0cc000 r-xp 00000000 fd:01 4290257 /usr/lib64/libnewt.so.0.52.15 7fe2dc0cc000-7fe2dc2cb000 ---p 00014000 fd:01 4290257 /usr/lib64/libnewt.so.0.52.15 7fe2dc2cb000-7fe2dc2cc000 r--p 00013000 fd:01 4290257 /usr/lib64/libnewt.so.0.52.15 7fe2dc2cc000-7fe2dc2cd000 rw-p 00014000 fd:01 4290257 /usr/lib64/libnewt.so.0.52.15 7fe2dc2cd000-7fe2dc2ef000 r-xp 00000000 fd:01 4212178 /usr/lib64/ld-2.17.so 7fe2dc4dc000-7fe2dc4e1000 rw-p 00000000 00:00 0 7fe2dc4eb000-7fe2dc4ee000 rw-p 00000000 00:00 0 7fe2dc4ee000-7fe2dc4ef000 r--p 00021000 fd:01 4212178 /usr/lib64/ld-2.17.so 7fe2dc4ef000-7fe2dc4f0000 rw-p 00022000 fd:01 4212178 /usr/lib64/ld-2.17.so 7fe2dc4f0000-7fe2dc4f1000 rw-p 00000000 00:00 0 7fff29871000-7fff29892000 rw-p 00000000 00:00 0 [stack] 7fff29928000-7fff2992a000 r-xp 00000000 00:00 0 [vdso] ffffffffff600000-ffffffffff601000 r-xp 00000000 00:00 0 [vsyscall] SIGABRT signal received from OS Abort - probably failed assertion. I'm sleeping for a few seconds so you can rea Fatal error... MondoRescue is terminating in response to a signal from the OS ---FATALERROR--- MondoRescue is terminating in response to a signal from the OS If you require technical support, please contact the mailing list. See http://www.mondorescue.org for details. The list's members can help you, if you attach that file to your e-mail. Log file: /var/log/mondoarchive.log Mondo has aborted. (archive_this_fileset) - filelist /mnt/mondo_image/tmp/frdatlxstadm/mondo.tmp.XL Errors occurred while archiving set 140. Please review logs. Execution run ended; result=254 Type 'less /var/log/mondoarchive.log' to see the output log Mondo backup process erreur. voir log /mnt/mondo_image/frdatlxstadm_20201128.log Purge ne gardant que les 5 derniers backups. Menage fichiers temporaires... [root@frdatlxstadm jcl]# }}}" 869 No Release File mondo 3.2.2 3.3.0 defect normal Bruno Cornec assigned KitchM 2020-09-23T19:03:27+02:00 2020-10-08T01:58:22+02:00 "E: The repository 'http://mondo.mirror.pclark.com/ftp/pub/mondorescue/debian/10 buster Release' does not have a Release file. Cannot install because of that." 338 restore problem mondo 2.2.8 defect blocker Bruno Cornec assigned Olaf Matthaei 2009-05-12T16:06:35+02:00 2013-12-19T18:26:54+01:00 "Hello, i'm using sles 10 sp2 x62_64 with mondo 2.2.8-1. The archive prozess running fine, but when i start restore on the same Hardware he stops every time at the same position. He can't configure the harddisks/raids. When i look of the partition with fdisk after mondo stops it looks not nice ( see fdisk.jpg ). I see on device /dev/cciss/c0d1p2 start and end cylinder at 1. The orignal system have no second partion on this device( see fdisk_original.jpg ). " 379 mondoarchive should try to protect itself against recursive links mondo 2.2.9.1 defect blocker Bruno Cornec new Bruno Cornec 2010-01-04T12:40:46+01:00 2013-12-19T18:26:54+01:00 "{{{ Excerpt from /var/log /mondoarchive.log after the occurrence of such an error: ~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ...... [Main] libmondo-filelist.c->mondo_makefilelist#1691: Including / in filelist /home/mondo.tmp.fIPstD/tmpfs/filelist.full Making catalog of / Making catalog of / opendir /home/students/11a/ekizer/Kugel_Willi & Erol/Kugel_Willi & Erol/Kugel_Willi & Erol/Kugel_Willi & Erol/Kugel_Willi & Erol/Kugel_Willi & Erol/Kugel_Willi & Erol/Kugel_Willi & Erol/Kugel_Willi & Erol/Kugel_Willi & Erol/Kugel_Willi & Erol/Kugel_Willi & Erol/Kugel_Willi & Erol/Kugel_Willi & Erol/Kugel_Willi & Erol/Kugel_Willi & Erol/Kugel_Willi & Erol/Kugel_Willi & Erol/Kugel_Willi & Er ý (No such file or directory) SIGABRT signal received from OS Abort - probably failed assertion. I'm sleeping for a few seconds so you can read the message. [Main] newt-specific.c->fatal_error#296: Fatal error received - 'MondoRescue is terminating in response to a signal from the OS' [Main] newt-specific.c->fatal_error#314: OK, I think I'm the main PID. [Main] newt-specific.c->fatal_error#322: I'm going to do some cleaning up now. [Main] newt-specific.c->fatal_error#323: killall mindi 2> /dev/null running: ps auxww | grep "" /mondo/do-not "" | awk '{print $2;}' | grep -v ""grep"" > /home/mondo.tmp.fIPstD/mondo-run-prog-thing.tmp 2> /home/mondo.tmp.fIPstD/mondo-run-prog-thing.err .... }}}" 15 mondorestore conitnue to restore even with FS full mondo 2.0.8 defect critical Bruno Cornec new Bruno Cornec 2006-08-01T00:15:34+02:00 2013-12-19T18:26:54+01:00 mondorestore doesn't check whether a file system is full and continue to restore on it. Check afio's return code maybe ? 783 wrong dependencies in mondo SLES 12 rpm package mondo 3.2.2 defect critical Bruno Cornec reopened Bruno Cornec 2015-11-06T15:50:19+01:00 2017-08-31T03:52:34+02:00 "When I run {{{ #zypper install mondo }}} on my sles 12 x86_64 VM server I receive the following error: {{{ Problem: nothing provides mkisofs needed by mondo-3.2.1-1.sles12.x86_64 Solution 1: do not install mondo-3.2.1-1.sles12.x86_64 Solution 2: break mondo-3.2.1-1.sles12.x86_64 by ignoring some of its dependencies ......snip........ # zypper search --provides mkisofs i | cdrkit-cdrtools-compat | Tool for Writing CDRs - cdrtools Compatibility Package | package }}} and the file is located in: /usr/bin/mkisofs and is a link to genisoimage. Issue on SLES12, not with SLES 10 & 11. " 280 Unable to backup to multiple tapes mondo 2.2.7 defect normal Bruno Cornec assigned Danjel Jungersen 2008-10-17T08:30:16+02:00 2013-12-19T18:26:54+01:00 "I'm running the currently latest release for debian amd64 from ftp.mondorescue.org. I'm running Debian stable. I have tried the version available in Debian stable repository, same/similar error. When backing up to more than 1 tape, the backup runs nicely, but when it verifies, it stops, just after starting the new tape. I get the same error if I try to restore from tape 2. I have an IBM LTO Ultrium 2 drive." 714 Cannot restore iso created with v3.0.4 mondorescue on RHEL5u6 mondo 3.0.4 3.0.5 defect critical Bruno Cornec assigned Matthew 2013-09-04T22:47:52+02:00 2016-03-21T19:46:29+01:00 "Hi, I have been have recently installed v3.0.4 on RHEL5u6. I have upgraded from v2.2.9.5 due to problems occuring when backing up large sparse files and it using v3.0.4. I have a major problem with the restore. 1. At the end of the restore I have the message ' No tarballs. Strange. Maybe you only backed up freakin' big files?'. 2. exit does not work. It complains about the trap command. 3. When I try to reboot grub is corrupted. I get error 15. The command I used to create the archive was /usr/sbin/mondoarchive -OVi -R -N -d /opt -S /opt/backups -T /opt/backups -E ""/opt|/opt/backups"" -s 16384mb -G -p mondo3.0.4-bkup Can anybody help me please. I have included the logs and error" 628 3.0.2-1 Fail to Restore from External Hard Disk mondo 3.0.2 3.0.5 defect major Bruno Cornec assigned SamK 2012-06-15T14:04:52+02:00 2013-09-30T19:57:26+02:00 "This ticket is raised at the request of Bruno as a result of a mailing list discussion. See archive: Date=June 10 2012 Title=3.0.2-1 Fail to Restore from External Hard Disk A single mondorescue-1.iso backup is successfully created directly to an external hard disk and stored in /mondo. Booting from the mondorescue.iso (mindi) CDROM * Boot codes: interactive noresize * Read from=Hard disk * Prefix=mondorescue * On what device do the ISO files live=/dev/sdb1 * What is disk format=ext4 * Are you restoring from an external hard drive=Yes * At what path on this device can the ISO files be found=/mondo * When mondorestore displays the message ""Failed to find config/file archives. Choose another source?"" * ALT-F2 * mount ""... /dev/sdb1 on /tmp/isodir type ext4 (ro,relatime,barrier=1,data=ordered)"" * ls -1 /mnt/isodir/mondo/*.iso ""/tmp/isodir/mondo/mondorescue-1.iso /tmp/isodir/mondo/mondorescue.iso"" It seems that mondorestore mounts the external disk OK but does not use the path to the directory holding the backup ISO. At the suggestion of Bruno mondorescue-1.iso was copied to the root of the external drive and the restore attempted again. This time the ISO is found but the restore fails at a later stage. Booting from the mondorescue.iso (mindi) CDROM * Boot codes: interactive noresize * Read from=Hard disk * Prefix=mondorescue * On what device do the ISO files live=/dev/sdb1 * What is disk format=ext4 * Are you restoring from an external hard drive=Yes * At what path on this device can the ISO files be found=/ * Editing Mountlist=OK * Save mountlist and continue=Yes * Erase and partition hard drives=Yes * Restore all data=Yes * A message is displayed ""Please insert ISO #1 and press Enter"" At this point the mondorestore.log was saved as it is not possible to proceed further. The log is attached. " 640 mondo.tmp.xxxxx & mondo.scratch.xxxxx Issues mondo 3.0.2 3.0.5 defect normal Bruno Cornec reopened SamK 2012-08-18T19:54:17+02:00 2013-09-29T15:21:12+02:00 "mindi-busybox_1.18.5-2 [[BR]] mindi_2.1.2-1 [[BR]] mondo_3.0.2-1[[BR]] [[BR]] Logs are attached for 2 identical backups to local external hard disk. One is specified via GUI the other via CLI. Both complete successfully but different results are obtained for mondo.tmp and mondo.scratch.[[BR]] [[BR]] '''Backup Via GUI'''[[BR]] {{{ Backup to = Hard Disk Storage dir = /media/BACKUP-REPO/backup/home/nfs/mondo Type of compression = gzip How much compression = Average ISO Size = 650 Prefix = mondoverass-single Backup paths = /bin Exclude paths = /home|/media Temporary directory = /tmp/mondo.tmp.xxxxxx Scratch directory = /tmp/mondo.scratch.xxxxx Backup extended attrib= yes Verify backup = no }}} mondo.tmp.xxxxx is not created in /tmp. It is created at /media/BACKUP-REPO/tmp/mondo.tmp.xxxxxx. Additionally it is not removed after the successful completion of the backup.[[BR]] mondo.scratch.xxxxx is removed OK.[[BR]] Logs:[[BR]] mindi.log.GUI[[BR]] mondoarchive.log.GUI[[BR]] [[BR]] [[BR]] '''Backup Via CLI'''[[BR]] {{{ mondoarchive -O -i -d /media/BACKUP-REPO/backup/home/nfs/mondo -G -4 -p mondoverass-single -s 650m -S /tmp -T /tmp -I ""/bin"" -E ""|/home|"" }}} mondo.scratch.xxxxx is not removed from /tmp/mondo.scratch.xxxxx[[BR]] mondo.tmp.xxxxx is removed OK.[[BR]] Logs:[[BR]] mindi.log.CLI[[BR]] mondoarchive.log.CLI[[BR]] " 862 compilation issue on Arch mondo 3.3.0 3.3.0 defect blocker Bruno Cornec new Bruno Cornec 2020-04-05T01:34:39+02:00 2020-04-05T01:34:39+02:00 "{{{ In file included from include/busybox.h:8, from applets/applets.c:9: include/libbb.h:397:1: error: unknown type name ‘DIR’ 397 | DIR *xopendir(const char *path) FAST_FUNC; | ^~~ include/libbb.h:398:1: error: unknown type name ‘DIR’ 398 | DIR *warn_opendir(const char *path) FAST_FUNC; | ^~~ In file included from include/busybox.h:8, from applets/applets.c:9: include/libbb.h:1522:2: error: unknown type name ‘DIR’ 1522 | DIR *dir; | ^~~ In file included from : include/libbb.h:1523:26: error: unknown type name ‘DIR’ 1523 | IF_FEATURE_SHOW_THREADS(DIR *task_dir;) | ^~~ ./include/autoconf.h:3289:38: note: in definition of macro ‘IF_FEATURE_SHOW_THREADS’ 3289 | #define IF_FEATURE_SHOW_THREADS(...) __VA_ARGS__ | ^~~~~~~~~~~ make[1]: *** [scripts/Makefile.build:198: applets/applets.o] Error 1 make: *** [Makefile:372: applets_dir] Error 2 ==> ERROR: A failure occurred in build(). Aborting... }}}" 875 DBG2: [Main] libmondo-archive.c->make_afioballs_and_images#1345: Warning - either /tmp/mondo.tmp.gRfPLr/filelist.0 or /tmp/mondo.tmp.gRfPLr/tmpfs/0.star.bz2 doesn't exist yet. I'll pause 5 secs. mondo 3.3.0 3.3.0 defect critical Bruno Cornec new spezialist 2021-04-22T16:32:11+02:00 2021-05-06T17:01:38+02:00 "Dear team, After updating CentOS-8.3.2011 to the latest version it is impossible to make a backup of the operating system. My backup shell command is: {{{ mondoarchive -ODFNi -R -6z -s 4480m -p `hostname -s`_`date +%A` -d /mnt/nfs_backups/`hostname -s`.back/BMR -E ""/mnt/nfs_backups|/opt/repo|/opt/repo-addons|/opt/repo-updates|/mnt/repo|/mnt/repo-addons|/mnt/repo-updates"" }}} The backup ends up with these messages: {{{ ---evalcall---1--- Calling MINDI for boot disk ---evalcall---2--- TASK: [********************] 100% done; 0:00 to go ---evalcall---E--- Boot+data disks were created OK Done. Preparing to archive your data Done. Archiving regular files to media Archiving regular files ---progress-form---1--- I am backing up your live filesystem now. ---progress-form---2--- Please wait. This may take a couple of hours. ---progress-form---3--- Working... ---progress-form---E--- ---progress-form---4--- TASK: [*...................] 1% done; 0:00 to go Errors occurred while archiving set 0. Please review logs. Errors occurred while archiving set 1. Please review logs. Errors occurred while archiving set 3. Please review logs. Errors occurred while archiving set 2. Please review logs. Errors occurred while archiving set 4. Please review logs. Errors occurred while archiving set 5. Please review logs. ... }}} At the same time, log file /var/log/mondoarchive.log is filled with the following entries: {{{ DBG2: [Main] libmondo-archive.c->make_afioballs_and_images#1345: Warning - either /tmp/mondo.tmp.JoDRON/filelist.0 or /tmp/mondo.tmp.JoDRON/tmpfs/0.star.bz2 doesn't exist yet. I'll pause 5 secs. DBG2: [Main] libmondo-archive.c->make_afioballs_and_images#1345: Warning - either /tmp/mondo.tmp.Fjucx6/filelist.0 or /tmp/mondo.tmp.Fjucx6/tmpfs/0.star.bz2 doesn't exist yet. I'll pause 5 secs. DBG2: [Main] libmondo-archive.c->make_afioballs_and_images#1345: Warning - either /tmp/mondo.tmp.0TxyCu/filelist.0 or /tmp/mondo.tmp.0TxyCu/tmpfs/0.star.bz2 doesn't exist yet. I'll pause 5 secs. }}} No file system overflow is observed in this case." 876 "afio: ""quit"" to abort, anything else to proceed. >" mondo 3.3.0 3.3.0 defect critical Bruno Cornec new spezialist 2021-04-26T10:17:51+02:00 2021-04-26T10:19:17+02:00 "Dear team, After updating CentOS-8.3.2011 to the latest version it is impossible to make a backup of the operating system. My backup shell command is: {{{ mondoarchive -ODFNi -6z -s 4480m -p `hostname -s`_`date +%A` -d /mnt/nfs_backups/`hostname -s`.back/BMR -E ""/mnt/nfs_backups|/opt/repo|/opt/repo-addons|/opt/repo-updates|/mnt/repo|/mnt/repo-addons|/mnt/repo-updates"" }}} The backup ends up with these messages: {{{ ---progress-form---1--- I am backing up your live filesystem now. ---progress-form---2--- ISO 1: [***.................] 13% used ---progress-form---3--- Please wait. This may take a couple of hours. ---progress-form---E--- ---progress-form---4--- TASK: [************........] 58% done; 1:41 to go afio: Ready for volume 2 on /tmp/mondo.tmp.CFlrP4/tmpfs/9.afio.bz2 afio: ""quit"" to abort, anything else to proceed. > afio: Ready for volume 3 on /tmp/mondo.tmp.CFlrP4/tmpfs/9.afio.bz2 afio: ""quit"" to abort, anything else to proceed. > afio: Ready for volume 4 on /tmp/mondo.tmp.CFlrP4/tmpfs/9.afio.bz2 afio: ""quit"" to abort, anything else to proceed. > quit afio: Ready for volume 2 on /tmp/mondo.tmp.CFlrP4/tmpfs/9.afio.bz2 afio: ""quit"" to abort, anything else to proceed. > ^C ^C Errors occurred while archiving set 9. Please review logs. ... }}} At the same time, log file /var/log/mondoarchive.log is filled with the following entries: {{{ DBG2: [Main] libmondo-archive.c->make_afioballs_and_images#1345: Warning - either /tmp/mondo.tmp.JoDRON/filelist.0 or /tmp/mondo.tmp.JoDRON/tmpfs/0.star.bz2 doesn't exist yet. I'll pause 5 secs. DBG2: [Main] libmondo-archive.c->make_afioballs_and_images#1345: Warning - either /tmp/mondo.tmp.gRfPLr/filelist.0 or /tmp/mondo.tmp.gRfPLr/tmpfs/0.star.bz2 doesn't exist yet. I'll pause 5 secs. DBG2: [Main] libmondo-archive.c->make_afioballs_and_images#1345: Warning - either /tmp/mondo.tmp.KpKgvM/filelist.0 or /tmp/mondo.tmp.KpKgvM/tmpfs/0.star.bz2 doesn't exist yet. I'll pause 5 secs. }}} And every time the error ""afio: ""quit"" to abort, anything else to proceed. >"", the 20GB /tmp directory overflows: {{{ Filesystem Type Size Used Avail Use% Mounted on /dev/mapper/cl_zabbix--zt0-root xfs 10G 619M 9.4G 7% / /dev/mapper/cl_zabbix--zt0-usr xfs 15G 3.2G 12G 21% /usr /dev/sda1 ext4 488M 236M 217M 53% /boot /dev/mapper/cl_zabbix--zt0-var xfs 15G 1.1G 14G 8% /var /dev/mapper/cl_zabbix--zt0-tmp xfs 20G 20G 108K 100% /tmp /dev/mapper/cl_zabbix--zt0-opt xfs 80G 78G 2.2G 98% /opt boostfs fuse.boostfs 201T 118T 84T 59% /mnt/nfs_backups }}} " 849 Restored VM Fails to Boot mondo 3.2.2 3.3.0 defect major Bruno Cornec assigned kevenw 2019-08-06T21:29:04+02:00 2020-03-04T21:15:52+01:00 "I'm having an issue with my mondorestore'ed VM failing to boot after the post-mondorestore reboot. I believe the bootloader (GRUB2) is not being setup correctly by mondorestore. I've attached mondorestore.log, and I have 3 areas of concern: 1. {{{ INFO: Found Device /dev/vda has a MBR partition type partition table format type on /dev/vda DBG2: [Main] ../src/mondorestore/mondo-prep.c->partition_device#1539: partition_device('/dev/vda', 1, 0, 'xfs', 1048576) --- starting DBG2: [Main] ../src/mondorestore/mondo-prep.c->partition_device#1554: Partitioning device /dev/vda1 (1024 MB) INFO: Found Device /dev/vda has a MBR partition type partition table format type on /dev/vda DBG1: [Main] ../src/mondorestore/mondo-prep.c->partition_device#1616: Doing the new all-in-one fdisk thing DBG1: [Main] ../src/mondorestore/mondo-prep.c->partition_device#1617: output = 'n p 1 +1048576K ' DBG1: [Main] ../src/mondorestore/mondo-prep.c->partition_device#1624: last line = p DBG1: [Main] ../src/mondorestore/mondo-prep.c->partition_device#1625: Failed to create partition 1 on /dev/vda; sending 'Enter'... }}} What would cause this? 2. {{{ DBG2: [Main] ../src/mondorestore/mondo-rstr-tools.c->run_grub#1476: mr-grub /dev/vda /tmp/mountlist.txt Now I'll use grub-install Launching: chroot /mnt/RESTORING grub-install /dev/vda chroot: can't execute 'grub-install': No such file or directory grub-install returned 127 Now I'll use grub2-install Installing for i386-pc platform. grub2-install: error: cannot find a GRUB drive for /dev/vda1. Check your device.map. grub2-install returned 1 }}} The device.map file has ""dev/vda"". I’ve also tried manually changing device.map to “/dev/vda1”, but I still see the same error. Any ideas why this might be occurring? 3. {{{ Trying a hack Checking usr/lib/grub/i386-pc Cannot find BOOTPATHNAME .............Cool. device (hd0) /dev/vda root (hd0,0) setup (hd0) quit chroot: can't execute 'grub': No such file or directory Hack returned res=0 }}} This is a bug in try_grub_hack() of mr-grub. If grub can't be found, the function returns a false positive. " 863 Error compiling on Fedora 32 mondo 3.2.2 3.3.0 defect normal Bruno Cornec new Bruno Cornec 2020-04-15T03:31:45+02:00 2020-04-15T03:31:45+02:00 "[fedora-32-x86_64] /usr/bin/ld: ../../src/common/libmondo.a(libmondo-tools.o):/home/pb/pb/projects/mondorescue/pbbuild/BUILD/mondo-3.3.0.0.20200415032050/src/common/libmondo-tools.c:57: multiple definition of `g_mondo_home'; mondorestore.o:/home/pb/pb/projects/mondorescue/pbbuild/BUILD/mondo-3.3.0.0.20200415032050/src/mondorestore/mondorestore.c:119: first defined here " 794 Provide SLES 11 SP4 support with UEFI mindi 3.2.1 3.3.1 defect blocker Bruno Cornec new Bruno Cornec 2016-04-16T12:43:00+02:00 2017-03-08T17:05:00+01:00 SLES 11 SP4 uses elilo as a boot loader in UEFI mode. This is not yet supported by mindi. 802 mindi aborts on Debian 8 on UEFI system mindi 3.2.2 3.3.1 defect blocker Bruno Cornec assigned Bruno Cornec 2016-07-06T14:52:38+02:00 2019-11-11T01:48:56+01:00 When trying to build an ISO image with mindi on Debian 8, it aborts. 861 mondorestore aborts with a hign numner of directories mondo 3.3.0 3.3.1 defect blocker Bruno Cornec new Bruno Cornec 2020-04-05T01:20:08+02:00 2020-04-05T01:20:08+02:00 "I tried to rescue some files from a backup, but mondorescue terminates. strace showed that the error occurs while reading filelist.full.gz. Probably because we have a filesystemstructure that goes 369 folders deep. {{{ >DBG2: [Main] libmondo-raid.c->load_raidtab_into_raidlist#595: Raidtab is very small or non-existent. Ignoring it. >DBG1: [Main] ../src/mondorestore/mondo-rstr-tools.c->process_filelist_and_biggielist#1036: /tmp/mondo.tmp.aqwIRa/tmp/filelist.full.gz exists >DBG1: [Main] ../src/mondorestore/mondo-rstr-tools.c->process_filelist_and_biggielist#1037: /tmp/mondo.tmp.aqwIRa/tmp/biggielist.txt exists >DBG2: [Main] ../src/mondorestore/mondo-rstr-tools.c->process_filelist_and_biggielist#1039: Filelist and biggielist already recovered from media. Yay! >INFO: root is mounted at /dev/sda >INFO: That doesn't mean /dev/sda is the root partition. It's just a debugging message. Relax. It's part of am_I_in_disaster_recovery_mode(). >DBG1: [Main] libmondo-devices.c->am_I_in_disaster_recovery_mode#164: Is this a ramdisk? result = FALSE >DBG2: [Main] ../src/mondorestore/mondo-rstr-tools.c->process_filelist_and_biggielist#1129: Forking >INFO: Pre-processing filelist >DBG4: [TH=19443] ../src/mondorestore/mondo-rstr-tools.c->process_filelist_and_biggielist#1144: grep -E '^/dev/.*' /tmp/mondo.tmp.aqwIRa/tmp/biggielist.txt > /tmp/mondo.tmp.aqwIRa/tmp/filelist.imagedevs >DBG3: [Main] ../src/mondorestore/mondo-rstr-tools.c->process_filelist_and_biggielist#1158: loading filelist >INFO: Loading filelist >INFO: SIGABRT signal received from OS }}}" 864 Fix compiler warnings mondo 3.3.0 3.3.1 defect major Bruno Cornec new Bruno Cornec 2020-05-28T15:30:06+02:00 2020-05-28T15:30:39+02:00 "{{{ [fedora-30-x86_64] In file included from /usr/include/string.h:495, [fedora-30-x86_64] from ../../src/include/my-stuff.h:60, [fedora-30-x86_64] from libmondo-archive.c:13: [fedora-30-x86_64] In function 'strncpy', [fedora-30-x86_64] inlined from 'call_mindi_to_supply_boot_disks' at libmondo-archive.c:489:4: [fedora-30-x86_64] /usr/include/bits/string_fortified.h:106:10: warning: '__builtin_strncpy' specified bound 128 equals destination size [-Wstringop-truncation] [fedora-30-x86_64] 106 | return __builtin___strncpy_chk (__dest, __src, __len, __bos (__dest)); [fedora-30-x86_64] | ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ [fedora-30-x86_64] In file included from /usr/include/string.h:495, [fedora-30-x86_64] from ../../src/include/my-stuff.h:60, [fedora-30-x86_64] from libmondo-cli.c:13: [fedora-30-x86_64] In function 'strncpy', [fedora-30-x86_64] inlined from 'process_switches' at libmondo-cli.c:468:3: [fedora-30-x86_64] /usr/include/bits/string_fortified.h:106:10: warning: '__builtin_strncpy' specified bound 128 equals destination size [-Wstringop-truncation] [fedora-30-x86_64] 106 | return __builtin___strncpy_chk (__dest, __src, __len, __bos (__dest)); [fedora-30-x86_64] | ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ [fedora-30-x86_64] In function 'strncpy', [fedora-30-x86_64] inlined from 'process_switches' at libmondo-cli.c:516:5: [fedora-30-x86_64] /usr/include/bits/string_fortified.h:106:10: warning: '__builtin_strncpy' specified bound 128 equals destination size [-Wstringop-truncation] [fedora-30-x86_64] 106 | return __builtin___strncpy_chk (__dest, __src, __len, __bos (__dest)); [fedora-30-x86_64] | ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ [fedora-30-x86_64] In function 'strncpy', [fedora-30-x86_64] inlined from 'process_switches' at libmondo-cli.c:663:3: [fedora-30-x86_64] /usr/include/bits/string_fortified.h:106:10: warning: '__builtin_strncpy' specified bound 128 equals destination size [-Wstringop-truncation] [fedora-30-x86_64] 106 | return __builtin___strncpy_chk (__dest, __src, __len, __bos (__dest)); [fedora-30-x86_64] | ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ [fedora-30-x86_64] In function 'strncpy', [fedora-30-x86_64] inlined from 'process_switches' at libmondo-cli.c:674:3: [fedora-30-x86_64] /usr/include/bits/string_fortified.h:106:10: warning: '__builtin_strncpy' specified bound 512 equals destination size [-Wstringop-truncation] [fedora-30-x86_64] 106 | return __builtin___strncpy_chk (__dest, __src, __len, __bos (__dest)); [fedora-30-x86_64] | ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ [fedora-30-x86_64] In function 'strncpy', [fedora-30-x86_64] inlined from 'process_switches' at libmondo-cli.c:682:3: [fedora-30-x86_64] /usr/include/bits/string_fortified.h:106:10: warning: '__builtin_strncpy' specified bound 128 equals destination size [-Wstringop-truncation] [fedora-30-x86_64] 106 | return __builtin___strncpy_chk (__dest, __src, __len, __bos (__dest)); [fedora-30-x86_64] | ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ [fedora-30-x86_64] In function 'strncpy', [fedora-30-x86_64] inlined from 'process_switches' at libmondo-cli.c:697:4: [fedora-30-x86_64] /usr/include/bits/string_fortified.h:106:10: warning: '__builtin_strncpy' specified bound 128 equals destination size [-Wstringop-truncation] [fedora-30-x86_64] 106 | return __builtin___strncpy_chk (__dest, __src, __len, __bos (__dest)); [fedora-30-x86_64] | ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ [fedora-30-x86_64] In function 'strncpy', [fedora-30-x86_64] inlined from 'process_switches' at libmondo-cli.c:688:4: [fedora-30-x86_64] /usr/include/bits/string_fortified.h:106:10: warning: '__builtin_strncpy' specified bound 128 equals destination size [-Wstringop-truncation] [fedora-30-x86_64] 106 | return __builtin___strncpy_chk (__dest, __src, __len, __bos (__dest)); [fedora-30-x86_64] | ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ [fedora-30-x86_64] In function 'strncpy', [fedora-30-x86_64] inlined from 'process_switches' at libmondo-cli.c:793:3: [fedora-30-x86_64] /usr/include/bits/string_fortified.h:106:10: warning: '__builtin_strncpy' specified bound 512 equals destination size [-Wstringop-truncation] [fedora-30-x86_64] 106 | return __builtin___strncpy_chk (__dest, __src, __len, __bos (__dest)); [fedora-30-x86_64] | ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ [fedora-30-x86_64] In function 'strncpy', [fedora-30-x86_64] inlined from 'process_switches' at libmondo-cli.c:797:3: [fedora-30-x86_64] /usr/include/bits/string_fortified.h:106:10: warning: '__builtin_strncpy' specified bound 512 equals destination size [-Wstringop-truncation] [fedora-30-x86_64] 106 | return __builtin___strncpy_chk (__dest, __src, __len, __bos (__dest)); [fedora-30-x86_64] | ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ [fedora-30-x86_64] In function 'strncpy', [fedora-30-x86_64] inlined from 'process_switches' at libmondo-cli.c:827:3: [fedora-30-x86_64] /usr/include/bits/string_fortified.h:106:10: warning: '__builtin_strncpy' specified bound 512 equals destination size [-Wstringop-truncation] [fedora-30-x86_64] 106 | return __builtin___strncpy_chk (__dest, __src, __len, __bos (__dest)); [fedora-30-x86_64] | ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ [fedora-30-x86_64] libmondo-devices.c: In function 'interactively_obtain_media_parameters_from_user': [fedora-30-x86_64] libmondo-devices.c:2562:32: warning: '/netfsdir' directive writing 9 bytes into a region of size between 1 and 128 [-Wformat-overflow=] [fedora-30-x86_64] 2562 | sprintf(bkpinfo->isodir, ""%s/netfsdir"", bkpinfo->tmpdir); [fedora-30-x86_64] | ^~~~~~~~~ [fedora-30-x86_64] In file included from /usr/include/stdio.h:867, [fedora-30-x86_64] from ../../src/include/my-stuff.h:40, [fedora-30-x86_64] from libmondo-devices.c:13: [fedora-30-x86_64] /usr/include/bits/stdio2.h:36:10: note: '__builtin___sprintf_chk' output between 10 and 137 bytes into a destination of size 128 [fedora-30-x86_64] 36 | return __builtin___sprintf_chk (__s, __USE_FORTIFY_LEVEL - 1, [fedora-30-x86_64] | ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ [fedora-30-x86_64] 37 | __bos (__s), __fmt, __va_arg_pack ()); [fedora-30-x86_64] | ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ [fedora-30-x86_64] In file included from /usr/include/string.h:495, [fedora-30-x86_64] from ../../src/include/my-stuff.h:60, [fedora-30-x86_64] from libmondo-devices.c:13: [fedora-30-x86_64] In function 'strncpy', [fedora-30-x86_64] inlined from 'interactively_obtain_media_parameters_from_user' at libmondo-devices.c:2738:4: [fedora-30-x86_64] /usr/include/bits/string_fortified.h:106:10: warning: '__builtin_strncpy' specified bound 128 equals destination size [-Wstringop-truncation] [fedora-30-x86_64] 106 | return __builtin___strncpy_chk (__dest, __src, __len, __bos (__dest)); [fedora-30-x86_64] | ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ }}}" 1 sprintf used without checks mondo 2.0.8 3.3.1 defect normal Bruno Cornec assigned Bruno Cornec 2006-07-31T23:07:22+02:00 2017-03-08T17:02:03+01:00 "reported by Yann Aubert ():[[BR]] many sprintf in mondo code are used without checks and may lead to seg. fault (ex: -E with a long list of excluded directories) " 36 mondoarchive should use an FHS-compliant location mondo 2.0.9 4.0.1 enhancement major Bruno Cornec assigned Bruno Cornec 2006-08-08T01:33:05+02:00 2008-11-17T12:44:19+01:00 for storing scratch and temporary data and both archive and boot images (see also Mondorescue wiki:StandardsCompliance) 35 mondo should have more item in configuration files mondo 2.0.9 4.0.1 enhancement minor Bruno Cornec new Bruno Cornec 2006-08-08T01:30:31+02:00 2007-04-02T16:40:04+02:00 168 Make ALL kernel modules be visible during restore mondo 2.2.3 4.0.2 enhancement normal Bruno Cornec assigned extace 2007-05-17T19:53:10+02:00 2007-05-20T22:26:16+02:00 "When restoring to a hardware setup different than the original (i.e. different RAID/SATA adapter) you can be caught in a catch22 situation wherer you can NOT load the needed kernel modules because mondo/mindi did NOT put ALL OF THEM on the bootable portion of the image. the only current solution is to KNOW the drivers needed BEFORE the mondoarchive (backup) is even done so that they can be ""modprobed"" into memory so that mondo/mindi makes surethey are available. A more appropriate and correct solution would be to have the ENTIRE kernel modules tree be accessible after booting in rescue mode (i.e. on new hardware). in case hardwaredetection fails (which it does if the disk controller driver is different from the original system), one could then have access to the ENTIRE kernel modules tree to be able to load up the proper driver and continue the restore. If it's not possible to stick it in the bootable section of the image (due to space) it SHOULD be possible to take the kernel modules tree and create that as an ISO on the C and make that loop mountable as needed. I got hit by this bug/defect/limitation, when designing a customer solution in a virtual environment and tried to transfer it over to real physical hardware, it had NO DRIVERS avail (no complete kernel modules tree), which resulting in me having to manually load the drivers in the virtual side before mondo-archiving so that they'd be available when booting the physical machine, but this was a hack and wasted numerous hours to get around a deficiency that should never have been present IMHO. " 42 Switch in Mondo to Stop it From Following Symlinks mondo 2.0.9 enhancement normal Bruno Cornec new nolan@… 2006-08-11T20:15:48+02:00 2013-12-19T18:26:54+01:00 "Would it be possible for mondo to include a switch that stops it from following symlinks? In a case like mine, where I am trying to do a full backup, it really isn't helpful for mondo to follow symlinks - I just need the symlinks to exist where they do now. This is in response to the post in the newsgroup entitled ""Mondo Seg Faults - Nothing in Logs?""" 104 Mondoarchive segfaults when encoutering deep filesystem arborescence mondo 2.2.0 defect normal Bruno Cornec assigned Even Rouault 2006-11-18T14:21:06+01:00 2013-12-19T18:26:54+01:00 "I got a segfault in mondoarchive during the catalog make stage, when trying to archive an EXT3 filesystem with a really really deep arborescence (consecutively to a scp or tar - I don't remember - of a dumb directory with a stupid symbolic link of the '.' file). After removing this arborescence, the process goes fine." 133 mr_strtok doesn't always give the same result mondo 2.2.1 defect normal andree new Bruno Cornec 2007-02-11T19:28:10+01:00 2013-12-19T18:26:54+01:00 "Multiple run of the same test-string program do not give the same result: {{{ 140 victoria2.home.musique-ancienne.org-bruno ~/mondo/svn/branches/stable/mondo/src/test > ./test-string string=|md0 : active raid10 hda1[0] hda12[3] hda6[2] hda5[1] | token=|md0|, lastpos=4 token=|active|, lastpos=13 token=|raid10|, lastpos=20 token=|hda1[0]|, lastpos=28 token=|hda12[3]|, lastpos=37 token=|hda6[2]|, lastpos=45 token=|hda5[1]|, lastpos=53 141 victoria2.home.musique-ancienne.org-bruno ~/mondo/svn/branches/stable/mondo/src/test > ./test-string string=|md0 : active raid10 hda1[0] hda12[3] hda6[2] hda5[1] | token=|md|, lastpos=3 token=|active|, lastpos=13 token=|raid1|, lastpos=19 token=|hda1[|, lastpos=26 token=|]|, lastpos=28 token=|hda12[3]|, lastpos=37 token=|hda6[2]|, lastpos=45 token=|hda5[1]|, lastpos=53 142 victoria2.home.musique-ancienne.org-bruno ~/mondo/svn/branches/stable/mondo/src/test > ./test-string string=|md0 : active raid10 hda1[0] hda12[3] hda6[2] hda5[1] | token=|md0|, lastpos=4 token=|active|, lastpos=13 token=|raid10|, lastpos=20 token=|hda1[0]|, lastpos=28 token=|hda12[3]|, lastpos=37 token=|hda6[2]|, lastpos=45 token=|hda5[1]|, lastpos=53 143 victoria2.home.musique-ancienne.org-bruno ~/mondo/svn/branches/stable/mondo/src/test > ./test-string string=|md0 : active raid10 hda1[0] hda12[3] hda6[2] hda5[1] | token=|md0|, lastpos=4 token=|active|, lastpos=13 token=|raid10|, lastpos=20 token=|hda1[0]|, lastpos=28 token=|hda12[3]|, lastpos=37 token=|hda6[2]|, lastpos=45 token=|hda5[1]|, lastpos=53 144 victoria2.home.musique-ancienne.org-bruno ~/mondo/svn/branches/stable/mondo/src/test > ./test-string string=|md0 : active raid10 hda1[0] hda12[3] hda6[2] hda5[1] | token=|md0|, lastpos=4 token=|active|, lastpos=13 token=|raid10|, lastpos=20 token=|hda1[0]|, lastpos=28 token=|hda12[3]|, lastpos=37 token=|hda6[2]|, lastpos=45 token=|hda5[1]|, lastpos=53 145 victoria2.home.musique-ancienne.org-bruno ~/mondo/svn/branches/stable/mondo/src/test > ./test-string string=|md0 : active raid10 hda1[0] hda12[3] hda6[2] hda5[1] | token=|md0|, lastpos=4 token=|active|, lastpos=13 token=|raid10|, lastpos=20 token=|hda1[0]|, lastpos=28 token=|hda12[3]|, lastpos=37 token=|hda6[2]|, lastpos=45 token=|hda5[1]|, lastpos=53 146 victoria2.home.musique-ancienne.org-bruno ~/mondo/svn/branches/stable/mondo/src/test > ./test-string string=|md0 : active raid10 hda1[0] hda12[3] hda6[2] hda5[1] | token=|md0|, lastpos=4 token=|activ|, lastpos=12 token=|raid10|, lastpos=20 token=|hda1[0]|, lastpos=28 token=|hda12[3]|, lastpos=37 token=|hda6[2]|, lastpos=45 token=|hda5[1]|, lastpos=53 147 victoria2.home.musique-ancienne.org-bruno ~/mondo/svn/branches/stable/mondo/src/test > ./test-string string=|md0 : active raid10 hda1[0] hda12[3] hda6[2] hda5[1] | token=|md0|, lastpos=4 token=|active|, lastpos=13 token=|raid10|, lastpos=20 token=|hda1[0]|, lastpos=28 token=|hda12[3]|, lastpos=37 token=|hda6[2]|, lastpos=45 token=|hda5[1]|, lastpos=53 148 victoria2.home.musique-ancienne.org-bruno ~/mondo/svn/branches/stable/mondo/src/test > ./test-string string=|md0 : active raid10 hda1[0] hda12[3] hda6[2] hda5[1] | token=|md0|, lastpos=4 token=|active|, lastpos=13 token=|raid10|, lastpos=20 token=|hda1[0]|, lastpos=28 token=|hda12[3]|, lastpos=37 token=|hda6[2]|, lastpos=45 token=|hda5[1]|, lastpos=53 149 victoria2.home.musique-ancienne.org-bruno ~/mondo/svn/branches/stable/mondo/src/test > ./test-string string=|md0 : active raid10 hda1[0] hda12[3] hda6[2] hda5[1] | token=|md0|, lastpos=4 token=|active|, lastpos=13 token=|raid10|, lastpos=20 token=|hda1[0]|, lastpos=28 token=|hda12[3]|, lastpos=37 token=|hda6[2]|, lastpos=45 token=|hda5[1]|, lastpos=53 150 victoria2.home.musique-ancienne.org-bruno ~/mondo/svn/branches/stable/mondo/src/test > ./test-string string=|md0 : active raid10 hda1[0] hda12[3] hda6[2] hda5[1] | token=|md0|, lastpos=4 token=|active|, lastpos=13 token=|raid10|, lastpos=20 token=|hda1[0]|, lastpos=28 token=|hda1|, lastpos=33 token=|[3]|, lastpos=37 token=|hda6[|, lastpos=43 token=|]|, lastpos=45 token=|hda5[1]|, lastpos=53 }}}" 167 VxFS support mondo 2.2.3 defect normal Bruno Cornec assigned Bruno Cornec 2007-05-15T23:43:32+02:00 2013-12-19T18:26:54+01:00 "- mondo doesn't support VxFS. More over, ran on a system with VxFS FS it umounts those FS at the end of the run, which it shouldn't. " 197 Count deleted files in compare and show total along with popup changelist. mondo 2.2.4 enhancement normal Bruno Cornec reopened Scott Cummings 2007-09-17T05:00:04+02:00 2013-12-19T18:26:54+01:00 "Hi Bruno, Here's a patch that I tried. I wanted mondorestore compare to explain some of the difference between the count it showed of significant file differences and the number of files that were listed in the non-matching filelist. Maybe this is obvious to everyone else, but load_filelist_into_array had a few different criteria for excluding files from the filelist and I wanted to verify which files it found that were deleted from the system. In load_filelist_into_array count the files that can't be found now in the file system. Display the total. Record the file names in a 'deleted.files' file. I hope this is helpful. Regards, Scott" 276 Adds full OCFS2 support mondo 2.2.6 defect normal Bruno Cornec assigned Bruno Cornec 2008-09-19T12:20:06+02:00 2013-12-19T18:26:54+01:00 Adds full OCFS2 support in order to be able to backup/restore RAC configurations. 279 Mondorestore interactive mode restores uselss empty dirs mondo 2.2.6 defect normal Bruno Cornec assigned Bruno Cornec 2008-10-14T17:34:08+02:00 2013-12-19T18:26:54+01:00 "t also restores a few other empty directories which weren't selected in the file list. They seem to be consistent, in that I've done it twice and it restored the same 3 empty directories (note that they weren't empty on the original system). Since no unwanted files from those directories were restored I suppose that it's not really a big problem, but it is odd. The unwanted directories restored in addition to what I asked for were: {{{ /home/vpopmail/domains/ticgroup.com.au/bud.growcott/Maildir/.Pallet control/cur /tmp /var/lib/mysql }}} I've noticed that they seem to be coming from the biggiefiles section even though they weren't selected. {{{ Done. Reassembling large files [Main] mondorestore.c->restore_all_biggiefiles_from_stream#2397: OK, there are 5 biggiefiles in the archives [Main] mondorestore.c->restore_a_biggiefile_from_stream#1395: /home/vpopmail/domains/ticgroup.com.au/bud.growcott/Maildir/.Pallet control/cur/1140740942.3798_596.rlo.com.au,S=86071333:2, --- pih=NO [Main] mondorestore.c->restore_a_biggiefile_from_stream#1418: Skipping /home/vpopmail/domains/ticgroup.com.au/bud.growcott/Maildir/.Pallet control/cur/1140740942.3798_596.rlo.com.au,S=86071333:2, (name isn't in biggielist subset) [Main] mondorestore.c->restore_a_biggiefile_from_stream#1481: Reassembling big file 1 (/home/vpopmail/domains/ticgroup.com.au/bud.growcott/Maildir/.Pallet control/cur/1140740942.3798_596.rlo.com.au,S=86071333:2,) [Main] mondorestore.c->restore_a_biggiefile_from_stream#1501: Pipe command = 'cat > ""/dev/null""' [Main] mondorestore.c->restore_a_biggiefile_from_stream#1515: Working on file #1, slice #0 [Main] mondorestore.c->restore_a_biggiefile_from_stream#1515: Working on file #1, slice #1 [Main] mondorestore.c->restore_a_biggiefile_from_stream#1515: Working on file #1, slice #2 [Main] mondorestore.c->restore_a_biggiefile_from_stream#1515: Working on file #1, slice #3 [Main] mondorestore.c->restore_a_biggiefile_from_stream#1515: Working on file #1, slice #4 [Main] mondorestore.c->restore_a_biggiefile_from_stream#1515: Working on file #1, slice #5 [Main] mondorestore.c->restore_a_biggiefile_from_stream#1515: Working on file #1, slice #6 [Main] mondorestore.c->restore_a_biggiefile_from_stream#1561: pathname_of_last_file_restored is now [Main] mondorestore.c->restore_a_biggiefile_from_stream#1573: biggiestruct.filename = /home/vpopmail/domains/ticgroup.com.au/bud.growcott/Maildir/.Pallet control/cur/1140740942.3798_596.rlo.com.au,S=86071333:2, [Main] mondorestore.c->restore_a_biggiefile_from_stream#1574: biggiestruct.checksum = 931bcc31faaebc228109f8f78c95f201 [Main] mondorestore.c->restore_all_biggiefiles_from_stream#2430: I believe I have restored [Main] mondorestore.c->restore_a_biggiefile_from_stream#1395: /home/vpopmail/domains/ticgroup.com.au/bud.growcott/Maildir/.Pallet control/cur/1140741010.3798_597.rlo.com.au,S=86075819:2, --- pih=NO [Main] mondorestore.c->restore_a_biggiefile_from_stream#1418: Skipping /home/vpopmail/domains/ticgroup.com.au/bud.growcott/Maildir/.Pallet control/cur/1140741010.3798_597.rlo.com.au,S=86075819:2, (name isn't in biggielist subset) [Main] mondorestore.c->restore_a_biggiefile_from_stream#1481: Reassembling big file 2 (/home/vpopmail/domains/ticgroup.com.au/bud.growcott/Maildir/.Pallet control/cur/1140741010.3798_597.rlo.com.au,S=86075819:2,) [Main] mondorestore.c->restore_a_biggiefile_from_stream#1501: Pipe command = 'cat > ""/dev/null""' [Main] mondorestore.c->restore_a_biggiefile_from_stream#1515: Working on file #2, slice #0 [Main] mondorestore.c->restore_a_biggiefile_from_stream#1515: Working on file #2, slice #1 [Main] mondorestore.c->restore_a_biggiefile_from_stream#1515: Working on file #2, slice #2 [Main] mondorestore.c->restore_a_biggiefile_from_stream#1515: Working on file #2, slice #3 [Main] mondorestore.c->restore_a_biggiefile_from_stream#1515: Working on file #2, slice #4 [Main] mondorestore.c->restore_a_biggiefile_from_stream#1515: Working on file #2, slice #5 [Main] mondorestore.c->restore_a_biggiefile_from_stream#1515: Working on file #2, slice #6 [Main] mondorestore.c->restore_a_biggiefile_from_stream#1561: pathname_of_last_file_restored is now [Main] mondorestore.c->restore_a_biggiefile_from_stream#1573: biggiestruct.filename = /home/vpopmail/domains/ticgroup.com.au/bud.growcott/Maildir/.Pallet control/cur/1140741010.3798_597.rlo.com.au,S=86075819:2, [Main] mondorestore.c->restore_a_biggiefile_from_stream#1574: biggiestruct.checksum = f9ba3e4c5d6b8daf10d5c47d4fcedc78 [Main] mondorestore.c->restore_all_biggiefiles_from_stream#2430: I believe I have restored [Main] mondorestore.c->restore_a_biggiefile_from_stream#1395: /home/vpopmail/domains/ticgroup.com.au/sapsupport.tar.gz --- pih=NO [Main] mondorestore.c->restore_a_biggiefile_from_stream#1418: Skipping /home/vpopmail/domains/ticgroup.com.au/sapsupport.tar.gz (name isn't in biggielist subset) [Main] mondorestore.c->restore_a_biggiefile_from_stream#1481: Reassembling big file 3 (/home/vpopmail/domains/ticgroup.com.au/sapsupport.tar.gz) [Main] mondorestore.c->restore_a_biggiefile_from_stream#1501: Pipe command = 'cat > ""/dev/null""' [Main] mondorestore.c->restore_a_biggiefile_from_stream#1515: Working on file #3, slice #0 [Main] mondorestore.c->restore_a_biggiefile_from_stream#1515: Working on file #3, slice #1 [Main] mondorestore.c->restore_a_biggiefile_from_stream#1515: Working on file #3, slice #2 [Main] mondorestore.c->restore_a_biggiefile_from_stream#1515: Working on file #3, slice #3 [Main] mondorestore.c->restore_a_biggiefile_from_stream#1515: Working on file #3, slice #4 [Main] mondorestore.c->restore_a_biggiefile_from_stream#1515: Working on file #3, slice #5 [Main] mondorestore.c->restore_a_biggiefile_from_stream#1515: Working on file #3, slice #6 [Main] mondorestore.c->restore_a_biggiefile_from_stream#1515: Working on file #3, slice #7 [Main] mondorestore.c->restore_a_biggiefile_from_stream#1561: pathname_of_last_file_restored is now [Main] mondorestore.c->restore_a_biggiefile_from_stream#1573: biggiestruct.filename = /home/vpopmail/domains/ticgroup.com.au/sapsupport.tar.gz [Main] mondorestore.c->restore_a_biggiefile_from_stream#1574: biggiestruct.checksum = 1e4aa002fbebb935d4a185d708782b51 [Main] mondorestore.c->restore_all_biggiefiles_from_stream#2430: I believe I have restored [Main] mondorestore.c->restore_a_biggiefile_from_stream#1395: /tmp/selected-files.txt --- pih=NO [Main] mondorestore.c->restore_a_biggiefile_from_stream#1418: Skipping /tmp/selected-files.txt (name isn't in biggielist subset) [Main] mondorestore.c->restore_a_biggiefile_from_stream#1481: Reassembling big file 4 (/tmp/selected-files.txt) [Main] mondorestore.c->restore_a_biggiefile_from_stream#1501: Pipe command = 'cat > ""/dev/null""' [Main] mondorestore.c->restore_a_biggiefile_from_stream#1515: Working on file #4, slice #0 [Main] mondorestore.c->restore_a_biggiefile_from_stream#1515: Working on file #4, slice #1 [Main] mondorestore.c->restore_a_biggiefile_from_stream#1515: Working on file #4, slice #2 [Main] mondorestore.c->restore_a_biggiefile_from_stream#1515: Working on file #4, slice #3 [Main] mondorestore.c->restore_a_biggiefile_from_stream#1515: Working on file #4, slice #4 [Main] mondorestore.c->restore_a_biggiefile_from_stream#1515: Working on file #4, slice #5 [Main] mondorestore.c->restore_a_biggiefile_from_stream#1515: Working on file #4, slice #6 [Main] mondorestore.c->restore_a_biggiefile_from_stream#1561: pathname_of_last_file_restored is now [Main] mondorestore.c->restore_a_biggiefile_from_stream#1573: biggiestruct.filename = /tmp/selected-files.txt [Main] mondorestore.c->restore_a_biggiefile_from_stream#1574: biggiestruct.checksum = 841aec6a37f6d2d2b9991eb31f9f6fd2 [Main] mondorestore.c->restore_all_biggiefiles_from_stream#2430: I believe I have restored [Main] mondorestore.c->restore_a_biggiefile_from_stream#1395: /var/lib/mysql/ibdata1 --- pih=NO [Main] mondorestore.c->restore_a_biggiefile_from_stream#1418: Skipping /var/lib/mysql/ibdata1 (name isn't in biggielist subset) [Main] mondorestore.c->restore_a_biggiefile_from_stream#1481: Reassembling big file 5 (/var/lib/mysql/ibdata1) [Main] mondorestore.c->restore_a_biggiefile_from_stream#1501: Pipe command = 'cat > ""/dev/null""' [Main] mondorestore.c->restore_a_biggiefile_from_stream#1515: Working on file #5, slice #0 [Main] mondorestore.c->restore_a_biggiefile_from_stream#1515: Working on file #5, slice #1 [Main] mondorestore.c->restore_a_biggiefile_from_stream#1515: Working on file #5, slice #2 [...] [Main] mondorestore.c->restore_a_biggiefile_from_stream#1515: Working on file #5, slice #3184 [Main] mondorestore.c->restore_a_biggiefile_from_stream#1515: Working on file #5, slice #3185 [Main] mondorestore.c->restore_a_biggiefile_from_stream#1515: Working on file #5, slice #3186 [Main] mondorestore.c->restore_a_biggiefile_from_stream#1515: Working on file #5, slice #3187 update_progress_form_full( I am now reassembling all the large files. ,Working on file #5, slice #3187, Please wait. This may take some time. ) --- g_current_progress=3216; g_maximum_progress=3215 [Main] mondorestore.c->restore_a_biggiefile_from_stream#1515: Working on file #5, slice #3188 update_progress_form_full( I am now reassembling all the large files. ,Working on file #5, slice #3188, Please wait. This may take some time. ) --- g_current_progress=3216; g_maximum_progress=3215 [Main] mondorestore.c->restore_a_biggiefile_from_stream#1515: Working on file #5, slice #3189 update_progress_form_full( I am now reassembling all the large files. ,Working on file #5, slice #3189, Please wait. This may take some time. ) --- g_current_progress=3216; g_maximum_progress=3215 [Main] mondorestore.c->restore_a_biggiefile_from_stream#1515: Working on file #5, slice #3190 update_progress_form_full( I am now reassembling all the large files. ,Working on file #5, slice #3190, Please wait. This may take some time. ) --- g_current_progress=3216; g_maximum_progress=3215 [Main] mondorestore.c->restore_a_biggiefile_from_stream#1515: Working on file #5, slice #3191 update_progress_form_full( I am now reassembling all the large files. ,Working on file #5, slice #3191, Please wait. This may take some time. ) --- g_current_progress=3216; g_maximum_progress=3215 [Main] mondorestore.c->restore_a_biggiefile_from_stream#1515: Working on file #5, slice #3192 update_progress_form_full( I am now reassembling all the large files. ,Working on file #5, slice #3192, Please wait. This may take some time. ) --- g_current_progress=3216; g_maximum_progress=3215 [Main] mondorestore.c->restore_a_biggiefile_from_stream#1515: Working on file #5, slice #3193 update_progress_form_full( I am now reassembling all the large files. ,Working on file #5, slice #3193, Please wait. This may take some time. ) --- g_current_progress=3216; g_maximum_progress=3215 [Main] mondorestore.c->restore_a_biggiefile_from_stream#1561: pathname_of_last_file_restored is now [Main] mondorestore.c->restore_a_biggiefile_from_stream#1573: biggiestruct.filename = /var/lib/mysql/ibdata1 [Main] mondorestore.c->restore_a_biggiefile_from_stream#1574: biggiestruct.checksum = 78161e8cd4e70e2c30ae89e5070f4ac0 [Main] mondorestore.c->restore_all_biggiefiles_from_stream#2430: I believe I have restored [Main] mondorestore.c->restore_all_biggiefiles_from_stream#2447: 5 biggiefiles in biggielist.txt; 5 biggiefiles processed today. [Main] mondorestore.c->restore_all_biggiefiles_from_stream#2470: mondorestore.c, restore_all_biggiefiles_from_stream, 2470: No biggiefiles selected. So, no biggie-EXATs to set. Done. [Main] libmondo-stream.c->closein_tape#120: closein_tape() -- entering [Main] libmondo-stream.c->closein_tape#138: closein_tape() -- leaving running: mt -f /dev/st0 offline > /storage/mondo.tmp.MXRHQj/mondo-run-prog-thing.tmp 2> /storage/mondo.tmp.MXRHQj/mondo-run-prog-thing.err --------------------------------start of output----------------------------- --------------------------------end of output------------------------------ ...ran just fine. :-) [Main] libmondo-devices.c->eject_device#235: Ejecting /dev/st0 running: eject /dev/st0 > /storage/mondo.tmp.MXRHQj/mondo-run-prog-thing.tmp 2> /storage/mondo.tmp.MXRHQj/mondo-run-prog-thing.err --------------------------------start of output----------------------------- --------------------------------end of output------------------------------ ...ran just fine. :-) [Main] libmondo-files.c->length_of_file#611: filename=/etc/raidtab Unable to openin filename (No such file or directory) running: ps | grep "" petris "" | awk '{print $1;}' | grep -v ""grep"" > /storage/mondo.tmp.MXRHQj/mondo-run-prog-thing.tmp 2> /storage/mondo.tmp.MXRHQj/mondo-run-prog-thing.err --------------------------------start of output----------------------------- --------------------------------end of output------------------------------ ...ran with res=256 running: kill `ps | grep "" petris "" | awk '{print $1;}' | grep -v ""grep""` > /storage/mondo.tmp.MXRHQj/mondo-run-prog-thing.tmp 2> /storage/mondo.tmp.MXRHQj/mondo-run-prog-thing.err --------------------------------start of output----------------------------- kill: usage: kill [-s sigspec | -n signum | -sigspec] [pid | job]... or kill -l [sigspec] --------------------------------end of output------------------------------ ...ran with res=256 [Main] mondorestore.c->restore_everything#2716: restore_everything() --- leaving Freeing memory formerly occupied by filelist [Main] libmondo-filelist.c->free_filelist#429: Finished freeing memory [Main] mondorestore.c->restore_to_live_filesystem#974: Tape : I don't need to unmount or eject the CD-ROM. running: umount /mnt/cdrom > /storage/mondo.tmp.MXRHQj/mondo-run-prog-thing.tmp 2> /storage/mondo.tmp.MXRHQj/mondo-run-prog-thing.err --------------------------------start of output----------------------------- umount: /mnt/cdrom: not mounted --------------------------------end of output------------------------------ ...ran with res=256 running: mt -f /dev/st0 offline > /storage/mondo.tmp.MXRHQj/mondo-run-prog-thing.tmp 2> /storage/mondo.tmp.MXRHQj/mondo-run-prog-thing.err --------------------------------start of output----------------------------- /dev/st0: Input/output error --------------------------------end of output------------------------------ ...ran with res=256 [Main] libmondo-devices.c->eject_device#235: Ejecting /dev/st0 running: eject /dev/st0 > /storage/mondo.tmp.MXRHQj/mondo-run-prog-thing.tmp 2> /storage/mondo.tmp.MXRHQj/mondo-run-prog-thing.err --------------------------------start of output----------------------------- --------------------------------end of output------------------------------ ...ran just fine. :-) [Main] mondorestore.c->main#3194: Still here. Yay. running: rm -Rf /storage/mondo.tmp.MXRHQj/* > /storage/mondo.tmp.MXRHQj/mondo-run-prog-thing.tmp 2> /storage/mondo.tmp.MXRHQj/mondo-run-prog-thing.err --------------------------------start of output----------------------------- --------------------------------end of output------------------------------ ...ran just fine. :-) [Main] libmondo-tools.c->unmount_boot_if_necessary#1309: starting [Main] libmondo-tools.c->unmount_boot_if_necessary#1316: leaving [Main] libmondo-files.c->register_pid#815: Unregistering PID running: umount /mnt/cdrom > /storage/mondo.tmp.MXRHQj/mondo-run-prog-thing.tmp 2> /storage/mondo.tmp.MXRHQj/mondo-run-prog-thing.err --------------------------------start of output----------------------------- umount: /mnt/cdrom: not mounted --------------------------------end of output------------------------------ ...ran with res=256 [Main] newt-specific.c->finish#406: Calling newtSuspend() }}} " 301 Add EMC Powerpathed boot from SAN support mondo 2.2.7 defect normal Bruno Cornec assigned Bruno Cornec 2008-12-14T10:47:18+01:00 2013-12-19T18:26:54+01:00 "Has anyone tried using Mondo with EMC Powerpathed boot from SAN drives? It works fine with boot from SAN drives, that are not running powerpath or mpxio. " 303 create a mondoarchive on an automounted nfs share without mounting first mondo 2.2.7 enhancement normal Bruno Cornec assigned Anthony Cicone 2009-01-06T21:33:20+01:00 2013-12-19T18:26:54+01:00 "I want to use the ""-n"" option with mondoarchive, to write to an automounted nfs share. For instance, we have have a NAS appliance called pisrh11, which has space carved up for nfs shares. On our servers, we are using the automounter, which automatically maps shares on pishr11, based on entries in the /etc/auto_* files. Here would be the automount file for application installed locally: {{{ # more /etc/auto_apps TRPperf -rw localhost:/export/appl/pkgs/& pb -rw localhost:/opt/& # PowerBroker java -rw localhost:/export/appl/pkgs/& AppManager -rw localhost:/export/appl/pkgs/AppManager/v8 }}} Here is the master automount file which points to some NIS maps: {{{ # more /etc/auto_master /trprmt/logs yp:auto.trprmt /nfs yp:auto.nfs /apps /etc/auto_apps }}} And here is the NIS entry for the mondoarchive shares: {{{ # ypcat auto.nfs|grep Linux -soft,bg,rw pishr:/images_Linux/trp -soft,bg,rw pishr11:/images_Linux/trp }}} Here is the share mounted: {{{ # pwd /root (piadm41)# cd /nfs/LinuxImages (piadm41)# pwd /nfs/LinuxImages (piadm41)# df -k . Filesystem 1K-blocks Used Available Use% Mounted on pishr:/images_Linux/trp 103257600 3244608 100012992 4% /nfs/LinuxImages (piadm41)# mount|grep Linux pishr:/images_Linux/trp on /nfs/LinuxImages type nfs (rw,soft,addr=10.22.214.26) }}} Thanks again. " 336 Pre-mondorestore script option mondo 2.2.8 enhancement normal Bruno Cornec reopened Dominic 2009-04-30T19:52:37+02:00 2013-12-19T18:26:54+01:00 "i.e. mondoarchive command line option to specify a script to run after the end of the boot and '''before''' any mondorestore action. For example, to start telnetd (if my other feature request is granted :-)). It would work like -P post-nuke option (IMO '-P' should also be '-post' and there should be new '-pre')." 348 Dynamic libraries openend with dlopen are not part of initrd mondo 2.2.9 defect normal Bruno Cornec new Bruno Cornec 2009-07-27T19:18:14+02:00 2013-12-19T18:26:54+01:00 "For program such as scp/ssh which do dlopen of some dyn. libs, those are not captured in mindi, so the command are unable to execute at restore time. If finding libdl in the the list of dyn. libs in ProcessLDD, then we should act to detect which dyn. libs will be loaded, by launching the command, maybe with --help to avoid potential problems." 349 error message on screen mondo 2.2.8 defect normal Bruno Cornec assigned JeffS 2009-07-28T17:30:47+02:00 2013-12-19T18:26:54+01:00 "while running mondoarchive I noticed this error. {{{ ---evalcall---E--- ---evalcall---1--- Making catalog of /home ---evalcall---2--- TASK: [*********...........] 44% done; 0:06 to go ---evalcall---E--- sh: -c: line 0: unexpected EOF while looking for matching `'' sh: -c: line 1: syntax error: unexpected end of file ---evalcall---1--- Making catalog of /home ---evalcall---2--- TASK: [***********.........] 53% done; 0:05 to go ---evalcall---E--- }}} It may be due to this: Under .java/.userprefs there were directories like below: I deleted them and mondo ran OK. {{{ ~/.java/.userPrefs/_!'8!cg""n!#4!b@""v!(}=> ls _!'0!}@""4!&8!d@""z!'`!cg""f!'k!bg""0!'`!cg""m!'%!}w""l _!'0!a@""u!&8!d@""z!'`!cg""f!'k!bg""0!'`!cg""m!'%!}w""l _!'0!}@""j!()!bw""z!&8!a@""u!'}!bw== cache display _!(%!d@""v!(@!~@""f!(:!bw""1!()!}w""l equations _!'k!~!""f!(%!d@""v!(@!~@""f!(:!e@""u!':= language license macros _!'@!~@""m!'%!d@""s!(@!|w""j!'g!}@""y!(@!|w""k!'`!~g""h!(`!b!""0!(:= portfolio prefs prefs.xml proxy watchscreens }}} " 350 Screenshots in documetation are illegible mondo-doc 2.2.8 defect normal Bruno Cornec assigned Tyson Clugg 2009-07-29T04:50:25+02:00 2013-12-19T18:26:54+01:00 "Documentation screenshots are illegible, for example [http://www.mondorescue.org/docs/mondorescue-howto.html#QUICKSTART Chapter 2. Quickstart] shows a 160x96 pixel image. Using mini images is fine for the HTML online version (which hyperlink to full size screenshots), but the PDF and postscript versions should include the full resolution images rather than the mini ones." 351 mondoarchive and exclude list problem mondo 2.2.8 defect normal Bruno Cornec assigned Pelephone 2009-09-03T12:40:17+02:00 2013-12-19T18:26:54+01:00 "Hey, I noticed that even if mondoarchive is running with exclude to some directories and exclude the NFS file systems, when the mondo is making the catalog, he is 'lstat'ing ALL the files including those to be excluded later. The problem is that we have servers with NFS mount point that holds millions of millions of files and the lstat is taking too long ( + making the NFS server work very hard). Is it possible somehow to change this behavior ?" 352 Adds VxVM support mondo 2.2.8 enhancement normal Bruno Cornec new Bruno Cornec 2009-09-03T14:57:35+02:00 2013-12-19T18:26:54+01:00 Adds veriats Volume Manager support 365 quiet option for mondoarchive mondo 2.2.9 defect normal Bruno Cornec new Bruno Cornec 2009-10-26T01:17:53+01:00 2013-12-19T18:26:54+01:00 For batch operations, it would be useful to have a quiet mode. 374 Support Encrypted FS mondo 2.2.9.1 defect normal Bruno Cornec new Bruno Cornec 2009-12-11T11:11:33+01:00 2013-12-19T18:26:54+01:00 TBD 386 Automagically toggle the -z flag when SELinux is on mondo 2.2.9.1 enhancement normal Bruno Cornec assigned Bruno Cornec 2010-01-15T20:55:49+01:00 2013-12-19T18:26:54+01:00 mondoarchive could indeed Automagically toggle the -z flag when SELinux is on. 396 Mondo does not timeout or exit if the tape drive fails mondo 2.2.9.1 defect normal Bruno Cornec new tastle73 2010-02-09T19:14:15+01:00 2013-12-19T18:26:54+01:00 "I noticed on a few occasions that when running mondorescue in verify or backup mode my tape drive will throw some kind of SCSI error. Rather than failing when it cannot read the tape, mondo runs away and takes 100% of cpu and never exits. The command is called from a script called from cron: {{{ mondoarchive -Vt -0 -d /dev/nst0 -o -N -e /var/log/mondoarchive.log: buffer (reader): failed to read input: Input/output error [Main] libmondo-stream.c->read_file_from_stream_FULL#1090: where_I_was_... = 11927552 [Main] libmondo-stream.c->start_to_read_from_next_tape#1438: Next tape requested. [Main] libmondo-stream.c->insist_on_this_tape_number#465: Insisting on tape #2 When the tape drive goes quiet, please insert volume 2 in this series. Waiting while the tape drive settles Waiting while the tape drive settles [Main] libmondo-stream.c->insist_on_this_tape_number#482: I assume user has inserted it. They _say_ they have... [Main] libmondo-stream.c->insist_on_this_tape_number#486: OK, I've finished insisting. On with the revelry. [Main] libmondo-stream.c->start_to_read_from_next_tape#1440: Opening IN the next tape root is mounted at /dev/mapper/vg-lv03 No, Schlomo, that doesn't mean /dev/mapper/vg-lv03 is the root partition. It's just a debugging message. Relax. It's part of am_I_in_disaster_recovery_mode() [Main] libmondo-devices.c->am_I_in_disaster_recovery_mode#147: Is this a ramdisk? result = 0 running: dd if=/dev/zero bs=1024 count=16k 2> /dev/null | buffer -o /dev/null -s 32768 -m 32m > /home/mondo.tmp.WCWYnD/mondo-run-prog-thing.tmp 2> /home/mond --------------------------------start of output----------------------------- --------------------------------end of output------------------------------ ...ran just fine. :-) Negotiated max buffer of 32 MB [Main] libmondo-fifo.c->open_device_via_buffer#121: Calling buffer --- command = 'buffer -m 32m -p20 -B -s32768 -i /dev/nst0 2>> /var/log/mondoarchiv [Main] libmondo-fifo.c->open_device_via_buffer#125: Successfully opened ('r') tape device /dev/nst0 running: ps auxww | grep ""buffer -m 32m -p20 -B -s32768 -i /dev/nst0 2>> /var/log/mondoarchive.log"" > /home/mondo.tmp.WCWYnD/mondo-run-prog-thing.tmp 2> /hom --------------------------------start of output----------------------------- root 25852 0.0 0.0 8700 968 ? S 01:15 0:00 sh -c buffer -m 32m -p20 -B -s32768 -i /dev/nst0 2>> /var/log/mondoarchive.log root 25855 0.0 0.0 8700 956 ? S 01:15 0:00 sh -c ps auxww | grep ""buffer -m 32m -p20 -B -s32768 -i /dev/nst0 2>> /var/log/mondoarchive. root 25857 0.0 0.0 6020 532 ? D 01:15 0:00 grep buffer -m 32m -p20 -B -s32768 -i /dev/nst0 2>> /var/log/mondoarchive.log --------------------------------end of output------------------------------ ...ran just fine. :-) running: ps auxww | grep buffer | grep -v grep > /home/mondo.tmp.WCWYnD/mondo-run-prog-thing.tmp 2> /home/mondo.tmp.WCWYnD/mondo-run-prog-thing.err --------------------------------start of output----------------------------- root 25852 0.0 0.0 8700 968 ? S 01:15 0:00 sh -c buffer -m 32m -p20 -B -s32768 -i /dev/nst0 2>> /var/log/mondoarchive.log root 25853 1.5 0.0 34284 344 ? D 01:15 0:00 buffer -m 32m -p20 -B -s32768 -i /dev/nst0 root 25854 0.0 0.0 34284 116 ? S 01:15 0:00 buffer -m 32m -p20 -B -s32768 -i /dev/nst0 --------------------------------end of output------------------------------ ...ran just fine. :-) Buffer successfully started. buffer (reader): failed to read input: Input/output error }}}" 406 persistent devices and naming by id mondo 2.2.9.2 enhancement normal Bruno Cornec assigned Chucky 2010-03-11T17:29:21+01:00 2013-12-19T18:26:54+01:00 "While backup, mondo should remember kernel node to /dev/disk/by-id mapping, and after restore automatically modify settings in /etc/fstab /boot/grub/menu.lst /boot/grub/device.map /etc/grub.conf Also, the /etc/udev/rules.d/70-persistent-net.rules /etc/udev/rules.d/70-persistent-cd.rules should be removed to prevent system to create shifted dev names. (eg. eth0 directly mapped to mac) And small one at the end, mondo scratch dirs aren't removed from backup. " 422 Support for FS > 2 TB mondo 2.2.9.3 defect normal Bruno Cornec new Bruno Cornec 2010-05-11T03:48:32+02:00 2013-12-19T18:26:54+01:00 "At restore time, when dealing with large FS, mondorestore should use parted to re-create the FS correctly: {{{ parted /dev/cciss/c1d0 mklabel gpt parted /dev/cciss/c1d0 mkpart primary 0 3290000 sleep 10 mke2fs -m0 -j -T largefile4 /dev/cciss/c1d0p1 mount /dev/cciss/c1d0p1 /video }}}" 423 Compare mode in mondoarchive doesn't work with -d option correctly. mondo 2.2.9.3 defect normal Bruno Cornec assigned Bruno Cornec 2010-06-04T03:53:12+02:00 2013-12-19T18:26:54+01:00 "When using {{{ /usr/sbin/mondoarchive -Vr -d /dev/sr0 -s 4480m -g }}} mondoarchive asked me what device to compare, even though I have it in the command line. (report from Robert E Laughlin)" 437 mondoarchive doesn't create multiple images on external USB drive mondo 2.2.9.4 defect normal Bruno Cornec new Bruno Cornec 2010-08-05T04:54:02+02:00 2013-12-19T18:26:54+01:00 mondoarchive with 6500MB done on an external harddisk. I must !! take 6500MB because when I take f.e. 1500MB and the image has to be split than I got an error like “harddisk full” even if the partition as 60GB free. 515 Provide a newt interface to LVM modifications mondo 2.2.9.7 enhancement normal Bruno Cornec new Bruno Cornec 2011-10-19T12:44:44+02:00 2013-12-19T18:26:54+01:00 MondoRescue should allow at restore time to modify the LVM setup (particular case when you change a disk size), based on what is in i-want-my-lvm 625 lvm size appear to zero mondo 3.0.1 enhancement normal Bruno Cornec assigned rue 2012-06-12T19:33:37+02:00 2013-12-19T18:26:54+01:00 "During restore, the partitions are correctly sized but the lvm size appear to zero. Mondorestore will size the lvm correctly when it will continue to process. The sizes are correctly computed by the script /tmp/i-want-my-lvm. But It should be good to have the lvm size not displayed to zero. " 642 mondoarchive -OVN does not exclude automounts mondo 3.0.2 defect normal Bruno Cornec assigned Daniel_B 2012-08-30T16:22:24+02:00 2014-07-24T22:18:58+02:00 "hello, mondoarchive -OVN does not exclude '''un'''mounted automounts from the catalog, so it backs up the complete mountpoint as it gets mounted when the actual backup starts. A scripted ls -l to the automount directories close before the backup does help but is not that nice! The used versions are: mondo-3.0.2-1.sles10 mindi-busybox-1.18.5-1.sles10 mindi-2.1.3-1.sles10 kind regards Daniel Berglar" 456 OBDR mode is not compatible with -H option of mondoarchive mondo 2.2.9.4 3.0.5 defect major Bruno Cornec assigned Bruno Cornec 2011-01-21T13:25:14+01:00 2012-06-05T00:03:19+02:00 "As reported on mondo ML: http://sourceforge.net/mailarchive/forum.php?thread_name=1295604747763-2300816.post%40n3.nabble.com&forum_name=mondo-devel " 506 NFS mount could be done automatically mondo 2.2.9.7 3.0.5 enhancement minor Bruno Cornec assigned Bruno Cornec 2011-10-19T12:26:45+02:00 2012-06-05T00:05:44+02:00 NFS mount could be done automatically instead of asking the user to do it manually. 684 Feature request: generic mondo ISO mondo 3.0.3 3.0.5 enhancement minor tux-59 new tux-59 2013-05-15T19:35:53+02:00 2013-05-15T19:35:53+02:00 "Hi, I'm using Mondorescue to back my servers (VM, Physical, etc...) up. I am using the NFS backup option and I have a PXE setup to restore my backup by using the network. It works fine, but I feel that it is quite complicated to maintain one ISO image per server. (mabe am I doing it the wrong way thought...) How do I proceed: When I make my backup, I create an ISO image which I upload to my NFS server by using the NFS backup option of mondoarchive. Then, I have to extract the vmlinuz and the initrd from the ISO image to get it aside the ISO file Then, I have to configure my PXE configuraiton file, with such entries: Example: mymachine-######ENTRY-BEGIN###### LABEL mymachine kernel /mondo/mymachine/mymachine-vmlinuz append initrd=/mondo/mymachine/mymachine-initrd load_ramdisk=1 prompt_ramdisk=0 ramdisk_blocksize=1024 ramdisk_size=128000 rw root=/dev/ram iso_mode acpi=off apm=off devfs=nomount exec-shield=0 pxe prefix=mymachine-19700101 INTERACTIVE ipconf=eth0:dhcp nfsmount=172.29.12.110:/tftpboot/mondo/mymachine MENU LABEL mymachine mymachine-######ENTRY-END###### Of course I have a little script that does the job. My request folows: It would be great to have only one ISO image to boot from; then you select the ISO image (the backup of the concerned machine) from the network (eg: NFS) and then you restore the backup. Maybe it is already possible, but I didn't find any way to get it working by myself... Thanks you by advance Best regards Tux-59" 691 Document the manual tape restore process mondo-doc 3.0.3 3.0.5 enhancement minor Bruno Cornec new Bruno Cornec 2013-05-22T04:00:48+02:00 2013-05-22T04:00:48+02:00 In case of emergency and blocking bug. 394 post= option not working mondo 2.2.9.2 3.0.5 defect normal Bruno Cornec assigned Bruno Cornec 2010-02-09T01:51:08+01:00 2012-06-05T00:02:44+02:00 It seems that the post option is not invoked correctly when used, whereas the pre= option is. To be checked closely. 507 Place scratch dir automatically on NFS mondo 2.2.9.7 3.0.5 enhancement normal Bruno Cornec assigned Bruno Cornec 2011-10-19T12:27:45+02:00 2012-06-05T00:06:11+02:00 How to put the scratch dir on the NFS mount automatically (mount is done inside mondo - normally - so user has no way as of now to specify the creation of the scratch dir under that mount point, which would be useful in that case. From code it seems that scratchdir is created on the fly so should work. 509 pre script limitation mondo 2.2.9.7 3.0.5 enhancement normal Bruno Cornec assigned Bruno Cornec 2011-10-19T12:31:57+02:00 2012-06-05T00:07:07+02:00 "Problem for pre script: it has to be at the root of the NFS share mounted. subdir are not handled, due to copy under /tmp as of now " 510 grub install issue with dm multipath mondo 2.2.9.7 3.0.5 defect normal Bruno Cornec assigned Bruno Cornec 2011-10-19T12:33:41+02:00 2012-06-05T00:07:27+02:00 Restoration is done by default for grub on sda (because multipath and GRUB found on sda, sdb, dm-2 => prefer to get a question at restore time + option in boot cli) Also useful for P2V. 603 DNS names do not work at restore time on RHEL 6.2 mondo 3.0.1 3.0.5 defect normal Bruno Cornec new Bruno Cornec 2012-04-03T19:13:59+02:00 2012-10-06T04:37:56+02:00 Using a DNS name for the NFS server storing the !MondoRescue ISO images doesn't work whereas using the IP address works, even with a correct /etc/resolv.conf. LInked to busybox ??? to be tested. 636 mondo doesn't handle SMBIOS NIC names from PCI card mondo 3.0.1 3.0.5 defect normal Bruno Cornec new Michael Shapiro 2012-07-31T00:35:00+02:00 2012-07-31T00:35:00+02:00 "* Server: Proliant ML350p Gen8 * OS: RHEL 6.1 x86_64 * Kernel boot line has: biosdevname=1 * Command line: mondoarchive -9NO -n mrou10:/nwinstall -p mondo-6.1-gen8 -d mondo/ml350g8 -s 650m On Gen8 servers, biosdevname results in a change in naming for network devices. Embedded NIC's will not be called ethX; they will be named emX. PCI card NIC's will be called pXpY where X is the card slot and Y is the port on the card. Here are the NIC's on the server: {{{ # ifconfig | grep Ethernet em1 Link encap:Ethernet HWaddr 9C:8E:99:4C:0C:48 em2 Link encap:Ethernet HWaddr 9C:8E:99:4C:0C:49 em3 Link encap:Ethernet HWaddr 9C:8E:99:4C:0C:4A em4 Link encap:Ethernet HWaddr 9C:8E:99:4C:0C:4B p4p1 Link encap:Ethernet HWaddr 00:26:55:DC:09:42 p4p2 Link encap:Ethernet HWaddr 00:26:55:DC:09:43 }}} Only p4p2 has an IP address configured: {{{ p4p2 Link encap:Ethernet HWaddr 00:26:55:DC:09:43 inet addr:16.118.11.226 Bcast:16.118.11.255 Mask:255.255.254.0 inet6 addr: fe80::226:55ff:fedc:943/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:590976 errors:0 dropped:0 overruns:0 frame:0 TX packets:1091811 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:41220986 (39.3 MiB) TX bytes:1656328201 (1.5 GiB) Interrupt:30 Memory:f7fa0000-f7fc0000 }}} The problem is that mondoarchive sets NETFS-DEV to em1 instead of p4p2. I'd be happy to modify the code if you let me know which source version to use. " 682 extend -A option to run command for USB as well mondo 3.0.3 3.0.5 enhancement normal Bruno Cornec new stefanbauer 2013-05-14T21:57:55+02:00 2013-05-14T21:57:55+02:00 "-A command is only executed, if the backup is written to CD/NFS/ISO. Please add / extend the option to also be executed if i backup to USB." 688 Improve Smart array support in case of driver conflicts mondo 3.0.3 3.0.5 enhancement normal Bruno Cornec new Bruno Cornec 2013-05-18T07:39:45+02:00 2013-05-18T07:39:45+02:00 "In some cases for Smart Array controllers, 2 drivers can support the same controller (e.g. P400 on SLES 11 SP1 working with both cciss and hpsa). This may lead to mondorestore loading the wrong one first, and the controller being badly supported, and thus the restore failing. Cf: http://h20000.www2.hp.com/bc/docs/support/SupportManual/c02677069/c02677069.pdf for details. MondoRescue could provide a tool based on this table, generating the name of the recomended driver to loader in forcemods at restore time, so that the right one is always loaded first." 710 Ability to use the HP ProLiant SD card slot for DR mondo 3.0.3 3.0.5 enhancement normal Bruno Cornec assigned Bruno Cornec 2013-07-22T18:31:39+02:00 2013-07-22T18:32:17+02:00 "It would be interesting to validate the usge of !MondoRescue with an SD card put in an HP !ProLiant server to use it as a DR mecanism. While it should'nt require any specific adaptation, it has never been tested so would at leat require that step to be performed. " 719 Ability to restore having DHCP on one NIC and NFS on another mondo 3.0.4 3.0.5 defect normal Bruno Cornec new Bruno Cornec 2013-10-07T21:39:51+02:00 2013-10-07T21:39:51+02:00 Ability to restore having DHCP on one NIC and NFS on another 739 Add support for guest mounted SMBFS mondo 3.0.4 3.0.5 enhancement normal Bruno Cornec new Bruno Cornec 2014-04-03T00:18:36+02:00 2014-04-03T00:18:36+02:00 mondoarchive needs to support mounting SMBFS/CIFS FS with -o guest to avoid passwd request. Allow support at both backup and restore time. 750 two initrd.img in mondorescue.iso mondo 3.0.4 3.0.5 defect normal Bruno Cornec new victor gattegno 2014-07-30T00:07:10+02:00 2014-07-30T00:07:10+02:00 "There are two initrd.img in mondorescue.iso - one in mondorescue.iso - the second one in mondorescue.iso too, under images/mindi-bootroot.65600.img Each initrd.img is 29 Mb size, and it's the same initrd.img duplicated, so mondorescue.iso could be 29 Mb lighter. " 756 [MondoRestore][Expert Mode] - Software Raid 1 - option to disable 'wait for md resync' mondo 3.0.4 3.0.5 enhancement normal Bruno Cornec new Ioan Indreias 2014-10-02T08:00:03+02:00 2014-10-02T08:00:03+02:00 "In current implementation when you choose to format a software RAID 1 partition it will wait till all devices are in sync. This is a good option but in case you have quite big partitions (eg 2TB) it will take too long (eg more than 4 hours) just to finish the sync phase. Please implement, in Expert Mode, an option that will allow to go to next stage when restore process is stuck in software raid resycn. For example allowing to press 'ESC' and answer 'Yes' to a question similar to 'Are you sure that you like to bypass software RAID resync?'" 835 EFI support issue on Ubuntu 16.04 mindi 3.2.2 3.3.0 defect blocker Bruno Cornec new Bruno Cornec 2018-02-28T12:04:37+01:00 2018-02-28T12:04:37+01:00 "{{{ INFO: Found ldlinux.c32 at /usr/lib/syslinux/modules/bios/ldlinux.c32 INFO: Found syslinux.efi at /usr/lib/SYSLINUX.EFI/efi64/syslinux.efi INFO: Found syslinux boot type INFO: Found ldlinux.e64 at /usr/lib/syslinux/modules/efi64/ldlinux.e64 INFO: Copying /usr/lib/syslinux/modules/efi64/ldlinux.e64 to /tmp/mindi.iD8bFg1P4n/bigdir.18592/EFI/BOOT cp: cannot stat '/usr/lib/syslinux/modules/efi64/ldlinux.e64/../libutil.c32': Not a directory FATAL ERROR. Cannot copy libutil.c32 to /tmp/mindi.iD8bFg1P4n/bigdir.18592/EFI/BOOT). Did you run out of disk space? }}}" 873 mindi aborts on opensuse 15.2 due to /run included mindi 3.3.0 3.3.0 defect critical Bruno Cornec assigned Bruno Cornec 2021-04-02T17:40:09+02:00 2021-04-02T19:04:52+02:00 "Despite the fact that /run is exceluded by mondoarchive from the set, it can be included by mindi in boot disks as shown on opensuse 15.2 The log shows that resolv.conf is redirected to /run/netconfig/resolv.conf which seems to make /run included as a whole, whereas it should't. " 797 ldlinux.c32 not found while booting mondo 3.2.2 3.3.0 defect normal Bruno Cornec assigned Petr Baláš 2016-04-30T21:08:27+02:00 2019-11-10T18:21:16+01:00 "Debian 8.4 - amd64 arch packages from deb ftp://ftp.mondorescue.org/debian 8 contrib UEFI system trying to boot generated CD, but it failed with error message that ldlinux.c32 can't be found Tried to copy all files form $scratch\EFI to $scratch (while backup is in progress) so I force ldlinux.c32 and configuration files to root dir on CD and evereything started to work again. mindi - 3.0.2-1 mindi-busybox - 1.21.1-1 mondo - 3.2.2-1" 817 Mondo/mindi creating unbootable ISOs mondo 3.0.2 3.3.0 defect normal Bruno Cornec new Craig E Johnson 2017-06-08T14:46:06+02:00 2018-04-09T15:02:55+02:00 "When attempting to boot/restore from the image(s), I get: {{{ ISOLINUX 3.82 3.82 ETCD Copyright (C) 1994-2009 H. Peter Anvin et al Could not find kernel image: linux boot: }}} Info from source server: {{{ # uname -a Linux j700s014 3.0.101-0.47.52-default #1 SMP Thu Mar 26 10:55:49 UTC 2015 (0e3c7c8) x86_64 x86_64 x86_64 GNU/Linux # rpm -qa | grep -i mondo perl-MondoRescue-3.2.2-1.sles11 mondo-3.2.2-1.sles11 # rpm -qa | grep -i mindi mindi-busybox-1.21.1-1.sles11 mindi-3.0.2-1.sles11 }}}" 852 mondorestore doesn't restore UUIDs for btrfs FS mondo 3.2.2 3.3.0 defect normal Bruno Cornec assigned Bruno Cornec 2019-11-11T23:59:26+01:00 2019-11-12T00:49:47+01:00 the script mr-label-partitions-as-necessary only restore labels for btrfs FS. UUIDs need to be taken in account 853 Compiler warning mondo 3.2.2 3.3.0 defect normal Bruno Cornec new Bruno Cornec 2019-11-15T10:46:36+01:00 2019-11-15T10:46:36+01:00 "rhel-8-x86_64] libmondo-devices.c:2560:32: warning: '/netfsdir' directive writing 9 bytes into a region of size between 1 and 128 [-Wformat-overflow=] [rhel-8-x86_64] sprintf(bkpinfo->isodir, ""%s/netfsdir"", bkpinfo->tmpdir); This is linked to #1" 854 Compiler warning mondo 3.2.2 3.3.0 defect normal Bruno Cornec new Bruno Cornec 2019-11-15T10:47:20+01:00 2019-11-15T10:47:20+01:00 "{{{ [rhel-8-x86_64] In file included from /usr/include/stdio.h:873, [rhel-8-x86_64] from ../../src/include/my-stuff.h:40, [rhel-8-x86_64] from libmondo-devices.c:13: [rhel-8-x86_64] /usr/include/bits/stdio2.h:36:10: note: '__builtin___sprintf_chk' output between 10 and 137 bytes into a destination of size 128 [rhel-8-x86_64] return __builtin___sprintf_chk (__s, __USE_FORTIFY_LEVEL - 1, [rhel-8-x86_64] ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ [rhel-8-x86_64] __bos (__s), __fmt, __va_arg_pack ()); [rhel-8-x86_64] ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ }}}" 855 Compiler warning mondo 3.2.2 3.3.0 defect normal Bruno Cornec new Bruno Cornec 2019-11-15T10:50:43+01:00 2019-11-15T10:50:43+01:00 "{{{ [rhel-8-x86_64] ../src/mondorestore/mondo-rstr-tools.c:737:35: warning: '%s' directive writing up to 511 bytes into a region of size 128 [-Wformat-overflow=] [rhel-8-x86_64] sprintf(bkpinfo->media_device, ""%s1"", value); [rhel-8-x86_64] ^~ ~~~~~ }}} linked again to #1" 856 error with /mnt/cdrom mondo 3.2.2 3.3.0 defect normal Bruno Cornec new Bruno Cornec 2019-11-15T11:28:32+01:00 2019-11-15T11:28:32+01:00 "{{{ mkdir: impossible de créer le répertoire « /mnt/cdrom »: Système de fichiers accessible en lecture seulement }}} on rhel 8. That should not be forced." 865 xorriso mandatory with UEFI on Debian > 8 mondo 3.2.2 3.3.0 defect normal Bruno Cornec new Bruno Cornec 2020-06-13T19:28:16+02:00 2020-06-13T19:28:16+02:00 "Check deps for deb issue for iso with mindi" 866 cretae mr_mkiso mondo 3.2.2 3.3.0 defect normal Bruno Cornec new Bruno Cornec 2020-06-13T19:29:49+02:00 2020-06-13T19:29:49+02:00 "calling either xorrisofs or mkisofs with the appropriate params As well a mr_burniso would be usefull" 867 Failed mondo recover mondo 3.2.2 3.3.0 defect normal Bruno Cornec new John S 2020-08-10T16:00:20+02:00 2020-08-12T14:28:26+02:00 "I am trying to clone a Centos5.6 server. I have run MondoArchive which has created 2 .iso files. I have created a blank VM and mounted the first iso and launched it. I get error: 'Could not find kernel image: linux' If I try '/vmlinuz initrd=/initrd.img' I get: 'Loading Invalid or corrupt kernel image' I have mounted the iso file on another machine and I can browse around the directories and the files seem to be where they should be. Is there anything I can do to get this working please? " 871 /dev/sdb vs. /dev/sda and mondoarchive to DVD-R via the GUI mindi-busybox 3.2.2 3.3.0 task normal Bruno Cornec new Chris Bayne 2021-02-02T00:43:38+01:00 2021-02-02T00:56:07+01:00 "Hello, I have a RHEL 6.7/RHAWK 6.5.6 system that I'm working on that's primary file system is /dev/sdb due to it's /dev/sda being used for other functionality on the system that's not for storage. Anyway, every time a I build a disk off of it or a net image, it kicks it into interactive mode and I have to trick it by editing each line to say ""/dev/sdaX"". This get it through the restore and it ends up coming out on the other side as /dev/sdb structure on the other end. This is fine for our lab as we all know what to do with it, but will most likely frustrate our customer. What settings would I have to change for this? I most likely have the Milestone and Version wrong as I'm at home and not in front of the machine, if that's important, i can get it to you on your return correspondence. Another requirement I have is to deliver build media to our customer and I have to have this build witnessed by a quality control engineer, meaning I will have to build this from the console using a DVD-R. When I use the mondoarchive GUI, I set it to maximum compression and gzip, everything else I use the defaults. it gets to about 84% and then will not format the disk. Is this a mondo/mindi setting or do you think this may be hardware related? are there any settings I should check? Chris Bayne " 877 fail to buackup rhel7 and can't creat .ISO image mondo 3.2.2 3.3.0 defect normal Bruno Cornec new ma 2021-05-21T08:05:33+02:00 2021-05-21T08:05:33+02:00 "See /var/log/mondoarchive.log for details of backup run " 878 Feature request: Add repository for openSUSE Leap 15.3 mondo 3.2.2 3.3.0 enhancement normal Bruno Cornec new Atronach 2021-08-03T23:22:11+02:00 2021-08-29T01:41:20+02:00 At http://www.mondorescue.org/ftp/opensuse/, the directory for latest openSUSE Leap version is for v15.2. 15.3 is out for 2 months now. Please add a repo for Leap 15.3. 880 use inxi for conf reporting mondo 3.3.0 3.3.0 enhancement normal Bruno Cornec new Bruno Cornec 2025-02-26T01:16:34+01:00 2025-02-26T01:16:34+01:00 "inxi -F -d -f -i -J -l -m -o -p -r -t -u -x -J -W gives the maximum report See availability for various distros." 881 Error building mondo-doc on Debian 11 mondo-doc 3.3.0 3.3.0 defect normal Bruno Cornec new Bruno Cornec 2025-05-09T01:24:31+02:00 2025-05-09T01:24:31+02:00 " {{{ [debian-11-x86_64] Converting images/10cd-mini.png to images/10cd-mini.eps [debian-11-x86_64] convert-im6.q16: attempt to perform an operation not allowed by the security policy `EPS' @ error/constitute.c/IsCoderAuthorized/426. [debian-11-x86_64] make[1]: *** [Makefile.howto:16 : images/10cd-mini.eps] Erreur 1 }}} " 790 mondorestore says a partition is occupied mondo 3.2.1 3.3.1 defect major Bruno Cornec assigned Bruno Cornec 2016-04-07T03:13:31+02:00 2017-03-08T16:43:24+01:00 "When restoring, mondorestore can say that a partition is occupied and stop preparing the disk. This can happen when the restore is done on an MBR disk whereas the original was GPT." 149 mondorestore should use efibootmgr to recreate menu entries on ia64 mondo 2.2.1 3.3.1 enhancement normal Bruno Cornec assigned Bruno Cornec 2007-03-21T00:07:02+01:00 2017-03-08T16:42:54+01:00 mondorestore should use efibootmgr to recreate menu entries on ia64. Without that it's actually difficult to know nd find on which device the system should boot. 762 Fail to create 1Tb USB's recovery disk mondo 3.2.0 3.3.1 defect normal porrego new porrego 2015-01-17T07:50:16+01:00 2017-03-08T17:13:14+01:00 "I'm running mondoarchive 3.2.0-r3332 and mindi 3.0.0-r3332 over Proliant G8 server with RHEL6. The system is the host of 3 virtual machines. I tried several times to do a full backup of the system using 1Tb USB's external disk, through the following command line @ mondoarchive -OU -d /dev/sdb -s 950G -G -l GRUB It fails at the end when slices files should be moved from tmp dir to the USB. The error message is that the device doesn't have enough space. The disk usage is never overpassing 10%. It seems that the number of slice files is higher than the number of files that a vfat filesystem is able to support. I ran the same command, but filtering all big files (-E). It was succesful. Do I have something wrong in the command line? or Should I include an additional option to use another filesystem in the USB? Thanks a lot in advance" 807 Improve hardlink support for mondoarchive mondo 3.2.2 3.3.1 defect normal Bruno Cornec new Bruno Cornec 2016-12-20T12:02:26+01:00 2016-12-20T12:02:26+01:00 "As reported on the mailing list: {{{ Running: mondo-3.2.2-1.rhel6.i386 mindi-busybox-1.21.1-1.rhel6.i386 mindi-3.0.2-1.rhel6.i386 afio-2.5-1.rhel6.i386 We’ve been using mondo for some time and I’m just realizing that it does not handle hardlinks very well. From testing the afio command (using the mondoarchive/restore commands), I have OBERSERVED that If you have two directories with the second one that essentially has hardlinks back to all the files in the first: Source directory file sizes: # du -sh 20151231-230001-226/backup/home/mrs/Downloads 20160131-230001-528/backup/home/mrs/Downloads 288M 20151231-230001-226/backup/home/mrs/Downloads 28K 20160131-230001-528/backup/home/mrs/Downloads Backup: Command: afio -o -b 131072 -M 16m -Z -P bzip2 -G 3 -T 3k /opt/NotBackedUp/RTP/test.afio.bz2 < /tmp/afio-filelist File size: # ls -l /opt/NotBackedUp/RTP/test.afio.bz2 -rw-r--r-- 1 root root 301203456 Dec 8 14:38 /opt/NotBackedUp/RTP/test.afio.bz2 Restore: Command: afio -i -M 8m -b 131072 -c 8 -P bzip2 -Z /opt/NotBackedUp/RTP/test.afio.bz2 File Size: # du -sh 20151231-230001-226/backup/home/mrs/Downloads 20160131-230001-528/backup/home/mrs/Downloads 288M 20151231-230001-226/backup/home/mrs/Downloads 28K 20160131-230001-528/backup/home/mrs/Downloads So, the afio commands preserve hard links; however, when I use mondoresecue, both the original file and linked file are full copies: Backup: Command: mondoarchive -Oi -I '/opt/azreserve/backintime/mrs/backintime/litho2399/mrs/1/20151231-230001-226/backup/home/mrs/Downloads |/opt/azreserve/backintime/mrs/backintime/litho2399/mrs/1/20160131-230001-528/backup/home/mrs/Downloads' -d /opt/NotBackedUp/RTP -s 4480m -p litho2399 ISO Size: -rw-r--r-- 1 root root 729956352 Dec 9 08:14 litho2399-1.iso Restore: Command: mondorestore -i -d /opt/NotBackedUp/RTP -p litho2399 -g -Z interactive File Size: # du -sh * 288M 20151231-230001-226 288M 20160131-230001-528 There appears to be two main issues: 1. Although afio does handle hardlinks correctly, given that afio is called for many times, with a subset (fileset) of files, it can only deal with hardlinks within the fileset. 2. The processing of big files is processed file-by-file and therefore does not deal with hardlinks across multiple files. This is not only a restore concern (mondorestore) but also a backup concern (mondoarchive) as the backups created can be much larger than required -- this is actually how I first noticed this issue. The following command can be used to identify linked files where the line as the format: : find -type f -links +1 -exec stat --format='%d %i %n' {} \; | sort Adjacent lines with the same “ ” would be common hard linked files. One could only backup the file on the first line with the matching “ ” and skip backing up the other matching lines. After the files are restored, the files could be relinked using the 2nd-Nth matching “ ” lines. I know I have given a worse case example (which is actually associated with using backintime); however, there are other examples one can find in system directories. For example, under /var on RHEL 6.x (where the first column displayed below is the number of hard links to the listed file): [root@litho2399 orig]# find /var -type f -links +1 -exec stat --format='%d %i %n' {} \; | sort > /tmp/rtp [root@litho2399 orig]# uniq -w 11 -d -c /tmp/rtp 2 2050 17257 /var/lib/yum/yumdb/w/e40d2bcd59c08093bb45f0eda7ed2d7c1456f2d7-wxPython-2.8.12.0-1.el6-i686/from_repo_revision 2 2050 17261 /var/lib/yum/yumdb/c/475ff8d21636d6e9cb3af91d71011c858d0c7aa8-codeblocks-contrib-12.11-1.el6-i686/from_repo_revision 2 2050 17266 /var/lib/yum/yumdb/c/b7fa7277e6bbdfb523f0ec297a21eeb019e40bbe-codeblocks-12.11-1.el6-i686/from_repo_timestamp 2 2050 271 /var/lib/yum/yumdb/d/8a66136827c3aa826f283e6a256b566426ced0ba-digilent.waveforms-3.3.5-1-i686/from_repo_revision 2 2050 284 /var/lib/yum/yumdb/d/42de7c6be8c1f756777eeea8123ba5c7f8d7d5e0-digilent.adept.runtime-2.16.5-1-i686/from_repo_revision 1344 2050 655402 /var/lib/yum/yumdb/a/03a419bfe569d6e344dd36f853c79da443db1be8-apache-tomcat-apis-0.1-1.el6-noarch/from_repo 702 2050 655403 /var/lib/yum/yumdb/a/03e545ccb78a949dc8fcda8130bb9e2c565f2d9d-aic94xx-firmware-30-2.el6-noarch/reason 1344 2050 655404 /var/lib/yum/yumdb/a/03a419bfe569d6e344dd36f853c79da443db1be8-apache-tomcat-apis-0.1-1.el6-noarch/releasever 1472 2050 655405 /var/lib/yum/yumdb/a/03a419bfe569d6e344dd36f853c79da443db1be8-apache-tomcat-apis-0.1-1.el6-noarch/checksum_type 1344 2050 655407 /var/lib/yum/yumdb/a/03a419bfe569d6e344dd36f853c79da443db1be8-apache-tomcat-apis-0.1-1.el6-noarch/from_repo_revision 1344 2050 655408 /var/lib/yum/yumdb/a/03a419bfe569d6e344dd36f853c79da443db1be8-apache-tomcat-apis-0.1-1.el6-noarch/from_repo_timestamp 1516 2050 655409 /var/lib/yum/yumdb/a/03a419bfe569d6e344dd36f853c79da443db1be8-apache-tomcat-apis-0.1-1.el6-noarch/installed_by 2 2050 655414 /var/lib/yum/yumdb/l/0e64afa12db909d75113daa05d5184bbd6df720e-libgdiplus0-debuginfo-2.6.7-0-i686/checksum_type 2 2050 658422 /var/lib/yum/yumdb/a/084996dd0259b07515e37af8f5d8b90ed1e568a5-alsa-lib-1.0.22-3.el6-i686/releasever 2 2050 658423 /var/lib/yum/yumdb/a/084996dd0259b07515e37af8f5d8b90ed1e568a5-alsa-lib-1.0.22-3.el6-i686/command_line 2 2050 658424 /var/lib/yum/yumdb/a/084996dd0259b07515e37af8f5d8b90ed1e568a5-alsa-lib-1.0.22-3.el6-i686/checksum_type 7 2050 663560 /var/lib/yum/yumdb/p/b8a5f820873b99c1f1e0e586ef296e2360d2ba3e-python-rhsm-0.99.12-1.el6-noarch/from_repo 7 2050 670757 /var/lib/yum/yumdb/p/b8a5f820873b99c1f1e0e586ef296e2360d2ba3e-python-rhsm-0.99.12-1.el6-noarch/checksum_type 11 2050 670801 /var/lib/yum/yumdb/a/136d85e53eba5dbacc4f1050ec26af1cb1976c05-azores-stepper-10.13.0-1.el6-i686/checksum_type 7 2050 670826 /var/lib/yum/yumdb/p/b8a5f820873b99c1f1e0e586ef296e2360d2ba3e-python-rhsm-0.99.12-1.el6-noarch/command_line 7 2050 670829 /var/lib/yum/yumdb/p/b8a5f820873b99c1f1e0e586ef296e2360d2ba3e-python-rhsm-0.99.12-1.el6-noarch/from_repo_revision 7 2050 670830 /var/lib/yum/yumdb/p/b8a5f820873b99c1f1e0e586ef296e2360d2ba3e-python-rhsm-0.99.12-1.el6-noarch/from_repo_timestamp 12 2050 670832 /var/lib/yum/yumdb/a/136d85e53eba5dbacc4f1050ec26af1cb1976c05-azores-stepper-10.13.0-1.el6-i686/from_repo 2 2050 672833 /var/lib/yum/yumdb/a/c28b3cbf37f510aa8e28d44c154507869321e3d6-alsa-lib-devel-1.0.22-3.el6-i686/from_repo_revision 16 2050 674545 /var/lib/yum/yumdb/g/4a031365276ab79a21f25843228d37b78b2a24b5-gnome-sharp2-opt-2.24.2-14.13-i686/checksum_type 16 2050 674582 /var/lib/yum/yumdb/g/4a031365276ab79a21f25843228d37b78b2a24b5-gnome-sharp2-opt-2.24.2-14.13-i686/reason 16 2050 674583 /var/lib/yum/yumdb/g/4a031365276ab79a21f25843228d37b78b2a24b5-gnome-sharp2-opt-2.24.2-14.13-i686/releasever 16 2050 674584 /var/lib/yum/yumdb/g/4a031365276ab79a21f25843228d37b78b2a24b5-gnome-sharp2-opt-2.24.2-14.13-i686/command_line 12 2050 674586 /var/lib/yum/yumdb/g/4a031365276ab79a21f25843228d37b78b2a24b5-gnome-sharp2-opt-2.24.2-14.13-i686/from_repo_revision 16 2050 674588 /var/lib/yum/yumdb/g/4a031365276ab79a21f25843228d37b78b2a24b5-gnome-sharp2-opt-2.24.2-14.13-i686/installed_by 2 2050 674592 /var/lib/yum/yumdb/m/b9832f7116d13777490a161cbf53a7bdbee0d8b2-mod_mono-opt-debuginfo-2.10.2-5.3-i686/from_repo_timestamp 2 2050 674600 /var/lib/yum/yumdb/m/4996a80c8aef80fcfa7a341fb5011e0eaec42ccf-mono-opt-debuginfo-3.2.3-3.1-i686/from_repo_timestamp 2 2050 674604 /var/lib/yum/yumdb/g/54b1ff522253bdf560503fb67c01060eeb5cd22c-gtk-sharp2-opt-2.12.21-24.6-i686/from_repo_timestamp 2 2050 674608 /var/lib/yum/yumdb/m/2cc8f7fd443072c6221af09d9bcf10e8581d50a0-mono-xsp-opt-debuginfo-3.2.0-4.3-i686/from_repo_timestamp 2 2050 674615 /var/lib/yum/yumdb/g/4a031365276ab79a21f25843228d37b78b2a24b5-gnome-sharp2-opt-2.24.2-14.13-i686/from_repo_timestamp 6 2050 674619 /var/lib/yum/yumdb/p/7e56c43f9c7f641eda990d7443b9d76c83150c6d-perl-XML-NamespaceSupport-1.10-3.el6-noarch/from_repo_revision 3 2050 674683 /var/lib/yum/yumdb/m/32e21aae1e2eacc09a131e24022d0505399a3029-maxima-5.30.0-1-i386/checksum_type 3 2050 674721 /var/lib/yum/yumdb/m/32e21aae1e2eacc09a131e24022d0505399a3029-maxima-5.30.0-1-i386/reason 3 2050 674722 /var/lib/yum/yumdb/m/32e21aae1e2eacc09a131e24022d0505399a3029-maxima-5.30.0-1-i386/releasever 3 2050 674723 /var/lib/yum/yumdb/m/32e21aae1e2eacc09a131e24022d0505399a3029-maxima-5.30.0-1-i386/command_line 6 2050 674725 /var/lib/yum/yumdb/m/32e21aae1e2eacc09a131e24022d0505399a3029-maxima-5.30.0-1-i386/from_repo_revision 3 2050 674726 /var/lib/yum/yumdb/m/32e21aae1e2eacc09a131e24022d0505399a3029-maxima-5.30.0-1-i386/installed_by 2 2050 674829 /var/lib/yum/yumdb/l/0e64afa12db909d75113daa05d5184bbd6df720e-libgdiplus0-debuginfo-2.6.7-0-i686/reason 2 2050 674830 /var/lib/yum/yumdb/l/0e64afa12db909d75113daa05d5184bbd6df720e-libgdiplus0-debuginfo-2.6.7-0-i686/releasever 2 2050 674831 /var/lib/yum/yumdb/l/0e64afa12db909d75113daa05d5184bbd6df720e-libgdiplus0-debuginfo-2.6.7-0-i686/command_line 2 2050 674834 /var/lib/yum/yumdb/l/0e64afa12db909d75113daa05d5184bbd6df720e-libgdiplus0-debuginfo-2.6.7-0-i686/installed_by 3 2050 674848 /var/lib/yum/yumdb/l/0e64afa12db909d75113daa05d5184bbd6df720e-libgdiplus0-debuginfo-2.6.7-0-i686/from_repo_revision 2 2050 674859 /var/lib/yum/yumdb/r/963fdbbd04f6f92d115457eeda885c1922cea350-rsyslog-5.8.10-10.el6_6-i686/from_repo_revision 2 2050 674861 /var/lib/yum/yumdb/r/865d7b4cf2b4a6d5df7d85d1cd9fb17dcaf813ab-rsyslog-4.6.2-3.el6-i686/from_repo_revision 2 2050 674908 /var/lib/yum/yumdb/r/ca156db33ce3d24a0f6ff43a018d16d21f4bf927-rsyslog-pgsql-4.6.2-3.el6-i686/from_repo_revision 2 2050 674919 /var/lib/yum/yumdb/p/c8cf57eb1d5bb11d98418e84b7c8b81f9c53b302-postgresql92-devel-9.2.13-1PGDG.rhel6-i686/from_repo_revision 3 2050 674943 /var/lib/yum/yumdb/a/136d85e53eba5dbacc4f1050ec26af1cb1976c05-azores-stepper-10.13.0-1.el6-i686/installed_by 2 2050 674958 /var/lib/yum/yumdb/e/c081bf3f386d737c4e04bbef9885d1f221fa6b1f-epel-release-6-8-noarch/releasever 2 2050 674961 /var/lib/yum/yumdb/e/c081bf3f386d737c4e04bbef9885d1f221fa6b1f-epel-release-6-8-noarch/from_repo_revision 11 2050 674980 /var/lib/yum/yumdb/a/136d85e53eba5dbacc4f1050ec26af1cb1976c05-azores-stepper-10.13.0-1.el6-i686/command_line 11 2050 674990 /var/lib/yum/yumdb/a/136d85e53eba5dbacc4f1050ec26af1cb1976c05-azores-stepper-10.13.0-1.el6-i686/from_repo_revision 11 2050 674993 /var/lib/yum/yumdb/a/136d85e53eba5dbacc4f1050ec26af1cb1976c05-azores-stepper-10.13.0-1.el6-i686/from_repo_timestamp 10 2050 675088 /var/lib/yum/yumdb/c/2ec2c1a91d71b164e123833748bbfd174490d9f5-codeblocks-contrib-devel-12.11-1.el6-i686/command_line 2 2050 675089 /var/lib/yum/yumdb/c/2ec2c1a91d71b164e123833748bbfd174490d9f5-codeblocks-contrib-devel-12.11-1.el6-i686/from_repo_revision 10 2050 675091 /var/lib/yum/yumdb/c/2ec2c1a91d71b164e123833748bbfd174490d9f5-codeblocks-contrib-devel-12.11-1.el6-i686/installed_by 2 2050 675100 /var/lib/yum/yumdb/w/8fdbbb7affde7b493f47213b1f2b0439aa53b1ec-wxGTK-media-2.8.12-1.el6-i686/from_repo_revision 2 2050 675102 /var/lib/yum/yumdb/h/2bfce3d5405e8542565926a0ea6101393ea6fc00-hpadu-9.40-12.0-i386/from_repo_revision 2 2050 675104 /var/lib/yum/yumdb/a/084996dd0259b07515e37af8f5d8b90ed1e568a5-alsa-lib-1.0.22-3.el6-i686/changed_by 2 2050 675209 /var/lib/yum/yumdb/V/0830b5b3ee7d1a9fbd413f82797213ab9a2244e4-VirtualBox-4.2-4.2.18_88780_el6-1-i686/from_repo_revision 2 2050 675465 /var/lib/yum/yumdb/g/b4879bf9e9e6ddd06e82bfb8742f0a2b3fc9dd03-graphviz-2.26.0-10.el6-i686/from_repo_revision 7 2050 675523 /var/lib/yum/yumdb/m/2ea545b7a1515f84d2d47778932edaf2bf1ac80e-mindi-busybox-1.21.1-1.rhel6-i386/checksum_type 7 2050 675527 /var/lib/yum/yumdb/m/2ea545b7a1515f84d2d47778932edaf2bf1ac80e-mindi-busybox-1.21.1-1.rhel6-i386/from_repo 5 2050 675528 /var/lib/yum/yumdb/p/2ea629d2b416dfff9149650d23a25c63b09e37c9-perl-MondoRescue-3.2.2-1.rhel6-noarch/reason 7 2050 675529 /var/lib/yum/yumdb/m/2ea545b7a1515f84d2d47778932edaf2bf1ac80e-mindi-busybox-1.21.1-1.rhel6-i386/command_line 7 2050 675531 /var/lib/yum/yumdb/m/2ea545b7a1515f84d2d47778932edaf2bf1ac80e-mindi-busybox-1.21.1-1.rhel6-i386/from_repo_revision 7 2050 675532 /var/lib/yum/yumdb/m/2ea545b7a1515f84d2d47778932edaf2bf1ac80e-mindi-busybox-1.21.1-1.rhel6-i386/from_repo_timestamp 22 2050 675597 /var/lib/yum/yumdb/e/9d21992ada1579835d5ebc4c5834095206cc96bb-expect-5.44.1.15-2.el6-i686/checksum_type 8 2050 676851 /var/lib/yum/yumdb/m/2ea545b7a1515f84d2d47778932edaf2bf1ac80e-mindi-busybox-1.21.1-1.rhel6-i386/changed_by 22 2050 676852 /var/lib/yum/yumdb/e/9d21992ada1579835d5ebc4c5834095206cc96bb-expect-5.44.1.15-2.el6-i686/reason 5 2050 676925 /var/lib/yum/yumdb/g/58747a60b64d5918bb51cf0b08f61ea526e44697-glibc-common-2.12-1.149.el6-i686/checksum_type 22 2050 676939 /var/lib/yum/yumdb/e/9d21992ada1579835d5ebc4c5834095206cc96bb-expect-5.44.1.15-2.el6-i686/releasever 22 2050 676940 /var/lib/yum/yumdb/e/9d21992ada1579835d5ebc4c5834095206cc96bb-expect-5.44.1.15-2.el6-i686/command_line 4 2050 676942 /var/lib/yum/yumdb/l/6758f02425e939788029d0a697a1369cca16ca15-libmonosgen-2_0-devel-2.10.8-0-i686/from_repo_revision 22 2050 676943 /var/lib/yum/yumdb/e/9d21992ada1579835d5ebc4c5834095206cc96bb-expect-5.44.1.15-2.el6-i686/installed_by 2 2050 676950 /var/lib/yum/yumdb/m/0e8652ba278ef64dbf11ba4202647613cdae652e-monodoc-core-2.10.8-0-i686/from_repo_revision 5 2050 676955 /var/lib/yum/yumdb/l/db2bb042bf2ec81fafc41fd29f4c13aa183e3b3e-libmono-2_0-devel-2.10.8-0-i686/from_repo_revision 2 2050 676968 /var/lib/yum/yumdb/m/1856ec125b12939dd2899349b54b33b76277af80-mono-nunit-2.10.8-0-i686/from_repo_revision 2 2050 676969 /var/lib/yum/yumdb/m/1856ec125b12939dd2899349b54b33b76277af80-mono-nunit-2.10.8-0-i686/from_repo_timestamp 4 2050 676978 /var/lib/yum/yumdb/m/3a8039e1e1b0945c0adedeff454cf9507b078922-mono-locale-extras-2.10.8-0-i686/from_repo_revision 2 2050 676982 /var/lib/yum/yumdb/m/6afb06c7fb6dc51ea3d0ed89487f282dd08786ec-mono-winfxcore-2.10.8-0-i686/from_repo_revision 2 2050 676987 /var/lib/yum/yumdb/m/7ba0c3b6b5cb82c752a05f0a3d4bf334ba78c778-mono-data-oracle-2.10.8-0-i686/from_repo_timestamp 4 2050 677016 /var/lib/yum/yumdb/m/2391d205db343537d2a06850e370c607f8f42049-mono-data-2.10.8-0-i686/from_repo_timestamp 2 2050 677020 /var/lib/yum/yumdb/m/2391d205db343537d2a06850e370c607f8f42049-mono-data-2.10.8-0-i686/from_repo_revision 5 2050 677063 /var/lib/yum/yumdb/g/58747a60b64d5918bb51cf0b08f61ea526e44697-glibc-common-2.12-1.149.el6-i686/releasever 5 2050 677064 /var/lib/yum/yumdb/g/58747a60b64d5918bb51cf0b08f61ea526e44697-glibc-common-2.12-1.149.el6-i686/command_line 8 2050 677066 /var/lib/yum/yumdb/g/58747a60b64d5918bb51cf0b08f61ea526e44697-glibc-common-2.12-1.149.el6-i686/from_repo_revision 5 2050 677067 /var/lib/yum/yumdb/g/58747a60b64d5918bb51cf0b08f61ea526e44697-glibc-common-2.12-1.149.el6-i686/changed_by 2 2050 677118 /var/lib/yum/yumdb/g/96105b5c34026798c8b6b09bcc6a74367e0459c3-glibc-2.12-1.149.el6-i686/from_repo_revision 2 2050 677144 /var/lib/yum/yumdb/a/084996dd0259b07515e37af8f5d8b90ed1e568a5-alsa-lib-1.0.22-3.el6-i686/from_repo_revision 2 2050 677177 /var/lib/yum/yumdb/f/8639d589d7d261712f91913de0bb01ff40f50701-flash-plugin-11.2.202.356-release-i386/from_repo_revision 2 2050 677206 /var/lib/yum/yumdb/p/450f3df42ed96b61cd4a19cd06c840193e29a004-pgdg-redhat93-9.3-1-noarch/from_repo_revision 4 2050 677435 /var/lib/yum/yumdb/r/3b4ea305112240efff1cec380950c14c9846b157-rsyslog-pgsql-5.8.10-8.el6-i686/releasever 5 2050 677442 /var/lib/yum/yumdb/r/3b4ea305112240efff1cec380950c14c9846b157-rsyslog-pgsql-5.8.10-8.el6-i686/changed_by 2 2050 677614 /var/lib/yum/yumdb/w/0d307cf66c7c0222cecd2bac8614820f6b8339c5-wine-debuginfo-1.6.1-1.el6-i686/from_repo_revision 846 2050 797947 /var/lib/yum/yumdb/a/03a419bfe569d6e344dd36f853c79da443db1be8-apache-tomcat-apis-0.1-1.el6-noarch/reason 115 2050 799157 /var/lib/yum/yumdb/a/5b903416bffc485120788f63f394293a90b6493e-apr-1.3.9-3.el6_1.2-i686/from_repo 152 2050 799158 /var/lib/yum/yumdb/a/136d85e53eba5dbacc4f1050ec26af1cb1976c05-azores-stepper-10.13.0-1.el6-i686/releasever 115 2050 799159 /var/lib/yum/yumdb/a/5b903416bffc485120788f63f394293a90b6493e-apr-1.3.9-3.el6_1.2-i686/command_line 115 2050 799161 /var/lib/yum/yumdb/a/5b903416bffc485120788f63f394293a90b6493e-apr-1.3.9-3.el6_1.2-i686/from_repo_revision 115 2050 799162 /var/lib/yum/yumdb/a/5b903416bffc485120788f63f394293a90b6493e-apr-1.3.9-3.el6_1.2-i686/from_repo_timestamp 28 2050 799205 /var/lib/yum/yumdb/a/136d85e53eba5dbacc4f1050ec26af1cb1976c05-azores-stepper-10.13.0-1.el6-i686/changed_by 2 2050 799303 /var/lib/yum/yumdb/a/030f78e56969f31a52a3caea30ee0487bb68aec8-autocutsel-0.9.0-1.el6.rf-i686/from_repo_revision 2 2050 799398 /var/lib/yum/yumdb/x/fce2a726144420b7dfd461fa152a772b618a5100-xinput_calibrator-0.7.5-3.el6-i686/from_repo_revision 2 2050 799407 /var/lib/yum/yumdb/e/b48edccc2177d2c50de279aa3eaa88e454a58c76-elotouch-4.0.1-1.el6-i686/from_repo_revision 2 2050 799425 /var/lib/yum/yumdb/x/ecd8cb43b935170df5e09fa17f7fcbd7e948f517-x11vnc-0.9.13-1.el6-i686/from_repo_revision 2 2050 799774 /var/lib/yum/yumdb/g/855cb24cfe57abe69fdd78397848cbf5e1281d51-gconf-editor-2.28.0-3.el6-i686/from_repo_revision 4 2050 801854 /var/lib/yum/yumdb/l/ae01bcacff82ee7abb6b85e90584037c62d20452-libmatchbox-devel-1.9-6.1.el6-i686/reason 4 2050 801855 /var/lib/yum/yumdb/l/ae01bcacff82ee7abb6b85e90584037c62d20452-libmatchbox-devel-1.9-6.1.el6-i686/releasever 4 2050 801856 /var/lib/yum/yumdb/l/ae01bcacff82ee7abb6b85e90584037c62d20452-libmatchbox-devel-1.9-6.1.el6-i686/command_line 4 2050 801857 /var/lib/yum/yumdb/l/ae01bcacff82ee7abb6b85e90584037c62d20452-libmatchbox-devel-1.9-6.1.el6-i686/checksum_type 6 2050 801859 /var/lib/yum/yumdb/l/ae01bcacff82ee7abb6b85e90584037c62d20452-libmatchbox-devel-1.9-6.1.el6-i686/from_repo_revision 4 2050 801860 /var/lib/yum/yumdb/l/ae01bcacff82ee7abb6b85e90584037c62d20452-libmatchbox-devel-1.9-6.1.el6-i686/installed_by 2 2050 801864 /var/lib/yum/yumdb/l/caee971c4eaae2bdf870dcc123bb1d50a521e679-libmatchbox-1.9-6.1.el6-i686/from_repo_revision 11 2050 802117 /var/lib/yum/yumdb/l/59375612f7becc19fced0669c9d11d5cacad51a1-libuuid-2.17.2-12.18.el6-i686/releasever 11 2050 802118 /var/lib/yum/yumdb/l/59375612f7becc19fced0669c9d11d5cacad51a1-libuuid-2.17.2-12.18.el6-i686/command_line 11 2050 802119 /var/lib/yum/yumdb/l/59375612f7becc19fced0669c9d11d5cacad51a1-libuuid-2.17.2-12.18.el6-i686/checksum_type 12 2050 802121 /var/lib/yum/yumdb/l/59375612f7becc19fced0669c9d11d5cacad51a1-libuuid-2.17.2-12.18.el6-i686/from_repo_revision 11 2050 802122 /var/lib/yum/yumdb/l/59375612f7becc19fced0669c9d11d5cacad51a1-libuuid-2.17.2-12.18.el6-i686/changed_by 10 2050 802129 /var/lib/yum/yumdb/o/16a3eb4b9f709be44afc6281651cece64a425b8c-openssl-1.0.1e-42.el6-i686/from_repo_revision 2 2050 805899 /var/lib/yum/yumdb/r/eeb376f92fa5919080a0f2fec36447fdaaacb313-rpmrebuild-2.11-1-noarch/from_repo_revision 4 2050 806426 /var/lib/yum/yumdb/r/3b4ea305112240efff1cec380950c14c9846b157-rsyslog-pgsql-5.8.10-8.el6-i686/command_line 4 2050 806427 /var/lib/yum/yumdb/r/3b4ea305112240efff1cec380950c14c9846b157-rsyslog-pgsql-5.8.10-8.el6-i686/checksum_type 4 2050 806429 /var/lib/yum/yumdb/r/3b4ea305112240efff1cec380950c14c9846b157-rsyslog-pgsql-5.8.10-8.el6-i686/from_repo_revision 4 2050 806433 /var/lib/yum/yumdb/s/2f49130f2a5c38ae30811fbbf3cad61d3cdd32fb-selinux-policy-targeted-3.7.19-154.el6-noarch/from_repo_revision 2 2050 806461 /var/lib/yum/yumdb/t/d024ed7800d06b4d49f7384e40fbd3fd4f00fa69-tg3-3.133d-1-i686/from_repo_revision 33 2050 936200 /var/lib/yum/yumdb/l/4b67c539a75863dbbd70e463c8f49a78882e1dae-libsmbclient-3.6.9-164.el6-i686/releasever 33 2050 936201 /var/lib/yum/yumdb/l/4b67c539a75863dbbd70e463c8f49a78882e1dae-libsmbclient-3.6.9-164.el6-i686/command_line 33 2050 936202 /var/lib/yum/yumdb/l/4b67c539a75863dbbd70e463c8f49a78882e1dae-libsmbclient-3.6.9-164.el6-i686/checksum_type 48 2050 939168 /var/lib/yum/yumdb/o/021df9edd3ecd9ad26d469f139ab7a06c6040502-ooobasis3.3-base-3.3.0-9567-i586/from_repo 48 2050 939169 /var/lib/yum/yumdb/o/021df9edd3ecd9ad26d469f139ab7a06c6040502-ooobasis3.3-base-3.3.0-9567-i586/reason 48 2050 939170 /var/lib/yum/yumdb/o/021df9edd3ecd9ad26d469f139ab7a06c6040502-ooobasis3.3-base-3.3.0-9567-i586/releasever 48 2050 939171 /var/lib/yum/yumdb/o/021df9edd3ecd9ad26d469f139ab7a06c6040502-ooobasis3.3-base-3.3.0-9567-i586/command_line 48 2050 939172 /var/lib/yum/yumdb/o/021df9edd3ecd9ad26d469f139ab7a06c6040502-ooobasis3.3-base-3.3.0-9567-i586/checksum_type 48 2050 939174 /var/lib/yum/yumdb/o/021df9edd3ecd9ad26d469f139ab7a06c6040502-ooobasis3.3-base-3.3.0-9567-i586/from_repo_revision 48 2050 939175 /var/lib/yum/yumdb/o/021df9edd3ecd9ad26d469f139ab7a06c6040502-ooobasis3.3-base-3.3.0-9567-i586/from_repo_timestamp 48 2050 939176 /var/lib/yum/yumdb/o/021df9edd3ecd9ad26d469f139ab7a06c6040502-ooobasis3.3-base-3.3.0-9567-i586/installed_by 2 2050 947545 /var/lib/yum/yumdb/l/7cde2ca1c2519ea3e07d36c8dd5f4a9faf7ad26b-libtdb-1.2.10-1.el6-i686/from_repo_revision 33 2050 947555 /var/lib/yum/yumdb/l/4b67c539a75863dbbd70e463c8f49a78882e1dae-libsmbclient-3.6.9-164.el6-i686/changed_by 2 2050 947559 /var/lib/yum/yumdb/l/dba64858a26f999e23d7310efa51c26abd65eaf3-libtevent-0.9.18-3.el6-i686/from_repo_revision 2 2050 947563 /var/lib/yum/yumdb/s/504b1c3c0747d9b2ada85b7087427cffdfcef917-samba-winbind-3.6.9-164.el6-i686/from_repo_revision 4 2050 947567 /var/lib/yum/yumdb/s/6427b02dc759e2a98100c604d220e814990ea851-samba-common-3.6.9-164.el6-i686/from_repo_revision 3 2050 947577 /var/lib/yum/yumdb/w/277175f9dbbddf85b3f6b89e14e1e9331d67eba1-wine-capi-1.6.1-1.el6-i686/from_repo_timestamp 2 2050 947581 /var/lib/yum/yumdb/w/53fd15fac28e7e967d746778905cc0f6b5146b85-wine-symbol-fonts-1.6.1-1.el6-noarch/from_repo_revision 2 2050 947587 /var/lib/yum/yumdb/w/7684fe9f9dd3d609f7424e6136dfe67bd036054b-wine-courier-fonts-1.6.1-1.el6-noarch/from_repo_timestamp 3 2050 947597 /var/lib/yum/yumdb/w/4c8df9cf7993a05f6792ca4d0b958cecf6bda368-wine-filesystem-1.6.1-1.el6-noarch/from_repo_timestamp 3 2050 947606 /var/lib/yum/yumdb/w/4c8df9cf7993a05f6792ca4d0b958cecf6bda368-wine-filesystem-1.6.1-1.el6-noarch/from_repo_revision 2 2050 947611 /var/lib/yum/yumdb/w/1af314b296dec36dff9bff6187d086dfba6d76ad-wine-pulseaudio-1.6.1-1.el6-i686/from_repo_timestamp 2 2050 947615 /var/lib/yum/yumdb/l/4b67c539a75863dbbd70e463c8f49a78882e1dae-libsmbclient-3.6.9-164.el6-i686/from_repo_revision 2 2050 947619 /var/lib/yum/yumdb/w/c7144eae073d13f62f61ade9b64ba29746bde102-wine-alsa-1.6.1-1.el6-i686/from_repo_timestamp 2 2050 947623 /var/lib/yum/yumdb/l/5821c74fc48112f6ac1776576ac1aba8b117e4ba-libtalloc-2.0.7-2.el6-i686/from_repo_revision 2 2050 947627 /var/lib/yum/yumdb/w/901b72771326da6b5185ca836f63c3c01d246f7a-wine-ms-sans-serif-fonts-1.6.1-1.el6-noarch/from_repo_revision 2 2050 947633 /var/lib/yum/yumdb/w/b82fc99c22ef55ffb291d99b232ff7a80f8c68dc-wine-desktop-1.6.1-1.el6-i686/from_repo_timestamp 2 2050 947637 /var/lib/yum/yumdb/s/076f80658661f0ef75aeb9b1ee4c45c4d7db17f1-samba-winbind-clients-3.6.9-164.el6-i686/from_repo_revision 2 2050 947682 /var/lib/yum/yumdb/w/3f74ab3304c3ff743a00ddfeb94a4bce2f53eb56-wine-system-fonts-1.6.1-1.el6-noarch/from_repo_timestamp 2 2050 947730 /var/lib/yum/yumdb/u/71fd822e504f21fb9ce7b6de4a2f0c60fa7564a1-uuid-1.6.1-10.el6-i686/from_repo_revision }}}" 809 allow mondoarchive to reuse a mindi image previously built mondo 3.2.2 3.3.1 enhancement normal Bruno Cornec new Bruno Cornec 2017-01-06T01:30:03+01:00 2017-01-06T01:30:03+01:00 "The idea is to avoid waiting each time for mindi to run and reuse the image created once with it for further mondoarchive run. That may have an impact on the restore media created so should be looked at closely." 822 kmod needed on opensuse 42.2 mondo 3.2.2 3.3.1 enhancement normal Bruno Cornec new Bruno Cornec 2017-08-02T17:48:40+02:00 2017-08-02T17:49:34+02:00 "In order to use mindi on opensuse 42.2 in a Docker container, the kmod package is needed, but not installed (whereas kmod-compat is installed and refers to a binary /usr/bin/kmod which is then not there). Probably an opensuse-42.2 issue with dependencies of kmod-compat and maybe with the upstream Docker ctn provided. More for reference here than action really." 830 Not able to boot using mondo/mindi mondo 3.2.2 3.3.1 defect normal Bruno Cornec new rachanarao123 2017-10-19T23:55:17+02:00 2018-04-09T14:47:50+02:00 "Hello, I am trying to restore a centos-6 32 bit system using nuke/interactive/expert option. However, system hangs after loading initrd images and I am not able to proceed further. I am able to install and take a backup of system successfully . I tried using mindi.iso images and behaviour is no different! Any help would be appreciated. I have attached mindi and mondo logs as well as screen shot of the error. Thanks and Regards, Rachana" 857 why do we have a mr-stabgrub-me mondo 3.2.2 3.3.1 enhancement normal Bruno Cornec assigned Bruno Cornec 2019-11-18T02:08:09+01:00 2019-11-18T19:45:32+01:00 ... when we have a mr-grub ? 858 format_device is in the wrong source code mondo 3.2.2 3.3.1 defect normal Bruno Cornec new Bruno Cornec 2019-11-18T02:10:27+01:00 2019-11-18T02:10:27+01:00 it's currently in mondo/src/mondorestore/mondo-prep.c and is only used at restore time, so should be moved. 859 fdisk on mageia 7 may asks for confirmation mondo 3.2.2 3.3.1 defect normal Bruno Cornec new Bruno Cornec 2020-01-29T02:06:14+01:00 2020-01-29T02:06:14+01:00 "When using fdisk on mageia 7 and creating new partitions after erasing previous one, fdisk asks for confirmation to erase a pre-existing formatted partition. What is the impact for MondoRescue at restore time ? It is also probably true on other recent distributions. fdisk --version fdisk de util-linux 2.33.2 " 868 provide supoprt for another tool to create backup sets mondo 3.2.2 3.3.1 defect normal Bruno Cornec new Bruno Cornec 2020-08-19T18:00:47+02:00 2020-08-19T18:01:29+02:00 afio and star have been removed from some distros so it would be interesting to provide support for other tools. 202 Backup of partition larger than local tmp and scratch space mondo 2.2.4 4.0.0 enhancement blocker Bruno Cornec assigned antunbalaz 2007-10-14T18:53:10+02:00 2010-09-18T11:30:16+02:00 "Hi, I am using mondorescue for some time without any problems for backups and replication of local linux machines, thank you very much! However, now that the time has come to backup the laptop of my boss, problem appeared :( I think I know what is causing it: I am trying to backup several partitions with the overall data size of approx. 80 GB to an NFS mount, but locally there is just 9 GB for scratch and tmp, and it seems that mondorescue wrongly checks if the partition on which tmp and scratch space are has enough space to store the whole amount of data that is being backed up. Details: laptop has windows NTFS partition of 75 GB, and SuSE linux is installed on the rest of HDD, with 9 GB of empty space on Linux. Backup is done to an NFS mount. If windows partition is not backed up, no problems (i.e. small linux partition can be backed up successfully). If windows partition is included (-x /dev/sda2), I get ""/dev/sda2: no such file"" after I see in the log file that the number of slices is correctly calculated for /dev/sda2. This is misleading message and should be fixed (not enough space is more appropriate, although also not correct). However, if I set scratch (-S) and tmp (-T) directory to be on the NFS mount (the same used for storing the backup iso images), then everything works, since on NFS mount there is enough space (200 GB+), wile on the local disk there is just 9 GB of free space. Of course, this is _very_ slow (15+ hours estimated), and in practice not feasible. Now, I have verified that (with the size of iso images not specified, defaulting to CD size) tmp directory on NFS mount never grows over 150-170 MB, and scratch directory on NFS mount never over 650 MB (of course), which means that local scratch and tmp can be used easily, but for some reason mondorescue fails to realize that and gives up (this happens after backup of linux partitions is finished, at the start of the backup of windows partition as biggiefile). Do you have any ideas how to easily fix this? Versions used: mondo-2.2.4-1.suse10.2.i586.rpm mindi-busybox-1.2.2-3.suse10.2.i586.rpm mindi-1.2.4-1.suse10.2.i586.rpm Thanks, Antun Balaz antun@phy.bg.ac.yu" 183 LVM restore incorrect when cloning mondo 2.2.4 4.0.0 enhancement major Bruno Cornec assigned Bruno Cornec 2007-07-23T12:12:26+02:00 2012-02-24T02:13:19+01:00 "When cloning and using a different HDD, LVM is not restored correctly as there is a need to change i-want-my-lvm on the fly. The only working solution for now is to edit it separately, run all the commands having a '#' at the begining, and relaunch mondorestore, without partitioning the disk. 2 potential ideas: 1/ propose to edit i-want-my-lvm (short term) 2/ automatically change the value for the disk, if it is changed by the user." 231 mondorescue: Storage Dir form input limited to 51 characters mondo 2.2.4 4.0.0 defect minor Bruno Cornec assigned bparnell 2008-01-11T17:00:03+01:00 2008-05-31T20:11:48+02:00 "In the mondorestore application under the ""Storage Dir"" form, the text entry for inputting the path to your ISO files seems to be limited to 51 characters. This is arrived via the following: Run mondorestore select OK Select ""Hard disk"" The form with the information: Storage dir. Please enter the full path name to the directory for your ISO images. Example: /mnt/raid0_0 is presented to the user, in the text input box I try to add a path greater than 51 characters and am not able to do so, The path gets truncated. This is with version 2.2.4. Best Regards, Bill" 67 mondoarchive should have an option to select NIC mondo 2.0.9 4.0.0 enhancement normal Bruno Cornec new Bruno Cornec 2006-09-22T18:15:56+02:00 2007-05-07T22:14:48+02:00 When doing archiving through the network, mondoarchive takes the first interface available. It should have an option to take the interface as a parameter. 94 Show Command Assembled in GUI mondo 2.2.0 4.0.0 enhancement normal Bruno Cornec new CAOgdin 2006-10-31T15:47:12+01:00 2007-03-19T01:03:32+01:00 "When one goes through the GUI and configures a backup, it sure would be nice if the mondoarchive command that has been assembled for execution (and, perhaps, the mondorecover command that could be used to restore) would be available to be saved in a file for future use. Perhaps this could be done by offering the user the option to save the command(s), and letting the user name the path&file where they will be saved? --Carol Anne" 152 Bootable USB that backs up to DVDs mindi 2.2.1 4.0.0 enhancement normal Bruno Cornec assigned vogelap 2007-04-16T17:14:19+02:00 2007-09-08T10:20:01+02:00 "I am requesting the following enhancements to Mondo/Mindi: A live CD (or other method of creating this) that would scan the system for necessary drivers and such to create a custom, bootable USB disk with the necessary drivers for the DVD burner, etc. The USB disk would contain a backup-to-DVD solution that created a backup and burned bootable DVDs (DVDs just like Mondo's current DVD backups). Just to be clear: I do '''not''' want to back up files to the USB drive -- I want to '''BOOT''' from the USB and burn backups to DVDs." 198 Wrong ext3 block size after restore mondo 2.2.4 4.0.0 defect normal Bruno Cornec assigned tboerkel 2007-09-24T17:22:58+02:00 2008-12-08T10:26:14+01:00 "When I restore a backup to a new hard disk and let Mondo do the partioning and formatting, it uses 1024 as ext3 block size, but the original hard disk had 4096." 213 XFS volumes with external log could not be mounted during restore mondo 2.2.0 4.0.0 defect normal Bruno Cornec assigned gekkoo 2007-11-11T19:27:16+01:00 2008-05-31T20:00:51+02:00 "As requested by Bruno in his reply to my posting in the Mondo mailing list with the same subject I fill a new ticket here: On my Debian system I run some lvm volumes with xfs filesystem and external logging. As I tried as a first step to compare the backup using the created CD image, Mondo Restore stoped because it could not mount the volumes which uses the external logging. The log-file shows, that Mondo tries to mount the volumes without the option for the external log. I schould attach the logfiles here but I don't find the option to do so in the moment. Hope I can attach them later... Greats Harald" 230 allow exclusion of files mondo 2.2.4 4.0.0 defect normal Bruno Cornec assigned Bruno Cornec 2008-01-09T00:16:33+01:00 2008-05-31T20:11:19+02:00 When dealing with very large files useless in a backup (aka a 22GB swap file e.g.) allow for their exclusion with -E or something similar. 267 UIDs / GIDs not enough bits mondo 2.2.5 4.0.0 defect normal Bruno Cornec assigned jwhit424 2008-06-26T22:58:09+02:00 2009-02-04T22:19:54+01:00 "user with uid 98765 becomes user 33229 after mondo restore. 98765 - 33229 = 65536. Integer Overflow. This is on RedHat 5 (32 bit) on VMware ESX 3.0.2. with mindi 2.0.1." 272 mondo should support other type of NICs mondo 2.2.6 4.0.0 defect normal Bruno Cornec assigned Bruno Cornec 2008-07-30T06:35:05+02:00 2008-10-03T02:07:52+02:00 mondo should support other type of NICs such as xenbrxx, vlanxx, ... 403 mondo ignore non system partitions mondo 2.2.9.2 4.0.0 defect normal Bruno Cornec assigned Chucky 2010-03-11T16:15:58+01:00 2011-08-22T12:02:30+02:00 "Hello, I have system, which contains non standard filesystem partitions (informix data parts). Mondo can't backup them (ofcourse), he ignores them. When I want to clone system, he don't know about these partitions and I have to make them by hand. When cloning multiple machines, it is annoying. I resolved this by saving (sfdisk -d) for all drives in system, and in modified post-init, if they didn't match current setup, I ask to repartition them. I wish mondo can parttion them in the same fashion. Moreover, it is philosophical that mondo should include two basic modes: restore to original system and clone system. In restore original, the system ramdisk & bootup process could be used to ensure correct module & device initialization, repartition drives to same configuration with NO questions :). In clone mode, there could be that nice features like inserting all modules, mountlist resizing and checking, many questions etc. Thanks running OpenSuse 11.1 & 11.2 64" 619 Improve cloning support mondo 3.0.1 4.0.0 enhancement normal Bruno Cornec new Bruno Cornec 2012-05-22T17:31:42+02:00 2014-04-03T00:22:53+02:00 When cloning with !MondoRescue, a change of disk from hda to sda e.g. lead to grub not installaing itself in the chroot, as the devices files are not there. They need to be copied from the / into the chroot.. Maybe udev can help ? 695 Mondo does not seem to support drbd mondo 3.0.3 4.0.0 enhancement normal Bruno Cornec assigned TJB 2013-06-04T16:38:42+02:00 2017-06-07T02:50:48+02:00 "Hi All, I have backed up a server running drbd and restored it to another server with the same hard disk configuration. When I try to look at the restored drbd partition using drbdadm role r0 I get the error message Unconfigured. When I try to check my replica mount, I see that /dev/drbd0 is not mounted and the mount point is now a folder on /dev/mapper/VolGroup00-LogVol00. I am running mondo V3.0.3-r3091. Any ideas on how to fix this most gratefully received. " 758 partial scratch dirs usage for USB media mondo 3.0.4 4.0.0 enhancement normal Bruno Cornec new Bruno Cornec 2014-10-31T12:30:16+01:00 2014-12-24T06:30:11+01:00 "When using a RW media such as a USB disk/key, mondoarchive could make a better usage of the scratch dir by making partial copies after a certain size, to avoid needing huge scratch dir sizes when using a large USB device. E;G.. a very large scrath dir is needed for a 128 GB USB disk." 810 Look at mbuffer instea of buffer mondo 3.2.2 4.0.0 enhancement normal Bruno Cornec new Bruno Cornec 2017-03-08T16:48:38+01:00 2017-03-08T16:48:38+01:00 69 mondoarchive NFS does not work with zeroconf installed mondo 2.0.9 4.0.2 defect normal Bruno Cornec assigned andree 2006-09-24T02:57:21+02:00 2009-09-26T17:31:12+02:00 "zeroconf (www.zeroconf.org) apparently adds an IP address from the 169.254.0.0/16 range to an interface. So, with zeroconf installed I get the following outout from 'ip addr': {{{ 1: lo: mtu 16436 qdisc noqueue link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo inet6 ::1/128 scope host valid_lft forever preferred_lft forever 2: eth0: mtu 1500 qdisc pfifo_fast qlen 1000 link/ether 00:11:d8:50:e0:80 brd ff:ff:ff:ff:ff:ff inet 169.254.134.104/16 brd 169.254.255.255 scope link eth0 inet 192.168.1.213/24 brd 192.168.1.255 scope global eth0 inet6 fe80::211:d8ff:fe50:e080/64 scope link valid_lft forever preferred_lft forever 3: eth1: mtu 1500 qdisc noop qlen 1000 link/ieee1394 00:e0:18:00:00:ce:cf:54 brd ff:ff:ff:ff:ff:ff:ff:ff 4: sit0: mtu 1480 qdisc noop link/sit 0.0.0.0 brd 0.0.0.0 }}} The interesting one here is 2: The 192.168.1.213 address is what is configured as a static address. 169.254.134.104 is what zeroconf adds. Networking in general works fine with this. However, mondoarchive uses ifconfig to obtain the IP address for the NFS config. 'ifconfig' gives: {{{ eth0 Link encap:Ethernet HWaddr 00:11:D8:50:E0:80 inet addr:169.254.134.104 Bcast:169.254.255.255 Mask:255.255.0.0 inet6 addr: fe80::211:d8ff:fe50:e080/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:13785 errors:0 dropped:0 overruns:0 frame:0 TX packets:10514 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:17528791 (16.7 MiB) TX bytes:977510 (954.5 KiB) Interrupt:177 lo Link encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 inet6 addr: ::1/128 Scope:Host UP LOOPBACK RUNNING MTU:16436 Metric:1 RX packets:358 errors:0 dropped:0 overruns:0 frame:0 TX packets:358 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:20284 (19.8 KiB) TX bytes:20284 (19.8 KiB) }}} which means it only gives the IP address configured by zeroconf. And that address is what is using during restore and of course doesn't work. I am not 100% sure what to do here but don't think it is super urgent. I mainly wanted it documented somewhere - maybe we should also put it in the wiki ? One interesting comment I saw is that apparently ifconfig is getting superseded by the ip command. Maybe we need at some stage replace ifconfig with ip. Cheers, Andree" 83 Create a package hierarchy to ease installation mondo 2.2.0 4.0.2 defect normal Bruno Cornec assigned Bruno Cornec 2006-10-12T16:03:15+02:00 2007-07-19T01:57:18+02:00 "Create new packages to help deploy mondo. Cf DistributionPackaging" 91 Error message goes to console, but not to log mondo 2.2.0 4.0.2 defect normal Bruno Cornec assigned CAOgdin 2006-10-28T20:18:39+02:00 2009-09-26T17:47:04+02:00 "During diagnosis of a different problem, I was presented with an on-screen (console) message reading, in part... > sh: -c: line 0: syntax error near unexpected token `(' > sh: -c: line 0: `mkisofs -no-emul-boot -b isolinux.bin -boot-load-size > 4 -boot-info-table -c boot.cat -o /backup//Mondo- (test) > -Birch-061025@2031-1.iso -J -r -p MondoRescue -publisher > www.mondorescue.org -A Mondo_Rescue_GPL -V 1 . >> > /var/log/mondo-archive.log 2>> /var/log/mondo-archive.log' > Call to mkisofs to make ISO (ISO #1) ...failed > ---promptdialogYN---1--- Failed to burn ISO #1. Retry? However, these error messages didn't appear in the log. When I submitted the information to the mondo-devel list, I included both the (compressed) lot, and this snapshot of the screen (above). It might be useful to make sure all error messages are echoed to the log, so sending you that log would be adequate for your further investigation." 98 continue even if wrong media inserted mondo 2.2.0 4.0.2 enhancement normal Bruno Cornec new Bruno Cornec 2006-11-01T18:43:17+01:00 2009-09-26T17:31:51+02:00 If you put a wrong media number in, mondo-restore should ask for the ight one instead of failling (Waiting for log for more details). 116 Encryption support mondo 2.2.0 4.0.2 enhancement normal Bruno Cornec new Bruno Cornec 2006-12-20T21:57:12+01:00 2009-11-10T14:23:00+01:00 "It would be very handy, if mondo could encrypt the backup with a password and ask for it during restore/compare." 118 In compare mode allow mountlist changes before operation mondo 2.2.1 4.0.2 enhancement normal Bruno Cornec assigned eboniface 2006-12-29T19:44:16+01:00 2009-09-26T17:33:05+02:00 "During the compare operation, mondorescue only uses the mountlist from the source system. If the target system does not have the same mountlist, compare will failed. The proposal is to add an interactive mode to change the mountlist before doing the compare operation." 122 Build a FreeBSD version mondo 2.2.1 4.0.2 enhancement normal Bruno Cornec new Bruno Cornec 2007-01-02T14:09:26+01:00 2008-05-31T14:11:46+02:00 Build a 5.5 FreeBSD version 139 Option in a restore from differencial (-D) backup to remove files deleted following full backup mondo 2.2.1 4.0.2 enhancement normal Bruno Cornec new mread 2007-02-26T23:59:06+01:00 2009-09-26T17:33:55+02:00 "Please include an enhancement to the restore function to remove restored files deleted from the original media between reference ""full backup"" and corresponding ""differential backup (-D)"". After a few restores from a ""differential"" and ""full"" backup set, one can end up with a whole bunch of previously deleted material that takes up increasing amounts of space. I realise this adds to the complexity of the ""differential"" process, probably requiring a comparison between file system and files backed up in the reference ""full"" backup and a listing of differences - rather than simply backing up all files with a modification date after the ""full"" backup, but it would improve the functionality of the ""differential"" backup/restore process hugely. Thanks." 171 "use ""say"" in sys|isolinux.cfg files" mondo 2.2.3 4.0.2 enhancement normal Bruno Cornec new Bruno Cornec 2007-06-08T14:47:43+02:00 2007-06-08T14:47:43+02:00 Cf http://syslinux.zytor.com/faq.php 196 Parallel BZip2 for SMP faster backups mondo 2.2.4 4.0.2 enhancement normal Bruno Cornec new lcg 2007-09-11T14:04:59+02:00 2007-09-15T20:39:04+02:00 "Hi all. I'm using Mondo in some Dual Xeon with Quad Core (total 8 CPU's) and I have just discovered a parallel version of BZIP2. The results are, obviously, spectacular compared with using the original bzip2 :) See PBZIP2 at http://compression.ca/pbzip2/ I think it would be good if there were some way to change the path or command used to call bzip2, so we can use pbzip2 instead of bzip2. Thank you very much for considering it, and congratulations for your work! Leo.-" 378 making mondo archives from a live USB mondo 2.2.9.1 4.0.2 defect normal Bruno Cornec assigned irfank 2010-01-02T07:25:11+01:00 2010-01-21T17:50:14+01:00 "I'm having troubles running Mondoarchive and Mindi on Ubuntu 9.10 64-bit using either versions from the repositories or versions from the website. I gather I could recompile a kernel to get it running, as I keep getting a FATAL ERROR: Libata module not found message. I suppose I could also find a version of the mindi-kernel to try to use the failsafe kernel, but it's not readily available without a lot of digging and searching. Right now, I'm figuring that it might just be easier to install a different, earlier version of Ubuntu on a separate partition, for the sole purpose of making mondoarchives. I can't see why this won't work. But it occurred to me that it might be possible to make a live USB Mondo Rescue linux version, which would allow people with insane kernels to make backups readily. I searched around through versions of DSL and others to see if this was something that had been done before, but couldn't find anything. Can anyone see any major problems with this approach? I'm a relative newbie with big gaps in my general knowledge, although not scared of reading howtos or using the command line if that seems the easiest way to do something. Thanks for any input that anyone can provide." 380 mondorestore should support a response file mondo 2.2.9.1 4.0.2 enhancement normal Bruno Cornec new Bruno Cornec 2010-01-07T13:01:04+01:00 2010-02-09T02:19:25+01:00 Having a response file for mondorestore could help automate every restoration layout automatically, whatever the user want to do. should be coupled with option -H at backup time. 613 Update user interface mondo 3.0.1 4.0.2 enhancement normal Bruno Cornec new bilyo 2012-04-15T00:54:39+02:00 2012-04-16T10:56:58+02:00 "Make user interface more user friendly, especially for non-tech users. A menu driven, point and click interface will give Mondorescue a modern appearance and functionality similar to other popular apps. It should have the ability to start from the ""Applications"" list or desktop in addition to the command line." 635 To check grub after mondorestore, add to mondorescue this shell-script mondo 3.0.2 4.0.2 enhancement normal Bruno Cornec new victor gattegno 2012-07-20T13:08:26+02:00 2016-04-11T15:47:01+02:00 "After mondorestore, in order to be able to check grub before rebooting, I recommend to add to mondorescue backup the shell-script [http://bootinfoscript.sourceforge.net bootinfoscript] and the GNU/Linux executables used by that script: fold, hexdump, blkid, filefrag... Line 303 and 327 of bootinfoscript shell-script are listed the executables used by it. " 125 Add option for suppress of evalcall and progress-form mondo 2.0.9 enhancement minor Bruno Cornec assigned andreas1234567@… 2007-01-09T10:27:50+01:00 2013-12-19T18:26:54+01:00 "I'm running mondoarchive from cron. The output from cron is sent as email to the local root account. This size of this output is often ''larger than 1MB'' due to a large number of lines starting with ""---evalcall---"" or ""---progress-form---"". I suggest the addition of an option that suppresses these messages (i.e. 'non-interactive mode'). {{{ # /usr/sbin/mondoarchive --version mondoarchive v2.0.9-780 $ uname -a Linux mylinux 2.6.9-42.0.3.EL # 1 Fri Oct 6 05:59:54 CDT 2006 i686 i686 i386 GNU/Linux }}} Thanks for the great software Bruno. Best regards, Andreas -- " 232 Owner of symbolic links is not restored correctly. mondo 2.2.4 defect normal Bruno Cornec assigned enakai 2008-01-17T08:52:23+01:00 2013-12-19T18:26:54+01:00 "I have restored RHEL5.1 with mondo-2.2.4-1.rhel5 and compared ""rpm -Va"" results taken before and after the restoration. And I found that ower user and group of symbolic links originally different from root.root was changed to root.root. {{{ # diff node01.2008011663155/rpm-Va node01.2008011684617/rpm-Va 1218a1219,1225 > .....UG. /usr/bin/rpmdb > .....UG. /usr/bin/rpmquery > .....UG. /usr/bin/rpmsign > .....UG. /usr/bin/rpmverify > .....UG. /usr/lib/rpm/rpme > .....UG. /usr/lib/rpm/rpmu > .....UG. /usr/lib/rpm/rpmv }}} These are all symbolic links to another file, for example; {{{ # ls -l /usr/bin/rpmdb lrwxrwxrwx 1 rpm rpm 15 Jan 16 17:29 /usr/bin/rpmdb -> ../lib/rpm/rpmd # ls -l /usr/bin/rpmdb lrwxrwxrwx 1 root root 15 Jan 16 17:29 /usr/bin/rpmdb -> ../lib/rpm/rpmd }}} As owners of linked ""real"" files were not modified, there's probably no practical issue. But I think, if possible, it's better to fix it. (Sorry for that I have no idea how to fix it.) RPMs I used are as below; {{{ afio-2.4.7-1.x86_64.rpm buffer-1.19-1.x86_64.rpm mindi-1.2.4-1.rhel5.x86_64.rpm mindi-busybox-1.2.2-3.rhel5.x86_64.rpm mondo-2.2.4-1.rhel5.x86_64.rpm }}} " 482 -V switching to verify timing issue mondo 2.2.9.6 3.0.5 defect minor Bruno Cornec assigned jsoff 2011-06-17T17:24:57+02:00 2012-06-05T00:07:58+02:00 "When I run mondoarchive using -V (verify) mondo asks for device /dev when switching from making the DVD to verifying the DVD. During the start of the verify mondo asks for the /dev. If I answer the /dev prompt immediately mondo then asks to abort the backup. But if I wait till the dvd activity stops then enter /dev/sr0 the verify proceeds and the mondoarchive with verify succeeds. log attached " 678 mondoarchive -x option with a few NTFS partitions mondo 3.0.3 3.0.5 enhancement minor Bruno Cornec new victor gattegno 2013-04-15T22:18:00+02:00 2013-04-15T22:18:50+02:00 "If there are some NTFS partitions to backup, should we use -x option this way ? {{{ -x ""/dev/sda1 /dev/sda2"" }}} As I see in /usr/sbin/mindi, line 3179 : {{{ IMAGE_DEVS=""`echo ""${10}"" | tr '|' ' '`"" }}} I think that we should rather use : {{{ -x ""/dev/sda1|/dev/sda2"" }}} Am I right ? That should be documented, i can do it after I get configmraion from you Bruno. " 387 Backup with SELINUX=permissive may result to restore errors due to /proc & /sys extended attributes mondo 2.2.9.1 3.0.5 defect normal Bruno Cornec assigned kritzenthaler 2010-01-20T11:26:19+01:00 2013-07-28T21:27:22+02:00 "[[BR]] This defect was observed on 2.2.9.2 (RHEL5.4). It should be the same on other distro though. The following errors are encountered when trying to restore the backup:[[BR]] {{{ setfattr: proc: Operation not supported setfattr: sys: Operation not supported }}} Due to that, the GUI restore phase does not seem to finalize properly for a lambda end-user (even if it may have no other impacts). It has been observed in the filelist-7 that /proc and /sys were backed-up with the following xattr:[[BR]] {{{ # file: proc security.selinux=0x73797374656d5f753a6f626a6563745f723a70726f635f743a733000 === # file: sys security.selinux=0x73797374656d5f753a6f626a6563745f723a73797366735f743a733000 }}} Even if /proc and /sys sub-files/sub-dirs are not backed-up, we should also fully remove /proc and /sys from the backup. I guess removing it from the backup would avoid that kind of issue at restore time. Note that the WA to set -E ""/proc /sys"" to exclude them did not work for me. " 489 Too many | generated when using an exclude list mondo 2.2.9.7 3.0.5 defect normal Bruno Cornec new Bruno Cornec 2011-06-30T08:46:12+02:00 2012-06-05T00:13:49+02:00 "{{{ [Main] libmondo-cli.c->process_switches#647: Finished with the -E option [Main] libmondo-cli.c->process_switches#666: -N means we're now excluding |/C3S_Deliveries|/mnt|/root/mondoISO|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||/dbora/oradata/C3S/SYS|/dbora/oradata/C3S/REDO|/dbora/oradata/C3S/INDEX|/dbora/oradata/C3S/DATA|/dbora/admin|/dbora/flash_recovery_area|/oracle/c3s_utl_dir|/oracle/product/10.2/dbs|/oracle/product/10.2/network/admin|/dbora/oradata/C3S/DATA/AVR|/oracle/BI_10.1.2/network/admin|/oracle/BI_10.1.2/Apache/Apache/conf|/home/c3s|/usr/local/jboss|/home/c3s/C3S_AVR| [...] [Main] libmondo-cli.c->handle_incoming_parameters#100: Switches:- [Main] libmondo-cli.c->handle_incoming_parameters#104: -5 [Main] libmondo-cli.c->handle_incoming_parameters#104: -E /C3S_Deliveries|/mnt|/root/mondoISO|/dev/dm-10|/dev/dm-11|/dev/dm-12|/dev/dm-13|/dev/dm-14|/dev/dm-15|/dev/dm-16|/dev/dm-17|/dev/dm-18|/dev/dm-19|/dev/dm-2|/dev/dm-20|/dev/dm-21|/dev/dm-22|/dev/dm-23|/dev/dm-24|/dev/dm-25|/dev/dm-26|/dev/dm-27|/dev/dm-28|/dev/dm-29|/dev/dm-3|/dev/dm-30|/dev/dm-31|/dev/dm-32|/dev/dm-33|/dev/dm-34|/dev/dm-35|/dev/dm-36|/dev/dm-37|/dev/dm-38|/dev/dm-39|/dev/dm-4|/dev/dm-40|/dev/dm-41|/dev/dm-42|/dev/dm-43|/dev/dm-44|/dev/dm-45|/dev/dm-46|/dev/dm-47|/dev/dm-48|/dev/dm-49|/dev/dm-5|/dev/dm-50|/dev/dm-51|/dev/dm-52|/dev/dm-53|/dev/dm-54|/dev/dm-55|/dev/dm-56|/dev/dm-57|/dev/dm-58|/dev/dm-59|/dev/dm-6|/dev/dm-60|/dev/dm-61|/dev/dm-62|/dev/dm-63|/dev/dm-64|/dev/dm-65|/dev/dm-66|/dev/dm-67|/dev/dm-68|/dev/dm-69|/dev/dm-7|/dev/dm-70|/dev/dm-71|/dev/dm-72|/dev/dm-73|/dev/dm-74|/dev/dm-75|/dev/dm-76|/dev/dm-77|/dev/dm-78|/dev/dm-79|/dev/dm-8|/dev/dm-80|/dev/dm-81|/dev/dm-9|/dev/mapper/mpath8|/dev/mapper/mpath9|/dev/mapper/mpath10|/dev/mapper/mpath11|/dev/mapper/mpath12|/dev/mapper/mpath13|/dev/mapper/mpath14|/dev/mapper/mpath15|/dev/mapper/mpath16|/dev/mapper/mpath17|/dev/mapper/mpath0|/dev/mapper/mpath18|/dev/mapper/mpath19|/dev/mapper/mpath20|/dev/mapper/mpath21|/dev/mapper/mpath22|/dev/mapper/mpath23|/dev/mapper/mpath24|/dev/mapper/mpath25|/dev/mapper/mpath26|/dev/mapper/mpath27|/dev/mapper/mpath1|/dev/mapper/mpath28|/dev/mapper/mpath29|/dev/mapper/mpath30|/dev/mapper/mpath31|/dev/mapper/mpath32|/dev/mapper/mpath33|/dev/mapper/mpath34|/dev/mapper/mpath35|/dev/mapper/mpath36|/dev/mapper/mpath37|/dev/mapper/mpath2|/dev/mapper/mpath38|/dev/mapper/mpath39|/dev/mapper/mpath40|/dev/mapper/mpath41|/dev/mapper/mpath42|/dev/mapper/mpath43|/dev/mapper/mpath44|/dev/mapper/mpath45|/dev/mapper/mpath46|/dev/mapper/mpath47|/dev/mapper/mpath3|/dev/mapper/mpath48|/dev/mapper/mpath49|/dev/mapper/mpath50|/dev/mapper/mpath51|/dev/mapper/mpath52|/dev/mapper/mpath53|/dev/mapper/mpath54|/dev/mapper/mpath55|/dev/mapper/mpath56|/dev/mapper/mpath57|/dev/mapper/mpath4|/dev/mapper/mpath58|/dev/mapper/mpath59|/dev/mapper/mpath60|/dev/mapper/mpath61|/dev/mapper/mpath62|/dev/mapper/mpath63|/dev/mapper/mpath64|/dev/mapper/mpath65|/dev/mapper/mpath66|/dev/mapper/mpath67|/dev/mapper/mpath5|/dev/mapper/mpath68|/dev/mapper/mpath69|/dev/mapper/mpath70|/dev/mapper/mpath71|/dev/mapper/mpath72|/dev/mapper/mpath73|/dev/mapper/mpath74|/dev/mapper/mpath75|/dev/mapper/mpath76|/dev/mapper/mpath77|/dev/mapper/mpath6|/dev/mapper/mpath78|/dev/mapper/mpath79|/dev/mapper/mpath7|/dbora/oradata/C3S/SYS|/dbora/oradata/C3S/REDO|/dbora/oradata/C3S/INDEX|/dbora/oradata/C3S/DATA|/dbora/admin|/dbora/flash_recovery_area|/oracle/c3s_utl_dir|/oracle/product/10.2/dbs|/oracle/product/10.2/network/admin|/dbora/oradata/C3S/DATA/AVR|/oracle/BI_10.1.2/network/admin|/oracle/BI_10.1.2/Apache/Apache/conf|/home/c3s|/usr/local/jboss|/home/c3s/C3S_AVR [Main] libmondo-cli.c->handle_incoming_parameters#104: -G 3|/dev/mapper/mpath14|/dev/mapper/mpath15|/dev/mapper/mpath16|/dev/mapper/mpath17|/dev/mapper/mpath0|/dev/mapper/mpath18|/dev/mapper/mpath19|/dev/mapper/mpath20|/dev/mapper/mpath21|/dev/mapper/mpath22|/dev/mapper/mpath23|/dev/mapper/mpath24|/dev/mapper/mpath25|/dev/mapper/mpath26|/dev/mapper/mpath27|/dev/mapper/mpath1|/dev/mapper/mpath28|/dev/mapper/mpath29|/dev/mapper/mpath30|/dev/mapper/mpath31|/dev/mapper/mpath32|/dev/mapper/mpath33|/dev/mapper/mpath34|/dev/mapper/mpath35|/dev/mapper/mpath36|/dev/mapper/mpath37|/dev/mapper/mpath2|/dev/mapper/mpath38|/dev/mapper/mpath39|/dev/mapper/mpath40|/dev/mapper/mpath41|/dev/mapper/mpath42|/dev/mapper/mpath43|/dev/mapper/mpath44|/dev/mapper/mpath45|/dev/mapper/mpath46|/dev/mapper/mpath47|/dev/mapper/mpath3|/dev/mapper/mpath48|/dev/mapper/mpath49|/dev/mapper/mpath50|/dev/mapper/mpath51|/dev/mapper/mpath52|/dev/mapper/mpath53|/dev/mapper/mpath54|/dev/mapper/mpath55|/dev/mapper/mpath56|/dev/mapper/mpath57|/dev/mapper/mpath4|/dev/mapper/mpath58|/dev/mapper/mpath59|/dev/mapper/mpath60|/dev/mapper/mpath61|/dev/mapper/mpath62|/dev/mapper/mpath63|/dev/mapper/mpath64|/dev/mapper/mpath65|/dev/mapper/mpath66|/dev/mapper/mpath67|/dev/mapper/mpath5|/dev/mapper/mpath68|/dev/mapper/mpath69|/dev/mapper/mpath70|/dev/mapper/mpath71|/dev/mapper/mpath72|/dev/mapper/mpath73|/dev/mapper/mpath74|/dev/mapper/mpath75|/dev/mapper/mpath76|/dev/mapper/mpath77|/dev/mapper/mpath6|/dev/mapper/mpath78|/dev/mapper/mpath79|/dev/mapper/mpath7|/dbora/oradata/C3S/SYS|/dbora/oradata/C3S/REDO|/dbora/oradata/C3S/INDEX|/dbora/oradata/C3S/DATA|/dbora/admin|/dbora/flash_recovery_area|/oracle/c3s_utl_dir|/oracle/product/10.2/dbs|/oracle/product/10.2/network/admin|/dbora/oradata/C3S/DATA/AVR|/oracle/BI_10.1.2/network/admin|/oracle/BI_10.1.2/Apache/Apache/conf|/home/c3s|/usr/local/jboss|/home/c3s/C3S_AVR [Main] libmondo-cli.c->handle_incoming_parameters#104: -N [Main] libmondo-cli.c->handle_incoming_parameters#104: -O [Main] libmondo-cli.c->handle_incoming_parameters#104: -T /tmp [Main] libmondo-cli.c->handle_incoming_parameters#104: -d /dev/st0 [Main] libmondo-cli.c->handle_incoming_parameters#104: -o [Main] libmondo-cli.c->handle_incoming_parameters#104: -t [...] }}} Also look at what happens with -G" 648 Additional Control Over Boot in Mindi Configuration mindi 3.0.2 3.0.5 enhancement trivial Bruno Cornec assigned Matthew Ross 2012-10-17T23:34:19+02:00 2012-10-23T20:27:53+02:00 "I have run into a scenario where it would be useful to have a little more control over how recovery media boots. In particular, the boot loader timeout and default boot option. For my purposes, it would be useful to have restoration media timeout quickly and boot into expert mode as a default. Once booted the user will be able to select backups from library disk to restore from via a script (that eventually call on mondorestore). Using mindi versus mondo would be an option to get expert working as the default but it would require that I handle the generation of CD/DVD media externally, something which mondo does nicely already. The changes required to implement this are minimal. Establish globals prior sourcing mindi.conf: {{{ MINDI_ADDITIONAL_BOOT_PARAMS=""..."" MINDI_DEFAULT_BOOT_OPTION="""" MINDI_BOOT_TIMEOUT="""" }}} in MakeBootConfFile, handle the mindi.conf default option and timeout for mondoarchive non-CDRECOVERY only: {{{ MakeBootConfFile() { ... # Compute which default option to boot from ... elif [ _""$MONDO_SHARE"" != _"""" ]; then if [ -e ""$MINDI_TMP/NETFS-DEV"" ]; then echo -en ""default${sep}iso\n"" elif [ ""$MINDI_DEFAULT_BOOT_OPTION"" != """" ]; then LogIt ""Overriding default boot option: $MINDI_DEFAULT_BOOT_OPTION"" echo -en ""default${sep}${MINDI_DEFAULT_BOOT_OPTION}\n"" else echo -en ""default${sep}interactive\n"" fi else .... # Handle timeout if [ ""$CDRECOVERY"" == ""yes"" ]; then echo -en ""timeout${sep}1000\n"" elif [ ""$MINDI_BOOT_TIMEOUT"" != """" ]; then LogIt ""Overriding boot timeout: $MINDI_BOOT_TIMEOUT"" echo -en ""timeout${sep}${MINDI_BOOT_TIMEOUT}\n"" else echo -en ""timeout${sep}300\n"" fi .... } }}} A small change but one that would be useful." 95 Physical extent size for volume group isn't preserved mondo 2.2.0 4.0.0 defect minor Bruno Cornec assigned Bruno Cornec 2006-11-01T00:25:25+01:00 2009-01-29T18:05:00+01:00 "The physical extent size for volume group isn't preserved but set to the default of 32MB. Not that it's a problem, just a note. (From ""Chua, Alfred"" )" 601 mondoarchive on shared directory : Operation not permitted mindi 3.0.1 4.0.0 enhancement minor Bruno Cornec reopened rue 2012-03-29T10:54:47+02:00 2015-05-27T23:37:40+02:00 "System is windows 7 Enterprise with Oracle VM Virtualbox running RHEL6 Mondo is installed on RHEL6. I tried to generate the iso file on the shared directory. $ mondoarchive -Oi -d /media/sf_VM_partage -E '/media/sf_VM_partage' -p `hostname`-`date +%Y-%m-%d` mondoarchive.log and mindi.log show : cp: cannot create special file `/media/sf_VM_partage/mondo.tmp.YoepwC/bigdir/dev/boot_device': Operation not permitted FATAL ERROR. Unable to create /dev/boot_device on ramdisk " 793 Incorrect localization after restore mondo 3.2.1 4.0.0 defect minor Bruno Cornec new Bruno Cornec 2016-04-14T02:40:48+02:00 2017-03-09T00:39:35+01:00 "After restoration and log on the system, there is a localization issue: On the master: {{{ # locale LANG=fr_FR.UTF-8 LC_CTYPE=""fr_FR.UTF-8"" LC_NUMERIC=""fr_FR.UTF-8"" LC_TIME=""fr_FR.UTF-8"" LC_COLLATE=""fr_FR.UTF-8"" LC_MONETARY=""fr_FR.UTF-8"" LC_MESSAGES=""fr_FR.UTF-8"" LC_PAPER=""fr_FR.UTF-8"" LC_NAME=""fr_FR.UTF-8"" LC_ADDRESS=""fr_FR.UTF-8"" LC_TELEPHONE=""fr_FR.UTF-8"" LC_MEASUREMENT=""fr_FR.UTF-8"" LC_IDENTIFICATION=""fr_FR.UTF-8"" LC_ALL= }}} On the restored system: {{{ # locale LANG=C LC_CTYPE=""C"" LC_NUMERIC=""C"" LC_TIME=""C"" LC_COLLATE=""C"" LC_MONETARY=""C"" LC_MESSAGES=""C"" LC_PAPER=""C"" LC_NAME=""C"" LC_ADDRESS=""C"" LC_TELEPHONE=""C"" LC_MEASUREMENT=""C"" LC_IDENTIFICATION=""C"" LC_ALL= }}}" 740 add iscsi support for RHEL4 mondo 3.0.4 4.0.0 enhancement normal Bruno Cornec new Bruno Cornec 2014-04-03T01:46:40+02:00 2014-04-03T01:46:40+02:00 "Some notes from an existing conf: - if iSCSI on RHEL4 then launch it and keep conf /etc/iscsi.conf + /etc/initiatorname.iscsi - need /dev/iscsictl (mknod ... c maj 0 from /proc/devices) & launch /sbin/iscsid" 788 No progress indicated when copying in USB mode mondo 3.2.1 4.0.0 defect normal Bruno Cornec new Bruno Cornec 2016-03-30T02:57:42+02:00 2017-03-08T17:14:58+01:00 Indicator stays at 1% instead of showing progress. 39 support for long opitions (GNU type) mondo 2.0.9 4.0.2 enhancement minor Bruno Cornec new Bruno Cornec 2006-08-08T01:35:46+02:00 2007-04-02T16:43:59+02:00 Introduce long names for command line options 85 abandoned files mondo 2.0.9 4.0.2 defect minor Bruno Cornec assigned jsoff 2006-10-13T20:10:41+02:00 2007-05-21T00:09:40+02:00 "On Suse 10.1 kernel 2.6.xxx using switches -S /tmp -T /tmp the following directories get orphaned in /tmp cd.xxxx mondo.scratch.xxxx tmp.mondo.xxxx On RH9 not using those switches the diretories are not left behind. " 86 graphic tape issue and text progress indicator mondo 2.2.0 4.0.2 defect minor Bruno Cornec assigned jsoff 2006-10-13T20:12:14+02:00 2009-09-26T17:43:24+02:00 "Ver 2.09 I noticed that when verifying biggie files in graphic mode the progress tape never goes over 1%. " 109 add a timestamp to the logfiles name mondo 2.2.0 4.0.2 enhancement minor Bruno Cornec assigned d3acon 2006-11-22T10:20:51+01:00 2008-01-17T01:38:05+01:00 It would be nice if you could add a timestamp to the filename of the logfile. So you wouldn't override the previous logfile and bugtracking would be easier. 5 Manual CD tray + DVD not supported yet. mondo 2.0.8 4.0.2 defect normal Bruno Cornec new bfahnoe@… 2006-07-31T23:20:23+02:00 2009-09-28T13:33:33+02:00 "When using Mondoarchive and a +DVD you must answer as follows to the question: Is your computer a laptop, or does the CD writer incorporate Burnproof technology? Answer No.[[BR]] It works if you answer No to this question even though the burner supports Burnproof." 40 have a live CD including mondo rescue mondo 2.0.9 4.0.2 enhancement normal Bruno Cornec assigned Bruno Cornec 2006-08-08T12:33:58+02:00 2006-11-29T10:44:36+01:00 This will allow backing up systems offline as well as backing up Window based systems. 75 Need a 'go back' option in ncurses interface mondo 2.0.9 4.0.2 enhancement normal Bruno Cornec new Brian McKee 2006-09-27T20:04:24+02:00 2009-09-28T13:33:53+02:00 Would be nice to be able to go back if you make a typo when using the mondo archive curses interface (i.e. choose CD-R when you meant Hard drive and you have to quit and start over)