Fwd: Re: Default ISO size not set?


On 2016-05-25 6:06 AM, Bruno Cornec wrote: > Admin - Muskoka Auto Parts Limited said on Tue, May 24, 2016 at 02:42:23PM -0400: >> mondoarchive -Oi -9 -F -d "stuff" -E "stuff" -N >> >>> Warning! CD is too big. It occupies 4901484 KB, which is more than the 650 KB al >> Even if I add -s 8g it fails. I gather it's because there is a single >> file over 4 gig in size and you can't stuff that in an ISO or break it >> up? > No it knows how to split files. Please provide the logfile with the -s 8g > so we can see what gets wrong in your case. > Thanks for offering to look Bruno. I don't think there are any sparse files involved, but there are a couple of sizable sqlite databases. Complete log file is available at https://transfer.sh/143VDp/mondoarchive.log for 14 days. (It seems it's too large to attach, and the mailing list rejects .zip) I think this is the relevant part, but not sure the implications. > [Main] libmondo-fork.c->eval_call_to_make_ISO#145: basic call > = 'genisoimage -r -p MondoRescue -publisher www.mondorescue.org -A > Mondo_Rescue_GPL_Version -J -boot-info-table -no-emul-boot -b > isolinux.bin -c boot.cat -boot-load-size 4 -o '_ISO_' -V _CD#_ .' > [Main] libmondo-fork.c->eval_call_to_make_ISO#146: > midway_call = 'genisoimage -r -p MondoRescue -publisher > www.mondorescue.org -A Mondo_Rescue_GPL_Version -J -boot-info-table > -no-emul-boot -b isolinux.bin -c boot.cat -boot-load-size 4 -o > '/var/mondoImages/webserver//mondorescue-1.iso' -V _CD#_ .' > [Main] libmondo-fork.c->eval_call_to_make_ISO#147: tmp = > 'genisoimage -r -p MondoRescue -publisher www.mondorescue.org -A > Mondo_Rescue_GPL_Version -J -boot-info-table -no-emul-boot -b > isolinux.bin -c boot.cat -boot-load-size 4 -o > '/var/mondoImages/webserver//mondorescue-1.iso' -V 1 .' > [Main] libmondo-fork.c->eval_call_to_make_ISO#148: > ultimate call = 'genisoimage -r -p MondoRescue -publisher > www.mondorescue.org -A Mondo_Rescue_GPL_Version -J -boot-info-table > -no-emul-boot -b isolinux.bin -c boot.cat -boot-load-size 4 -o > '/var/mondoImages/webserver//mondorescue-1.iso' -V 1 .' > Please be patient. Do not be alarmed by on-screen inactivity. > [Main] libmondo-fork.c->eval_call_to_make_ISO#154: Calling > open_evalcall_form() with what_i_am_doing='Running mkisofs to make ISO #1' > [Main] libmondo-fork.c->eval_call_to_make_ISO#187: command = > 'genisoimage -r -p MondoRescue -publisher www.mondorescue.org -A > Mondo_Rescue_GPL_Version -J -boot-info-table -no-emul-boot -b > isolinux.bin -c boot.cat -boot-load-size 4 -o > '/var/mondoImages/webserver//mondorescue-1.iso' -V 1 . >> > /var/log/mondoarchive.log' > [Main] > libmondo-fork.c->run_external_binary_with_percentage_indicator_NEW#668: > command = 'genisoimage -r -p MondoRescue -publisher > www.mondorescue.org -A Mondo_Rescue_GPL_Version -J -boot-info-table > -no-emul-boot -b isolinux.bin -c boot.cat -boot-load-size 4 -o > '/var/mondoImages/webserver//mondorescue-1.iso' -V 1 . >> > /var/log/mondoarchive.log 2>> /var/log/mondoarchive.log' > Running mkisofs to make ISO #1 > Running mkisofs to make ISO #1 > [Main] libmondo-fork.c->run_prog_in_bkgd_then_exit#627: > sz_command = 'genisoimage -r -p MondoRescue -publisher > www.mondorescue.org -A Mondo_Rescue_GPL_Version -J -boot-info-table > -no-emul-boot -b isolinux.bin -c boot.cat -boot-load-size 4 -o > '/var/mondoImages/webserver//mondorescue-1.iso' -V 1 . >> > /var/log/mondoarchive.log 2>> /var/log/mondoarchive.log' > I: -input-charset not specified, using utf-8 (detected in locale settings) > File ./archives/60.afio.bz2 is larger than 4GiB-1. > -allow-limited-size was not specified. There is no way do represent > this file size. Aborting. > [Main] libmondo-fork.c->run_prog_in_bkgd_then_exit#632: > child res = 256 > [Main] > libmondo-fork.c->run_external_binary_with_percentage_indicator_NEW#704: > Parent res = 256 > Call to mkisofs to make ISO (ISO #1) ...failed > [Main] libmondo-archive.c->make_iso_fs#1994: WARNING - make_iso_fs > returned an error

------------------------------------------------------------------------------
Mobile security can be enabling, not merely restricting. Employees who
bring their own devices (BYOD) to work are irked by the imposition of MDM
restrictions. Mobile Device Manager Plus allows you to control only the
apps on BYO-devices by containerizing them, leaving personal data untouched!
https://ad.doubleclick.net/ddm/clk/304595813;131938128;j
_______________________________________________
Mondo-devel mailing list
Mondo-devel <at> lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mondo-devel

Default ISO size not set?

Good afternoon,

On a recently set up CentOS machine, using mondo  x86_64   3.0.4 1.rhel6

If I do

    mondoarchive -Oi -9 -F -d "stuff" -E "stuff" -N

I get

Call to mkisofs to make ISO (ISO #1) ...OK Warning! CD is too big. It occupies 4901484 KB, which is more than the 650 KB al Please be patient. Do not be alarmed by on-screen inactivity. Call to mkisofs to make ISO (ISO #2) ...failed Execution run ended; result=1 Type 'less /var/log/mondoarchive.log' to see the output log

Even if I add -s 8g it fails.  I gather it's because there is a single file over 4 gig in size and you can't stuff that in an ISO or break it up?

But if I can't use ISO images, how do I back it up locally?   My current process backs it up locally, then encrypts the isos and then rsyncs them to remote storage.

I've tried combinations of -n and -d but haven't figured it out...

Comments appreciated,

Brian
------------------------------------------------------------------------------
Mobile security can be enabling, not merely restricting. Employees who
bring their own devices (BYOD) to work are irked by the imposition of MDM
restrictions. Mobile Device Manager Plus allows you to control only the
apps on BYO-devices by containerizing them, leaving personal data untouched!
https://ad.doubleclick.net/ddm/clk/304595813;131938128;j
_______________________________________________
Mondo-devel mailing list
Mondo-devel <at> lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mondo-devel
Bruno Cornec | 21 May 02:29 2016

Re: [ANNOUNCE] Project mondorescue version 3.2.2 is now available

John Pearson said on Fri, Apr 29, 2016 at 11:01:02AM +0930:
>I note there are no packages for the i386 platform running Debian 8; 
>can that be fixed?

Done.

Bruno.
--

-- 
Open Source Profession, WW Linux Community Lead  http://www.hpintelco.net
HPE EMEA EG Open Source Technology Strategist http://hp.com/go/opensource
FLOSS projects:     http://mondorescue.org     http://project-builder.org
Musique ancienne? http://www.musique-ancienne.org http://www.medieval.org

------------------------------------------------------------------------------
Mobile security can be enabling, not merely restricting. Employees who
bring their own devices (BYOD) to work are irked by the imposition of MDM
restrictions. Mobile Device Manager Plus allows you to control only the
apps on BYO-devices by containerizing them, leaving personal data untouched!
https://ad.doubleclick.net/ddm/clk/304595813;131938128;j
Bruno Cornec | 21 May 02:29 2016

Re: [ANNOUNCE] Project mondorescue version 3.2.2 is now available

Rob Borland said on Fri, Apr 29, 2016 at 06:34:11AM +0200:
>Thanks for all the hard work that went into this release.
>I'd appreciate having a package for Debian 7 on i386, when you are ready.

Done.
Bruno.
--

-- 
Open Source Profession, WW Linux Community Lead  http://www.hpintelco.net
HPE EMEA EG Open Source Technology Strategist http://hp.com/go/opensource
FLOSS projects:     http://mondorescue.org     http://project-builder.org
Musique ancienne? http://www.musique-ancienne.org http://www.medieval.org

------------------------------------------------------------------------------
Mobile security can be enabling, not merely restricting. Employees who
bring their own devices (BYOD) to work are irked by the imposition of MDM
restrictions. Mobile Device Manager Plus allows you to control only the
apps on BYO-devices by containerizing them, leaving personal data untouched!
https://ad.doubleclick.net/ddm/clk/304595813;131938128;j
spezialist | 19 May 11:20 2016
Picon

Mondo Archive v3.2.2-r3578: ASSERTION FAILED: `call[0]!='\0''

Hi all!

I found here such error on CentOS-6.7 when using an option -n (mondoarchive tries to mount automatically a
NFS resource from /etc/fstab):

==================================================
# mondoarchive -K 10 -O -p snmpproxy-kv0 -n nfs://10.3.33.100:/export/DCIM_backups -d
/snmpproxy-kv0.back/BMR -E "/data/tmp/mondo|/mnt/nfs_backups" -T /data/tmp/mondo -S
/data/tmp/mondo -F -s 4480m -6z
See /var/log/mondoarchive.log for details of backup run.
Checking sanity of your Linux distribution
Done.
Network share 10.3.33.100:/export/DCIM_backups is not mounted. Trying to mount i
ASSERTION FAILED: `call[0]!='\0''
        at libmondo-fork.c:53 in call_program_and_get_last_line_of_output

(I)gnore, ignore (A)ll, (D)ebug, a(B)ort, or (E)xit? d
(Unknown) signal received from OS
(Unknown)
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.
Execution run ended; result=254
Type 'less /var/log/mondoarchive.log' to see the output log
==================================================

Interestingly, but despite this error, mondoarchive actually normally mounted the specified NFS
resource. Besides, manually this NFS resource is also mounted without errors:

==================================================
# mount -vvvvvvvvvvvvvvvvv 10.3.33.100:/export/DCIM_backups
mount: fstab path: "/etc/fstab"
mount: mtab path:  "/etc/mtab"
mount: lock path:  "/etc/mtab~"
mount: temp path:  "/etc/mtab.tmp"
mount: UID:        0
mount: eUID:       0
mount: spec:  "10.3.33.100:/export/DCIM_backups"
mount: node:  "/mnt/nfs_backups"
mount: types: "nfs"
mount: opts:  "noauto,noatime,nolock,mountproto=tcp"
final mount options: 'nolock,mountproto=tcp'
mount: external mount: argv[0] = "/sbin/mount.nfs"
mount: external mount: argv[1] = "10.3.33.100:/export/DCIM_backups"
mount: external mount: argv[2] = "/mnt/nfs_backups"
mount: external mount: argv[3] = "-v"
mount: external mount: argv[4] = "-o"
mount: external mount: argv[5] = "rw,noauto,noatime,nolock,mountproto=tcp"
mount.nfs: timeout set for Thu May 19 11:54:23 2016
mount.nfs: trying text-based options 'nolock,mountproto=tcp,addr=10.3.33.100,mountaddr=10.3.33.100'
mount.nfs: prog 100003, trying vers=3, prot=6
mount.nfs: trying 10.3.33.100 prog 100003 vers 3 prot TCP port 2049
mount.nfs: prog 100005, trying vers=3, prot=6
mount.nfs: trying 10.3.33.100 prog 100005 vers 3 prot TCP port 32770
10.3.33.100:/export/DCIM_backups on /mnt/nfs_backups type nfs (rw,noauto,noatime,nolock,mountproto=tcp)

# cd /mnt/nfs_backups/snmpproxy-kv0.back/BMR; pwd
/mnt/nfs_backups/snmpproxy-kv0.back/BMR

# umount -vvvvvvvvvvvvvvvvv 10.3.33.100:/export/DCIM_backups
Trying to umount 10.3.33.100:/export/DCIM_backups
Legacy NFS mount point detected
umount.nfs: prog 100005, trying vers=3, prot=6
umount.nfs: trying 10.3.33.100 prog 100005 vers 3 prot TCP port 32770
10.3.33.100:/export/DCIM_backups umounted
==================================================

I send a log file in attachment.

Besides, it is possible to see one more bug: in spite of the fact that in command line the tmpdir and
scratchdir is /data/tmp/mondo is specified, mondoarchive uses the standard directory /tmp (see a log file).

Very thanks for the support.

--
Чорнобиль форева!

-- реклама -----------------------------------------------------------
Старт продаж ЖК "Новая Англия"! Цена от 14 900 грн/кв.м!
http://h.holder.com.ua/c?tz&z1585&b117887&s03908&r[rndID]&u
Attachment (mondoarchive.log): application/octet-stream, 14 KiB
------------------------------------------------------------------------------
Mobile security can be enabling, not merely restricting. Employees who
bring their own devices (BYOD) to work are irked by the imposition of MDM
restrictions. Mobile Device Manager Plus allows you to control only the
apps on BYO-devices by containerizing them, leaving personal data untouched!
https://ad.doubleclick.net/ddm/clk/304595813;131938128;j
_______________________________________________
Mondo-devel mailing list
Mondo-devel <at> lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mondo-devel
Raj Mahesh | 17 May 07:30 2016

Restore Process Failure

Dear Team,

I am using the mondo rescue software to backup my live linux system. i had successfully backed up the whole system on a DVD which i could not restore. then again i backed up to a hard drive and while restoring i got errors as Volume group not found. Can you please tell me how to restore the data. i am trying to do it on a VM. i also want to verify if the backed up data is correct. Kindly help.

Regards,
Raj
------------------------------------------------------------------------------
Mobile security can be enabling, not merely restricting. Employees who
bring their own devices (BYOD) to work are irked by the imposition of MDM
restrictions. Mobile Device Manager Plus allows you to control only the
apps on BYO-devices by containerizing them, leaving personal data untouched!
https://ad.doubleclick.net/ddm/clk/304595813;131938128;j
_______________________________________________
Mondo-devel mailing list
Mondo-devel <at> lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mondo-devel
John McMillan | 18 May 00:48 2016
Picon

Mindi help needed

I am just beginning to learn to  use mondo-mindi.  I have downloaded mondo and mindi-busybox and started by following the "Testing Mindi" instructions.  When I run the command "sudo mindi" with "no" to the first question (there is no second question) I get the error :

FATAL ERROR. PBDI - cannot find  kernel

Logs attached.  Thank you for your help.
John McMillan
Attachment (mindi.log): text/x-log, 66 KiB
Attachment (mondoarchive.log): text/x-log, 6610 bytes
------------------------------------------------------------------------------
Mobile security can be enabling, not merely restricting. Employees who
bring their own devices (BYOD) to work are irked by the imposition of MDM
restrictions. Mobile Device Manager Plus allows you to control only the
apps on BYO-devices by containerizing them, leaving personal data untouched!
https://ad.doubleclick.net/ddm/clk/304595813;131938128;j
_______________________________________________
Mondo-devel mailing list
Mondo-devel <at> lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mondo-devel
Pichon, Mathieu (Nokia - FR | 13 May 14:35 2016
Picon

Restore a HP G9 server with UEFI and redHat 6.6

Hello,


I try to backup/restore a HP G9 server with UEFI and redHat 6.6.
After restore, it is impossible to mount “/” partition, it seems we have bad UUID for both “/” ( dev/sda8) et /boot/EFI ( dev/sda2) partitions.

 

We can’t access log files because we can’t mount “/” partition so we don’t access /var/log/mondoarchive.log.


Can you help to investigate?
Regards,

Mathieu PICHON

------------------------------------------------------------------------------
Mobile security can be enabling, not merely restricting. Employees who
bring their own devices (BYOD) to work are irked by the imposition of MDM
restrictions. Mobile Device Manager Plus allows you to control only the
apps on BYO-devices by containerizing them, leaving personal data untouched!
https://ad.doubleclick.net/ddm/clk/304595813;131938128;j
_______________________________________________
Mondo-devel mailing list
Mondo-devel <at> lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mondo-devel
Steven M. Schweda | 13 May 19:39 2016

Re: [MondoRescue] #784: mondoarchive or mondorestore SEGV with tape management

   Any news?  (Has anyone actually tried this program using a tape
drive?)

From:	ALP::SMS          "Steven M. Schweda" 28-APR-2016 23:57:44.89
To:	MONDO-DEVEL <at> LISTS.SOURCEFORGE.NET
Subj:	Re: [MondoRescue] #784: mondoarchive or mondorestore SEGV with tape management

>  Is part of 3.2.2

   Thanks.  Now it gets all the way to asking for the tape block size
before exploding. 

deb74# mondoarchive --version
mondoarchive v3.2.2-r3578
See man page for help

deb74# mondoarchive

Backup to: Tape drive

What is the /dev entry of your tape streamer?
      /dev/st0

What is the block size of your tape streamer?
      32768 [default]  "OK" is followed by a screenfull of white text on
a blue background (some lost, I believe):

7f8e550b2000-7f8e550b3000 r--p 0001f000 08:11 1311221                   
/lib/x86_64-linux-gnu/ld-2.13.so
                    7f8e550b3000-7f8e550b4000 rw-p 00020000 08:11
1311221                    /lib/x86_64-linux-gnu/ld-2.13.so
                                             7f8e550b4000-7f8e550b5000
rw-p 00000000 00:00 0 
             7ffc000ce000-7ffc000ef000 rw-p 00000000 00:00 0                         
[stack]
             7ffc001e6000-7ffc001e7000 r-xp 00000000 00:00 0                         
[vdso]
            ffffffffff600000-ffffffffff601000 r-xp 00000000 00:00 0            
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
SIGABRT signal received from OS                                            
If you require technical support, please contact the mailing list.nds so
you can re
                                                              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.

   The process does not exit, and "kill -TERM" leaves the
terminal/emulator in a modified state (colors, intr = <undef>; quit =
<undef>; eof = ^A; susp = <undef>; lnext = <undef>; -icrnl, -opost,
opost, -icanon, -iexten, -echo, noflsh, -echoctl, -echoke, ...).

   An actual exit handler which restored the original terminal settings
might be a good thing.

   And, before the program explodes, my Mac xterm shows garbage for box
borders in the char-cell GUI, which, I assume, were supposed to be
line-drawing characters.

   Another, minor annoyance: When I see a question like "What is the
/dev entry of your tape streamer?", I assume that the questioner wants
the part of the answer which is not already known.  That is, in this
case, "st0", not the whole device path, "/dev/st0".  Naturally, if the
victim specifies "st0", the program output is the usual (unhelpful):

See /var/log/mondoarchive.log for details of backup run.
Checking sanity of your Linux distribution
Done.
Execution run ended; result=1
Type 'less /var/log/mondoarchive.log' to see the output log

   Admittedly, there is a useful message hidden in that mess (if you can
find it):
INFO: ls: cannot access st0: No such file or directory

   A helpful program might try "/dev/≤user_input>" if plain
"<user_input>" does not exist.  Or, the question could be phrased more
helpfully, for example:
      Tape device path (e.g.: /dev/st0 or st0)?
Just a thought. 

   Old news: http://trac.mondorescue.org/register still fails:

Register an account
Error

The password file could not be updated. Trac requires read and write
access to both the password file and its parent directory.

   As usual, if you need more info, please let me know.

------------------------------------------------------------------------

   Steven M. Schweda               sms <at> antinode.info

------------------------------------------------------------------------------
Mobile security can be enabling, not merely restricting. Employees who
bring their own devices (BYOD) to work are irked by the imposition of MDM
restrictions. Mobile Device Manager Plus allows you to control only the
apps on BYO-devices by containerizing them, leaving personal data untouched!
https://ad.doubleclick.net/ddm/clk/304595813;131938128;j
Bruno Cornec | 13 May 11:48 2016

Re: mondoarchive won't run

Hello Leo,

Leo Koelemij said on Thu, Apr 28, 2016 at 09:19:50PM +0200:
>>Leo Koelemij said on Tue, Apr 19, 2016 at 03:18:18PM +0200:
>>>Unable to alloc memory in mr_asprintf
>>>DBG1: libmondo-devices.c-≥mr_asprintf#2385: Unable to alloc memory in mr_asprintf
>>I'm able to reproduce and have fixed it in rev [3576]. Thanks for your report and log.
>I used the new ones:
>
>Xubuntu 12.04
>libmondorescue-perl_3.2.320160414030156-0_all.deb
>mindi_3.0.320160414030156-0_amd64.deb
>mondo_3.2.320160414030156-0_amd64.deb
>Mindi busybox 1.21.1-1

They do not seem to be newer in fact. please now use the upstream 3.2.2 official version at ftp://ftp.mondorescue.org/ubuntu/12.04

>>So you can take that advise and use the -f and -l option in your case.
>I added the information:
>sudo mondoarchive -Ot -d /dev/st0 -g -f /dev/sdd -l GRUB -I /home/leo/WP60
>Backup runs fine.

Ok. So you have a workaround.

>But when I want to verify the backup with:
>sudo mondoarchive -Vt -d /dev/st0 -g -f /dev/sdd -l GRUB -I /home/leo/WP60
>I stops after a while, nothing happens any more. I enclose the log file
>Before the program stops I get:
>
>ASSERTION FAILED: `orig_fname[0]!='\0''
>    at libmondo-verify.c:581 in verify_an_afioball_from_stream
>
>(I)gnore, ignore (A)ll, (D)ebug, a(B)ort, or (E)xit? D    ( I thought 
>that debug was the wisest choice.)

Ok. I've made a ticket for this one:
http://trac.mondorescue.org/ticket/798

>I boot from sdb with IBM's bootmanager and I choose Xubuntu which is on sdd:
>It is in dutch, Most partitions are OS/2 with JFS

In order to help me, as my dutch isn't fluent, could you just relaunch with:

LANGUAGE=C LANG=C fdisk -l

on a bash shell please ?

>> Apparaat Opstart   Begin       Einde     Blokken   ID  Systeem
>>/dev/sdb1   *          63       16064        8001    a  OS/2 opstartmanager

I think that may be the problem BTW :-)

>when I start mondoarchive without options I get, after I filled in: 
>/dev/st0:
>Unable to alloc memory in mr_asprintf

That should be fixed in the official version. Your version is before the revision fixing that problem.

Bruno.
--

-- 
Open Source Profession, WW Linux Community Lead  http://www.hpintelco.net
HPE EMEA EG Open Source Technology Strategist http://hp.com/go/opensource
FLOSS projects:     http://mondorescue.org     http://project-builder.org
Musique ancienne? http://www.musique-ancienne.org http://www.medieval.org

------------------------------------------------------------------------------
Mobile security can be enabling, not merely restricting. Employees who
bring their own devices (BYOD) to work are irked by the imposition of MDM
restrictions. Mobile Device Manager Plus allows you to control only the
apps on BYO-devices by containerizing them, leaving personal data untouched!
https://ad.doubleclick.net/ddm/clk/304595813;131938128;j
Esteban Monge | 11 May 19:07 2016
Picon

mondorestore delete all and format partitions

Hello:

I am using mondorescue a long time ago... I can make restores without 
touching the partition scheme... but when I need to restore partitions 
mondorestore deletes all partitions.

My scenario is:
RHEL 5.10
MondoRescue 3.2.2

Server with two virtual hard disk:
boot /dev/vda1
rootvg /dev/vda2
appvg /dev/vdb

rootvg/LogVol00 -> SWAP
rootvg/LogVol01 -> /

appvg/applv -> /backupsMR

I make backups with:
/usr/sbin/mondoarchive -Ovi -S /scratch -d /backupsMR -9 -s 4300m -E 
'/backupsMR|/scratch'

When use mondorestore with live so from iso, I remove from mountlist:
/dev/vdb1   lvm   lvm
/dev/mapper/appvg-applv /backupsMR/ ext3

To avoid deleting logical volumen and formatting... But mondorestore 
stills erasing all data from /dev/mapper/appvg-applv

I doesn't know what is wrong... with previous versions of development 
version of mondorescue worked... but I can recover the rpm backup... was 
deleted =(...

I also have aesthetic problems with curses interface. I doesn't know if 
is the spice driver from KVM, and when I choose options get wrong mount 
points...

For example principal menu aspect:
http://imgur.com/tj8H4uw

The mountlist screen:
http://imgur.com/IPa1QDl

Again the mountlist screen:
http://imgur.com/AkQCARf

As you can see some garbage keeps in screen "/ /" characters. I don't if 
these garbage impact of change the behaviour of mondorestore...

Thanks for you patience and advice...

Great work!

------------------------------------------------------------------------------
Mobile security can be enabling, not merely restricting. Employees who
bring their own devices (BYOD) to work are irked by the imposition of MDM
restrictions. Mobile Device Manager Plus allows you to control only the
apps on BYO-devices by containerizing them, leaving personal data untouched!
https://ad.doubleclick.net/ddm/clk/304595813;131938128;j

Gmane