Re: [Mondo-devel] Segmentation error running mondoarchive v3.2.0-r3332

classic Classic list List threaded Threaded
22 messages Options
12
Reply | Threaded
Open this post in threaded view
|

Re: [Mondo-devel] Segmentation error running mondoarchive v3.2.0-r3332

Philippe Lefevre
Hi all,

If it may help, I just noticed that also happen with just a mondoarchive -v

[phlsys]root:/var/log# mondoarchive -v
mondoarchive v3.2.0-r3332
See man page for help
Erreur de segmentation

Please find attached a strace log :

Rgds,
Philippe


Le 27/12/2014 11:17, [hidden email] a écrit :

> Hi all,
>
> it seems that something goes wrong with mondo I could link to the latest
> Debian version of MondoRescue.
>
> I updated my version last thursday and this morning (I have a
> differential backup launched every friday night and one full a month) it
> failed.
> Unfortunately there are no much relevant informations in logs.
>
> The errors raised is :
>
>     # mondoarchive -D -OV -i -N -G -s 780M -p sys-D7.7-diff_141227100000
>     -T /graveur -S /graveur -d
>     /media/sauvegardes/phlsys/D7.7/sys/141227100000 -I
>     "/|/|/opt/calibre|/opt/Zuma" -E
>     "/bases/sybase|/graveur|/home|/opt|/photos|/quemu|/Sauvegardes|/var/crash|/var/backups|/var/log|/var/mail|/var/spool|/vbox|/videos|/www"
>     See /var/log/mondoarchive.log for details of backup run.
>     Checking sanity of your Linux distribution
>     Done.
>     Erreur de segmentation                /* Segmentation error */
>
> Please find attached the log files that seems to find out an issue with
> LVM disks
>
>     INFO: Mindi v3.0.0-r3332
>     INFO: Le disque /dev/mapper/data1vg-photoslv ne contient pas une
>     table de partitions valable
>              /* there is no valid partition table in
>     /dev/mapper/data1vg-photoslv disk */
>
> I have no issues with my LVM disks. Please find on below my LVM disks
> configuration
>
>     lvm> vgs
>       VG      #PV #LV #SN Attr   VSize   VFree
>       data1vg   1   7   0 wz--n- 931,51g 504,60g
>       sysvg     1   1   0 wz--n-  95,12g  78,84g
>
>     lvm> lvs
>       LV        VG      Attr     LSize   Pool Origin Data%  Move Log
>     Copy%  Convert
>       baseslv   data1vg -wi-ao--  
>     1,86g                                          
>       graveurlv data1vg -wi-ao--
>     20,00g                                          
>       homelv    data1vg -wi-ao--
>     50,00g                                          
>       photoslv  data1vg -wi-ao--
>     70,00g                                          
>       vboxlv    data1vg -wi-ao--
>     130,39g                                          
>       videoslv  data1vg -wi-ao--
>     150,00g                                          
>       wwwlv     data1vg -wi-ao--  
>     4,66g                                          
>       optlv     sysvg   -wi-ao--  16,28g
>
>     lvm> lvscan
>       ACTIVE            '/dev/data1vg/photoslv' [70,00 GiB] inherit
>       ACTIVE            '/dev/data1vg/videoslv' [150,00 GiB] inherit
>       ACTIVE            '/dev/data1vg/homelv' [50,00 GiB] inherit
>       ACTIVE            '/dev/data1vg/graveurlv' [20,00 GiB] inherit
>       ACTIVE            '/dev/data1vg/wwwlv' [4,66 GiB] inherit
>       ACTIVE            '/dev/data1vg/baseslv' [1,86 GiB] inherit
>       ACTIVE            '/dev/data1vg/vboxlv' [130,39 GiB] inherit
>       ACTIVE            '/dev/sysvg/optlv' [16,28 GiB] inherit
>
>     root@phlsys:/home/phl/Scripts# df -h
>     Sys. fich.                                             Taille Util.
>     Dispo Uti% Monté sur
>     rootfs                                                    92G  
>     11G   77G  12% /
>     udev                                                      10M    
>     0   10M   0% /dev
>     tmpfs                                                    397M  968K
>     396M   1% /run
>     /dev/disk/by-uuid/4a5a9317-0b70-4796-a094-d61c01891c81    92G  
>     11G   77G  12% /
>     tmpfs                                                    5,0M     0
>     5,0M   0% /run/lock
>     tmpfs                                                    985M  324K
>     985M   1% /run/shm
>     /dev/mapper/sysvg-optlv                                   17G   15G
>     845M  95% /opt
>     /dev/mapper/data1vg-homelv                                50G   40G
>     7,2G  85% /home
>     /dev/mapper/data1vg-wwwlv                                4,6G  2,5G
>     1,9G  58% /www
>     /dev/mapper/data1vg-baseslv                              1,9G  720M
>     1,1G  41% /bases
>     /dev/mapper/data1vg-photoslv                              69G  
>     43G   23G  66% /photos
>     /dev/mapper/data1vg-videoslv                             148G
>     104G   37G  74% /videos
>     /dev/mapper/data1vg-vboxlv                               129G
>     100G   23G  82% /vbox
>     /dev/mapper/data1vg-graveurlv                             20G
>     8,1G   11G  44% /graveur
>
>
> The latest mondo upgrade dated of 25th of december was (it worked fine
> before this upgrade)
>
>     Start-Date: 2014-12-25  18:55:08
>     Commandline: /usr/sbin/synaptic
>     Install: libprojectbuilder-perl:amd64 (0.12.6-1, automatic),
>     libmondorescue-perl:amd64 (3.2.0-1, automatic)
>     Upgrade: mindi:amd64 (2.1.7-1, 3.0.0-1), mondo:amd64 (3.0.4-1,
>     3.2.0-1), mindi-busybox:amd64 (1.18.5-3, 1.21.1-1)
>     End-Date: 2014-12-25  18:55:31
>
> The Debian distro used is
>
>     root@phlsys:/home/phl/Scripts# uname -a
>     Linux phlsys 3.2.0-4-amd64 #1 SMP Debian 3.2.63-2+deb7u2 x86_64
>     GNU/Linux
>
> Anyone have an idea to try to debug this.
>
> Thanks for any help.
>
> By the way, I whish you all an happy new year 2015 with all the best in
> your lifes
> Kind regards,
> Philippe
>
>


------------------------------------------------------------------------------
Dive into the World of Parallel Programming! The Go Parallel Website,
sponsored by Intel and developed in partnership with Slashdot Media, is your
hub for all things parallel software development, from weekly thought
leadership blogs to news, videos, case studies, tutorials and more. Take a
look and join the conversation now. http://goparallel.sourceforge.net
_______________________________________________
Mondo-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/mondo-devel

mondoarchive_strace.log (6K) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Re: [Mondo-devel] Segmentation error running mondoarchive v3.2.0-r3332

Philippe Lefevre
Hi list,

Some more information about my issue.

I can confirm that in my case it is related to this new release as a I
did a downgrade and successfully built a new full backup.

I uninstalled and purged
  libmondorescue-perl_3.2.0-1_all.deb
  mindi-busybox_1.21.1-1_amd64.deb
  mindi_3.0.0-1_amd64.deb
  mondo_3.2.0-1_amd64.deb

and reinstalled the previous version
  mindi-busybox 1.18.5-3
  mindi 2.1.7-1
  mondo 3.0.4-1

I also compiled mondo 3.2.0 from sources and ran gdb against the
simpliest command that raise the seg error. It shows :

Starting program:
/home/phl/telechargements/mondo-3.2.0/src/mondoarchive/mondoarchive -v
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
mondoarchive v3.2.0-r3332
See man page for help

Program received signal SIGSEGV, Segmentation fault.
0x00007ffff76629aa in vfprintf () from /lib/x86_64-linux-gnu/libc.so.6
(gdb) bt
#0  0x00007ffff76629aa in vfprintf () from /lib/x86_64-linux-gnu/libc.so.6
#1  0x00007ffff7688fca in vasprintf () from /lib/x86_64-linux-gnu/libc.so.6
#2  0x00000000004367c4 in mr_asprintf_int
(strp=strp@entry=0x7fffffffe0d0, line=line@entry=258,
file=file@entry=0x44187f "libmondo-fork.c",
    fmt=fmt@entry=0x441d38 "%s > %s/mondo-run-prog-thing.tmp 2>
%s/mondo-run-prog-thing.err") at mr_mem.c:62
#3  0x000000000041e0f0 in run_program_and_log_output
(program=program@entry=0x43c4b4 "umount -d /mnt/cdrom",
debug_level=debug_level@entry=0)
    at libmondo-fork.c:258
#4  0x000000000042ec19 in finish (signal=signal@entry=0) at
newt-specific.c:388
#5  0x0000000000403430 in main (argc=2, argv=0x7fffffffe668) at
mondoarchive.c:176
(gdb)


function code exerpt

   56 void mr_asprintf_int(char **strp, int line, const char *file,
const char *fmt, ...) {
   57
   58 int res = 0;
   59 va_list args;
   60
   61 va_start(args,fmt);
   62 res = vasprintf(strp, fmt, args);
   63 if (res == -1) {
   64 mr_msg_int(1,line,file,"Unable to alloc memory in
mr_asprintf\nExiting...");
   65 mr_exit(-1,"Unable to alloc memory in mr_asprintf");
   66 }
   67 va_end(args);
   68 }


Breakpoint 1, mr_asprintf_int (strp=strp@entry=0x7fffffffe0d0,
line=line@entry=258, file=file@entry=0x44187f "libmondo-fork.c",
    fmt=fmt@entry=0x441d38 "%s > %s/mondo-run-prog-thing.tmp 2>
%s/mondo-run-prog-thing.err") at mr_mem.c:56
56 void mr_asprintf_int(char **strp, int line, const char *file, const
char *fmt, ...) {
(gdb) s
61 va_start(args,fmt);
(gdb) display fmt
1: fmt = 0x441d38 "%s > %s/mondo-run-prog-thing.tmp 2>
%s/mondo-run-prog-thing.err"
(gdb) display args
2: args = {{gp_offset = 4158558940, fp_offset = 32767, overflow_arg_area
= 0x7ffff7fd5000, reg_save_area = 0x7ffff7ffd9d8}}
(gdb) s
62 res = vasprintf(strp, fmt, args);
2: args = {{gp_offset = 4158558940, fp_offset = 32767, overflow_arg_area
= 0x7ffff7fd5000, reg_save_area = 0x7ffff7ffd9d8}}
1: fmt = 0x441d38 "%s > %s/mondo-run-prog-thing.tmp 2>
%s/mondo-run-prog-thing.err"
(gdb) s
61 va_start(args,fmt);
2: args = {{gp_offset = 4158558940, fp_offset = 32767, overflow_arg_area
= 0x7ffff7fd5000, reg_save_area = 0x7ffff7ffd9d8}}
1: fmt = 0x441d38 "%s > %s/mondo-run-prog-thing.tmp 2>
%s/mondo-run-prog-thing.err"
(gdb) s
62 res = vasprintf(strp, fmt, args);
2: args = {{gp_offset = 32, fp_offset = 48, overflow_arg_area =
0x7fffffffe0b0, reg_save_area = 0x7fffffffdfe0}}
1: fmt = 0x441d38 "%s > %s/mondo-run-prog-thing.tmp 2>
%s/mondo-run-prog-thing.err"
(gdb) display res
3: res = 0
(gdb) s

Program received signal SIGSEGV, Segmentation fault.
0x00007ffff76629aa in vfprintf () from /lib/x86_64-linux-gnu/libc.so.6
(gdb)


It seems there is an issue with mr_asprintf_int but sorry I don't feel
strong enought to get more deeply into the mondo code and analyze it
properly ...

I hope this help ...

Regards,
Philippe


Le 27/12/2014 11:17, [hidden email] a écrit :

> Hi all,
>
> it seems that something goes wrong with mondo I could link to the latest
> Debian version of MondoRescue.
>
> I updated my version last thursday and this morning (I have a
> differential backup launched every friday night and one full a month) it
> failed.
> Unfortunately there are no much relevant informations in logs.
>
> The errors raised is :
>
>     # mondoarchive -D -OV -i -N -G -s 780M -p sys-D7.7-diff_141227100000
>     -T /graveur -S /graveur -d
>     /media/sauvegardes/phlsys/D7.7/sys/141227100000 -I
>     "/|/|/opt/calibre|/opt/Zuma" -E
>     "/bases/sybase|/graveur|/home|/opt|/photos|/quemu|/Sauvegardes|/var/crash|/var/backups|/var/log|/var/mail|/var/spool|/vbox|/videos|/www"
>     See /var/log/mondoarchive.log for details of backup run.
>     Checking sanity of your Linux distribution
>     Done.
>     Erreur de segmentation                /* Segmentation error */
>
> Please find attached the log files that seems to find out an issue with
> LVM disks
>
>     INFO: Mindi v3.0.0-r3332
>     INFO: Le disque /dev/mapper/data1vg-photoslv ne contient pas une
>     table de partitions valable
>              /* there is no valid partition table in
>     /dev/mapper/data1vg-photoslv disk */
>
> I have no issues with my LVM disks. Please find on below my LVM disks
> configuration
>
>     lvm> vgs
>       VG      #PV #LV #SN Attr   VSize   VFree
>       data1vg   1   7   0 wz--n- 931,51g 504,60g
>       sysvg     1   1   0 wz--n-  95,12g  78,84g
>
>     lvm> lvs
>       LV        VG      Attr     LSize   Pool Origin Data%  Move Log
>     Copy%  Convert
>       baseslv   data1vg -wi-ao--  
>     1,86g                                          
>       graveurlv data1vg -wi-ao--
>     20,00g                                          
>       homelv    data1vg -wi-ao--
>     50,00g                                          
>       photoslv  data1vg -wi-ao--
>     70,00g                                          
>       vboxlv    data1vg -wi-ao--
>     130,39g                                          
>       videoslv  data1vg -wi-ao--
>     150,00g                                          
>       wwwlv     data1vg -wi-ao--  
>     4,66g                                          
>       optlv     sysvg   -wi-ao--  16,28g
>
>     lvm> lvscan
>       ACTIVE            '/dev/data1vg/photoslv' [70,00 GiB] inherit
>       ACTIVE            '/dev/data1vg/videoslv' [150,00 GiB] inherit
>       ACTIVE            '/dev/data1vg/homelv' [50,00 GiB] inherit
>       ACTIVE            '/dev/data1vg/graveurlv' [20,00 GiB] inherit
>       ACTIVE            '/dev/data1vg/wwwlv' [4,66 GiB] inherit
>       ACTIVE            '/dev/data1vg/baseslv' [1,86 GiB] inherit
>       ACTIVE            '/dev/data1vg/vboxlv' [130,39 GiB] inherit
>       ACTIVE            '/dev/sysvg/optlv' [16,28 GiB] inherit
>
>     root@phlsys:/home/phl/Scripts# df -h
>     Sys. fich.                                             Taille Util.
>     Dispo Uti% Monté sur
>     rootfs                                                    92G  
>     11G   77G  12% /
>     udev                                                      10M    
>     0   10M   0% /dev
>     tmpfs                                                    397M  968K
>     396M   1% /run
>     /dev/disk/by-uuid/4a5a9317-0b70-4796-a094-d61c01891c81    92G  
>     11G   77G  12% /
>     tmpfs                                                    5,0M     0
>     5,0M   0% /run/lock
>     tmpfs                                                    985M  324K
>     985M   1% /run/shm
>     /dev/mapper/sysvg-optlv                                   17G   15G
>     845M  95% /opt
>     /dev/mapper/data1vg-homelv                                50G   40G
>     7,2G  85% /home
>     /dev/mapper/data1vg-wwwlv                                4,6G  2,5G
>     1,9G  58% /www
>     /dev/mapper/data1vg-baseslv                              1,9G  720M
>     1,1G  41% /bases
>     /dev/mapper/data1vg-photoslv                              69G  
>     43G   23G  66% /photos
>     /dev/mapper/data1vg-videoslv                             148G
>     104G   37G  74% /videos
>     /dev/mapper/data1vg-vboxlv                               129G
>     100G   23G  82% /vbox
>     /dev/mapper/data1vg-graveurlv                             20G
>     8,1G   11G  44% /graveur
>
>
> The latest mondo upgrade dated of 25th of december was (it worked fine
> before this upgrade)
>
>     Start-Date: 2014-12-25  18:55:08
>     Commandline: /usr/sbin/synaptic
>     Install: libprojectbuilder-perl:amd64 (0.12.6-1, automatic),
>     libmondorescue-perl:amd64 (3.2.0-1, automatic)
>     Upgrade: mindi:amd64 (2.1.7-1, 3.0.0-1), mondo:amd64 (3.0.4-1,
>     3.2.0-1), mindi-busybox:amd64 (1.18.5-3, 1.21.1-1)
>     End-Date: 2014-12-25  18:55:31
>
> The Debian distro used is
>
>     root@phlsys:/home/phl/Scripts# uname -a
>     Linux phlsys 3.2.0-4-amd64 #1 SMP Debian 3.2.63-2+deb7u2 x86_64
>     GNU/Linux
>
> Anyone have an idea to try to debug this.
>
> Thanks for any help.
>
> By the way, I whish you all an happy new year 2015 with all the best in
> your lifes
> Kind regards,
> Philippe
>
>



------------------------------------------------------------------------------
Dive into the World of Parallel Programming! The Go Parallel Website,
sponsored by Intel and developed in partnership with Slashdot Media, is your
hub for all things parallel software development, from weekly thought
leadership blogs to news, videos, case studies, tutorials and more. Take a
look and join the conversation now. http://goparallel.sourceforge.net
_______________________________________________
Mondo-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/mondo-devel
Reply | Threaded
Open this post in threaded view
|

Re: [Mondo-devel] Segmentation error running mondoarchive v3.2.0-r3332

Gattegno, Victor (GSD CSC / GCC)
Hello Philippe,

Good gdb work, but don't focus on "mondoarchive -v" segmentation fault, it's a known failing bug. It's better to debug mondoarchive with the options that you use.

 In your 27/12/2014 test and post:
 - did you posted too the associated /var/log/mondoarchive.log (compressed) ?
 - you used -I (with / included twice) and -E options, it's better to use only -E option.

What's the result of "ulimit -a" on your Debian ?

I wish to you - and to all this mailig-list users - a nice year 2015.

Rgds,
Victor

-----Original Message-----
From: Philippe Lefevre [mailto:[hidden email]]
Sent: samedi 3 janvier 2015 14:32
To: [hidden email]
Subject: Re: [Mondo-devel] Segmentation error running mondoarchive v3.2.0-r3332

Hi list,

Some more information about my issue.

I can confirm that in my case it is related to this new release as a I did a downgrade and successfully built a new full backup.

I uninstalled and purged
  libmondorescue-perl_3.2.0-1_all.deb
  mindi-busybox_1.21.1-1_amd64.deb
  mindi_3.0.0-1_amd64.deb
  mondo_3.2.0-1_amd64.deb

and reinstalled the previous version
  mindi-busybox 1.18.5-3
  mindi 2.1.7-1
  mondo 3.0.4-1

I also compiled mondo 3.2.0 from sources and ran gdb against the simpliest command that raise the seg error. It shows :

Starting program:
/home/phl/telechargements/mondo-3.2.0/src/mondoarchive/mondoarchive -v [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
mondoarchive v3.2.0-r3332
See man page for help

Program received signal SIGSEGV, Segmentation fault.
0x00007ffff76629aa in vfprintf () from /lib/x86_64-linux-gnu/libc.so.6
(gdb) bt
#0  0x00007ffff76629aa in vfprintf () from /lib/x86_64-linux-gnu/libc.so.6
#1  0x00007ffff7688fca in vasprintf () from /lib/x86_64-linux-gnu/libc.so.6
#2  0x00000000004367c4 in mr_asprintf_int (strp=strp@entry=0x7fffffffe0d0, line=line@entry=258, file=file@entry=0x44187f "libmondo-fork.c",
    fmt=fmt@entry=0x441d38 "%s > %s/mondo-run-prog-thing.tmp 2>
%s/mondo-run-prog-thing.err") at mr_mem.c:62
#3  0x000000000041e0f0 in run_program_and_log_output
(program=program@entry=0x43c4b4 "umount -d /mnt/cdrom",
debug_level=debug_level@entry=0)
    at libmondo-fork.c:258
#4  0x000000000042ec19 in finish (signal=signal@entry=0) at
newt-specific.c:388
#5  0x0000000000403430 in main (argc=2, argv=0x7fffffffe668) at
mondoarchive.c:176
(gdb)


function code exerpt

   56 void mr_asprintf_int(char **strp, int line, const char *file, const char *fmt, ...) {
   57
   58 int res = 0;
   59 va_list args;
   60
   61 va_start(args,fmt);
   62 res = vasprintf(strp, fmt, args);
   63 if (res == -1) {
   64 mr_msg_int(1,line,file,"Unable to alloc memory in
mr_asprintf\nExiting...");
   65 mr_exit(-1,"Unable to alloc memory in mr_asprintf");
   66 }
   67 va_end(args);
   68 }


Breakpoint 1, mr_asprintf_int (strp=strp@entry=0x7fffffffe0d0, line=line@entry=258, file=file@entry=0x44187f "libmondo-fork.c",
    fmt=fmt@entry=0x441d38 "%s > %s/mondo-run-prog-thing.tmp 2>
%s/mondo-run-prog-thing.err") at mr_mem.c:56
56 void mr_asprintf_int(char **strp, int line, const char *file, const
char *fmt, ...) {
(gdb) s
61 va_start(args,fmt);
(gdb) display fmt
1: fmt = 0x441d38 "%s > %s/mondo-run-prog-thing.tmp 2> %s/mondo-run-prog-thing.err"
(gdb) display args
2: args = {{gp_offset = 4158558940, fp_offset = 32767, overflow_arg_area = 0x7ffff7fd5000, reg_save_area = 0x7ffff7ffd9d8}}
(gdb) s
62 res = vasprintf(strp, fmt, args);
2: args = {{gp_offset = 4158558940, fp_offset = 32767, overflow_arg_area = 0x7ffff7fd5000, reg_save_area = 0x7ffff7ffd9d8}}
1: fmt = 0x441d38 "%s > %s/mondo-run-prog-thing.tmp 2> %s/mondo-run-prog-thing.err"
(gdb) s
61 va_start(args,fmt);
2: args = {{gp_offset = 4158558940, fp_offset = 32767, overflow_arg_area = 0x7ffff7fd5000, reg_save_area = 0x7ffff7ffd9d8}}
1: fmt = 0x441d38 "%s > %s/mondo-run-prog-thing.tmp 2> %s/mondo-run-prog-thing.err"
(gdb) s
62 res = vasprintf(strp, fmt, args);
2: args = {{gp_offset = 32, fp_offset = 48, overflow_arg_area = 0x7fffffffe0b0, reg_save_area = 0x7fffffffdfe0}}
1: fmt = 0x441d38 "%s > %s/mondo-run-prog-thing.tmp 2> %s/mondo-run-prog-thing.err"
(gdb) display res
3: res = 0
(gdb) s

Program received signal SIGSEGV, Segmentation fault.
0x00007ffff76629aa in vfprintf () from /lib/x86_64-linux-gnu/libc.so.6
(gdb)


It seems there is an issue with mr_asprintf_int but sorry I don't feel strong enought to get more deeply into the mondo code and analyze it properly ...

I hope this help ...

Regards,
Philippe


Le 27/12/2014 11:17, [hidden email] a écrit :

> Hi all,
>
> it seems that something goes wrong with mondo I could link to the
> latest Debian version of MondoRescue.
>
> I updated my version last thursday and this morning (I have a
> differential backup launched every friday night and one full a month)
> it failed.
> Unfortunately there are no much relevant informations in logs.
>
> The errors raised is :
>
>     # mondoarchive -D -OV -i -N -G -s 780M -p sys-D7.7-diff_141227100000
>     -T /graveur -S /graveur -d
>     /media/sauvegardes/phlsys/D7.7/sys/141227100000 -I
>     "/|/|/opt/calibre|/opt/Zuma" -E
>     "/bases/sybase|/graveur|/home|/opt|/photos|/quemu|/Sauvegardes|/var/crash|/var/backups|/var/log|/var/mail|/var/spool|/vbox|/videos|/www"
>     See /var/log/mondoarchive.log for details of backup run.
>     Checking sanity of your Linux distribution
>     Done.
>     Erreur de segmentation                /* Segmentation error */
>
> Please find attached the log files that seems to find out an issue
> with LVM disks
>
>     INFO: Mindi v3.0.0-r3332
>     INFO: Le disque /dev/mapper/data1vg-photoslv ne contient pas une
>     table de partitions valable
>              /* there is no valid partition table in
>     /dev/mapper/data1vg-photoslv disk */
>
> I have no issues with my LVM disks. Please find on below my LVM disks
> configuration
>
>     lvm> vgs
>       VG      #PV #LV #SN Attr   VSize   VFree
>       data1vg   1   7   0 wz--n- 931,51g 504,60g
>       sysvg     1   1   0 wz--n-  95,12g  78,84g
>
>     lvm> lvs
>       LV        VG      Attr     LSize   Pool Origin Data%  Move Log
>     Copy%  Convert
>       baseslv   data1vg -wi-ao--  
>     1,86g                                          
>       graveurlv data1vg -wi-ao--
>     20,00g                                          
>       homelv    data1vg -wi-ao--
>     50,00g                                          
>       photoslv  data1vg -wi-ao--
>     70,00g                                          
>       vboxlv    data1vg -wi-ao--
>     130,39g                                          
>       videoslv  data1vg -wi-ao--
>     150,00g                                          
>       wwwlv     data1vg -wi-ao--  
>     4,66g                                          
>       optlv     sysvg   -wi-ao--  16,28g
>
>     lvm> lvscan
>       ACTIVE            '/dev/data1vg/photoslv' [70,00 GiB] inherit
>       ACTIVE            '/dev/data1vg/videoslv' [150,00 GiB] inherit
>       ACTIVE            '/dev/data1vg/homelv' [50,00 GiB] inherit
>       ACTIVE            '/dev/data1vg/graveurlv' [20,00 GiB] inherit
>       ACTIVE            '/dev/data1vg/wwwlv' [4,66 GiB] inherit
>       ACTIVE            '/dev/data1vg/baseslv' [1,86 GiB] inherit
>       ACTIVE            '/dev/data1vg/vboxlv' [130,39 GiB] inherit
>       ACTIVE            '/dev/sysvg/optlv' [16,28 GiB] inherit
>
>     root@phlsys:/home/phl/Scripts# df -h
>     Sys. fich.                                             Taille Util.
>     Dispo Uti% Monté sur
>     rootfs                                                    92G  
>     11G   77G  12% /
>     udev                                                      10M    
>     0   10M   0% /dev
>     tmpfs                                                    397M  968K
>     396M   1% /run
>     /dev/disk/by-uuid/4a5a9317-0b70-4796-a094-d61c01891c81    92G  
>     11G   77G  12% /
>     tmpfs                                                    5,0M     0
>     5,0M   0% /run/lock
>     tmpfs                                                    985M  324K
>     985M   1% /run/shm
>     /dev/mapper/sysvg-optlv                                   17G   15G
>     845M  95% /opt
>     /dev/mapper/data1vg-homelv                                50G   40G
>     7,2G  85% /home
>     /dev/mapper/data1vg-wwwlv                                4,6G  2,5G
>     1,9G  58% /www
>     /dev/mapper/data1vg-baseslv                              1,9G  720M
>     1,1G  41% /bases
>     /dev/mapper/data1vg-photoslv                              69G  
>     43G   23G  66% /photos
>     /dev/mapper/data1vg-videoslv                             148G
>     104G   37G  74% /videos
>     /dev/mapper/data1vg-vboxlv                               129G
>     100G   23G  82% /vbox
>     /dev/mapper/data1vg-graveurlv                             20G
>     8,1G   11G  44% /graveur
>
>
> The latest mondo upgrade dated of 25th of december was (it worked fine
> before this upgrade)
>
>     Start-Date: 2014-12-25  18:55:08
>     Commandline: /usr/sbin/synaptic
>     Install: libprojectbuilder-perl:amd64 (0.12.6-1, automatic),
>     libmondorescue-perl:amd64 (3.2.0-1, automatic)
>     Upgrade: mindi:amd64 (2.1.7-1, 3.0.0-1), mondo:amd64 (3.0.4-1,
>     3.2.0-1), mindi-busybox:amd64 (1.18.5-3, 1.21.1-1)
>     End-Date: 2014-12-25  18:55:31
>
> The Debian distro used is
>
>     root@phlsys:/home/phl/Scripts# uname -a
>     Linux phlsys 3.2.0-4-amd64 #1 SMP Debian 3.2.63-2+deb7u2 x86_64
>     GNU/Linux
>
> Anyone have an idea to try to debug this.
>
> Thanks for any help.
>
> By the way, I whish you all an happy new year 2015 with all the best
> in your lifes Kind regards, Philippe
>
>



------------------------------------------------------------------------------
Dive into the World of Parallel Programming! The Go Parallel Website,
sponsored by Intel and developed in partnership with Slashdot Media, is your
hub for all things parallel software development, from weekly thought
leadership blogs to news, videos, case studies, tutorials and more. Take a
look and join the conversation now. http://goparallel.sourceforge.net
_______________________________________________
Mondo-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/mondo-devel
------------------------------------------------------------------------------
Dive into the World of Parallel Programming! The Go Parallel Website,
sponsored by Intel and developed in partnership with Slashdot Media, is your
hub for all things parallel software development, from weekly thought
leadership blogs to news, videos, case studies, tutorials and more. Take a
look and join the conversation now. http://goparallel.sourceforge.net
_______________________________________________
Mondo-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/mondo-devel
Reply | Threaded
Open this post in threaded view
|

Re: [Mondo-devel] Segmentation error running mondoarchive v3.2.0-r3332

Philippe Lefevre
Thanks for your help and reply Victor,

I should be able to replay with all of that before the end of the week
and let you know.
Regarding the double /, it is due to my shell script which build the
final request. I will also do a try without it.

I believe I couldn't remove -I flag as in the exclude part there is /opt
and I want to include only 2 directories /opt/zuma and /opt/calibre. At
least, I should use -I "/opt/calibre|/opt/Zuma" right?

PS: my system backup is run by root and ulimit is setted unlimited:

# ulimit -a
core file size          (blocks, -c) 0
data seg size           (kbytes, -d) unlimited
scheduling priority             (-e) 0
file size               (blocks, -f) unlimited
pending signals                 (-i) 31106
max locked memory       (kbytes, -l) 64
max memory size         (kbytes, -m) unlimited
open files                      (-n) 1024
pipe size            (512 bytes, -p) 8
POSIX message queues     (bytes, -q) 819200
real-time priority              (-r) 0
stack size              (kbytes, -s) 8192
cpu time               (seconds, -t) unlimited
max user processes              (-u) 31106
virtual memory          (kbytes, -v) unlimited
file locks                      (-x) unlimited


Rgds,
Philippe


Le 05/01/2015 16:32, Gattegno, Victor (GSD CSC / GCC) a écrit :

> Hello Philippe,
>
> Good gdb work, but don't focus on "mondoarchive -v" segmentation fault, it's a known failing bug. It's better to debug mondoarchive with the options that you use.
>
>  In your 27/12/2014 test and post:
>  - did you posted too the associated /var/log/mondoarchive.log (compressed) ?
>  - you used -I (with / included twice) and -E options, it's better to use only -E option.
>
> What's the result of "ulimit -a" on your Debian ?
>
> I wish to you - and to all this mailig-list users - a nice year 2015.
>
> Rgds,
> Victor
>
> -----Original Message-----
> From: Philippe Lefevre [mailto:[hidden email]]
> Sent: samedi 3 janvier 2015 14:32
> To: [hidden email]
> Subject: Re: [Mondo-devel] Segmentation error running mondoarchive v3.2.0-r3332
>
> Hi list,
>
> Some more information about my issue.
>
> I can confirm that in my case it is related to this new release as a I did a downgrade and successfully built a new full backup.
>
> I uninstalled and purged
>   libmondorescue-perl_3.2.0-1_all.deb
>   mindi-busybox_1.21.1-1_amd64.deb
>   mindi_3.0.0-1_amd64.deb
>   mondo_3.2.0-1_amd64.deb
>
> and reinstalled the previous version
>   mindi-busybox 1.18.5-3
>   mindi 2.1.7-1
>   mondo 3.0.4-1
>
> I also compiled mondo 3.2.0 from sources and ran gdb against the simpliest command that raise the seg error. It shows :
>
> Starting program:
> /home/phl/telechargements/mondo-3.2.0/src/mondoarchive/mondoarchive -v [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
> mondoarchive v3.2.0-r3332
> See man page for help
>
> Program received signal SIGSEGV, Segmentation fault.
> 0x00007ffff76629aa in vfprintf () from /lib/x86_64-linux-gnu/libc.so.6
> (gdb) bt
> #0  0x00007ffff76629aa in vfprintf () from /lib/x86_64-linux-gnu/libc.so.6
> #1  0x00007ffff7688fca in vasprintf () from /lib/x86_64-linux-gnu/libc.so.6
> #2  0x00000000004367c4 in mr_asprintf_int (strp=strp@entry=0x7fffffffe0d0, line=line@entry=258, file=file@entry=0x44187f "libmondo-fork.c",
>     fmt=fmt@entry=0x441d38 "%s > %s/mondo-run-prog-thing.tmp 2>
> %s/mondo-run-prog-thing.err") at mr_mem.c:62
> #3  0x000000000041e0f0 in run_program_and_log_output
> (program=program@entry=0x43c4b4 "umount -d /mnt/cdrom",
> debug_level=debug_level@entry=0)
>     at libmondo-fork.c:258
> #4  0x000000000042ec19 in finish (signal=signal@entry=0) at
> newt-specific.c:388
> #5  0x0000000000403430 in main (argc=2, argv=0x7fffffffe668) at
> mondoarchive.c:176
> (gdb)
>
>
> function code exerpt
>
>    56 void mr_asprintf_int(char **strp, int line, const char *file, const char *fmt, ...) {
>    57
>    58 int res = 0;
>    59 va_list args;
>    60
>    61 va_start(args,fmt);
>    62 res = vasprintf(strp, fmt, args);
>    63 if (res == -1) {
>    64 mr_msg_int(1,line,file,"Unable to alloc memory in
> mr_asprintf\nExiting...");
>    65 mr_exit(-1,"Unable to alloc memory in mr_asprintf");
>    66 }
>    67 va_end(args);
>    68 }
>
>
> Breakpoint 1, mr_asprintf_int (strp=strp@entry=0x7fffffffe0d0, line=line@entry=258, file=file@entry=0x44187f "libmondo-fork.c",
>     fmt=fmt@entry=0x441d38 "%s > %s/mondo-run-prog-thing.tmp 2>
> %s/mondo-run-prog-thing.err") at mr_mem.c:56
> 56 void mr_asprintf_int(char **strp, int line, const char *file, const
> char *fmt, ...) {
> (gdb) s
> 61 va_start(args,fmt);
> (gdb) display fmt
> 1: fmt = 0x441d38 "%s > %s/mondo-run-prog-thing.tmp 2> %s/mondo-run-prog-thing.err"
> (gdb) display args
> 2: args = {{gp_offset = 4158558940, fp_offset = 32767, overflow_arg_area = 0x7ffff7fd5000, reg_save_area = 0x7ffff7ffd9d8}}
> (gdb) s
> 62 res = vasprintf(strp, fmt, args);
> 2: args = {{gp_offset = 4158558940, fp_offset = 32767, overflow_arg_area = 0x7ffff7fd5000, reg_save_area = 0x7ffff7ffd9d8}}
> 1: fmt = 0x441d38 "%s > %s/mondo-run-prog-thing.tmp 2> %s/mondo-run-prog-thing.err"
> (gdb) s
> 61 va_start(args,fmt);
> 2: args = {{gp_offset = 4158558940, fp_offset = 32767, overflow_arg_area = 0x7ffff7fd5000, reg_save_area = 0x7ffff7ffd9d8}}
> 1: fmt = 0x441d38 "%s > %s/mondo-run-prog-thing.tmp 2> %s/mondo-run-prog-thing.err"
> (gdb) s
> 62 res = vasprintf(strp, fmt, args);
> 2: args = {{gp_offset = 32, fp_offset = 48, overflow_arg_area = 0x7fffffffe0b0, reg_save_area = 0x7fffffffdfe0}}
> 1: fmt = 0x441d38 "%s > %s/mondo-run-prog-thing.tmp 2> %s/mondo-run-prog-thing.err"
> (gdb) display res
> 3: res = 0
> (gdb) s
>
> Program received signal SIGSEGV, Segmentation fault.
> 0x00007ffff76629aa in vfprintf () from /lib/x86_64-linux-gnu/libc.so.6
> (gdb)
>
>
> It seems there is an issue with mr_asprintf_int but sorry I don't feel strong enought to get more deeply into the mondo code and analyze it properly ...
>
> I hope this help ...
>
> Regards,
> Philippe
>
>
> Le 27/12/2014 11:17, [hidden email] a écrit :
>> Hi all,
>>
>> it seems that something goes wrong with mondo I could link to the
>> latest Debian version of MondoRescue.
>>
>> I updated my version last thursday and this morning (I have a
>> differential backup launched every friday night and one full a month)
>> it failed.
>> Unfortunately there are no much relevant informations in logs.
>>
>> The errors raised is :
>>
>>     # mondoarchive -D -OV -i -N -G -s 780M -p sys-D7.7-diff_141227100000
>>     -T /graveur -S /graveur -d
>>     /media/sauvegardes/phlsys/D7.7/sys/141227100000 -I
>>     "/|/|/opt/calibre|/opt/Zuma" -E
>>     "/bases/sybase|/graveur|/home|/opt|/photos|/quemu|/Sauvegardes|/var/crash|/var/backups|/var/log|/var/mail|/var/spool|/vbox|/videos|/www"
>>     See /var/log/mondoarchive.log for details of backup run.
>>     Checking sanity of your Linux distribution
>>     Done.
>>     Erreur de segmentation                /* Segmentation error */
>>
>> Please find attached the log files that seems to find out an issue
>> with LVM disks
>>
>>     INFO: Mindi v3.0.0-r3332
>>     INFO: Le disque /dev/mapper/data1vg-photoslv ne contient pas une
>>     table de partitions valable
>>              /* there is no valid partition table in
>>     /dev/mapper/data1vg-photoslv disk */
>>
>> I have no issues with my LVM disks. Please find on below my LVM disks
>> configuration
>>
>>     lvm> vgs
>>       VG      #PV #LV #SN Attr   VSize   VFree
>>       data1vg   1   7   0 wz--n- 931,51g 504,60g
>>       sysvg     1   1   0 wz--n-  95,12g  78,84g
>>
>>     lvm> lvs
>>       LV        VG      Attr     LSize   Pool Origin Data%  Move Log
>>     Copy%  Convert
>>       baseslv   data1vg -wi-ao--  
>>     1,86g                                          
>>       graveurlv data1vg -wi-ao--
>>     20,00g                                          
>>       homelv    data1vg -wi-ao--
>>     50,00g                                          
>>       photoslv  data1vg -wi-ao--
>>     70,00g                                          
>>       vboxlv    data1vg -wi-ao--
>>     130,39g                                          
>>       videoslv  data1vg -wi-ao--
>>     150,00g                                          
>>       wwwlv     data1vg -wi-ao--  
>>     4,66g                                          
>>       optlv     sysvg   -wi-ao--  16,28g
>>
>>     lvm> lvscan
>>       ACTIVE            '/dev/data1vg/photoslv' [70,00 GiB] inherit
>>       ACTIVE            '/dev/data1vg/videoslv' [150,00 GiB] inherit
>>       ACTIVE            '/dev/data1vg/homelv' [50,00 GiB] inherit
>>       ACTIVE            '/dev/data1vg/graveurlv' [20,00 GiB] inherit
>>       ACTIVE            '/dev/data1vg/wwwlv' [4,66 GiB] inherit
>>       ACTIVE            '/dev/data1vg/baseslv' [1,86 GiB] inherit
>>       ACTIVE            '/dev/data1vg/vboxlv' [130,39 GiB] inherit
>>       ACTIVE            '/dev/sysvg/optlv' [16,28 GiB] inherit
>>
>>     root@phlsys:/home/phl/Scripts# df -h
>>     Sys. fich.                                             Taille Util.
>>     Dispo Uti% Monté sur
>>     rootfs                                                    92G  
>>     11G   77G  12% /
>>     udev                                                      10M    
>>     0   10M   0% /dev
>>     tmpfs                                                    397M  968K
>>     396M   1% /run
>>     /dev/disk/by-uuid/4a5a9317-0b70-4796-a094-d61c01891c81    92G  
>>     11G   77G  12% /
>>     tmpfs                                                    5,0M     0
>>     5,0M   0% /run/lock
>>     tmpfs                                                    985M  324K
>>     985M   1% /run/shm
>>     /dev/mapper/sysvg-optlv                                   17G   15G
>>     845M  95% /opt
>>     /dev/mapper/data1vg-homelv                                50G   40G
>>     7,2G  85% /home
>>     /dev/mapper/data1vg-wwwlv                                4,6G  2,5G
>>     1,9G  58% /www
>>     /dev/mapper/data1vg-baseslv                              1,9G  720M
>>     1,1G  41% /bases
>>     /dev/mapper/data1vg-photoslv                              69G  
>>     43G   23G  66% /photos
>>     /dev/mapper/data1vg-videoslv                             148G
>>     104G   37G  74% /videos
>>     /dev/mapper/data1vg-vboxlv                               129G
>>     100G   23G  82% /vbox
>>     /dev/mapper/data1vg-graveurlv                             20G
>>     8,1G   11G  44% /graveur
>>
>>
>> The latest mondo upgrade dated of 25th of december was (it worked fine
>> before this upgrade)
>>
>>     Start-Date: 2014-12-25  18:55:08
>>     Commandline: /usr/sbin/synaptic
>>     Install: libprojectbuilder-perl:amd64 (0.12.6-1, automatic),
>>     libmondorescue-perl:amd64 (3.2.0-1, automatic)
>>     Upgrade: mindi:amd64 (2.1.7-1, 3.0.0-1), mondo:amd64 (3.0.4-1,
>>     3.2.0-1), mindi-busybox:amd64 (1.18.5-3, 1.21.1-1)
>>     End-Date: 2014-12-25  18:55:31
>>
>> The Debian distro used is
>>
>>     root@phlsys:/home/phl/Scripts# uname -a
>>     Linux phlsys 3.2.0-4-amd64 #1 SMP Debian 3.2.63-2+deb7u2 x86_64
>>     GNU/Linux
>>
>> Anyone have an idea to try to debug this.
>>
>> Thanks for any help.
>>
>> By the way, I whish you all an happy new year 2015 with all the best
>> in your lifes Kind regards, Philippe
>>
>>
>
>
>
> ------------------------------------------------------------------------------
> Dive into the World of Parallel Programming! The Go Parallel Website,
> sponsored by Intel and developed in partnership with Slashdot Media, is your
> hub for all things parallel software development, from weekly thought
> leadership blogs to news, videos, case studies, tutorials and more. Take a
> look and join the conversation now. http://goparallel.sourceforge.net
> _______________________________________________
> Mondo-devel mailing list
> [hidden email]
> https://lists.sourceforge.net/lists/listinfo/mondo-devel
> ------------------------------------------------------------------------------
> Dive into the World of Parallel Programming! The Go Parallel Website,
> sponsored by Intel and developed in partnership with Slashdot Media, is your
> hub for all things parallel software development, from weekly thought
> leadership blogs to news, videos, case studies, tutorials and more. Take a
> look and join the conversation now. http://goparallel.sourceforge.net
> _______________________________________________
> Mondo-devel mailing list
> [hidden email]
> https://lists.sourceforge.net/lists/listinfo/mondo-devel
>



------------------------------------------------------------------------------
Dive into the World of Parallel Programming! The Go Parallel Website,
sponsored by Intel and developed in partnership with Slashdot Media, is your
hub for all things parallel software development, from weekly thought
leadership blogs to news, videos, case studies, tutorials and more. Take a
look and join the conversation now. http://goparallel.sourceforge.net
_______________________________________________
Mondo-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/mondo-devel
Reply | Threaded
Open this post in threaded view
|

Re: [Mondo-devel] Segmentation error running mondoarchive v3.2.0-r3332

Gattegno, Victor (GSD CSC / GCC)
Hello Philippe,

From mondoarchive man : " When using the -I option with the -E option, the -E content should be subdirectories of those mentioned in the -I only, as -I takes precedence."

But if your -I and -E combination works it's ok (check if /opt/zuma and /opt/calibre are well backuped and restored).

Regards,
Victor

-----Original Message-----
From: Philippe Lefevre [mailto:[hidden email]]
Sent: lundi 5 janvier 2015 21:42
To: [hidden email]
Subject: Re: [Mondo-devel] Segmentation error running mondoarchive v3.2.0-r3332

Thanks for your help and reply Victor,

I should be able to replay with all of that before the end of the week and let you know.
Regarding the double /, it is due to my shell script which build the final request. I will also do a try without it.

I believe I couldn't remove -I flag as in the exclude part there is /opt and I want to include only 2 directories /opt/zuma and /opt/calibre. At least, I should use -I "/opt/calibre|/opt/Zuma" right?

PS: my system backup is run by root and ulimit is setted unlimited:

# ulimit -a
core file size          (blocks, -c) 0
data seg size           (kbytes, -d) unlimited
scheduling priority             (-e) 0
file size               (blocks, -f) unlimited
pending signals                 (-i) 31106
max locked memory       (kbytes, -l) 64
max memory size         (kbytes, -m) unlimited
open files                      (-n) 1024
pipe size            (512 bytes, -p) 8
POSIX message queues     (bytes, -q) 819200
real-time priority              (-r) 0
stack size              (kbytes, -s) 8192
cpu time               (seconds, -t) unlimited
max user processes              (-u) 31106
virtual memory          (kbytes, -v) unlimited
file locks                      (-x) unlimited


Rgds,
Philippe


Le 05/01/2015 16:32, Gattegno, Victor (GSD CSC / GCC) a écrit :

> Hello Philippe,
>
> Good gdb work, but don't focus on "mondoarchive -v" segmentation fault, it's a known failing bug. It's better to debug mondoarchive with the options that you use.
>
>  In your 27/12/2014 test and post:
>  - did you posted too the associated /var/log/mondoarchive.log (compressed) ?
>  - you used -I (with / included twice) and -E options, it's better to use only -E option.
>
> What's the result of "ulimit -a" on your Debian ?
>
> I wish to you - and to all this mailig-list users - a nice year 2015.
>
> Rgds,
> Victor
>
> -----Original Message-----
> From: Philippe Lefevre [mailto:[hidden email]]
> Sent: samedi 3 janvier 2015 14:32
> To: [hidden email]
> Subject: Re: [Mondo-devel] Segmentation error running mondoarchive
> v3.2.0-r3332
>
> Hi list,
>
> Some more information about my issue.
>
> I can confirm that in my case it is related to this new release as a I did a downgrade and successfully built a new full backup.
>
> I uninstalled and purged
>   libmondorescue-perl_3.2.0-1_all.deb
>   mindi-busybox_1.21.1-1_amd64.deb
>   mindi_3.0.0-1_amd64.deb
>   mondo_3.2.0-1_amd64.deb
>
> and reinstalled the previous version
>   mindi-busybox 1.18.5-3
>   mindi 2.1.7-1
>   mondo 3.0.4-1
>
> I also compiled mondo 3.2.0 from sources and ran gdb against the simpliest command that raise the seg error. It shows :
>
> Starting program:
> /home/phl/telechargements/mondo-3.2.0/src/mondoarchive/mondoarchive -v [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
> mondoarchive v3.2.0-r3332
> See man page for help
>
> Program received signal SIGSEGV, Segmentation fault.
> 0x00007ffff76629aa in vfprintf () from /lib/x86_64-linux-gnu/libc.so.6
> (gdb) bt
> #0  0x00007ffff76629aa in vfprintf () from
> /lib/x86_64-linux-gnu/libc.so.6
> #1  0x00007ffff7688fca in vasprintf () from
> /lib/x86_64-linux-gnu/libc.so.6
> #2  0x00000000004367c4 in mr_asprintf_int (strp=strp@entry=0x7fffffffe0d0, line=line@entry=258, file=file@entry=0x44187f "libmondo-fork.c",
>     fmt=fmt@entry=0x441d38 "%s > %s/mondo-run-prog-thing.tmp 2>
> %s/mondo-run-prog-thing.err") at mr_mem.c:62
> #3  0x000000000041e0f0 in run_program_and_log_output
> (program=program@entry=0x43c4b4 "umount -d /mnt/cdrom",
> debug_level=debug_level@entry=0)
>     at libmondo-fork.c:258
> #4  0x000000000042ec19 in finish (signal=signal@entry=0) at
> newt-specific.c:388
> #5  0x0000000000403430 in main (argc=2, argv=0x7fffffffe668) at
> mondoarchive.c:176
> (gdb)
>
>
> function code exerpt
>
>    56 void mr_asprintf_int(char **strp, int line, const char *file, const char *fmt, ...) {
>    57
>    58 int res = 0;
>    59 va_list args;
>    60
>    61 va_start(args,fmt);
>    62 res = vasprintf(strp, fmt, args);
>    63 if (res == -1) {
>    64 mr_msg_int(1,line,file,"Unable to alloc memory in
> mr_asprintf\nExiting...");
>    65 mr_exit(-1,"Unable to alloc memory in mr_asprintf");
>    66 }
>    67 va_end(args);
>    68 }
>
>
> Breakpoint 1, mr_asprintf_int (strp=strp@entry=0x7fffffffe0d0, line=line@entry=258, file=file@entry=0x44187f "libmondo-fork.c",
>     fmt=fmt@entry=0x441d38 "%s > %s/mondo-run-prog-thing.tmp 2>
> %s/mondo-run-prog-thing.err") at mr_mem.c:56
> 56 void mr_asprintf_int(char **strp, int line, const char *file, const
> char *fmt, ...) {
> (gdb) s
> 61 va_start(args,fmt);
> (gdb) display fmt
> 1: fmt = 0x441d38 "%s > %s/mondo-run-prog-thing.tmp 2> %s/mondo-run-prog-thing.err"
> (gdb) display args
> 2: args = {{gp_offset = 4158558940, fp_offset = 32767,
> overflow_arg_area = 0x7ffff7fd5000, reg_save_area = 0x7ffff7ffd9d8}}
> (gdb) s
> 62 res = vasprintf(strp, fmt, args);
> 2: args = {{gp_offset = 4158558940, fp_offset = 32767,
> overflow_arg_area = 0x7ffff7fd5000, reg_save_area = 0x7ffff7ffd9d8}}
> 1: fmt = 0x441d38 "%s > %s/mondo-run-prog-thing.tmp 2> %s/mondo-run-prog-thing.err"
> (gdb) s
> 61 va_start(args,fmt);
> 2: args = {{gp_offset = 4158558940, fp_offset = 32767,
> overflow_arg_area = 0x7ffff7fd5000, reg_save_area = 0x7ffff7ffd9d8}}
> 1: fmt = 0x441d38 "%s > %s/mondo-run-prog-thing.tmp 2> %s/mondo-run-prog-thing.err"
> (gdb) s
> 62 res = vasprintf(strp, fmt, args);
> 2: args = {{gp_offset = 32, fp_offset = 48, overflow_arg_area =
> 0x7fffffffe0b0, reg_save_area = 0x7fffffffdfe0}}
> 1: fmt = 0x441d38 "%s > %s/mondo-run-prog-thing.tmp 2> %s/mondo-run-prog-thing.err"
> (gdb) display res
> 3: res = 0
> (gdb) s
>
> Program received signal SIGSEGV, Segmentation fault.
> 0x00007ffff76629aa in vfprintf () from /lib/x86_64-linux-gnu/libc.so.6
> (gdb)
>
>
> It seems there is an issue with mr_asprintf_int but sorry I don't feel strong enought to get more deeply into the mondo code and analyze it properly ...
>
> I hope this help ...
>
> Regards,
> Philippe
>
>
> Le 27/12/2014 11:17, [hidden email] a écrit :
>> Hi all,
>>
>> it seems that something goes wrong with mondo I could link to the
>> latest Debian version of MondoRescue.
>>
>> I updated my version last thursday and this morning (I have a
>> differential backup launched every friday night and one full a month)
>> it failed.
>> Unfortunately there are no much relevant informations in logs.
>>
>> The errors raised is :
>>
>>     # mondoarchive -D -OV -i -N -G -s 780M -p sys-D7.7-diff_141227100000
>>     -T /graveur -S /graveur -d
>>     /media/sauvegardes/phlsys/D7.7/sys/141227100000 -I
>>     "/|/|/opt/calibre|/opt/Zuma" -E
>>     "/bases/sybase|/graveur|/home|/opt|/photos|/quemu|/Sauvegardes|/var/crash|/var/backups|/var/log|/var/mail|/var/spool|/vbox|/videos|/www"
>>     See /var/log/mondoarchive.log for details of backup run.
>>     Checking sanity of your Linux distribution
>>     Done.
>>     Erreur de segmentation                /* Segmentation error */
>>
>> Please find attached the log files that seems to find out an issue
>> with LVM disks
>>
>>     INFO: Mindi v3.0.0-r3332
>>     INFO: Le disque /dev/mapper/data1vg-photoslv ne contient pas une
>>     table de partitions valable
>>              /* there is no valid partition table in
>>     /dev/mapper/data1vg-photoslv disk */
>>
>> I have no issues with my LVM disks. Please find on below my LVM disks
>> configuration
>>
>>     lvm> vgs
>>       VG      #PV #LV #SN Attr   VSize   VFree
>>       data1vg   1   7   0 wz--n- 931,51g 504,60g
>>       sysvg     1   1   0 wz--n-  95,12g  78,84g
>>
>>     lvm> lvs
>>       LV        VG      Attr     LSize   Pool Origin Data%  Move Log
>>     Copy%  Convert
>>       baseslv   data1vg -wi-ao--  
>>     1,86g                                          
>>       graveurlv data1vg -wi-ao--
>>     20,00g                                          
>>       homelv    data1vg -wi-ao--
>>     50,00g                                          
>>       photoslv  data1vg -wi-ao--
>>     70,00g                                          
>>       vboxlv    data1vg -wi-ao--
>>     130,39g                                          
>>       videoslv  data1vg -wi-ao--
>>     150,00g                                          
>>       wwwlv     data1vg -wi-ao--  
>>     4,66g                                          
>>       optlv     sysvg   -wi-ao--  16,28g
>>
>>     lvm> lvscan
>>       ACTIVE            '/dev/data1vg/photoslv' [70,00 GiB] inherit
>>       ACTIVE            '/dev/data1vg/videoslv' [150,00 GiB] inherit
>>       ACTIVE            '/dev/data1vg/homelv' [50,00 GiB] inherit
>>       ACTIVE            '/dev/data1vg/graveurlv' [20,00 GiB] inherit
>>       ACTIVE            '/dev/data1vg/wwwlv' [4,66 GiB] inherit
>>       ACTIVE            '/dev/data1vg/baseslv' [1,86 GiB] inherit
>>       ACTIVE            '/dev/data1vg/vboxlv' [130,39 GiB] inherit
>>       ACTIVE            '/dev/sysvg/optlv' [16,28 GiB] inherit
>>
>>     root@phlsys:/home/phl/Scripts# df -h
>>     Sys. fich.                                             Taille Util.
>>     Dispo Uti% Monté sur
>>     rootfs                                                    92G  
>>     11G   77G  12% /
>>     udev                                                      10M    
>>     0   10M   0% /dev
>>     tmpfs                                                    397M  968K
>>     396M   1% /run
>>     /dev/disk/by-uuid/4a5a9317-0b70-4796-a094-d61c01891c81    92G  
>>     11G   77G  12% /
>>     tmpfs                                                    5,0M     0
>>     5,0M   0% /run/lock
>>     tmpfs                                                    985M  324K
>>     985M   1% /run/shm
>>     /dev/mapper/sysvg-optlv                                   17G   15G
>>     845M  95% /opt
>>     /dev/mapper/data1vg-homelv                                50G   40G
>>     7,2G  85% /home
>>     /dev/mapper/data1vg-wwwlv                                4,6G  2,5G
>>     1,9G  58% /www
>>     /dev/mapper/data1vg-baseslv                              1,9G  720M
>>     1,1G  41% /bases
>>     /dev/mapper/data1vg-photoslv                              69G  
>>     43G   23G  66% /photos
>>     /dev/mapper/data1vg-videoslv                             148G
>>     104G   37G  74% /videos
>>     /dev/mapper/data1vg-vboxlv                               129G
>>     100G   23G  82% /vbox
>>     /dev/mapper/data1vg-graveurlv                             20G
>>     8,1G   11G  44% /graveur
>>
>>
>> The latest mondo upgrade dated of 25th of december was (it worked
>> fine before this upgrade)
>>
>>     Start-Date: 2014-12-25  18:55:08
>>     Commandline: /usr/sbin/synaptic
>>     Install: libprojectbuilder-perl:amd64 (0.12.6-1, automatic),
>>     libmondorescue-perl:amd64 (3.2.0-1, automatic)
>>     Upgrade: mindi:amd64 (2.1.7-1, 3.0.0-1), mondo:amd64 (3.0.4-1,
>>     3.2.0-1), mindi-busybox:amd64 (1.18.5-3, 1.21.1-1)
>>     End-Date: 2014-12-25  18:55:31
>>
>> The Debian distro used is
>>
>>     root@phlsys:/home/phl/Scripts# uname -a
>>     Linux phlsys 3.2.0-4-amd64 #1 SMP Debian 3.2.63-2+deb7u2 x86_64
>>     GNU/Linux
>>
>> Anyone have an idea to try to debug this.
>>
>> Thanks for any help.
>>
>> By the way, I whish you all an happy new year 2015 with all the best
>> in your lifes Kind regards, Philippe
>>
>>
>
>
>
> ----------------------------------------------------------------------
> -------- Dive into the World of Parallel Programming! The Go Parallel
> Website, sponsored by Intel and developed in partnership with Slashdot
> Media, is your hub for all things parallel software development, from
> weekly thought leadership blogs to news, videos, case studies,
> tutorials and more. Take a look and join the conversation now.
> http://goparallel.sourceforge.net 
> _______________________________________________
> Mondo-devel mailing list
> [hidden email]
> https://lists.sourceforge.net/lists/listinfo/mondo-devel
> ----------------------------------------------------------------------
> -------- Dive into the World of Parallel Programming! The Go Parallel
> Website, sponsored by Intel and developed in partnership with Slashdot
> Media, is your hub for all things parallel software development, from
> weekly thought leadership blogs to news, videos, case studies,
> tutorials and more. Take a look and join the conversation now.
> http://goparallel.sourceforge.net 
> _______________________________________________
> Mondo-devel mailing list
> [hidden email]
> https://lists.sourceforge.net/lists/listinfo/mondo-devel
>



------------------------------------------------------------------------------
Dive into the World of Parallel Programming! The Go Parallel Website, sponsored by Intel and developed in partnership with Slashdot Media, is your hub for all things parallel software development, from weekly thought leadership blogs to news, videos, case studies, tutorials and more. Take a look and join the conversation now. http://goparallel.sourceforge.net _______________________________________________
Mondo-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/mondo-devel
------------------------------------------------------------------------------
Dive into the World of Parallel Programming! The Go Parallel Website,
sponsored by Intel and developed in partnership with Slashdot Media, is your
hub for all things parallel software development, from weekly thought
leadership blogs to news, videos, case studies, tutorials and more. Take a
look and join the conversation now. http://goparallel.sourceforge.net
_______________________________________________
Mondo-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/mondo-devel
Reply | Threaded
Open this post in threaded view
|

Re: [Mondo-devel] Segmentation error running mondoarchive v3.2.0-r3332

Philippe Lefevre
Hello list,

sorry Gaetagno for the delay, I was not able to find some time long
enought to go back into my issue.

I did it today (without removing the two slashes in order to be in the
same situation) and .... what I compiled worked fine with what I have
compiled. (I noticed the -v bug, thanks  ;)  )

Run mondoarchive via dbg:
[phlsys]root:/home/phl/mondo-3.2.0# gdb -args mondoarchive -D -OV -i -N
-G -s 780M -p sys-D7.7-diff_150105212200 -T /graveur -S /graveur -d
/graveur -I "/|/|/opt/Zuma" -E
"/bases/sybase|/graveur|/home|/opt|/photos|/quemu|/Sauvegardes|/var/crash|/var/backups|/var/log|/var/mail|/var/spool|/vbox|/videos|/www"

and:
....
Data archived OK.
Mondoarchive ran OK.
See /var/log/mondoarchive.log for details of backup run.
Execution run ended; result=0
Type 'less /var/log/mondoarchive.log' to see the output log
[Inferior 1 (process 19382) exited normally]
(gdb) quit


So I reinstalled the official debian package:

Sélection du paquet libmondorescue-perl précédemment désélectionné.
(Lecture de la base de données... 279208 fichiers et répertoires déjà
installés.)
Dépaquetage de libmondorescue-perl (à partir de
.../libmondorescue-perl_3.2.0-1_all.deb) ...
Préparation du remplacement de mindi-busybox 1.18.5-3 (en utilisant
.../mindi-busybox_1.21.1-1_amd64.deb) ...
Dépaquetage de la mise à jour de mindi-busybox ...
Préparation du remplacement de mindi 2.1.7-1 (en utilisant
.../mindi_3.0.0-1_amd64.deb) ...
Dépaquetage de la mise à jour de mindi ...
Préparation du remplacement de mondo 3.0.4-1 (en utilisant
.../mondo_3.2.0-1_amd64.deb) ...
Dépaquetage de la mise à jour de mondo ...
Traitement des actions différées (« triggers ») pour « man-db »...
Paramétrage de libmondorescue-perl (3.2.0-1) ...
Paramétrage de mindi-busybox (1.21.1-1) ...
Paramétrage de mindi (3.0.0-1) ...
Installation de la nouvelle version du fichier de configuration
/etc/mindi/deplist.d/minimal.conf ...
Installation de la nouvelle version du fichier de configuration
/etc/mindi/deplist.d/udev.conf ...
Installation de la nouvelle version du fichier de configuration
/etc/mindi/deplist.d/ProLiant.conf ...
Installation de la nouvelle version du fichier de configuration
/etc/mindi/deplist.d/base.conf ...
Installation de la nouvelle version du fichier de configuration
/etc/mindi/deplist.d/lvm.conf ...
Installation de la nouvelle version du fichier de configuration
/etc/mindi/perl-scripts ...
Paramétrage de mondo (3.2.0-1) ...


but launched in the same way, it crashed again with a segmentation error:

[phlsys]root:/home/phl/telechargements/mondo-3.2.0# mondoarchive -D -OV
-i -N -G -s 780M -p sys-D7.7-diff_150105212200 -T /graveur -S /graveur
-d /graveur -I "/|/|/opt/Zuma" -E
"/bases/sybase|/graveur|/home|/opt|/photos|/quemu|/Sauvegardes|/var/crash|/var/backups|/var/log|/var/mail|/var/spool|/vbox|/videos|/www"
See /var/log/mondoarchive.log for details of backup run.
Checking sanity of your Linux distribution
Done.
Erreur de segmentation



Please find attached the relevant mondoarchive.log file.
It seems to be stopped before logging something about the fault.
I franckly don't know what I could do more.
Do you have an idea about what I could do to explore deeper this issue ?
Something might be going wrong into the deb pkg ???
I got it with apt using:
   deb ftp://ftp.mondorescue.org//debian 7 contrib


Thanks for your help.
Regards,
Philippe





Le 06/01/2015 17:28, Gattegno, Victor (GSD CSC / GCC) a écrit :

> Hello Philippe,
>
> From mondoarchive man : " When using the -I option with the -E option, the -E content should be subdirectories of those mentioned in the -I only, as -I takes precedence."
>
> But if your -I and -E combination works it's ok (check if /opt/zuma and /opt/calibre are well backuped and restored).
>
> Regards,
> Victor
>
> -----Original Message-----
> From: Philippe Lefevre [mailto:[hidden email]]
> Sent: lundi 5 janvier 2015 21:42
> To: [hidden email]
> Subject: Re: [Mondo-devel] Segmentation error running mondoarchive v3.2.0-r3332
>
> Thanks for your help and reply Victor,
>
> I should be able to replay with all of that before the end of the week and let you know.
> Regarding the double /, it is due to my shell script which build the final request. I will also do a try without it.
>
> I believe I couldn't remove -I flag as in the exclude part there is /opt and I want to include only 2 directories /opt/zuma and /opt/calibre. At least, I should use -I "/opt/calibre|/opt/Zuma" right?
>
> PS: my system backup is run by root and ulimit is setted unlimited:
>
> # ulimit -a
> core file size          (blocks, -c) 0
> data seg size           (kbytes, -d) unlimited
> scheduling priority             (-e) 0
> file size               (blocks, -f) unlimited
> pending signals                 (-i) 31106
> max locked memory       (kbytes, -l) 64
> max memory size         (kbytes, -m) unlimited
> open files                      (-n) 1024
> pipe size            (512 bytes, -p) 8
> POSIX message queues     (bytes, -q) 819200
> real-time priority              (-r) 0
> stack size              (kbytes, -s) 8192
> cpu time               (seconds, -t) unlimited
> max user processes              (-u) 31106
> virtual memory          (kbytes, -v) unlimited
> file locks                      (-x) unlimited
>
>
> Rgds,
> Philippe
>
>
> Le 05/01/2015 16:32, Gattegno, Victor (GSD CSC / GCC) a écrit :
>> Hello Philippe,
>>
>> Good gdb work, but don't focus on "mondoarchive -v" segmentation fault, it's a known failing bug. It's better to debug mondoarchive with the options that you use.
>>
>>  In your 27/12/2014 test and post:
>>  - did you posted too the associated /var/log/mondoarchive.log (compressed) ?
>>  - you used -I (with / included twice) and -E options, it's better to use only -E option.
>>
>> What's the result of "ulimit -a" on your Debian ?
>>
>> I wish to you - and to all this mailig-list users - a nice year 2015.
>>
>> Rgds,
>> Victor
>>
>> -----Original Message-----
>> From: Philippe Lefevre [mailto:[hidden email]]
>> Sent: samedi 3 janvier 2015 14:32
>> To: [hidden email]
>> Subject: Re: [Mondo-devel] Segmentation error running mondoarchive
>> v3.2.0-r3332
>>
>> Hi list,
>>
>> Some more information about my issue.
>>
>> I can confirm that in my case it is related to this new release as a I did a downgrade and successfully built a new full backup.
>>
>> I uninstalled and purged
>>   libmondorescue-perl_3.2.0-1_all.deb
>>   mindi-busybox_1.21.1-1_amd64.deb
>>   mindi_3.0.0-1_amd64.deb
>>   mondo_3.2.0-1_amd64.deb
>>
>> and reinstalled the previous version
>>   mindi-busybox 1.18.5-3
>>   mindi 2.1.7-1
>>   mondo 3.0.4-1
>>
>> I also compiled mondo 3.2.0 from sources and ran gdb against the simpliest command that raise the seg error. It shows :
>>
>> Starting program:
>> /home/phl/telechargements/mondo-3.2.0/src/mondoarchive/mondoarchive -v [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
>> mondoarchive v3.2.0-r3332
>> See man page for help
>>
>> Program received signal SIGSEGV, Segmentation fault.
>> 0x00007ffff76629aa in vfprintf () from /lib/x86_64-linux-gnu/libc.so.6
>> (gdb) bt
>> #0  0x00007ffff76629aa in vfprintf () from
>> /lib/x86_64-linux-gnu/libc.so.6
>> #1  0x00007ffff7688fca in vasprintf () from
>> /lib/x86_64-linux-gnu/libc.so.6
>> #2  0x00000000004367c4 in mr_asprintf_int (strp=strp@entry=0x7fffffffe0d0, line=line@entry=258, file=file@entry=0x44187f "libmondo-fork.c",
>>     fmt=fmt@entry=0x441d38 "%s > %s/mondo-run-prog-thing.tmp 2>
>> %s/mondo-run-prog-thing.err") at mr_mem.c:62
>> #3  0x000000000041e0f0 in run_program_and_log_output
>> (program=program@entry=0x43c4b4 "umount -d /mnt/cdrom",
>> debug_level=debug_level@entry=0)
>>     at libmondo-fork.c:258
>> #4  0x000000000042ec19 in finish (signal=signal@entry=0) at
>> newt-specific.c:388
>> #5  0x0000000000403430 in main (argc=2, argv=0x7fffffffe668) at
>> mondoarchive.c:176
>> (gdb)
>>
>>
>> function code exerpt
>>
>>    56 void mr_asprintf_int(char **strp, int line, const char *file, const char *fmt, ...) {
>>    57
>>    58 int res = 0;
>>    59 va_list args;
>>    60
>>    61 va_start(args,fmt);
>>    62 res = vasprintf(strp, fmt, args);
>>    63 if (res == -1) {
>>    64 mr_msg_int(1,line,file,"Unable to alloc memory in
>> mr_asprintf\nExiting...");
>>    65 mr_exit(-1,"Unable to alloc memory in mr_asprintf");
>>    66 }
>>    67 va_end(args);
>>    68 }
>>
>>
>> Breakpoint 1, mr_asprintf_int (strp=strp@entry=0x7fffffffe0d0, line=line@entry=258, file=file@entry=0x44187f "libmondo-fork.c",
>>     fmt=fmt@entry=0x441d38 "%s > %s/mondo-run-prog-thing.tmp 2>
>> %s/mondo-run-prog-thing.err") at mr_mem.c:56
>> 56 void mr_asprintf_int(char **strp, int line, const char *file, const
>> char *fmt, ...) {
>> (gdb) s
>> 61 va_start(args,fmt);
>> (gdb) display fmt
>> 1: fmt = 0x441d38 "%s > %s/mondo-run-prog-thing.tmp 2> %s/mondo-run-prog-thing.err"
>> (gdb) display args
>> 2: args = {{gp_offset = 4158558940, fp_offset = 32767,
>> overflow_arg_area = 0x7ffff7fd5000, reg_save_area = 0x7ffff7ffd9d8}}
>> (gdb) s
>> 62 res = vasprintf(strp, fmt, args);
>> 2: args = {{gp_offset = 4158558940, fp_offset = 32767,
>> overflow_arg_area = 0x7ffff7fd5000, reg_save_area = 0x7ffff7ffd9d8}}
>> 1: fmt = 0x441d38 "%s > %s/mondo-run-prog-thing.tmp 2> %s/mondo-run-prog-thing.err"
>> (gdb) s
>> 61 va_start(args,fmt);
>> 2: args = {{gp_offset = 4158558940, fp_offset = 32767,
>> overflow_arg_area = 0x7ffff7fd5000, reg_save_area = 0x7ffff7ffd9d8}}
>> 1: fmt = 0x441d38 "%s > %s/mondo-run-prog-thing.tmp 2> %s/mondo-run-prog-thing.err"
>> (gdb) s
>> 62 res = vasprintf(strp, fmt, args);
>> 2: args = {{gp_offset = 32, fp_offset = 48, overflow_arg_area =
>> 0x7fffffffe0b0, reg_save_area = 0x7fffffffdfe0}}
>> 1: fmt = 0x441d38 "%s > %s/mondo-run-prog-thing.tmp 2> %s/mondo-run-prog-thing.err"
>> (gdb) display res
>> 3: res = 0
>> (gdb) s
>>
>> Program received signal SIGSEGV, Segmentation fault.
>> 0x00007ffff76629aa in vfprintf () from /lib/x86_64-linux-gnu/libc.so.6
>> (gdb)
>>
>>
>> It seems there is an issue with mr_asprintf_int but sorry I don't feel strong enought to get more deeply into the mondo code and analyze it properly ...
>>
>> I hope this help ...
>>
>> Regards,
>> Philippe
>>
>>
>> Le 27/12/2014 11:17, [hidden email] a écrit :
>>> Hi all,
>>>
>>> it seems that something goes wrong with mondo I could link to the
>>> latest Debian version of MondoRescue.
>>>
>>> I updated my version last thursday and this morning (I have a
>>> differential backup launched every friday night and one full a month)
>>> it failed.
>>> Unfortunately there are no much relevant informations in logs.
>>>
>>> The errors raised is :
>>>
>>>     # mondoarchive -D -OV -i -N -G -s 780M -p sys-D7.7-diff_141227100000
>>>     -T /graveur -S /graveur -d
>>>     /media/sauvegardes/phlsys/D7.7/sys/141227100000 -I
>>>     "/|/|/opt/calibre|/opt/Zuma" -E
>>>     "/bases/sybase|/graveur|/home|/opt|/photos|/quemu|/Sauvegardes|/var/crash|/var/backups|/var/log|/var/mail|/var/spool|/vbox|/videos|/www"
>>>     See /var/log/mondoarchive.log for details of backup run.
>>>     Checking sanity of your Linux distribution
>>>     Done.
>>>     Erreur de segmentation                /* Segmentation error */
>>>
>>> Please find attached the log files that seems to find out an issue
>>> with LVM disks
>>>
>>>     INFO: Mindi v3.0.0-r3332
>>>     INFO: Le disque /dev/mapper/data1vg-photoslv ne contient pas une
>>>     table de partitions valable
>>>              /* there is no valid partition table in
>>>     /dev/mapper/data1vg-photoslv disk */
>>>
>>> I have no issues with my LVM disks. Please find on below my LVM disks
>>> configuration
>>>
>>>     lvm> vgs
>>>       VG      #PV #LV #SN Attr   VSize   VFree
>>>       data1vg   1   7   0 wz--n- 931,51g 504,60g
>>>       sysvg     1   1   0 wz--n-  95,12g  78,84g
>>>
>>>     lvm> lvs
>>>       LV        VG      Attr     LSize   Pool Origin Data%  Move Log
>>>     Copy%  Convert
>>>       baseslv   data1vg -wi-ao--  
>>>     1,86g                                          
>>>       graveurlv data1vg -wi-ao--
>>>     20,00g                                          
>>>       homelv    data1vg -wi-ao--
>>>     50,00g                                          
>>>       photoslv  data1vg -wi-ao--
>>>     70,00g                                          
>>>       vboxlv    data1vg -wi-ao--
>>>     130,39g                                          
>>>       videoslv  data1vg -wi-ao--
>>>     150,00g                                          
>>>       wwwlv     data1vg -wi-ao--  
>>>     4,66g                                          
>>>       optlv     sysvg   -wi-ao--  16,28g
>>>
>>>     lvm> lvscan
>>>       ACTIVE            '/dev/data1vg/photoslv' [70,00 GiB] inherit
>>>       ACTIVE            '/dev/data1vg/videoslv' [150,00 GiB] inherit
>>>       ACTIVE            '/dev/data1vg/homelv' [50,00 GiB] inherit
>>>       ACTIVE            '/dev/data1vg/graveurlv' [20,00 GiB] inherit
>>>       ACTIVE            '/dev/data1vg/wwwlv' [4,66 GiB] inherit
>>>       ACTIVE            '/dev/data1vg/baseslv' [1,86 GiB] inherit
>>>       ACTIVE            '/dev/data1vg/vboxlv' [130,39 GiB] inherit
>>>       ACTIVE            '/dev/sysvg/optlv' [16,28 GiB] inherit
>>>
>>>     root@phlsys:/home/phl/Scripts# df -h
>>>     Sys. fich.                                             Taille Util.
>>>     Dispo Uti% Monté sur
>>>     rootfs                                                    92G  
>>>     11G   77G  12% /
>>>     udev                                                      10M    
>>>     0   10M   0% /dev
>>>     tmpfs                                                    397M  968K
>>>     396M   1% /run
>>>     /dev/disk/by-uuid/4a5a9317-0b70-4796-a094-d61c01891c81    92G  
>>>     11G   77G  12% /
>>>     tmpfs                                                    5,0M     0
>>>     5,0M   0% /run/lock
>>>     tmpfs                                                    985M  324K
>>>     985M   1% /run/shm
>>>     /dev/mapper/sysvg-optlv                                   17G   15G
>>>     845M  95% /opt
>>>     /dev/mapper/data1vg-homelv                                50G   40G
>>>     7,2G  85% /home
>>>     /dev/mapper/data1vg-wwwlv                                4,6G  2,5G
>>>     1,9G  58% /www
>>>     /dev/mapper/data1vg-baseslv                              1,9G  720M
>>>     1,1G  41% /bases
>>>     /dev/mapper/data1vg-photoslv                              69G  
>>>     43G   23G  66% /photos
>>>     /dev/mapper/data1vg-videoslv                             148G
>>>     104G   37G  74% /videos
>>>     /dev/mapper/data1vg-vboxlv                               129G
>>>     100G   23G  82% /vbox
>>>     /dev/mapper/data1vg-graveurlv                             20G
>>>     8,1G   11G  44% /graveur
>>>
>>>
>>> The latest mondo upgrade dated of 25th of december was (it worked
>>> fine before this upgrade)
>>>
>>>     Start-Date: 2014-12-25  18:55:08
>>>     Commandline: /usr/sbin/synaptic
>>>     Install: libprojectbuilder-perl:amd64 (0.12.6-1, automatic),
>>>     libmondorescue-perl:amd64 (3.2.0-1, automatic)
>>>     Upgrade: mindi:amd64 (2.1.7-1, 3.0.0-1), mondo:amd64 (3.0.4-1,
>>>     3.2.0-1), mindi-busybox:amd64 (1.18.5-3, 1.21.1-1)
>>>     End-Date: 2014-12-25  18:55:31
>>>
>>> The Debian distro used is
>>>
>>>     root@phlsys:/home/phl/Scripts# uname -a
>>>     Linux phlsys 3.2.0-4-amd64 #1 SMP Debian 3.2.63-2+deb7u2 x86_64
>>>     GNU/Linux
>>>
>>> Anyone have an idea to try to debug this.
>>>
>>> Thanks for any help.
>>>
>>> By the way, I whish you all an happy new year 2015 with all the best
>>> in your lifes Kind regards, Philippe
>>>
>>>
>>
>>
>>
>> ----------------------------------------------------------------------
>> -------- Dive into the World of Parallel Programming! The Go Parallel
>> Website, sponsored by Intel and developed in partnership with Slashdot
>> Media, is your hub for all things parallel software development, from
>> weekly thought leadership blogs to news, videos, case studies,
>> tutorials and more. Take a look and join the conversation now.
>> http://goparallel.sourceforge.net 
>> _______________________________________________
>> Mondo-devel mailing list
>> [hidden email]
>> https://lists.sourceforge.net/lists/listinfo/mondo-devel
>> ----------------------------------------------------------------------
>> -------- Dive into the World of Parallel Programming! The Go Parallel
>> Website, sponsored by Intel and developed in partnership with Slashdot
>> Media, is your hub for all things parallel software development, from
>> weekly thought leadership blogs to news, videos, case studies,
>> tutorials and more. Take a look and join the conversation now.
>> http://goparallel.sourceforge.net 
>> _______________________________________________
>> Mondo-devel mailing list
>> [hidden email]
>> https://lists.sourceforge.net/lists/listinfo/mondo-devel
>>
>
>
>
> ------------------------------------------------------------------------------
> Dive into the World of Parallel Programming! The Go Parallel Website, sponsored by Intel and developed in partnership with Slashdot Media, is your hub for all things parallel software development, from weekly thought leadership blogs to news, videos, case studies, tutorials and more. Take a look and join the conversation now. http://goparallel.sourceforge.net _______________________________________________
> Mondo-devel mailing list
> [hidden email]
> https://lists.sourceforge.net/lists/listinfo/mondo-devel
> ------------------------------------------------------------------------------
> Dive into the World of Parallel Programming! The Go Parallel Website,
> sponsored by Intel and developed in partnership with Slashdot Media, is your
> hub for all things parallel software development, from weekly thought
> leadership blogs to news, videos, case studies, tutorials and more. Take a
> look and join the conversation now. http://goparallel.sourceforge.net
> _______________________________________________
> Mondo-devel mailing list
> [hidden email]
> https://lists.sourceforge.net/lists/listinfo/mondo-devel
>


------------------------------------------------------------------------------
New Year. New Location. New Benefits. New Data Center in Ashburn, VA.
GigeNET is offering a free month of service with a new server in Ashburn.
Choose from 2 high performing configs, both with 100TB of bandwidth.
Higher redundancy.Lower latency.Increased capacity.Completely compliant.
http://p.sf.net/sfu/gigenet
_______________________________________________
Mondo-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/mondo-devel

mondoarchive.log.gz (2K) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Re: [Mondo-devel] Segmentation error running mondoarchive v3.2.0-r3332

Gattegno, Victor (GSD CSC / GCC)
Hi Philippe,

You used again two time "/"  in the include :
-I "/|/|/opt/Zuma"

Your mondorachive.log file ends with :
DBG4: [Main] libmondo-files.c->find_home_of_exe#349: find_home_of_exe --- Found afio at /usr/bin/afio

You can try a few things :

Try mindi alone :
# mindi
Do you want to use your own kernel to build the boot disk ([y]/n) ? y

Try your mondoarchive command without -E, with only -I, and choice only one directory, example :
-I "/opt/Zuma"

Try your mondoarchive command with more debug, example with -K 5, or with -K 99 (which is full debug mode, be aware that the log file could grow from 200 Kb to 50 Mb).

Rgds,
Victor

-----Original Message-----
From: Philippe Lefevre [mailto:[hidden email]]
Sent: samedi 17 janvier 2015 20:14
To: Mondo mailing list
Subject: Re: [Mondo-devel] Segmentation error running mondoarchive v3.2.0-r3332

Hello list,

sorry Gaetagno for the delay, I was not able to find some time long enought to go back into my issue.

I did it today (without removing the two slashes in order to be in the same situation) and .... what I compiled worked fine with what I have compiled. (I noticed the -v bug, thanks  ;)  )

Run mondoarchive via dbg:
[phlsys]root:/home/phl/mondo-3.2.0# gdb -args mondoarchive -D -OV -i -N -G -s 780M -p sys-D7.7-diff_150105212200 -T /graveur -S /graveur -d /graveur -I "/|/|/opt/Zuma" -E "/bases/sybase|/graveur|/home|/opt|/photos|/quemu|/Sauvegardes|/var/crash|/var/backups|/var/log|/var/mail|/var/spool|/vbox|/videos|/www"

and:
....
Data archived OK.
Mondoarchive ran OK.
See /var/log/mondoarchive.log for details of backup run.
Execution run ended; result=0
Type 'less /var/log/mondoarchive.log' to see the output log [Inferior 1 (process 19382) exited normally]
(gdb) quit


So I reinstalled the official debian package:

Sélection du paquet libmondorescue-perl précédemment désélectionné.
(Lecture de la base de données... 279208 fichiers et répertoires déjà
installés.)
Dépaquetage de libmondorescue-perl (à partir de
.../libmondorescue-perl_3.2.0-1_all.deb) ...
Préparation du remplacement de mindi-busybox 1.18.5-3 (en utilisant
.../mindi-busybox_1.21.1-1_amd64.deb) ...
Dépaquetage de la mise à jour de mindi-busybox ...
Préparation du remplacement de mindi 2.1.7-1 (en utilisant
.../mindi_3.0.0-1_amd64.deb) ...
Dépaquetage de la mise à jour de mindi ...
Préparation du remplacement de mondo 3.0.4-1 (en utilisant
.../mondo_3.2.0-1_amd64.deb) ...
Dépaquetage de la mise à jour de mondo ...
Traitement des actions différées (« triggers ») pour « man-db »...
Paramétrage de libmondorescue-perl (3.2.0-1) ...
Paramétrage de mindi-busybox (1.21.1-1) ...
Paramétrage de mindi (3.0.0-1) ...
Installation de la nouvelle version du fichier de configuration /etc/mindi/deplist.d/minimal.conf ...
Installation de la nouvelle version du fichier de configuration /etc/mindi/deplist.d/udev.conf ...
Installation de la nouvelle version du fichier de configuration /etc/mindi/deplist.d/ProLiant.conf ...
Installation de la nouvelle version du fichier de configuration /etc/mindi/deplist.d/base.conf ...
Installation de la nouvelle version du fichier de configuration /etc/mindi/deplist.d/lvm.conf ...
Installation de la nouvelle version du fichier de configuration /etc/mindi/perl-scripts ...
Paramétrage de mondo (3.2.0-1) ...


but launched in the same way, it crashed again with a segmentation error:

[phlsys]root:/home/phl/telechargements/mondo-3.2.0# mondoarchive -D -OV -i -N -G -s 780M -p sys-D7.7-diff_150105212200 -T /graveur -S /graveur -d /graveur -I "/|/|/opt/Zuma" -E "/bases/sybase|/graveur|/home|/opt|/photos|/quemu|/Sauvegardes|/var/crash|/var/backups|/var/log|/var/mail|/var/spool|/vbox|/videos|/www"
See /var/log/mondoarchive.log for details of backup run.
Checking sanity of your Linux distribution Done.
Erreur de segmentation



Please find attached the relevant mondoarchive.log file.
It seems to be stopped before logging something about the fault.
I franckly don't know what I could do more.
Do you have an idea about what I could do to explore deeper this issue ?
Something might be going wrong into the deb pkg ???
I got it with apt using:
   deb ftp://ftp.mondorescue.org//debian 7 contrib


Thanks for your help.
Regards,
Philippe





Le 06/01/2015 17:28, Gattegno, Victor (GSD CSC / GCC) a écrit :

> Hello Philippe,
>
> From mondoarchive man : " When using the -I option with the -E option, the -E content should be subdirectories of those mentioned in the -I only, as -I takes precedence."
>
> But if your -I and -E combination works it's ok (check if /opt/zuma and /opt/calibre are well backuped and restored).
>
> Regards,
> Victor
>
> -----Original Message-----
> From: Philippe Lefevre [mailto:[hidden email]]
> Sent: lundi 5 janvier 2015 21:42
> To: [hidden email]
> Subject: Re: [Mondo-devel] Segmentation error running mondoarchive
> v3.2.0-r3332
>
> Thanks for your help and reply Victor,
>
> I should be able to replay with all of that before the end of the week and let you know.
> Regarding the double /, it is due to my shell script which build the final request. I will also do a try without it.
>
> I believe I couldn't remove -I flag as in the exclude part there is /opt and I want to include only 2 directories /opt/zuma and /opt/calibre. At least, I should use -I "/opt/calibre|/opt/Zuma" right?
>
> PS: my system backup is run by root and ulimit is setted unlimited:
>
> # ulimit -a
> core file size          (blocks, -c) 0
> data seg size           (kbytes, -d) unlimited
> scheduling priority             (-e) 0
> file size               (blocks, -f) unlimited
> pending signals                 (-i) 31106
> max locked memory       (kbytes, -l) 64
> max memory size         (kbytes, -m) unlimited
> open files                      (-n) 1024
> pipe size            (512 bytes, -p) 8
> POSIX message queues     (bytes, -q) 819200
> real-time priority              (-r) 0
> stack size              (kbytes, -s) 8192
> cpu time               (seconds, -t) unlimited
> max user processes              (-u) 31106
> virtual memory          (kbytes, -v) unlimited
> file locks                      (-x) unlimited
>
>
> Rgds,
> Philippe
>
>
> Le 05/01/2015 16:32, Gattegno, Victor (GSD CSC / GCC) a écrit :
>> Hello Philippe,
>>
>> Good gdb work, but don't focus on "mondoarchive -v" segmentation fault, it's a known failing bug. It's better to debug mondoarchive with the options that you use.
>>
>>  In your 27/12/2014 test and post:
>>  - did you posted too the associated /var/log/mondoarchive.log (compressed) ?
>>  - you used -I (with / included twice) and -E options, it's better to use only -E option.
>>
>> What's the result of "ulimit -a" on your Debian ?
>>
>> I wish to you - and to all this mailig-list users - a nice year 2015.
>>
>> Rgds,
>> Victor
>>
>> -----Original Message-----
>> From: Philippe Lefevre [mailto:[hidden email]]
>> Sent: samedi 3 janvier 2015 14:32
>> To: [hidden email]
>> Subject: Re: [Mondo-devel] Segmentation error running mondoarchive
>> v3.2.0-r3332
>>
>> Hi list,
>>
>> Some more information about my issue.
>>
>> I can confirm that in my case it is related to this new release as a I did a downgrade and successfully built a new full backup.
>>
>> I uninstalled and purged
>>   libmondorescue-perl_3.2.0-1_all.deb
>>   mindi-busybox_1.21.1-1_amd64.deb
>>   mindi_3.0.0-1_amd64.deb
>>   mondo_3.2.0-1_amd64.deb
>>
>> and reinstalled the previous version
>>   mindi-busybox 1.18.5-3
>>   mindi 2.1.7-1
>>   mondo 3.0.4-1
>>
>> I also compiled mondo 3.2.0 from sources and ran gdb against the simpliest command that raise the seg error. It shows :
>>
>> Starting program:
>> /home/phl/telechargements/mondo-3.2.0/src/mondoarchive/mondoarchive -v [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
>> mondoarchive v3.2.0-r3332
>> See man page for help
>>
>> Program received signal SIGSEGV, Segmentation fault.
>> 0x00007ffff76629aa in vfprintf () from
>> /lib/x86_64-linux-gnu/libc.so.6
>> (gdb) bt
>> #0  0x00007ffff76629aa in vfprintf () from
>> /lib/x86_64-linux-gnu/libc.so.6
>> #1  0x00007ffff7688fca in vasprintf () from
>> /lib/x86_64-linux-gnu/libc.so.6
>> #2  0x00000000004367c4 in mr_asprintf_int (strp=strp@entry=0x7fffffffe0d0, line=line@entry=258, file=file@entry=0x44187f "libmondo-fork.c",
>>     fmt=fmt@entry=0x441d38 "%s > %s/mondo-run-prog-thing.tmp 2>
>> %s/mondo-run-prog-thing.err") at mr_mem.c:62
>> #3  0x000000000041e0f0 in run_program_and_log_output
>> (program=program@entry=0x43c4b4 "umount -d /mnt/cdrom",
>> debug_level=debug_level@entry=0)
>>     at libmondo-fork.c:258
>> #4  0x000000000042ec19 in finish (signal=signal@entry=0) at
>> newt-specific.c:388
>> #5  0x0000000000403430 in main (argc=2, argv=0x7fffffffe668) at
>> mondoarchive.c:176
>> (gdb)
>>
>>
>> function code exerpt
>>
>>    56 void mr_asprintf_int(char **strp, int line, const char *file, const char *fmt, ...) {
>>    57
>>    58 int res = 0;
>>    59 va_list args;
>>    60
>>    61 va_start(args,fmt);
>>    62 res = vasprintf(strp, fmt, args);
>>    63 if (res == -1) {
>>    64 mr_msg_int(1,line,file,"Unable to alloc memory in
>> mr_asprintf\nExiting...");
>>    65 mr_exit(-1,"Unable to alloc memory in mr_asprintf");
>>    66 }
>>    67 va_end(args);
>>    68 }
>>
>>
>> Breakpoint 1, mr_asprintf_int (strp=strp@entry=0x7fffffffe0d0, line=line@entry=258, file=file@entry=0x44187f "libmondo-fork.c",
>>     fmt=fmt@entry=0x441d38 "%s > %s/mondo-run-prog-thing.tmp 2>
>> %s/mondo-run-prog-thing.err") at mr_mem.c:56
>> 56 void mr_asprintf_int(char **strp, int line, const char *file, const
>> char *fmt, ...) {
>> (gdb) s
>> 61 va_start(args,fmt);
>> (gdb) display fmt
>> 1: fmt = 0x441d38 "%s > %s/mondo-run-prog-thing.tmp 2> %s/mondo-run-prog-thing.err"
>> (gdb) display args
>> 2: args = {{gp_offset = 4158558940, fp_offset = 32767,
>> overflow_arg_area = 0x7ffff7fd5000, reg_save_area = 0x7ffff7ffd9d8}}
>> (gdb) s
>> 62 res = vasprintf(strp, fmt, args);
>> 2: args = {{gp_offset = 4158558940, fp_offset = 32767,
>> overflow_arg_area = 0x7ffff7fd5000, reg_save_area = 0x7ffff7ffd9d8}}
>> 1: fmt = 0x441d38 "%s > %s/mondo-run-prog-thing.tmp 2> %s/mondo-run-prog-thing.err"
>> (gdb) s
>> 61 va_start(args,fmt);
>> 2: args = {{gp_offset = 4158558940, fp_offset = 32767,
>> overflow_arg_area = 0x7ffff7fd5000, reg_save_area = 0x7ffff7ffd9d8}}
>> 1: fmt = 0x441d38 "%s > %s/mondo-run-prog-thing.tmp 2> %s/mondo-run-prog-thing.err"
>> (gdb) s
>> 62 res = vasprintf(strp, fmt, args);
>> 2: args = {{gp_offset = 32, fp_offset = 48, overflow_arg_area =
>> 0x7fffffffe0b0, reg_save_area = 0x7fffffffdfe0}}
>> 1: fmt = 0x441d38 "%s > %s/mondo-run-prog-thing.tmp 2> %s/mondo-run-prog-thing.err"
>> (gdb) display res
>> 3: res = 0
>> (gdb) s
>>
>> Program received signal SIGSEGV, Segmentation fault.
>> 0x00007ffff76629aa in vfprintf () from
>> /lib/x86_64-linux-gnu/libc.so.6
>> (gdb)
>>
>>
>> It seems there is an issue with mr_asprintf_int but sorry I don't feel strong enought to get more deeply into the mondo code and analyze it properly ...
>>
>> I hope this help ...
>>
>> Regards,
>> Philippe
>>
>>
>> Le 27/12/2014 11:17, [hidden email] a écrit :
>>> Hi all,
>>>
>>> it seems that something goes wrong with mondo I could link to the
>>> latest Debian version of MondoRescue.
>>>
>>> I updated my version last thursday and this morning (I have a
>>> differential backup launched every friday night and one full a
>>> month) it failed.
>>> Unfortunately there are no much relevant informations in logs.
>>>
>>> The errors raised is :
>>>
>>>     # mondoarchive -D -OV -i -N -G -s 780M -p sys-D7.7-diff_141227100000
>>>     -T /graveur -S /graveur -d
>>>     /media/sauvegardes/phlsys/D7.7/sys/141227100000 -I
>>>     "/|/|/opt/calibre|/opt/Zuma" -E
>>>     "/bases/sybase|/graveur|/home|/opt|/photos|/quemu|/Sauvegardes|/var/crash|/var/backups|/var/log|/var/mail|/var/spool|/vbox|/videos|/www"
>>>     See /var/log/mondoarchive.log for details of backup run.
>>>     Checking sanity of your Linux distribution
>>>     Done.
>>>     Erreur de segmentation                /* Segmentation error */
>>>
>>> Please find attached the log files that seems to find out an issue
>>> with LVM disks
>>>
>>>     INFO: Mindi v3.0.0-r3332
>>>     INFO: Le disque /dev/mapper/data1vg-photoslv ne contient pas une
>>>     table de partitions valable
>>>              /* there is no valid partition table in
>>>     /dev/mapper/data1vg-photoslv disk */
>>>
>>> I have no issues with my LVM disks. Please find on below my LVM
>>> disks configuration
>>>
>>>     lvm> vgs
>>>       VG      #PV #LV #SN Attr   VSize   VFree
>>>       data1vg   1   7   0 wz--n- 931,51g 504,60g
>>>       sysvg     1   1   0 wz--n-  95,12g  78,84g
>>>
>>>     lvm> lvs
>>>       LV        VG      Attr     LSize   Pool Origin Data%  Move Log
>>>     Copy%  Convert
>>>       baseslv   data1vg -wi-ao--  
>>>     1,86g                                          
>>>       graveurlv data1vg -wi-ao--
>>>     20,00g                                          
>>>       homelv    data1vg -wi-ao--
>>>     50,00g                                          
>>>       photoslv  data1vg -wi-ao--
>>>     70,00g                                          
>>>       vboxlv    data1vg -wi-ao--
>>>     130,39g                                          
>>>       videoslv  data1vg -wi-ao--
>>>     150,00g                                          
>>>       wwwlv     data1vg -wi-ao--  
>>>     4,66g                                          
>>>       optlv     sysvg   -wi-ao--  16,28g
>>>
>>>     lvm> lvscan
>>>       ACTIVE            '/dev/data1vg/photoslv' [70,00 GiB] inherit
>>>       ACTIVE            '/dev/data1vg/videoslv' [150,00 GiB] inherit
>>>       ACTIVE            '/dev/data1vg/homelv' [50,00 GiB] inherit
>>>       ACTIVE            '/dev/data1vg/graveurlv' [20,00 GiB] inherit
>>>       ACTIVE            '/dev/data1vg/wwwlv' [4,66 GiB] inherit
>>>       ACTIVE            '/dev/data1vg/baseslv' [1,86 GiB] inherit
>>>       ACTIVE            '/dev/data1vg/vboxlv' [130,39 GiB] inherit
>>>       ACTIVE            '/dev/sysvg/optlv' [16,28 GiB] inherit
>>>
>>>     root@phlsys:/home/phl/Scripts# df -h
>>>     Sys. fich.                                             Taille Util.
>>>     Dispo Uti% Monté sur
>>>     rootfs                                                    92G  
>>>     11G   77G  12% /
>>>     udev                                                      10M    
>>>     0   10M   0% /dev
>>>     tmpfs                                                    397M  968K
>>>     396M   1% /run
>>>     /dev/disk/by-uuid/4a5a9317-0b70-4796-a094-d61c01891c81    92G  
>>>     11G   77G  12% /
>>>     tmpfs                                                    5,0M     0
>>>     5,0M   0% /run/lock
>>>     tmpfs                                                    985M  324K
>>>     985M   1% /run/shm
>>>     /dev/mapper/sysvg-optlv                                   17G   15G
>>>     845M  95% /opt
>>>     /dev/mapper/data1vg-homelv                                50G   40G
>>>     7,2G  85% /home
>>>     /dev/mapper/data1vg-wwwlv                                4,6G  2,5G
>>>     1,9G  58% /www
>>>     /dev/mapper/data1vg-baseslv                              1,9G  720M
>>>     1,1G  41% /bases
>>>     /dev/mapper/data1vg-photoslv                              69G  
>>>     43G   23G  66% /photos
>>>     /dev/mapper/data1vg-videoslv                             148G
>>>     104G   37G  74% /videos
>>>     /dev/mapper/data1vg-vboxlv                               129G
>>>     100G   23G  82% /vbox
>>>     /dev/mapper/data1vg-graveurlv                             20G
>>>     8,1G   11G  44% /graveur
>>>
>>>
>>> The latest mondo upgrade dated of 25th of december was (it worked
>>> fine before this upgrade)
>>>
>>>     Start-Date: 2014-12-25  18:55:08
>>>     Commandline: /usr/sbin/synaptic
>>>     Install: libprojectbuilder-perl:amd64 (0.12.6-1, automatic),
>>>     libmondorescue-perl:amd64 (3.2.0-1, automatic)
>>>     Upgrade: mindi:amd64 (2.1.7-1, 3.0.0-1), mondo:amd64 (3.0.4-1,
>>>     3.2.0-1), mindi-busybox:amd64 (1.18.5-3, 1.21.1-1)
>>>     End-Date: 2014-12-25  18:55:31
>>>
>>> The Debian distro used is
>>>
>>>     root@phlsys:/home/phl/Scripts# uname -a
>>>     Linux phlsys 3.2.0-4-amd64 #1 SMP Debian 3.2.63-2+deb7u2 x86_64
>>>     GNU/Linux
>>>
>>> Anyone have an idea to try to debug this.
>>>
>>> Thanks for any help.
>>>
>>> By the way, I whish you all an happy new year 2015 with all the best
>>> in your lifes Kind regards, Philippe
>>>
>>>
>>
>>
>>
>> ---------------------------------------------------------------------
>> -
>> -------- Dive into the World of Parallel Programming! The Go Parallel
>> Website, sponsored by Intel and developed in partnership with
>> Slashdot Media, is your hub for all things parallel software
>> development, from weekly thought leadership blogs to news, videos,
>> case studies, tutorials and more. Take a look and join the conversation now.
>> http://goparallel.sourceforge.net
>> _______________________________________________
>> Mondo-devel mailing list
>> [hidden email]
>> https://lists.sourceforge.net/lists/listinfo/mondo-devel
>> ---------------------------------------------------------------------
>> -
>> -------- Dive into the World of Parallel Programming! The Go Parallel
>> Website, sponsored by Intel and developed in partnership with
>> Slashdot Media, is your hub for all things parallel software
>> development, from weekly thought leadership blogs to news, videos,
>> case studies, tutorials and more. Take a look and join the conversation now.
>> http://goparallel.sourceforge.net
>> _______________________________________________
>> Mondo-devel mailing list
>> [hidden email]
>> https://lists.sourceforge.net/lists/listinfo/mondo-devel
>>
>
>
>
> ----------------------------------------------------------------------
> -------- Dive into the World of Parallel Programming! The Go Parallel
> Website, sponsored by Intel and developed in partnership with Slashdot
> Media, is your hub for all things parallel software development, from
> weekly thought leadership blogs to news, videos, case studies,
> tutorials and more. Take a look and join the conversation now.
> http://goparallel.sourceforge.net 
> _______________________________________________
> Mondo-devel mailing list
> [hidden email]
> https://lists.sourceforge.net/lists/listinfo/mondo-devel
> ----------------------------------------------------------------------
> -------- Dive into the World of Parallel Programming! The Go Parallel
> Website, sponsored by Intel and developed in partnership with Slashdot
> Media, is your hub for all things parallel software development, from
> weekly thought leadership blogs to news, videos, case studies,
> tutorials and more. Take a look and join the conversation now.
> http://goparallel.sourceforge.net 
> _______________________________________________
> Mondo-devel mailing list
> [hidden email]
> https://lists.sourceforge.net/lists/listinfo/mondo-devel
>


------------------------------------------------------------------------------
New Year. New Location. New Benefits. New Data Center in Ashburn, VA.
GigeNET is offering a free month of service with a new server in Ashburn.
Choose from 2 high performing configs, both with 100TB of bandwidth.
Higher redundancy.Lower latency.Increased capacity.Completely compliant.
http://p.sf.net/sfu/gigenet
_______________________________________________
Mondo-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/mondo-devel
Reply | Threaded
Open this post in threaded view
|

Re: [Mondo-devel] Segmentation error running mondoarchive v3.2.0-r3332

Philippe Lefevre
Hello Gaetagno,

Regarding the two slashes, as I said, I used the same syntax to get into
the same bug situation.


I did a try with only one / in the -I option and got the same
segmentation violation exception.


Mindi launched alone as your example and it ran fine and the iso file
successfully built.
Please find attached the mindi.log file.

[phlsys]root:/home/phl/Devel/mondo# ls -al /var/cache/mindi/mindi.iso
-rw-r----- 1 root root 98721792 janv. 19 22:09 /var/cache/mindi/mindi.iso



Ran mondoarchive with -K99 option crashed again with the sigsegv signal.
Please find attached the mondoarchive.log file.
Unfortunately, I'm afraid it is not so verbose than we would ...
This time, the log ends with :

DBG1: [Main] libmondo-cli.c->process_switches#181: Loglevel forced to 99
DBG20: [Main] libmondo-files.c->does_file_exist#188: /usr/bin/afio exists
DBG4: [Main] libmondo-files.c->find_home_of_exe#349: find_home_of_exe
--- Found afio at /usr/bin/afio



Running mondo without - E option crashed in the same way and with same
mondoarchive.log file.
[phlsys]root:/home/phl/Devel/mondo# /usr/sbin/mondoarchive -K99 -D -OV
-i -N -G -s 780M -p sys-D7.7-diff_150105212200 -T /graveur -S /graveur
-d /graveur -I "/opt/zuma"
See /var/log/mondoarchive.log for details of backup run.
Checking sanity of your Linux distribution
Done.
Erreur de segmentation


Thank you for your time Gaetagno.
Kind regards,
Philippe



Le 19/01/2015 12:17, Gattegno, Victor (GSD CSC / GCC) a écrit :

> Hi Philippe,
>
> You used again two time "/"  in the include :
> -I "/|/|/opt/Zuma"
>
> Your mondorachive.log file ends with :
> DBG4: [Main] libmondo-files.c->find_home_of_exe#349: find_home_of_exe --- Found afio at /usr/bin/afio
>
> You can try a few things :
>
> Try mindi alone :
> # mindi
> Do you want to use your own kernel to build the boot disk ([y]/n) ? y
>
> Try your mondoarchive command without -E, with only -I, and choice only one directory, example :
> -I "/opt/Zuma"
>
> Try your mondoarchive command with more debug, example with -K 5, or with -K 99 (which is full debug mode, be aware that the log file could grow from 200 Kb to 50 Mb).
>
> Rgds,
> Victor
>
> -----Original Message-----
> From: Philippe Lefevre [mailto:[hidden email]]
> Sent: samedi 17 janvier 2015 20:14
> To: Mondo mailing list
> Subject: Re: [Mondo-devel] Segmentation error running mondoarchive v3.2.0-r3332
>
> Hello list,
>
> sorry Gaetagno for the delay, I was not able to find some time long enought to go back into my issue.
>
> I did it today (without removing the two slashes in order to be in the same situation) and .... what I compiled worked fine with what I have compiled. (I noticed the -v bug, thanks  ;)  )
>
> Run mondoarchive via dbg:
> [phlsys]root:/home/phl/mondo-3.2.0# gdb -args mondoarchive -D -OV -i -N -G -s 780M -p sys-D7.7-diff_150105212200 -T /graveur -S /graveur -d /graveur -I "/|/|/opt/Zuma" -E "/bases/sybase|/graveur|/home|/opt|/photos|/quemu|/Sauvegardes|/var/crash|/var/backups|/var/log|/var/mail|/var/spool|/vbox|/videos|/www"
>
> and:
> ....
> Data archived OK.
> Mondoarchive ran OK.
> See /var/log/mondoarchive.log for details of backup run.
> Execution run ended; result=0
> Type 'less /var/log/mondoarchive.log' to see the output log [Inferior 1 (process 19382) exited normally]
> (gdb) quit
>
>
> So I reinstalled the official debian package:
>
> Sélection du paquet libmondorescue-perl précédemment désélectionné.
> (Lecture de la base de données... 279208 fichiers et répertoires déjà
> installés.)
> Dépaquetage de libmondorescue-perl (à partir de
> .../libmondorescue-perl_3.2.0-1_all.deb) ...
> Préparation du remplacement de mindi-busybox 1.18.5-3 (en utilisant
> .../mindi-busybox_1.21.1-1_amd64.deb) ...
> Dépaquetage de la mise à jour de mindi-busybox ...
> Préparation du remplacement de mindi 2.1.7-1 (en utilisant
> .../mindi_3.0.0-1_amd64.deb) ...
> Dépaquetage de la mise à jour de mindi ...
> Préparation du remplacement de mondo 3.0.4-1 (en utilisant
> .../mondo_3.2.0-1_amd64.deb) ...
> Dépaquetage de la mise à jour de mondo ...
> Traitement des actions différées (« triggers ») pour « man-db »...
> Paramétrage de libmondorescue-perl (3.2.0-1) ...
> Paramétrage de mindi-busybox (1.21.1-1) ...
> Paramétrage de mindi (3.0.0-1) ...
> Installation de la nouvelle version du fichier de configuration /etc/mindi/deplist.d/minimal.conf ...
> Installation de la nouvelle version du fichier de configuration /etc/mindi/deplist.d/udev.conf ...
> Installation de la nouvelle version du fichier de configuration /etc/mindi/deplist.d/ProLiant.conf ...
> Installation de la nouvelle version du fichier de configuration /etc/mindi/deplist.d/base.conf ...
> Installation de la nouvelle version du fichier de configuration /etc/mindi/deplist.d/lvm.conf ...
> Installation de la nouvelle version du fichier de configuration /etc/mindi/perl-scripts ...
> Paramétrage de mondo (3.2.0-1) ...
>
>
> but launched in the same way, it crashed again with a segmentation error:
>
> [phlsys]root:/home/phl/telechargements/mondo-3.2.0# mondoarchive -D -OV -i -N -G -s 780M -p sys-D7.7-diff_150105212200 -T /graveur -S /graveur -d /graveur -I "/|/|/opt/Zuma" -E "/bases/sybase|/graveur|/home|/opt|/photos|/quemu|/Sauvegardes|/var/crash|/var/backups|/var/log|/var/mail|/var/spool|/vbox|/videos|/www"
> See /var/log/mondoarchive.log for details of backup run.
> Checking sanity of your Linux distribution Done.
> Erreur de segmentation
>
>
>
> Please find attached the relevant mondoarchive.log file.
> It seems to be stopped before logging something about the fault.
> I franckly don't know what I could do more.
> Do you have an idea about what I could do to explore deeper this issue ?
> Something might be going wrong into the deb pkg ???
> I got it with apt using:
>    deb ftp://ftp.mondorescue.org//debian 7 contrib
>
>
> Thanks for your help.
> Regards,
> Philippe
>
>
>
>
>
> Le 06/01/2015 17:28, Gattegno, Victor (GSD CSC / GCC) a écrit :
>> Hello Philippe,
>>
>> From mondoarchive man : " When using the -I option with the -E option, the -E content should be subdirectories of those mentioned in the -I only, as -I takes precedence."
>>
>> But if your -I and -E combination works it's ok (check if /opt/zuma and /opt/calibre are well backuped and restored).
>>
>> Regards,
>> Victor
>>
>> -----Original Message-----
>> From: Philippe Lefevre [mailto:[hidden email]]
>> Sent: lundi 5 janvier 2015 21:42
>> To: [hidden email]
>> Subject: Re: [Mondo-devel] Segmentation error running mondoarchive
>> v3.2.0-r3332
>>
>> Thanks for your help and reply Victor,
>>
>> I should be able to replay with all of that before the end of the week and let you know.
>> Regarding the double /, it is due to my shell script which build the final request. I will also do a try without it.
>>
>> I believe I couldn't remove -I flag as in the exclude part there is /opt and I want to include only 2 directories /opt/zuma and /opt/calibre. At least, I should use -I "/opt/calibre|/opt/Zuma" right?
>>
>> PS: my system backup is run by root and ulimit is setted unlimited:
>>
>> # ulimit -a
>> core file size          (blocks, -c) 0
>> data seg size           (kbytes, -d) unlimited
>> scheduling priority             (-e) 0
>> file size               (blocks, -f) unlimited
>> pending signals                 (-i) 31106
>> max locked memory       (kbytes, -l) 64
>> max memory size         (kbytes, -m) unlimited
>> open files                      (-n) 1024
>> pipe size            (512 bytes, -p) 8
>> POSIX message queues     (bytes, -q) 819200
>> real-time priority              (-r) 0
>> stack size              (kbytes, -s) 8192
>> cpu time               (seconds, -t) unlimited
>> max user processes              (-u) 31106
>> virtual memory          (kbytes, -v) unlimited
>> file locks                      (-x) unlimited
>>
>>
>> Rgds,
>> Philippe
>>
>>
>> Le 05/01/2015 16:32, Gattegno, Victor (GSD CSC / GCC) a écrit :
>>> Hello Philippe,
>>>
>>> Good gdb work, but don't focus on "mondoarchive -v" segmentation fault, it's a known failing bug. It's better to debug mondoarchive with the options that you use.
>>>
>>>  In your 27/12/2014 test and post:
>>>  - did you posted too the associated /var/log/mondoarchive.log (compressed) ?
>>>  - you used -I (with / included twice) and -E options, it's better to use only -E option.
>>>
>>> What's the result of "ulimit -a" on your Debian ?
>>>
>>> I wish to you - and to all this mailig-list users - a nice year 2015.
>>>
>>> Rgds,
>>> Victor
>>>
>>> -----Original Message-----
>>> From: Philippe Lefevre [mailto:[hidden email]]
>>> Sent: samedi 3 janvier 2015 14:32
>>> To: [hidden email]
>>> Subject: Re: [Mondo-devel] Segmentation error running mondoarchive
>>> v3.2.0-r3332
>>>
>>> Hi list,
>>>
>>> Some more information about my issue.
>>>
>>> I can confirm that in my case it is related to this new release as a I did a downgrade and successfully built a new full backup.
>>>
>>> I uninstalled and purged
>>>   libmondorescue-perl_3.2.0-1_all.deb
>>>   mindi-busybox_1.21.1-1_amd64.deb
>>>   mindi_3.0.0-1_amd64.deb
>>>   mondo_3.2.0-1_amd64.deb
>>>
>>> and reinstalled the previous version
>>>   mindi-busybox 1.18.5-3
>>>   mindi 2.1.7-1
>>>   mondo 3.0.4-1
>>>
>>> I also compiled mondo 3.2.0 from sources and ran gdb against the simpliest command that raise the seg error. It shows :
>>>
>>> Starting program:
>>> /home/phl/telechargements/mondo-3.2.0/src/mondoarchive/mondoarchive -v [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
>>> mondoarchive v3.2.0-r3332
>>> See man page for help
>>>
>>> Program received signal SIGSEGV, Segmentation fault.
>>> 0x00007ffff76629aa in vfprintf () from
>>> /lib/x86_64-linux-gnu/libc.so.6
>>> (gdb) bt
>>> #0  0x00007ffff76629aa in vfprintf () from
>>> /lib/x86_64-linux-gnu/libc.so.6
>>> #1  0x00007ffff7688fca in vasprintf () from
>>> /lib/x86_64-linux-gnu/libc.so.6
>>> #2  0x00000000004367c4 in mr_asprintf_int (strp=strp@entry=0x7fffffffe0d0, line=line@entry=258, file=file@entry=0x44187f "libmondo-fork.c",
>>>     fmt=fmt@entry=0x441d38 "%s > %s/mondo-run-prog-thing.tmp 2>
>>> %s/mondo-run-prog-thing.err") at mr_mem.c:62
>>> #3  0x000000000041e0f0 in run_program_and_log_output
>>> (program=program@entry=0x43c4b4 "umount -d /mnt/cdrom",
>>> debug_level=debug_level@entry=0)
>>>     at libmondo-fork.c:258
>>> #4  0x000000000042ec19 in finish (signal=signal@entry=0) at
>>> newt-specific.c:388
>>> #5  0x0000000000403430 in main (argc=2, argv=0x7fffffffe668) at
>>> mondoarchive.c:176
>>> (gdb)
>>>
>>>
>>> function code exerpt
>>>
>>>    56 void mr_asprintf_int(char **strp, int line, const char *file, const char *fmt, ...) {
>>>    57
>>>    58 int res = 0;
>>>    59 va_list args;
>>>    60
>>>    61 va_start(args,fmt);
>>>    62 res = vasprintf(strp, fmt, args);
>>>    63 if (res == -1) {
>>>    64 mr_msg_int(1,line,file,"Unable to alloc memory in
>>> mr_asprintf\nExiting...");
>>>    65 mr_exit(-1,"Unable to alloc memory in mr_asprintf");
>>>    66 }
>>>    67 va_end(args);
>>>    68 }
>>>
>>>
>>> Breakpoint 1, mr_asprintf_int (strp=strp@entry=0x7fffffffe0d0, line=line@entry=258, file=file@entry=0x44187f "libmondo-fork.c",
>>>     fmt=fmt@entry=0x441d38 "%s > %s/mondo-run-prog-thing.tmp 2>
>>> %s/mondo-run-prog-thing.err") at mr_mem.c:56
>>> 56 void mr_asprintf_int(char **strp, int line, const char *file, const
>>> char *fmt, ...) {
>>> (gdb) s
>>> 61 va_start(args,fmt);
>>> (gdb) display fmt
>>> 1: fmt = 0x441d38 "%s > %s/mondo-run-prog-thing.tmp 2> %s/mondo-run-prog-thing.err"
>>> (gdb) display args
>>> 2: args = {{gp_offset = 4158558940, fp_offset = 32767,
>>> overflow_arg_area = 0x7ffff7fd5000, reg_save_area = 0x7ffff7ffd9d8}}
>>> (gdb) s
>>> 62 res = vasprintf(strp, fmt, args);
>>> 2: args = {{gp_offset = 4158558940, fp_offset = 32767,
>>> overflow_arg_area = 0x7ffff7fd5000, reg_save_area = 0x7ffff7ffd9d8}}
>>> 1: fmt = 0x441d38 "%s > %s/mondo-run-prog-thing.tmp 2> %s/mondo-run-prog-thing.err"
>>> (gdb) s
>>> 61 va_start(args,fmt);
>>> 2: args = {{gp_offset = 4158558940, fp_offset = 32767,
>>> overflow_arg_area = 0x7ffff7fd5000, reg_save_area = 0x7ffff7ffd9d8}}
>>> 1: fmt = 0x441d38 "%s > %s/mondo-run-prog-thing.tmp 2> %s/mondo-run-prog-thing.err"
>>> (gdb) s
>>> 62 res = vasprintf(strp, fmt, args);
>>> 2: args = {{gp_offset = 32, fp_offset = 48, overflow_arg_area =
>>> 0x7fffffffe0b0, reg_save_area = 0x7fffffffdfe0}}
>>> 1: fmt = 0x441d38 "%s > %s/mondo-run-prog-thing.tmp 2> %s/mondo-run-prog-thing.err"
>>> (gdb) display res
>>> 3: res = 0
>>> (gdb) s
>>>
>>> Program received signal SIGSEGV, Segmentation fault.
>>> 0x00007ffff76629aa in vfprintf () from
>>> /lib/x86_64-linux-gnu/libc.so.6
>>> (gdb)
>>>
>>>
>>> It seems there is an issue with mr_asprintf_int but sorry I don't feel strong enought to get more deeply into the mondo code and analyze it properly ...
>>>
>>> I hope this help ...
>>>
>>> Regards,
>>> Philippe
>>>
>>>
>>> Le 27/12/2014 11:17, [hidden email] a écrit :
>>>> Hi all,
>>>>
>>>> it seems that something goes wrong with mondo I could link to the
>>>> latest Debian version of MondoRescue.
>>>>
>>>> I updated my version last thursday and this morning (I have a
>>>> differential backup launched every friday night and one full a
>>>> month) it failed.
>>>> Unfortunately there are no much relevant informations in logs.
>>>>
>>>> The errors raised is :
>>>>
>>>>     # mondoarchive -D -OV -i -N -G -s 780M -p sys-D7.7-diff_141227100000
>>>>     -T /graveur -S /graveur -d
>>>>     /media/sauvegardes/phlsys/D7.7/sys/141227100000 -I
>>>>     "/|/|/opt/calibre|/opt/Zuma" -E
>>>>     "/bases/sybase|/graveur|/home|/opt|/photos|/quemu|/Sauvegardes|/var/crash|/var/backups|/var/log|/var/mail|/var/spool|/vbox|/videos|/www"
>>>>     See /var/log/mondoarchive.log for details of backup run.
>>>>     Checking sanity of your Linux distribution
>>>>     Done.
>>>>     Erreur de segmentation                /* Segmentation error */
>>>>
>>>> Please find attached the log files that seems to find out an issue
>>>> with LVM disks
>>>>
>>>>     INFO: Mindi v3.0.0-r3332
>>>>     INFO: Le disque /dev/mapper/data1vg-photoslv ne contient pas une
>>>>     table de partitions valable
>>>>              /* there is no valid partition table in
>>>>     /dev/mapper/data1vg-photoslv disk */
>>>>
>>>> I have no issues with my LVM disks. Please find on below my LVM
>>>> disks configuration
>>>>
>>>>     lvm> vgs
>>>>       VG      #PV #LV #SN Attr   VSize   VFree
>>>>       data1vg   1   7   0 wz--n- 931,51g 504,60g
>>>>       sysvg     1   1   0 wz--n-  95,12g  78,84g
>>>>
>>>>     lvm> lvs
>>>>       LV        VG      Attr     LSize   Pool Origin Data%  Move Log
>>>>     Copy%  Convert
>>>>       baseslv   data1vg -wi-ao--  
>>>>     1,86g                                          
>>>>       graveurlv data1vg -wi-ao--
>>>>     20,00g                                          
>>>>       homelv    data1vg -wi-ao--
>>>>     50,00g                                          
>>>>       photoslv  data1vg -wi-ao--
>>>>     70,00g                                          
>>>>       vboxlv    data1vg -wi-ao--
>>>>     130,39g                                          
>>>>       videoslv  data1vg -wi-ao--
>>>>     150,00g                                          
>>>>       wwwlv     data1vg -wi-ao--  
>>>>     4,66g                                          
>>>>       optlv     sysvg   -wi-ao--  16,28g
>>>>
>>>>     lvm> lvscan
>>>>       ACTIVE            '/dev/data1vg/photoslv' [70,00 GiB] inherit
>>>>       ACTIVE            '/dev/data1vg/videoslv' [150,00 GiB] inherit
>>>>       ACTIVE            '/dev/data1vg/homelv' [50,00 GiB] inherit
>>>>       ACTIVE            '/dev/data1vg/graveurlv' [20,00 GiB] inherit
>>>>       ACTIVE            '/dev/data1vg/wwwlv' [4,66 GiB] inherit
>>>>       ACTIVE            '/dev/data1vg/baseslv' [1,86 GiB] inherit
>>>>       ACTIVE            '/dev/data1vg/vboxlv' [130,39 GiB] inherit
>>>>       ACTIVE            '/dev/sysvg/optlv' [16,28 GiB] inherit
>>>>
>>>>     root@phlsys:/home/phl/Scripts# df -h
>>>>     Sys. fich.                                             Taille Util.
>>>>     Dispo Uti% Monté sur
>>>>     rootfs                                                    92G  
>>>>     11G   77G  12% /
>>>>     udev                                                      10M    
>>>>     0   10M   0% /dev
>>>>     tmpfs                                                    397M  968K
>>>>     396M   1% /run
>>>>     /dev/disk/by-uuid/4a5a9317-0b70-4796-a094-d61c01891c81    92G  
>>>>     11G   77G  12% /
>>>>     tmpfs                                                    5,0M     0
>>>>     5,0M   0% /run/lock
>>>>     tmpfs                                                    985M  324K
>>>>     985M   1% /run/shm
>>>>     /dev/mapper/sysvg-optlv                                   17G   15G
>>>>     845M  95% /opt
>>>>     /dev/mapper/data1vg-homelv                                50G   40G
>>>>     7,2G  85% /home
>>>>     /dev/mapper/data1vg-wwwlv                                4,6G  2,5G
>>>>     1,9G  58% /www
>>>>     /dev/mapper/data1vg-baseslv                              1,9G  720M
>>>>     1,1G  41% /bases
>>>>     /dev/mapper/data1vg-photoslv                              69G  
>>>>     43G   23G  66% /photos
>>>>     /dev/mapper/data1vg-videoslv                             148G
>>>>     104G   37G  74% /videos
>>>>     /dev/mapper/data1vg-vboxlv                               129G
>>>>     100G   23G  82% /vbox
>>>>     /dev/mapper/data1vg-graveurlv                             20G
>>>>     8,1G   11G  44% /graveur
>>>>
>>>>
>>>> The latest mondo upgrade dated of 25th of december was (it worked
>>>> fine before this upgrade)
>>>>
>>>>     Start-Date: 2014-12-25  18:55:08
>>>>     Commandline: /usr/sbin/synaptic
>>>>     Install: libprojectbuilder-perl:amd64 (0.12.6-1, automatic),
>>>>     libmondorescue-perl:amd64 (3.2.0-1, automatic)
>>>>     Upgrade: mindi:amd64 (2.1.7-1, 3.0.0-1), mondo:amd64 (3.0.4-1,
>>>>     3.2.0-1), mindi-busybox:amd64 (1.18.5-3, 1.21.1-1)
>>>>     End-Date: 2014-12-25  18:55:31
>>>>
>>>> The Debian distro used is
>>>>
>>>>     root@phlsys:/home/phl/Scripts# uname -a
>>>>     Linux phlsys 3.2.0-4-amd64 #1 SMP Debian 3.2.63-2+deb7u2 x86_64
>>>>     GNU/Linux
>>>>
>>>> Anyone have an idea to try to debug this.
>>>>
>>>> Thanks for any help.
>>>>
>>>> By the way, I whish you all an happy new year 2015 with all the best
>>>> in your lifes Kind regards, Philippe
>>>>
>>>>
>>>
>>>
>>>
>>> ---------------------------------------------------------------------
>>> -
>>> -------- Dive into the World of Parallel Programming! The Go Parallel
>>> Website, sponsored by Intel and developed in partnership with
>>> Slashdot Media, is your hub for all things parallel software
>>> development, from weekly thought leadership blogs to news, videos,
>>> case studies, tutorials and more. Take a look and join the conversation now.
>>> http://goparallel.sourceforge.net
>>> _______________________________________________
>>> Mondo-devel mailing list
>>> [hidden email]
>>> https://lists.sourceforge.net/lists/listinfo/mondo-devel
>>> ---------------------------------------------------------------------
>>> -
>>> -------- Dive into the World of Parallel Programming! The Go Parallel
>>> Website, sponsored by Intel and developed in partnership with
>>> Slashdot Media, is your hub for all things parallel software
>>> development, from weekly thought leadership blogs to news, videos,
>>> case studies, tutorials and more. Take a look and join the conversation now.
>>> http://goparallel.sourceforge.net
>>> _______________________________________________
>>> Mondo-devel mailing list
>>> [hidden email]
>>> https://lists.sourceforge.net/lists/listinfo/mondo-devel
>>>
>>
>>
>>
>> ----------------------------------------------------------------------
>> -------- Dive into the World of Parallel Programming! The Go Parallel
>> Website, sponsored by Intel and developed in partnership with Slashdot
>> Media, is your hub for all things parallel software development, from
>> weekly thought leadership blogs to news, videos, case studies,
>> tutorials and more. Take a look and join the conversation now.
>> http://goparallel.sourceforge.net 
>> _______________________________________________
>> Mondo-devel mailing list
>> [hidden email]
>> https://lists.sourceforge.net/lists/listinfo/mondo-devel
>> ----------------------------------------------------------------------
>> -------- Dive into the World of Parallel Programming! The Go Parallel
>> Website, sponsored by Intel and developed in partnership with Slashdot
>> Media, is your hub for all things parallel software development, from
>> weekly thought leadership blogs to news, videos, case studies,
>> tutorials and more. Take a look and join the conversation now.
>> http://goparallel.sourceforge.net 
>> _______________________________________________
>> Mondo-devel mailing list
>> [hidden email]
>> https://lists.sourceforge.net/lists/listinfo/mondo-devel
>>
>
>
> ------------------------------------------------------------------------------
> New Year. New Location. New Benefits. New Data Center in Ashburn, VA.
> GigeNET is offering a free month of service with a new server in Ashburn.
> Choose from 2 high performing configs, both with 100TB of bandwidth.
> Higher redundancy.Lower latency.Increased capacity.Completely compliant.
> http://p.sf.net/sfu/gigenet
> _______________________________________________
> Mondo-devel mailing list
> [hidden email]
> https://lists.sourceforge.net/lists/listinfo/mondo-devel
>


------------------------------------------------------------------------------
New Year. New Location. New Benefits. New Data Center in Ashburn, VA.
GigeNET is offering a free month of service with a new server in Ashburn.
Choose from 2 high performing configs, both with 100TB of bandwidth.
Higher redundancy.Lower latency.Increased capacity.Completely compliant.
http://p.sf.net/sfu/gigenet
_______________________________________________
Mondo-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/mondo-devel

mindi.log (30K) Download Attachment
mondoarchive.log (6K) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Re: [Mondo-devel] Segmentation error running mondoarchive v3.2.0-r3332

Bruno Cornec-2
Hello,

Philippe Lefevre said on Mon, Jan 19, 2015 at 10:34:24PM +0100:

> >>> #2  0x00000000004367c4 in mr_asprintf_int (strp=strp@entry=0x7fffffffe0d0, line=line@entry=258, file=file@entry=0x44187f "libmondo-fork.c",
> >>>     fmt=fmt@entry=0x441d38 "%s > %s/mondo-run-prog-thing.tmp 2>
> >>> %s/mondo-run-prog-thing.err") at mr_mem.c:62
> >>> #3  0x000000000041e0f0 in run_program_and_log_output
> >>> (program=program@entry=0x43c4b4 "umount -d /mnt/cdrom",
> >>> debug_level=debug_level@entry=0)
> >>>     at libmondo-fork.c:258
> >>> #4  0x000000000042ec19 in finish (signal=signal@entry=0) at
> >>> newt-specific.c:388
> >>> #5  0x0000000000403430 in main (argc=2, argv=0x7fffffffe668) at
> >>> mondoarchive.c:176
> >>> (gdb)

Could the umount -d /mnt/cdrom command be the culprit of what you see on
your system ?
What does it retunr and writes ?

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

------------------------------------------------------------------------------
New Year. New Location. New Benefits. New Data Center in Ashburn, VA.
GigeNET is offering a free month of service with a new server in Ashburn.
Choose from 2 high performing configs, both with 100TB of bandwidth.
Higher redundancy.Lower latency.Increased capacity.Completely compliant.
http://p.sf.net/sfu/gigenet
_______________________________________________
Mondo-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/mondo-devel
Reply | Threaded
Open this post in threaded view
|

Re: [Mondo-devel] Segmentation error running mondoarchive v3.2.0-r3332

Philippe Lefevre
Hello Bruno,

I have this kind of message for a long time into the mondoarchive logs
even with the previous version which run fine.
As I don't use any cdrom for my backups (only iso files on HD) the cdrom
is always empty.

Here is what it returns umounting my empty cdrom:

[phlsys]root:/home/phl# umount -d /mnt/cdrom
umount : /mnt/cdrom : n'est pas monté
[phlsys]root:/home/phl# echo $?
1

Kind regards,
Philippe




Le 20/01/2015 01:20, Bruno Cornec a écrit :

> Hello,
>
> Philippe Lefevre said on Mon, Jan 19, 2015 at 10:34:24PM +0100:
>>>>> #2  0x00000000004367c4 in mr_asprintf_int (strp=strp@entry=0x7fffffffe0d0, line=line@entry=258, file=file@entry=0x44187f "libmondo-fork.c",
>>>>>     fmt=fmt@entry=0x441d38 "%s > %s/mondo-run-prog-thing.tmp 2>
>>>>> %s/mondo-run-prog-thing.err") at mr_mem.c:62
>>>>> #3  0x000000000041e0f0 in run_program_and_log_output
>>>>> (program=program@entry=0x43c4b4 "umount -d /mnt/cdrom",
>>>>> debug_level=debug_level@entry=0)
>>>>>     at libmondo-fork.c:258
>>>>> #4  0x000000000042ec19 in finish (signal=signal@entry=0) at
>>>>> newt-specific.c:388
>>>>> #5  0x0000000000403430 in main (argc=2, argv=0x7fffffffe668) at
>>>>> mondoarchive.c:176
>>>>> (gdb)
>
> Could the umount -d /mnt/cdrom command be the culprit of what you see on
> your system ?
> What does it retunr and writes ?
>
> Bruno.
>



------------------------------------------------------------------------------
New Year. New Location. New Benefits. New Data Center in Ashburn, VA.
GigeNET is offering a free month of service with a new server in Ashburn.
Choose from 2 high performing configs, both with 100TB of bandwidth.
Higher redundancy.Lower latency.Increased capacity.Completely compliant.
http://p.sf.net/sfu/gigenet
_______________________________________________
Mondo-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/mondo-devel
Reply | Threaded
Open this post in threaded view
|

Re: [Mondo-devel] Segmentation error running mondoarchive v3.2.0-r3332

Philippe Lefevre
Hello Gattegno,

regarding the "-v" bug you took me about, it has awakened into me some
curiosity.

As I said, I developped with C a long time ago and now I don't feel to
be strong enought with mondo to get into it deeply.
However I had a look into the code and found that, since the 3.2 release
some improvements where done using the function finish() instead of
exit() in order to be sure that all checks and free memory are well done
when the program is stopped.

I noticed that in the case of -v option is given, finish(0) function is
called at the very end of the test. finish() then call mr_asprintf where
va_xxxxx C macros finally fail raising a sigsegv.
This is probably due to a not initialised pointer.

In the case of mondarchive is started with -v option, I think it is not
needed to terminate the test with finish(0) as neither any device check
nor malloc where done. So here, using exit(0) instead of finish(0) works
well and without sigsegv.

I think it can be done in the same way when the root test is done. By
the way, IMHO, it might be interesting for a non root user to get the
mondoarchive release anyway. At the moment, if you do mondoarchive -v as
non root, it only states that you must be root and you must use a sudo
to get the release number.
Hence I invert both root and -v tests and, even in the case where the -v
option is used, the warning message "you're not root" is also displayed.

I hope this help ... thousand of pardons if I'm wrong ...

Please find on bellow the part of the modified mondoarchive.c code.

Kind regards,
Philippe




Original 3.2.0 code
===================
        /* Make sure I'm root; abort if not */
        if (getuid() != 0) {
                fprintf(stderr, "Please run as root.\r\n");
                finish(127);
        }

        /* If -V, -v or --version then echo version no. and quit */
        if (argc == 2 && (!strcmp(argv[argc - 1], "-v") || !strcmp(argv[argc -
1], "-V") || !strcmp(argv[argc - 1], "--version"))) {
                printf("mondoarchive v%s\nSee man page for help\n", PACKAGE_VERSION);
                finish(0);
        }



Modified 3.2.0 code
===================
        /* If -V, -v or --version then echo version no. and quit */
        if (argc == 2 && (!strcmp(argv[argc - 1], "-v") || !strcmp(argv[argc -
1], "-V") || !strcmp(argv[argc - 1], "--version"))) {
                printf("mondoarchive v%s\nSee man page for help\n", PACKAGE_VERSION);
                if (getuid() != 0) fprintf(stderr, "Please run as root.\r\n");
                exit(0);
        }

        /* Make sure I'm root; abort if not */
        if (getuid() != 0) {
                fprintf(stderr, "Please run as root.\r\n");
                exit(127);
        }



Le 20/01/2015 20:06, Philippe Lefevre a écrit :

> Hello Bruno,
>
> I have this kind of message for a long time into the mondoarchive logs
> even with the previous version which run fine.
> As I don't use any cdrom for my backups (only iso files on HD) the cdrom
> is always empty.
>
> Here is what it returns umounting my empty cdrom:
>
> [phlsys]root:/home/phl# umount -d /mnt/cdrom
> umount : /mnt/cdrom : n'est pas monté
> [phlsys]root:/home/phl# echo $?
> 1
>
> Kind regards,
> Philippe
>
>
>
>
> Le 20/01/2015 01:20, Bruno Cornec a écrit :
>> Hello,
>>
>> Philippe Lefevre said on Mon, Jan 19, 2015 at 10:34:24PM +0100:
>>>>>> #2  0x00000000004367c4 in mr_asprintf_int (strp=strp@entry=0x7fffffffe0d0, line=line@entry=258, file=file@entry=0x44187f "libmondo-fork.c",
>>>>>>     fmt=fmt@entry=0x441d38 "%s > %s/mondo-run-prog-thing.tmp 2>
>>>>>> %s/mondo-run-prog-thing.err") at mr_mem.c:62
>>>>>> #3  0x000000000041e0f0 in run_program_and_log_output
>>>>>> (program=program@entry=0x43c4b4 "umount -d /mnt/cdrom",
>>>>>> debug_level=debug_level@entry=0)
>>>>>>     at libmondo-fork.c:258
>>>>>> #4  0x000000000042ec19 in finish (signal=signal@entry=0) at
>>>>>> newt-specific.c:388
>>>>>> #5  0x0000000000403430 in main (argc=2, argv=0x7fffffffe668) at
>>>>>> mondoarchive.c:176
>>>>>> (gdb)
>>
>> Could the umount -d /mnt/cdrom command be the culprit of what you see on
>> your system ?
>> What does it retunr and writes ?
>>
>> Bruno.
>>
>
>
>



------------------------------------------------------------------------------
New Year. New Location. New Benefits. New Data Center in Ashburn, VA.
GigeNET is offering a free month of service with a new server in Ashburn.
Choose from 2 high performing configs, both with 100TB of bandwidth.
Higher redundancy.Lower latency.Increased capacity.Completely compliant.
http://p.sf.net/sfu/gigenet
_______________________________________________
Mondo-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/mondo-devel
Reply | Threaded
Open this post in threaded view
|

Re: [Mondo-devel] Segmentation error running mondoarchive v3.2.0-r3332

Bruno Cornec-2
Hello Philippe,

Philippe Lefevre said on Sun, Jan 25, 2015 at 11:02:43AM +0100:
> I noticed that in the case of -v option is given, finish(0) function is
> called at the very end of the test. finish() then call mr_asprintf where
> va_xxxxx C macros finally fail raising a sigsegv.
> This is probably due to a not initialised pointer.

Yep.

> In the case of mondarchive is started with -v option, I think it is not
> needed to terminate the test with finish(0) as neither any device check
> nor malloc where done. So here, using exit(0) instead of finish(0) works
> well and without sigsegv.
>
> I think it can be done in the same way when the root test is done. By
> the way, IMHO, it might be interesting for a non root user to get the
> mondoarchive release anyway. At the moment, if you do mondoarchive -v as
> non root, it only states that you must be root and you must use a sudo
> to get the release number.
> Hence I invert both root and -v tests and, even in the case where the -v
> option is used, the warning message "you're not root" is also displayed.
>
> I hope this help ... thousand of pardons if I'm wrong ...

It definitely helps ! Your patch is in rev 3333
http://trac.mondorescue.org/changeset?reponame=&new=3333%40branches%2F3.2&old=3332%40branches%2F3.2

Thanks a lot for having taking time to dig into it !
Bruno.
--
Open Source Profession, Linux Community Lead WW http://opensource.hp.com
EMEA EG Open Source Technology Strategist       http://hpintelco.net
FLOSS projects:     http://mondorescue.org     http://project-builder.org 
Musique ancienne? http://www.musique-ancienne.org http://www.medieval.org

------------------------------------------------------------------------------
New Year. New Location. New Benefits. New Data Center in Ashburn, VA.
GigeNET is offering a free month of service with a new server in Ashburn.
Choose from 2 high performing configs, both with 100TB of bandwidth.
Higher redundancy.Lower latency.Increased capacity.Completely compliant.
http://p.sf.net/sfu/gigenet
_______________________________________________
Mondo-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/mondo-devel
Reply | Threaded
Open this post in threaded view
|

Re: [Mondo-devel] Segmentation error running mondoarchive v3.2.0-r3332

Bruno Cornec-2
In reply to this post by Philippe Lefevre
Hello Philippe,

This is now fixed as described in BR:
http://trac.mondorescue.org/ticket/764#comment:2

Bruno.

Philippe Lefevre said on Mon, Jan 19, 2015 at 10:34:24PM +0100:

> Hello Gaetagno,
>
> Regarding the two slashes, as I said, I used the same syntax to get into
> the same bug situation.
>
>
> I did a try with only one / in the -I option and got the same
> segmentation violation exception.
>
>
> Mindi launched alone as your example and it ran fine and the iso file
> successfully built.
> Please find attached the mindi.log file.
>
> [phlsys]root:/home/phl/Devel/mondo# ls -al /var/cache/mindi/mindi.iso
> -rw-r----- 1 root root 98721792 janv. 19 22:09 /var/cache/mindi/mindi.iso
>
>
>
> Ran mondoarchive with -K99 option crashed again with the sigsegv signal.
> Please find attached the mondoarchive.log file.
> Unfortunately, I'm afraid it is not so verbose than we would ...
> This time, the log ends with :
>
> DBG1: [Main] libmondo-cli.c->process_switches#181: Loglevel forced to 99
> DBG20: [Main] libmondo-files.c->does_file_exist#188: /usr/bin/afio exists
> DBG4: [Main] libmondo-files.c->find_home_of_exe#349: find_home_of_exe
> --- Found afio at /usr/bin/afio
>
>
>
> Running mondo without - E option crashed in the same way and with same
> mondoarchive.log file.
> [phlsys]root:/home/phl/Devel/mondo# /usr/sbin/mondoarchive -K99 -D -OV
> -i -N -G -s 780M -p sys-D7.7-diff_150105212200 -T /graveur -S /graveur
> -d /graveur -I "/opt/zuma"
> See /var/log/mondoarchive.log for details of backup run.
> Checking sanity of your Linux distribution
> Done.
> Erreur de segmentation
>
>
> Thank you for your time Gaetagno.
> Kind regards,
> Philippe
>
>
>
> Le 19/01/2015 12:17, Gattegno, Victor (GSD CSC / GCC) a écrit :
> > Hi Philippe,
> >
> > You used again two time "/"  in the include :
> > -I "/|/|/opt/Zuma"
> >
> > Your mondorachive.log file ends with :
> > DBG4: [Main] libmondo-files.c->find_home_of_exe#349: find_home_of_exe --- Found afio at /usr/bin/afio
> >
> > You can try a few things :
> >
> > Try mindi alone :
> > # mindi
> > Do you want to use your own kernel to build the boot disk ([y]/n) ? y
> >
> > Try your mondoarchive command without -E, with only -I, and choice only one directory, example :
> > -I "/opt/Zuma"
> >
> > Try your mondoarchive command with more debug, example with -K 5, or with -K 99 (which is full debug mode, be aware that the log file could grow from 200 Kb to 50 Mb).
> >
> > Rgds,
> > Victor
> >
> > -----Original Message-----
> > From: Philippe Lefevre [mailto:[hidden email]]
> > Sent: samedi 17 janvier 2015 20:14
> > To: Mondo mailing list
> > Subject: Re: [Mondo-devel] Segmentation error running mondoarchive v3.2.0-r3332
> >
> > Hello list,
> >
> > sorry Gaetagno for the delay, I was not able to find some time long enought to go back into my issue.
> >
> > I did it today (without removing the two slashes in order to be in the same situation) and .... what I compiled worked fine with what I have compiled. (I noticed the -v bug, thanks  ;)  )
> >
> > Run mondoarchive via dbg:
> > [phlsys]root:/home/phl/mondo-3.2.0# gdb -args mondoarchive -D -OV -i -N -G -s 780M -p sys-D7.7-diff_150105212200 -T /graveur -S /graveur -d /graveur -I "/|/|/opt/Zuma" -E "/bases/sybase|/graveur|/home|/opt|/photos|/quemu|/Sauvegardes|/var/crash|/var/backups|/var/log|/var/mail|/var/spool|/vbox|/videos|/www"
> >
> > and:
> > ....
> > Data archived OK.
> > Mondoarchive ran OK.
> > See /var/log/mondoarchive.log for details of backup run.
> > Execution run ended; result=0
> > Type 'less /var/log/mondoarchive.log' to see the output log [Inferior 1 (process 19382) exited normally]
> > (gdb) quit
> >
> >
> > So I reinstalled the official debian package:
> >
> > Sélection du paquet libmondorescue-perl précédemment désélectionné.
> > (Lecture de la base de données... 279208 fichiers et répertoires déjà
> > installés.)
> > Dépaquetage de libmondorescue-perl (à partir de
> > .../libmondorescue-perl_3.2.0-1_all.deb) ...
> > Préparation du remplacement de mindi-busybox 1.18.5-3 (en utilisant
> > .../mindi-busybox_1.21.1-1_amd64.deb) ...
> > Dépaquetage de la mise à jour de mindi-busybox ...
> > Préparation du remplacement de mindi 2.1.7-1 (en utilisant
> > .../mindi_3.0.0-1_amd64.deb) ...
> > Dépaquetage de la mise à jour de mindi ...
> > Préparation du remplacement de mondo 3.0.4-1 (en utilisant
> > .../mondo_3.2.0-1_amd64.deb) ...
> > Dépaquetage de la mise à jour de mondo ...
> > Traitement des actions différées (« triggers ») pour « man-db »...
> > Paramétrage de libmondorescue-perl (3.2.0-1) ...
> > Paramétrage de mindi-busybox (1.21.1-1) ...
> > Paramétrage de mindi (3.0.0-1) ...
> > Installation de la nouvelle version du fichier de configuration /etc/mindi/deplist.d/minimal.conf ...
> > Installation de la nouvelle version du fichier de configuration /etc/mindi/deplist.d/udev.conf ...
> > Installation de la nouvelle version du fichier de configuration /etc/mindi/deplist.d/ProLiant.conf ...
> > Installation de la nouvelle version du fichier de configuration /etc/mindi/deplist.d/base.conf ...
> > Installation de la nouvelle version du fichier de configuration /etc/mindi/deplist.d/lvm.conf ...
> > Installation de la nouvelle version du fichier de configuration /etc/mindi/perl-scripts ...
> > Paramétrage de mondo (3.2.0-1) ...
> >
> >
> > but launched in the same way, it crashed again with a segmentation error:
> >
> > [phlsys]root:/home/phl/telechargements/mondo-3.2.0# mondoarchive -D -OV -i -N -G -s 780M -p sys-D7.7-diff_150105212200 -T /graveur -S /graveur -d /graveur -I "/|/|/opt/Zuma" -E "/bases/sybase|/graveur|/home|/opt|/photos|/quemu|/Sauvegardes|/var/crash|/var/backups|/var/log|/var/mail|/var/spool|/vbox|/videos|/www"
> > See /var/log/mondoarchive.log for details of backup run.
> > Checking sanity of your Linux distribution Done.
> > Erreur de segmentation
> >
> >
> >
> > Please find attached the relevant mondoarchive.log file.
> > It seems to be stopped before logging something about the fault.
> > I franckly don't know what I could do more.
> > Do you have an idea about what I could do to explore deeper this issue ?
> > Something might be going wrong into the deb pkg ???
> > I got it with apt using:
> >    deb ftp://ftp.mondorescue.org//debian 7 contrib
> >
> >
> > Thanks for your help.
> > Regards,
> > Philippe
> >
> >
> >
> >
> >
> > Le 06/01/2015 17:28, Gattegno, Victor (GSD CSC / GCC) a écrit :
> >> Hello Philippe,
> >>
> >> From mondoarchive man : " When using the -I option with the -E option, the -E content should be subdirectories of those mentioned in the -I only, as -I takes precedence."
> >>
> >> But if your -I and -E combination works it's ok (check if /opt/zuma and /opt/calibre are well backuped and restored).
> >>
> >> Regards,
> >> Victor
> >>
> >> -----Original Message-----
> >> From: Philippe Lefevre [mailto:[hidden email]]
> >> Sent: lundi 5 janvier 2015 21:42
> >> To: [hidden email]
> >> Subject: Re: [Mondo-devel] Segmentation error running mondoarchive
> >> v3.2.0-r3332
> >>
> >> Thanks for your help and reply Victor,
> >>
> >> I should be able to replay with all of that before the end of the week and let you know.
> >> Regarding the double /, it is due to my shell script which build the final request. I will also do a try without it.
> >>
> >> I believe I couldn't remove -I flag as in the exclude part there is /opt and I want to include only 2 directories /opt/zuma and /opt/calibre. At least, I should use -I "/opt/calibre|/opt/Zuma" right?
> >>
> >> PS: my system backup is run by root and ulimit is setted unlimited:
> >>
> >> # ulimit -a
> >> core file size          (blocks, -c) 0
> >> data seg size           (kbytes, -d) unlimited
> >> scheduling priority             (-e) 0
> >> file size               (blocks, -f) unlimited
> >> pending signals                 (-i) 31106
> >> max locked memory       (kbytes, -l) 64
> >> max memory size         (kbytes, -m) unlimited
> >> open files                      (-n) 1024
> >> pipe size            (512 bytes, -p) 8
> >> POSIX message queues     (bytes, -q) 819200
> >> real-time priority              (-r) 0
> >> stack size              (kbytes, -s) 8192
> >> cpu time               (seconds, -t) unlimited
> >> max user processes              (-u) 31106
> >> virtual memory          (kbytes, -v) unlimited
> >> file locks                      (-x) unlimited
> >>
> >>
> >> Rgds,
> >> Philippe
> >>
> >>
> >> Le 05/01/2015 16:32, Gattegno, Victor (GSD CSC / GCC) a écrit :
> >>> Hello Philippe,
> >>>
> >>> Good gdb work, but don't focus on "mondoarchive -v" segmentation fault, it's a known failing bug. It's better to debug mondoarchive with the options that you use.
> >>>
> >>>  In your 27/12/2014 test and post:
> >>>  - did you posted too the associated /var/log/mondoarchive.log (compressed) ?
> >>>  - you used -I (with / included twice) and -E options, it's better to use only -E option.
> >>>
> >>> What's the result of "ulimit -a" on your Debian ?
> >>>
> >>> I wish to you - and to all this mailig-list users - a nice year 2015.
> >>>
> >>> Rgds,
> >>> Victor
> >>>
> >>> -----Original Message-----
> >>> From: Philippe Lefevre [mailto:[hidden email]]
> >>> Sent: samedi 3 janvier 2015 14:32
> >>> To: [hidden email]
> >>> Subject: Re: [Mondo-devel] Segmentation error running mondoarchive
> >>> v3.2.0-r3332
> >>>
> >>> Hi list,
> >>>
> >>> Some more information about my issue.
> >>>
> >>> I can confirm that in my case it is related to this new release as a I did a downgrade and successfully built a new full backup.
> >>>
> >>> I uninstalled and purged
> >>>   libmondorescue-perl_3.2.0-1_all.deb
> >>>   mindi-busybox_1.21.1-1_amd64.deb
> >>>   mindi_3.0.0-1_amd64.deb
> >>>   mondo_3.2.0-1_amd64.deb
> >>>
> >>> and reinstalled the previous version
> >>>   mindi-busybox 1.18.5-3
> >>>   mindi 2.1.7-1
> >>>   mondo 3.0.4-1
> >>>
> >>> I also compiled mondo 3.2.0 from sources and ran gdb against the simpliest command that raise the seg error. It shows :
> >>>
> >>> Starting program:
> >>> /home/phl/telechargements/mondo-3.2.0/src/mondoarchive/mondoarchive -v [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
> >>> mondoarchive v3.2.0-r3332
> >>> See man page for help
> >>>
> >>> Program received signal SIGSEGV, Segmentation fault.
> >>> 0x00007ffff76629aa in vfprintf () from
> >>> /lib/x86_64-linux-gnu/libc.so.6
> >>> (gdb) bt
> >>> #0  0x00007ffff76629aa in vfprintf () from
> >>> /lib/x86_64-linux-gnu/libc.so.6
> >>> #1  0x00007ffff7688fca in vasprintf () from
> >>> /lib/x86_64-linux-gnu/libc.so.6
> >>> #2  0x00000000004367c4 in mr_asprintf_int (strp=strp@entry=0x7fffffffe0d0, line=line@entry=258, file=file@entry=0x44187f "libmondo-fork.c",
> >>>     fmt=fmt@entry=0x441d38 "%s > %s/mondo-run-prog-thing.tmp 2>
> >>> %s/mondo-run-prog-thing.err") at mr_mem.c:62
> >>> #3  0x000000000041e0f0 in run_program_and_log_output
> >>> (program=program@entry=0x43c4b4 "umount -d /mnt/cdrom",
> >>> debug_level=debug_level@entry=0)
> >>>     at libmondo-fork.c:258
> >>> #4  0x000000000042ec19 in finish (signal=signal@entry=0) at
> >>> newt-specific.c:388
> >>> #5  0x0000000000403430 in main (argc=2, argv=0x7fffffffe668) at
> >>> mondoarchive.c:176
> >>> (gdb)
> >>>
> >>>
> >>> function code exerpt
> >>>
> >>>    56 void mr_asprintf_int(char **strp, int line, const char *file, const char *fmt, ...) {
> >>>    57
> >>>    58 int res = 0;
> >>>    59 va_list args;
> >>>    60
> >>>    61 va_start(args,fmt);
> >>>    62 res = vasprintf(strp, fmt, args);
> >>>    63 if (res == -1) {
> >>>    64 mr_msg_int(1,line,file,"Unable to alloc memory in
> >>> mr_asprintf\nExiting...");
> >>>    65 mr_exit(-1,"Unable to alloc memory in mr_asprintf");
> >>>    66 }
> >>>    67 va_end(args);
> >>>    68 }
> >>>
> >>>
> >>> Breakpoint 1, mr_asprintf_int (strp=strp@entry=0x7fffffffe0d0, line=line@entry=258, file=file@entry=0x44187f "libmondo-fork.c",
> >>>     fmt=fmt@entry=0x441d38 "%s > %s/mondo-run-prog-thing.tmp 2>
> >>> %s/mondo-run-prog-thing.err") at mr_mem.c:56
> >>> 56 void mr_asprintf_int(char **strp, int line, const char *file, const
> >>> char *fmt, ...) {
> >>> (gdb) s
> >>> 61 va_start(args,fmt);
> >>> (gdb) display fmt
> >>> 1: fmt = 0x441d38 "%s > %s/mondo-run-prog-thing.tmp 2> %s/mondo-run-prog-thing.err"
> >>> (gdb) display args
> >>> 2: args = {{gp_offset = 4158558940, fp_offset = 32767,
> >>> overflow_arg_area = 0x7ffff7fd5000, reg_save_area = 0x7ffff7ffd9d8}}
> >>> (gdb) s
> >>> 62 res = vasprintf(strp, fmt, args);
> >>> 2: args = {{gp_offset = 4158558940, fp_offset = 32767,
> >>> overflow_arg_area = 0x7ffff7fd5000, reg_save_area = 0x7ffff7ffd9d8}}
> >>> 1: fmt = 0x441d38 "%s > %s/mondo-run-prog-thing.tmp 2> %s/mondo-run-prog-thing.err"
> >>> (gdb) s
> >>> 61 va_start(args,fmt);
> >>> 2: args = {{gp_offset = 4158558940, fp_offset = 32767,
> >>> overflow_arg_area = 0x7ffff7fd5000, reg_save_area = 0x7ffff7ffd9d8}}
> >>> 1: fmt = 0x441d38 "%s > %s/mondo-run-prog-thing.tmp 2> %s/mondo-run-prog-thing.err"
> >>> (gdb) s
> >>> 62 res = vasprintf(strp, fmt, args);
> >>> 2: args = {{gp_offset = 32, fp_offset = 48, overflow_arg_area =
> >>> 0x7fffffffe0b0, reg_save_area = 0x7fffffffdfe0}}
> >>> 1: fmt = 0x441d38 "%s > %s/mondo-run-prog-thing.tmp 2> %s/mondo-run-prog-thing.err"
> >>> (gdb) display res
> >>> 3: res = 0
> >>> (gdb) s
> >>>
> >>> Program received signal SIGSEGV, Segmentation fault.
> >>> 0x00007ffff76629aa in vfprintf () from
> >>> /lib/x86_64-linux-gnu/libc.so.6
> >>> (gdb)
> >>>
> >>>
> >>> It seems there is an issue with mr_asprintf_int but sorry I don't feel strong enought to get more deeply into the mondo code and analyze it properly ...
> >>>
> >>> I hope this help ...
> >>>
> >>> Regards,
> >>> Philippe
> >>>
> >>>
> >>> Le 27/12/2014 11:17, [hidden email] a écrit :
> >>>> Hi all,
> >>>>
> >>>> it seems that something goes wrong with mondo I could link to the
> >>>> latest Debian version of MondoRescue.
> >>>>
> >>>> I updated my version last thursday and this morning (I have a
> >>>> differential backup launched every friday night and one full a
> >>>> month) it failed.
> >>>> Unfortunately there are no much relevant informations in logs.
> >>>>
> >>>> The errors raised is :
> >>>>
> >>>>     # mondoarchive -D -OV -i -N -G -s 780M -p sys-D7.7-diff_141227100000
> >>>>     -T /graveur -S /graveur -d
> >>>>     /media/sauvegardes/phlsys/D7.7/sys/141227100000 -I
> >>>>     "/|/|/opt/calibre|/opt/Zuma" -E
> >>>>     "/bases/sybase|/graveur|/home|/opt|/photos|/quemu|/Sauvegardes|/var/crash|/var/backups|/var/log|/var/mail|/var/spool|/vbox|/videos|/www"
> >>>>     See /var/log/mondoarchive.log for details of backup run.
> >>>>     Checking sanity of your Linux distribution
> >>>>     Done.
> >>>>     Erreur de segmentation                /* Segmentation error */
> >>>>
> >>>> Please find attached the log files that seems to find out an issue
> >>>> with LVM disks
> >>>>
> >>>>     INFO: Mindi v3.0.0-r3332
> >>>>     INFO: Le disque /dev/mapper/data1vg-photoslv ne contient pas une
> >>>>     table de partitions valable
> >>>>              /* there is no valid partition table in
> >>>>     /dev/mapper/data1vg-photoslv disk */
> >>>>
> >>>> I have no issues with my LVM disks. Please find on below my LVM
> >>>> disks configuration
> >>>>
> >>>>     lvm> vgs
> >>>>       VG      #PV #LV #SN Attr   VSize   VFree
> >>>>       data1vg   1   7   0 wz--n- 931,51g 504,60g
> >>>>       sysvg     1   1   0 wz--n-  95,12g  78,84g
> >>>>
> >>>>     lvm> lvs
> >>>>       LV        VG      Attr     LSize   Pool Origin Data%  Move Log
> >>>>     Copy%  Convert
> >>>>       baseslv   data1vg -wi-ao--  
> >>>>     1,86g                                          
> >>>>       graveurlv data1vg -wi-ao--
> >>>>     20,00g                                          
> >>>>       homelv    data1vg -wi-ao--
> >>>>     50,00g                                          
> >>>>       photoslv  data1vg -wi-ao--
> >>>>     70,00g                                          
> >>>>       vboxlv    data1vg -wi-ao--
> >>>>     130,39g                                          
> >>>>       videoslv  data1vg -wi-ao--
> >>>>     150,00g                                          
> >>>>       wwwlv     data1vg -wi-ao--  
> >>>>     4,66g                                          
> >>>>       optlv     sysvg   -wi-ao--  16,28g
> >>>>
> >>>>     lvm> lvscan
> >>>>       ACTIVE            '/dev/data1vg/photoslv' [70,00 GiB] inherit
> >>>>       ACTIVE            '/dev/data1vg/videoslv' [150,00 GiB] inherit
> >>>>       ACTIVE            '/dev/data1vg/homelv' [50,00 GiB] inherit
> >>>>       ACTIVE            '/dev/data1vg/graveurlv' [20,00 GiB] inherit
> >>>>       ACTIVE            '/dev/data1vg/wwwlv' [4,66 GiB] inherit
> >>>>       ACTIVE            '/dev/data1vg/baseslv' [1,86 GiB] inherit
> >>>>       ACTIVE            '/dev/data1vg/vboxlv' [130,39 GiB] inherit
> >>>>       ACTIVE            '/dev/sysvg/optlv' [16,28 GiB] inherit
> >>>>
> >>>>     root@phlsys:/home/phl/Scripts# df -h
> >>>>     Sys. fich.                                             Taille Util.
> >>>>     Dispo Uti% Monté sur
> >>>>     rootfs                                                    92G  
> >>>>     11G   77G  12% /
> >>>>     udev                                                      10M    
> >>>>     0   10M   0% /dev
> >>>>     tmpfs                                                    397M  968K
> >>>>     396M   1% /run
> >>>>     /dev/disk/by-uuid/4a5a9317-0b70-4796-a094-d61c01891c81    92G  
> >>>>     11G   77G  12% /
> >>>>     tmpfs                                                    5,0M     0
> >>>>     5,0M   0% /run/lock
> >>>>     tmpfs                                                    985M  324K
> >>>>     985M   1% /run/shm
> >>>>     /dev/mapper/sysvg-optlv                                   17G   15G
> >>>>     845M  95% /opt
> >>>>     /dev/mapper/data1vg-homelv                                50G   40G
> >>>>     7,2G  85% /home
> >>>>     /dev/mapper/data1vg-wwwlv                                4,6G  2,5G
> >>>>     1,9G  58% /www
> >>>>     /dev/mapper/data1vg-baseslv                              1,9G  720M
> >>>>     1,1G  41% /bases
> >>>>     /dev/mapper/data1vg-photoslv                              69G  
> >>>>     43G   23G  66% /photos
> >>>>     /dev/mapper/data1vg-videoslv                             148G
> >>>>     104G   37G  74% /videos
> >>>>     /dev/mapper/data1vg-vboxlv                               129G
> >>>>     100G   23G  82% /vbox
> >>>>     /dev/mapper/data1vg-graveurlv                             20G
> >>>>     8,1G   11G  44% /graveur
> >>>>
> >>>>
> >>>> The latest mondo upgrade dated of 25th of december was (it worked
> >>>> fine before this upgrade)
> >>>>
> >>>>     Start-Date: 2014-12-25  18:55:08
> >>>>     Commandline: /usr/sbin/synaptic
> >>>>     Install: libprojectbuilder-perl:amd64 (0.12.6-1, automatic),
> >>>>     libmondorescue-perl:amd64 (3.2.0-1, automatic)
> >>>>     Upgrade: mindi:amd64 (2.1.7-1, 3.0.0-1), mondo:amd64 (3.0.4-1,
> >>>>     3.2.0-1), mindi-busybox:amd64 (1.18.5-3, 1.21.1-1)
> >>>>     End-Date: 2014-12-25  18:55:31
> >>>>
> >>>> The Debian distro used is
> >>>>
> >>>>     root@phlsys:/home/phl/Scripts# uname -a
> >>>>     Linux phlsys 3.2.0-4-amd64 #1 SMP Debian 3.2.63-2+deb7u2 x86_64
> >>>>     GNU/Linux
> >>>>
> >>>> Anyone have an idea to try to debug this.
> >>>>
> >>>> Thanks for any help.
> >>>>
> >>>> By the way, I whish you all an happy new year 2015 with all the best
> >>>> in your lifes Kind regards, Philippe
> >>>>
> >>>>
> >>>
> >>>
> >>>
> >>> ---------------------------------------------------------------------
> >>> -
> >>> -------- Dive into the World of Parallel Programming! The Go Parallel
> >>> Website, sponsored by Intel and developed in partnership with
> >>> Slashdot Media, is your hub for all things parallel software
> >>> development, from weekly thought leadership blogs to news, videos,
> >>> case studies, tutorials and more. Take a look and join the conversation now.
> >>> http://goparallel.sourceforge.net
> >>> _______________________________________________
> >>> Mondo-devel mailing list
> >>> [hidden email]
> >>> https://lists.sourceforge.net/lists/listinfo/mondo-devel
> >>> ---------------------------------------------------------------------
> >>> -
> >>> -------- Dive into the World of Parallel Programming! The Go Parallel
> >>> Website, sponsored by Intel and developed in partnership with
> >>> Slashdot Media, is your hub for all things parallel software
> >>> development, from weekly thought leadership blogs to news, videos,
> >>> case studies, tutorials and more. Take a look and join the conversation now.
> >>> http://goparallel.sourceforge.net
> >>> _______________________________________________
> >>> Mondo-devel mailing list
> >>> [hidden email]
> >>> https://lists.sourceforge.net/lists/listinfo/mondo-devel
> >>>
> >>
> >>
> >>
> >> ----------------------------------------------------------------------
> >> -------- Dive into the World of Parallel Programming! The Go Parallel
> >> Website, sponsored by Intel and developed in partnership with Slashdot
> >> Media, is your hub for all things parallel software development, from
> >> weekly thought leadership blogs to news, videos, case studies,
> >> tutorials and more. Take a look and join the conversation now.
> >> http://goparallel.sourceforge.net 
> >> _______________________________________________
> >> Mondo-devel mailing list
> >> [hidden email]
> >> https://lists.sourceforge.net/lists/listinfo/mondo-devel
> >> ----------------------------------------------------------------------
> >> -------- Dive into the World of Parallel Programming! The Go Parallel
> >> Website, sponsored by Intel and developed in partnership with Slashdot
> >> Media, is your hub for all things parallel software development, from
> >> weekly thought leadership blogs to news, videos, case studies,
> >> tutorials and more. Take a look and join the conversation now.
> >> http://goparallel.sourceforge.net 
> >> _______________________________________________
> >> Mondo-devel mailing list
> >> [hidden email]
> >> https://lists.sourceforge.net/lists/listinfo/mondo-devel
> >>
> >
> >
> > ------------------------------------------------------------------------------
> > New Year. New Location. New Benefits. New Data Center in Ashburn, VA.
> > GigeNET is offering a free month of service with a new server in Ashburn.
> > Choose from 2 high performing configs, both with 100TB of bandwidth.
> > Higher redundancy.Lower latency.Increased capacity.Completely compliant.
> > http://p.sf.net/sfu/gigenet
> > _______________________________________________
> > Mondo-devel mailing list
> > [hidden email]
> > https://lists.sourceforge.net/lists/listinfo/mondo-devel
> >
>
>

> mindi v3.0.0-r3332
> x86_64 architecture detected
> mindi called with the following arguments:
> --makemountlist /tmp/mondo.tmp.4v41Vd/mountlist.txt.test
> Start date : lundi 19 janvier 2015, 22:16:43 (UTC+0100)
> -----------------------------
> MONDO_SHARE = /usr/share/mondo
> MINDI_LIB = /usr/lib/mindi
> MINDI_SBIN = /usr/sbin
> MINDI_CONF = /etc/mindi
> -----------------------------
>  Mindi configuration file    
> -----------------------------
> -----------------------------
> In Mindi
> --------
> EXTRA_SPACE = 120000
> BOOT_SIZE = 65600
> --------
> INFO: Found isolinux.bin at /usr/lib/syslinux/isolinux.bin
> INFO: LVM set to v2
> ----------
> mount result:
> -------------
> sysfs on /sys type sysfs (rw,nosuid,nodev,noexec,relatime)
> proc on /proc type proc (rw,nosuid,nodev,noexec,relatime)
> udev on /dev type devtmpfs (rw,relatime,size=10240k,nr_inodes=497709,mode=755)
> devpts on /dev/pts type devpts (rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000)
> tmpfs on /run type tmpfs (rw,nosuid,noexec,relatime,size=406288k,mode=755)
> /dev/disk/by-uuid/4a5a9317-0b70-4796-a094-d61c01891c81 on / type ext4 (rw,relatime,errors=remount-ro,user_xattr,barrier=1,data=ordered)
> tmpfs on /run/lock type tmpfs (rw,nosuid,nodev,noexec,relatime,size=5120k)
> tmpfs on /run/shm type tmpfs (rw,nosuid,nodev,noexec,relatime,size=1008560k)
> /dev/mapper/sysvg-optlv on /opt type ext4 (rw,relatime,errors=remount-ro,user_xattr,barrier=1,data=ordered)
> /dev/mapper/data1vg-homelv on /home type ext4 (rw,relatime,errors=remount-ro,user_xattr,barrier=1,data=ordered)
> /dev/mapper/data1vg-wwwlv on /www type ext4 (rw,relatime,errors=remount-ro,user_xattr,barrier=1,data=ordered)
> /dev/mapper/data1vg-baseslv on /bases type ext4 (rw,relatime,errors=remount-ro,user_xattr,barrier=1,data=ordered)
> /dev/mapper/data1vg-photoslv on /photos type ext4 (rw,relatime,errors=remount-ro,user_xattr,barrier=1,data=ordered)
> /dev/mapper/data1vg-videoslv on /videos type ext4 (rw,relatime,errors=remount-ro,user_xattr,barrier=1,data=ordered)
> /dev/mapper/data1vg-vboxlv on /vbox type ext4 (rw,relatime,errors=remount-ro,user_xattr,barrier=1,data=ordered)
> /dev/mapper/data1vg-graveurlv on /graveur type ext4 (rw,relatime,errors=remount-ro,user_xattr,barrier=1,data=ordered)
> rpc_pipefs on /var/lib/nfs/rpc_pipefs type rpc_pipefs (rw,relatime)
> binfmt_misc on /proc/sys/fs/binfmt_misc type binfmt_misc (rw,nosuid,nodev,noexec,relatime)
> No file /etc/raidtab
> -------------
> No file /etc/mdadm.conf
> -------------
> cat /proc/cmdline
> -------------
> BOOT_IMAGE=/boot/vmlinuz-3.2.0-4-amd64 root=UUID=4a5a9317-0b70-4796-a094-d61c01891c81 ro quiet
> -------------
> cat /proc/swaps:
> -------------
> Filename Type Size Used Priority
> /dev/sda6                               partition 979928 11992 -1
> -------------
> cat /proc/mdstat:
> -------------
> Personalities : [linear] [raid0] [raid1] [raid6] [raid5] [raid4]
> unused devices: <none>
> -------------
> cat /proc/partitions:
> -------------
> major minor  #blocks  name
>
>    8        0  312571224 sda
>    8        1      56196 sda1
>    8        2   10485760 sda2
>    8        3  103643080 sda3
>    8        4          1 sda4
>    8        5   97659103 sda5
>    8        6     979933 sda6
>    8        7   99741696 sda7
>   11        0    1048575 sr0
>    8       16  976762584 sdb
>    8       17  976761560 sdb1
>  253        0   73400320 dm-0
>  253        1  157286400 dm-1
>  253        2   52428800 dm-2
>  253        3   20971520 dm-3
>  253        4    4886528 dm-4
>  253        5    1953792 dm-5
>  253        6  136720384 dm-6
>  253        7   17072128 dm-7
> -------------
> cat /proc/filesystems:
> -------------
> nodev sysfs
> nodev rootfs
> nodev bdev
> nodev proc
> nodev cgroup
> nodev cpuset
> nodev tmpfs
> nodev devtmpfs
> nodev debugfs
> nodev securityfs
> nodev sockfs
> nodev pipefs
> nodev anon_inodefs
> nodev devpts
> nodev ramfs
> nodev hugetlbfs
> nodev pstore
> nodev mqueue
> nodev usbfs
> ext4
> nodev ecryptfs
> nodev rpc_pipefs
> nodev nfs
> nodev nfs4
> nodev nfsd
> nodev binfmt_misc
> msdos
> vfat
> iso9660
> ext2
> -------------
> lsmod result:
> -------------
> Module                  Size  Used by
> nls_utf8               12456  0
> nls_cp437              16553  0
> ext2                   59231  0
> raid456                48453  0
> async_raid6_recov      12574  1 raid456
> async_memcpy           12387  2 async_raid6_recov,raid456
> async_pq               12605  2 async_raid6_recov,raid456
> raid6_pq               82624  2 async_pq,async_raid6_recov
> async_xor              12422  3 async_pq,async_raid6_recov,raid456
> xor                    12605  1 async_xor
> async_tx               12604  5 async_xor,async_pq,async_memcpy,async_raid6_recov,raid456
> raid1                  30714  0
> raid0                  12904  0
> linear                 12735  0
> isofs                  35173  0
> brd                    12772  0
> vfat                   17316  0
> msdos                  17077  0
> fat                    45642  2 msdos,vfat
> pci_stub               12429  1
> vboxpci                19096  0
> vboxnetadp             25443  0
> vboxnetflt             23657  0
> vboxdrv               304550  3 vboxnetflt,vboxnetadp,vboxpci
> nfnetlink_log          17212  0
> nfnetlink              12906  1 nfnetlink_log
> parport_pc             22364  0
> ppdev                  12763  0
> lp                     17149  0
> parport                31858  3 lp,ppdev,parport_pc
> ip6t_REJECT            12512  2
> xt_multiport           12548  2
> xt_conntrack           12681  18
> iptable_nat            12928  0
> binfmt_misc            12957  1
> iptable_mangle         12536  0
> nfsd                  216181  2
> nfs                   308353  0
> nfs_acl                12511  2 nfs,nfsd
> auth_rpcgss            37143  2 nfs,nfsd
> fscache                36739  1 nfs
> lockd                  67306  2 nfs,nfsd
> sunrpc                173730  6 lockd,auth_rpcgss,nfs_acl,nfs,nfsd
> ip6t_LOG               12609  4
> xt_hl                  12449  6
> ip6t_rt                12499  3
> nf_conntrack_ipv6      13316  7
> nf_defrag_ipv6         12832  1 nf_conntrack_ipv6
> ipt_REJECT             12502  1
> ipt_LOG                12605  12
> xt_limit               12638  19
> xt_tcpudp              12570  62
> xt_addrtype            12557  4
> xt_state               12503  21
> ip6table_filter        12540  1
> ip6_tables             22175  3 ip6table_filter,ip6t_rt,ip6t_LOG
> nf_conntrack_netbios_ns    12445  0
> nf_conntrack_broadcast    12365  1 nf_conntrack_netbios_ns
> nf_nat_ftp             12460  0
> nf_nat                 18242  2 nf_nat_ftp,iptable_nat
> nf_conntrack_ipv4      14078  35 nf_nat,iptable_nat
> nf_defrag_ipv4         12483  1 nf_conntrack_ipv4
> nf_conntrack_ftp       12605  1 nf_nat_ftp
> nf_conntrack           52720  10 nf_conntrack_ftp,nf_conntrack_ipv4,nf_nat,nf_nat_ftp,nf_conntrack_broadcast,nf_conntrack_netbios_ns,xt_state,nf_conntrack_ipv6,iptable_nat,xt_conntrack
> iptable_filter         12536  1
> ip_tables              22042  3 iptable_filter,iptable_mangle,iptable_nat
> x_tables               19118  18 ip_tables,iptable_filter,ip6_tables,ip6table_filter,xt_state,xt_addrtype,xt_tcpudp,xt_limit,ipt_LOG,ipt_REJECT,ip6t_rt,xt_hl,ip6t_LOG,iptable_mangle,iptable_nat,xt_conntrack,xt_multiport,ip6t_REJECT
> loop                   22641  0
> ecryptfs               81507  0
> dm_crypt               22586  0
> snd_hda_codec_hdmi     30824  1
> snd_usb_audio          89083  2
> snd_usbmidi_lib        23369  1 snd_usb_audio
> snd_seq_midi           12848  0
> snd_seq_midi_event     13316  1 snd_seq_midi
> snd_rawmidi            23060  2 snd_seq_midi,snd_usbmidi_lib
> snd_hda_codec_idt      53792  1
> tuner_simple           17175  1
> tuner_types            16409  1 tuner_simple
> wm8775                 12749  1
> tda9887                12645  1
> tda8290                17278  0
> tuner                  17497  2
> cx25840                39782  1
> ivtv                  129010  0
> cx2341x                21461  1 ivtv
> snd_hda_intel          26259  2
> snd_hda_codec          78031  3 snd_hda_intel,snd_hda_codec_idt,snd_hda_codec_hdmi
> snd_hwdep              13186  2 snd_hda_codec,snd_usb_audio
> snd_pcm                68083  4 snd_hda_codec,snd_hda_intel,snd_usb_audio,snd_hda_codec_hdmi
> tveeprom               20593  1 ivtv
> v4l2_common            13222  5 cx2341x,ivtv,cx25840,tuner,wm8775
> videodev               70889  6 v4l2_common,cx2341x,ivtv,cx25840,tuner,wm8775
> v4l2_compat_ioctl32    16655  1 videodev
> media                  18148  1 videodev
> nv_tco                 12914  0
> i2c_algo_bit           12841  1 ivtv
> snd_page_alloc         13003  2 snd_pcm,snd_hda_intel
> snd_seq                45126  2 snd_seq_midi_event,snd_seq_midi
> snd_seq_device         13176  3 snd_seq,snd_rawmidi,snd_seq_midi
> i2c_nforce2            12584  0
> dcdbas                 13307  0
> edac_mce_amd           17103  0
> edac_core              35258  0
> evdev                  17562  18
> powernow_k8            17618  1
> mperf                  12453  1 powernow_k8
> k8temp                 12647  0
> psmouse                69265  0
> snd_timer              22917  2 snd_seq,snd_pcm
> i2c_core               23876  12 i2c_nforce2,i2c_algo_bit,videodev,v4l2_common,tveeprom,ivtv,cx25840,tuner,tda8290,tda9887,wm8775,tuner_simple
> serio_raw              12931  0
> fglrx                2634136  183
> pcspkr                 12579  0
> snd                    52893  20 snd_timer,snd_seq_device,snd_seq,snd_pcm,snd_hwdep,snd_hda_codec,snd_hda_intel,snd_hda_codec_idt,snd_rawmidi,snd_usbmidi_lib,snd_usb_audio,snd_hda_codec_hdmi
> processor              28149  1 powernow_k8
> button                 12937  1 fglrx
> soundcore              13065  1 snd
> thermal_sys            18040  1 processor
> ext4                  350804  9
> crc16                  12343  1 ext4
> jbd2                   62115  1 ext4
> mbcache                13114  2 ext4,ext2
> dm_mod                 63645  29 dm_crypt
> md_mod                 87742  4 linear,raid0,raid1,raid456
> sg                     25874  0
> sd_mod                 36136  6
> sr_mod                 21899  0
> cdrom                  35401  1 sr_mod
> crc_t10dif             12348  1 sd_mod
> usbhid                 36418  0
> hid                    81372  1 usbhid
> usb_storage            43870  0
> ata_generic            12479  0
> ohci_hcd               26563  0
> sata_nv                26690  4
> libata                140630  2 sata_nv,ata_generic
> ehci_hcd               40249  0
> b44                    27751  0
> ssb                    44714  1 b44
> mmc_core               68400  1 ssb
> mii                    12675  1 b44
> pcmcia                 32734  1 ssb
> pcmcia_core            18294  1 pcmcia
> scsi_mod              162321  5 libata,usb_storage,sr_mod,sd_mod,sg
> usbcore               128741  7 ehci_hcd,ohci_hcd,usb_storage,usbhid,snd_usbmidi_lib,snd_usb_audio
> usb_common             12354  1 usbcore
> -------------
> FORCE_MODS:
> -------------
>
> -------------
> DENY_MODS:
> -------------
> kqemu vxfen
> -------------
> df result:
> ----------
> Sys. fich.                                             Type        1K-blocks     Util. Disponible Uti% Mont?? sur
> rootfs                                                 rootfs       96124904  10822540   80419412  12% /
> sysfs                                                  sysfs               0         0          0    - /sys
> proc                                                   proc                0         0          0    - /proc
> udev                                                   devtmpfs        10240         0      10240   0% /dev
> devpts                                                 devpts              0         0          0    - /dev/pts
> tmpfs                                                  tmpfs          406288       944     405344   1% /run
> /dev/disk/by-uuid/4a5a9317-0b70-4796-a094-d61c01891c81 ext4         96124904  10822540   80419412  12% /
> tmpfs                                                  tmpfs            5120         0       5120   0% /run/lock
> tmpfs                                                  tmpfs         1008560       276    1008284   1% /run/shm
> /dev/mapper/sysvg-optlv                                ext4         16803708  15010400     939704  95% /opt
> /dev/mapper/data1vg-homelv                             ext4         51606140  41866076    7119008  86% /home
> /dev/mapper/data1vg-wwwlv                              ext4          4809704   2794384    1770996  62% /www
> /dev/mapper/data1vg-baseslv                            ext4          1923084    737276    1088120  41% /bases
> /dev/mapper/data1vg-photoslv                           ext4         72248648  45036992   23541896  66% /photos
> /dev/mapper/data1vg-videoslv                           ext4        154818540 108302512   38651708  74% /videos
> /dev/mapper/data1vg-vboxlv                             ext4        134573320 104068176   23669128  82% /vbox
> /dev/mapper/data1vg-graveurlv                          ext4         20642428   8094972   11498880  42% /graveur
> rpc_pipefs                                             rpc_pipefs          0         0          0    - /var/lib/nfs/rpc_pipefs
> binfmt_misc                                            binfmt_misc         0         0          0    - /proc/sys/fs/binfmt_misc
> -------------
> df -i result:
> ----------
> Sys. fich.                                              Inodes IUtil.  ILibre IUti% Mont?? sur
> rootfs                                                 6111232 313566 5797666    6% /
> udev                                                    497709    610  497099    1% /dev
> tmpfs                                                   507860    667  507193    1% /run
> /dev/disk/by-uuid/4a5a9317-0b70-4796-a094-d61c01891c81 6111232 313566 5797666    6% /
> tmpfs                                                   507860      3  507857    1% /run/lock
> tmpfs                                                   507860     15  507845    1% /run/shm
> /dev/mapper/sysvg-optlv                                1068960  54781 1014179    6% /opt
> /dev/mapper/data1vg-homelv                             3276800  83092 3193708    3% /home
> /dev/mapper/data1vg-wwwlv                               305824  43214  262610   15% /www
> /dev/mapper/data1vg-baseslv                             122160   1213  120947    1% /bases
> /dev/mapper/data1vg-photoslv                           4587520  23609 4563911    1% /photos
> /dev/mapper/data1vg-videoslv                           9830400    180 9830220    1% /videos
> /dev/mapper/data1vg-vboxlv                             8552448     91 8552357    1% /vbox
> /dev/mapper/data1vg-graveurlv                          1310720     80 1310640    1% /graveur
> -------------
> -------------
> INFO: /boot/grub/grub.cfg content
> -------------
> #
> # DO NOT EDIT THIS FILE
> #
> # It is automatically generated by grub-mkconfig using templates
> # from /etc/grub.d and settings from /etc/default/grub
> #
>
> ### BEGIN /etc/grub.d/00_header ###
> if [ -s $prefix/grubenv ]; then
>   load_env
> fi
> set default="0"
> if [ "${prev_saved_entry}" ]; then
>   set saved_entry="${prev_saved_entry}"
>   save_env saved_entry
>   set prev_saved_entry=
>   save_env prev_saved_entry
>   set boot_once=true
> fi
>
> function savedefault {
>   if [ -z "${boot_once}" ]; then
>     saved_entry="${chosen}"
>     save_env saved_entry
>   fi
> }
>
> function load_video {
>   insmod vbe
>   insmod vga
>   insmod video_bochs
>   insmod video_cirrus
> }
>
> insmod part_msdos
> insmod ext2
> set root='(hd0,msdos5)'
> search --no-floppy --fs-uuid --set=root 4a5a9317-0b70-4796-a094-d61c01891c81
> if loadfont /usr/share/grub/unicode.pf2 ; then
>   set gfxmode=640x480
>   load_video
>   insmod gfxterm
>   insmod part_msdos
>   insmod ext2
>   set root='(hd0,msdos5)'
>   search --no-floppy --fs-uuid --set=root 4a5a9317-0b70-4796-a094-d61c01891c81
>   set locale_dir=($root)/boot/grub/locale
>   set lang=fr_FR
>   insmod gettext
> fi
> terminal_output gfxterm
> set timeout=5
> ### END /etc/grub.d/00_header ###
>
> ### BEGIN /etc/grub.d/05_debian_theme ###
> insmod part_msdos
> insmod ext2
> set root='(hd0,msdos5)'
> search --no-floppy --fs-uuid --set=root 4a5a9317-0b70-4796-a094-d61c01891c81
> insmod png
> if background_image /usr/share/images/desktop-base/joy-grub.png; then
>   set color_normal=white/black
>   set color_highlight=black/white
> else
>   set menu_color_normal=cyan/blue
>   set menu_color_highlight=white/blue
> fi
> ### END /etc/grub.d/05_debian_theme ###
>
> ### BEGIN /etc/grub.d/10_linux ###
> menuentry 'Debian GNU/Linux, avec Linux 3.2.0-4-amd64' --class debian --class gnu-linux --class gnu --class os {
> load_video
> insmod gzio
> insmod part_msdos
> insmod ext2
> set root='(hd0,msdos5)'
> search --no-floppy --fs-uuid --set=root 4a5a9317-0b70-4796-a094-d61c01891c81
> echo 'Chargement de Linux 3.2.0-4-amd64 ...'
> linux /boot/vmlinuz-3.2.0-4-amd64 root=UUID=4a5a9317-0b70-4796-a094-d61c01891c81 ro  quiet
> echo 'Chargement du disque m??moire initial ...'
> initrd /boot/initrd.img-3.2.0-4-amd64
> }
> menuentry 'Debian GNU/Linux, avec Linux 3.2.0-4-amd64 (mode de d??pannage)' --class debian --class gnu-linux --class gnu --class os {
> load_video
> insmod gzio
> insmod part_msdos
> insmod ext2
> set root='(hd0,msdos5)'
> search --no-floppy --fs-uuid --set=root 4a5a9317-0b70-4796-a094-d61c01891c81
> echo 'Chargement de Linux 3.2.0-4-amd64 ...'
> linux /boot/vmlinuz-3.2.0-4-amd64 root=UUID=4a5a9317-0b70-4796-a094-d61c01891c81 ro single
> echo 'Chargement du disque m??moire initial ...'
> initrd /boot/initrd.img-3.2.0-4-amd64
> }
> ### END /etc/grub.d/10_linux ###
>
> ### BEGIN /etc/grub.d/20_linux_xen ###
> ### END /etc/grub.d/20_linux_xen ###
>
> ### BEGIN /etc/grub.d/20_memtest86+ ###
> menuentry "Memory test (memtest86+)" {
> insmod part_msdos
> insmod ext2
> set root='(hd0,msdos5)'
> search --no-floppy --fs-uuid --set=root 4a5a9317-0b70-4796-a094-d61c01891c81
> linux16 /boot/memtest86+.bin
> }
> menuentry "Memory test (memtest86+, serial console 115200)" {
> insmod part_msdos
> insmod ext2
> set root='(hd0,msdos5)'
> search --no-floppy --fs-uuid --set=root 4a5a9317-0b70-4796-a094-d61c01891c81
> linux16 /boot/memtest86+.bin console=ttyS0,115200n8
> }
> menuentry "Memory test (memtest86+, experimental multiboot)" {
> insmod part_msdos
> insmod ext2
> set root='(hd0,msdos5)'
> search --no-floppy --fs-uuid --set=root 4a5a9317-0b70-4796-a094-d61c01891c81
> multiboot /boot/memtest86+_multiboot.bin
> }
> menuentry "Memory test (memtest86+, serial console 115200, experimental multiboot)" {
> insmod part_msdos
> insmod ext2
> set root='(hd0,msdos5)'
> search --no-floppy --fs-uuid --set=root 4a5a9317-0b70-4796-a094-d61c01891c81
> multiboot /boot/memtest86+_multiboot.bin console=ttyS0,115200n8
> }
> ### END /etc/grub.d/20_memtest86+ ###
>
> ### BEGIN /etc/grub.d/30_os-prober ###
> menuentry "Windows Vista (loader) (on /dev/sda3)" --class windows --class os {
> insmod part_msdos
> insmod ntfs
> set root='(hd0,msdos3)'
> search --no-floppy --fs-uuid --set=root 0C6CE0BA6CE0A026
> chainloader +1
> }
> ### END /etc/grub.d/30_os-prober ###
>
> ### BEGIN /etc/grub.d/40_custom ###
> # This file provides an easy way to add custom menu entries.  Simply type the
> # menu entries you want to add after this comment.  Be careful not to change
> # the 'exec tail' line above.
> ### END /etc/grub.d/40_custom ###
>
> ### BEGIN /etc/grub.d/41_custom ###
> if [ -f  $prefix/custom.cfg ]; then
>   source $prefix/custom.cfg;
> fi
> ### END /etc/grub.d/41_custom ###
> -------------
> -------------
> INFO: /boot/grub/device.map content
> -------------
> (hd0) /dev/disk/by-id/ata-ST3320620AS_5QF2VWM8
> -------------
> Full fdisk info
> ---------------
>
> Disque /dev/sda??: 320.1??Go, 320072933376??octets
> 255??t??tes, 63??secteurs/piste, 38913??cylindres, total 625142448??secteurs
> Unit??s = secteurs de 1 * 512 = 512??octets
> Taille de secteur (logique / physique)??: 512??octets / 512??octets
> taille d'E/S (minimale / optimale)??: 512??octets / 512??octets
> Identifiant de disque??: 0x58000000
>
> P??riph??rique Amorce  D??but        Fin      Blocs     Id  Syst??me
> /dev/sda1              63      112454       56196   de  Dell Utility
> /dev/sda2          112640    21084159    10485760    7  HPFS/NTFS/exFAT
> /dev/sda3   *    21093345   228379505   103643080+   7  HPFS/NTFS/exFAT
> /dev/sda4       228380101   625141759   198380829+   5  ??tendue
> /dev/sda5       228380103   423698309    97659103+  83  Linux
> /dev/sda6       423698373   425658239      979933+  82  partition d'??change Linux / Solaris
> /dev/sda7       425658368   625141759    99741696   8e  LVM Linux
>
> Disque /dev/sdb??: 1000.2??Go, 1000204886016??octets
> 81??t??tes, 63??secteurs/piste, 382818??cylindres, total 1953525168??secteurs
> Unit??s = secteurs de 1 * 512 = 512??octets
> Taille de secteur (logique / physique)??: 512??octets / 512??octets
> taille d'E/S (minimale / optimale)??: 512??octets / 512??octets
> Identifiant de disque??: 0x0003513f
>
> P??riph??rique Amorce  D??but        Fin      Blocs     Id  Syst??me
> /dev/sdb1            2048  1953525167   976761560   8e  LVM Linux
>
> Disque /dev/mapper/data1vg-photoslv??: 75.2??Go, 75161927680??octets
> 255??t??tes, 63??secteurs/piste, 9137??cylindres, total 146800640??secteurs
> Unit??s = secteurs de 1 * 512 = 512??octets
> Taille de secteur (logique / physique)??: 512??octets / 512??octets
> taille d'E/S (minimale / optimale)??: 512??octets / 512??octets
> Identifiant de disque??: 0x00000000
>
>
> Disque /dev/mapper/data1vg-videoslv??: 161.1??Go, 161061273600??octets
> 255??t??tes, 63??secteurs/piste, 19581??cylindres, total 314572800??secteurs
> Unit??s = secteurs de 1 * 512 = 512??octets
> Taille de secteur (logique / physique)??: 512??octets / 512??octets
> taille d'E/S (minimale / optimale)??: 512??octets / 512??octets
> Identifiant de disque??: 0x00000000
>
>
> Disque /dev/mapper/data1vg-homelv??: 53.7??Go, 53687091200??octets
> 255??t??tes, 63??secteurs/piste, 6527??cylindres, total 104857600??secteurs
> Unit??s = secteurs de 1 * 512 = 512??octets
> Taille de secteur (logique / physique)??: 512??octets / 512??octets
> taille d'E/S (minimale / optimale)??: 512??octets / 512??octets
> Identifiant de disque??: 0x00000000
>
>
> Disque /dev/mapper/data1vg-graveurlv??: 21.5??Go, 21474836480??octets
> 255??t??tes, 63??secteurs/piste, 2610??cylindres, total 41943040??secteurs
> Unit??s = secteurs de 1 * 512 = 512??octets
> Taille de secteur (logique / physique)??: 512??octets / 512??octets
> taille d'E/S (minimale / optimale)??: 512??octets / 512??octets
> Identifiant de disque??: 0x00000000
>
>
> Disque /dev/mapper/data1vg-wwwlv??: 5003??Mo, 5003804672??octets
> 255??t??tes, 63??secteurs/piste, 608??cylindres, total 9773056??secteurs
> Unit??s = secteurs de 1 * 512 = 512??octets
> Taille de secteur (logique / physique)??: 512??octets / 512??octets
> taille d'E/S (minimale / optimale)??: 512??octets / 512??octets
> Identifiant de disque??: 0x00000000
>
>
> Disque /dev/mapper/data1vg-baseslv??: 2000??Mo, 2000683008??octets
> 255??t??tes, 63??secteurs/piste, 243??cylindres, total 3907584??secteurs
> Unit??s = secteurs de 1 * 512 = 512??octets
> Taille de secteur (logique / physique)??: 512??octets / 512??octets
> taille d'E/S (minimale / optimale)??: 512??octets / 512??octets
> Identifiant de disque??: 0x00000000
>
>
> Disque /dev/mapper/data1vg-vboxlv??: 140.0??Go, 140001673216??octets
> 255??t??tes, 63??secteurs/piste, 17020??cylindres, total 273440768??secteurs
> Unit??s = secteurs de 1 * 512 = 512??octets
> Taille de secteur (logique / physique)??: 512??octets / 512??octets
> taille d'E/S (minimale / optimale)??: 512??octets / 512??octets
> Identifiant de disque??: 0x00000000
>
>
> Disque /dev/mapper/sysvg-optlv??: 17.5??Go, 17481859072??octets
> 255??t??tes, 63??secteurs/piste, 2125??cylindres, total 34144256??secteurs
> Unit??s = secteurs de 1 * 512 = 512??octets
> Taille de secteur (logique / physique)??: 512??octets / 512??octets
> taille d'E/S (minimale / optimale)??: 512??octets / 512??octets
> Identifiant de disque??: 0x00000000
>
> ----------------
> ------------------------------------
> Your raw fstab file looks like this:
> ------------------------------------
> # /etc/fstab: static file system information.
> #
> # Use 'blkid' to print the universally unique identifier for a
> # device; this may be used with UUID= as a more robust way to name devices
> # that works even if disks are added and removed. See fstab(5).
> #
> # <file system>        <mount point>     <type>      <options>                   <dump> <pass>
> # / was on /dev/sda5 during installation
> UUID=4a5a9317-0b70-4796-a094-d61c01891c81 /    ext4  errors=remount-ro           0      1
> # swap was on /dev/sda6 during installation
> UUID=b4d7e5c0-207b-4a67-8b58-20523c509b87 none swap  sw                          0      0
>
> /dev/sr0               /media/cdrom0     udf,iso9660 user,noauto                 0      0
>
> #/dev/sysvg/homelv      /home             ext4        relatime,errors=remount-ro  0      1
> /dev/sysvg/optlv       /opt              ext4        relatime,errors=remount-ro  0      1
>
> /dev/data1vg/homelv    /home             ext4        relatime,errors=remount-ro  0      2
> /dev/data1vg/wwwlv     /www              ext4        relatime,errors=remount-ro  0      2
> /dev/data1vg/baseslv   /bases            ext4        relatime,errors=remount-ro  0      2
> /dev/data1vg/photoslv  /photos           ext4        relatime,errors=remount-ro  0      2
> /dev/data1vg/videoslv  /videos           ext4        relatime,errors=remount-ro  0      2
> /dev/data1vg/vboxlv    /vbox             ext4        relatime,errors=remount-ro  0      2
> /dev/data1vg/graveurlv /graveur          ext4        relatime,errors=remount-ro  0      2
>
> # /dev/data0vg/homelv    /data0vg/home     ext4        relatime,errors=remount-ro  0      2
> # /dev/data0vg/wwwlv     /data0vg/www      ext4        relatime,errors=remount-ro  0      2
> # /dev/data0vg/baseslv   /data0vg/bases    ext4        relatime,errors=remount-ro  0      2
> # /dev/data0vg/photoslv  /data0vg/photos   ext4        relatime,errors=remount-ro  0      2
> # /dev/data0vg/videoslv  /data0vg/videos   ext4        relatime,errors=remount-ro  0      2
> # /dev/data0vg/vboxlv    /data0vg/vbox     ext4        relatime,errors=remount-ro  0      2
>
> # /dev/data2vg/homelv    /data2vg/home     ext4        relatime,errors=remount-ro  0      2
> # /dev/data2vg/wwwlv     /data2vg/www      ext4        relatime,errors=remount-ro  0      2
> # /dev/data2vg/baseslv   /data2vg/bases    ext4        relatime,errors=remount-ro  0      2
> # /dev/data2vg/photoslv  /data2vg/photos   ext4        relatime,errors=remount-ro  0      2
> # /dev/data2vg/videoslv  /data2vg/videos   ext4        relatime,errors=remount-ro  0      2
> # /dev/data2vg/vboxlv    /data2vg/vbox     ext4        relatime,errors=remount-ro  0      2
> -----------------------------------
> Your mountlist will look like this:
> -----------------------------------
> INFO: Analyzing LVM...
> DEVICE          MOUNTPOINT      FORMAT          SIZE MB       LABEL/UUID    
> ------          ----------      ------          -------       ----------    
> INFO: Examining /dev/sdb1 (mount=lvm fmt=lvm psz=976761560)
> /dev/sdb1       lvm             lvm              953868 c9qZKK-bpqn-sY7P-fWH2-SBlo-YsXS-udCgP7
> INFO: Examining /dev/sda7 (mount=lvm fmt=lvm psz=99741696)
> /dev/sda7       lvm             lvm               97404 yuL0j7-wJtb-ANiO-Omxi-AuEE-wCkJ-pfhEWi
> INFO: Examining /dev/sda5 (mount=/ fmt=ext4 psz=97659103)
> /dev/sda5       /               ext4              95370 4a5a9317-0b70-4796-a094-d61c01891c81
> INFO: Examining /dev/sda6 (mount=swap fmt=swap psz=979928)
> /dev/sda6       swap            swap                956 b4d7e5c0-207b-4a67-8b58-20523c509b87
> INFO: Examining /dev/sysvg/optlv (mount=/opt fmt=ext4 psz=lvm)
> /dev/sysvg/optlv /opt            ext4                lvm f1c4b976-0101-47ac-9ff8-c5a9e567553b
> INFO: Examining /dev/data1vg/homelv (mount=/home fmt=ext4 psz=lvm)
> /dev/data1vg/homelv /home           ext4                lvm e063df74-3fff-45ac-927d-bc6a60bd2970
> INFO: Examining /dev/data1vg/wwwlv (mount=/www fmt=ext4 psz=lvm)
> /dev/data1vg/wwwlv /www            ext4                lvm 7942603b-20c8-483a-ab36-98ee20ab7700
> INFO: Examining /dev/data1vg/baseslv (mount=/bases fmt=ext4 psz=lvm)
> /dev/data1vg/baseslv /bases          ext4                lvm 09f40cc9-fc3b-4205-a466-df38e5774a59
> INFO: Examining /dev/data1vg/photoslv (mount=/photos fmt=ext4 psz=lvm)
> /dev/data1vg/photoslv /photos         ext4                lvm 11ff707f-da12-46a3-9218-87fcf38ddc2f
> INFO: Examining /dev/data1vg/videoslv (mount=/videos fmt=ext4 psz=lvm)
> /dev/data1vg/videoslv /videos         ext4                lvm 11e0f5ef-75e4-4b7b-b34e-c9112b731f57
> INFO: Examining /dev/data1vg/vboxlv (mount=/vbox fmt=ext4 psz=lvm)
> /dev/data1vg/vboxlv /vbox           ext4                lvm 69e8fcf6-9518-4c3c-9052-53096c873cc4
> INFO: Examining /dev/data1vg/graveurlv (mount=/graveur fmt=ext4 psz=lvm)
> /dev/data1vg/graveurlv /graveur        ext4                lvm a5d30c9b-d333-46a3-8c28-ef2c4c1d9185
> -----------------------------------
> Mindi 3.0.0-r3332 is exiting
> End date : lundi 19 janvier 2015, 22:16:59 (UTC+0100)

> INFO: Time started: Mon Jan 19 22:16:43 2015
>
> DBG2: [TH=22705] libmondo-tools.c->setup_tmpdir#715: bkpinfo->tmpdir is being set to /tmp/mondo.tmp.4v41Vd
> DBG2: [TH=22705] libmondo-tools.c->setup_scratchdir#736: Purging old scratchdir /mondo.scratch.*
> DBG2: [TH=22705] libmondo-tools.c->setup_scratchdir#757: bkpinfo->scratchdir is being set to /tmp/mondo.scratch.3mNp4N
> INFO: root is mounted at /dev/disk/by-uuid/aa9317-0b70-4796-a094-d61c01891c81
>
> INFO: That doesn't mean /dev/disk/by-uuid/aa9317-0b70-4796-a094-d61c01891c81 is the root partition. It's just a debugging message. Relax. It's part of am_I_in_disaster_recovery_mode().
> DBG1: [TH=22705] libmondo-devices.c->am_I_in_disaster_recovery_mode#163: Is this a ramdisk? result = FALSE
> INFO: running: dmesg -n1 > /tmp/mondo.tmp.4v41Vd/mondo-run-prog-thing.tmp 2> /tmp/mondo.tmp.4v41Vd/mondo-run-prog-thing.err
> INFO: --------------------------------start of output-----------------------------
> INFO: --------------------------------end of output------------------------------
> INFO: ...ran just fine. :-)
> INFO: Mondo Archive v3.2.0-r3332 --- http://www.mondorescue.org
> INFO: running x86_64 binaries
> INFO: running on x86_64 architecture
> INFO: -----------------------------------------------------------
> INFO: NB: Mondo logs almost everything, so don't panic if you see
> INFO: some error messages.  Please read them carefully before you
> INFO: decide to break out in a cold sweat.    Despite (or perhaps
> INFO: because of) the wealth of messages. some users are inclined
> INFO: to stop reading this log. If Mondo stopped for some reason,
> INFO: chances are it's detailed here.  More than likely there's a
> INFO: message at the very end of this log that will tell you what
> INFO: is wrong. Please read it!                          -Devteam
> INFO: -----------------------------------------------------------
> INFO: Zero...
> DBG1: [Main] mondoarchive.c->welcome_to_mondoarchive#96: One...
> DBG2: [Main] mondoarchive.c->welcome_to_mondoarchive#97: Two...
> DBG3: [Main] mondoarchive.c->welcome_to_mondoarchive#98: Three...
> DBG4: [Main] mondoarchive.c->welcome_to_mondoarchive#99: Four...
> DBG2: [Main] mondoarchive.c->distro_specific_kludges_at_start_of_mondoarchive#114: Unmounting old ramdisks if necessary
> INFO: running: mount | grep cdrom | grep super > /tmp/mondo.tmp.4v41Vd/mondo-run-prog-thing.tmp 2> /tmp/mondo.tmp.4v41Vd/mondo-run-prog-thing.err
> INFO: --------------------------------start of output-----------------------------
> INFO: --------------------------------end of output------------------------------
> INFO: ...ran with res=256
> INFO: running: mount | grep floppy | grep super > /tmp/mondo.tmp.4v41Vd/mondo-run-prog-thing.tmp 2> /tmp/mondo.tmp.4v41Vd/mondo-run-prog-thing.err
> INFO: --------------------------------start of output-----------------------------
> INFO: --------------------------------end of output------------------------------
> INFO: ...ran with res=256
> DBG1: [Main] libmondo-tools.c->mount_boot_if_necessary#1155: Started sub
> DBG4: [Main] libmondo-tools.c->mount_boot_if_necessary#1156: About to set g_boot_mountpt[0] to '\0'
> DBG4: [Main] libmondo-tools.c->mount_boot_if_necessary#1158: Done. Great. Seeting command to something
> DBG4: [Main] libmondo-tools.c->mount_boot_if_necessary#1160: Cool. Command = 'grep -v ":" /etc/fstab | grep -vE '^#.*$' | grep -E "[ ]/boot[ ]" | tr -s ' ' ' ' | cut -f1 | head -n1'
> DBG4: [Main] libmondo-tools.c->mount_boot_if_necessary#1164: tmp = ''
> DBG2: [Main] libmondo-tools.c->mount_boot_if_necessary#1165: /boot is at  according to /etc/fstab
> DBG3: [Main] libmondo-tools.c->mount_boot_if_necessary#1182: command = mount | grep -E '^'
> DBG1: [Main] libmondo-tools.c->mount_boot_if_necessary#1205: Ended sub
> DBG1: [Main] libmondo-tools.c->get_kernel_version#245: g_kernel_version = 3.200000
> INFO: running: rm -Rf /var/cache/mondo/changed.files* > /tmp/mondo.tmp.4v41Vd/mondo-run-prog-thing.tmp 2> /tmp/mondo.tmp.4v41Vd/mondo-run-prog-thing.err
> INFO: --------------------------------start of output-----------------------------
> INFO: --------------------------------end of output------------------------------
> INFO: ...ran just fine. :-)
> INFO: Checking sanity of your Linux distribution
> INFO: running: grep ramdisk /proc/devices > /tmp/mondo.tmp.4v41Vd/mondo-run-prog-thing.tmp 2> /tmp/mondo.tmp.4v41Vd/mondo-run-prog-thing.err
> INFO: --------------------------------start of output-----------------------------
> INFO: 1 ramdisk
> INFO: --------------------------------end of output------------------------------
> INFO: ...ran just fine. :-)
> INFO: running: mount | grep -Ew 'vfat|fat|dos' | grep -vE "/dev/fd|nexdisk" > /tmp/mondo.tmp.4v41Vd/mondo-run-prog-thing.tmp 2> /tmp/mondo.tmp.4v41Vd/mondo-run-prog-thing.err
> INFO: --------------------------------start of output-----------------------------
> INFO: --------------------------------end of output------------------------------
> INFO: ...ran with res=256
> DBG4: [Main] libmondo-files.c->find_home_of_exe#349: find_home_of_exe --- Found cmp at /usr/bin/cmp
> INFO: running: mindi -V > /tmp/mondo.tmp.4v41Vd/mondo-run-prog-thing.tmp 2> /tmp/mondo.tmp.4v41Vd/mondo-run-prog-thing.err
> INFO: --------------------------------start of output-----------------------------
> INFO: Mindi v3.0.0-r3332
> INFO: Le disque /dev/mapper/data1vg-photoslv ne contient pas une table de partitions valable
> INFO: Le disque /dev/mapper/data1vg-videoslv ne contient pas une table de partitions valable
> INFO: Le disque /dev/mapper/data1vg-homelv ne contient pas une table de partitions valable
> INFO: Le disque /dev/mapper/data1vg-graveurlv ne contient pas une table de partitions valable
> INFO: Le disque /dev/mapper/data1vg-wwwlv ne contient pas une table de partitions valable
> INFO: Le disque /dev/mapper/data1vg-baseslv ne contient pas une table de partitions valable
> INFO: Le disque /dev/mapper/data1vg-vboxlv ne contient pas une table de partitions valable
> INFO: Le disque /dev/mapper/sysvg-optlv ne contient pas une table de partitions valable
> INFO: --------------------------------end of output------------------------------
> INFO: ...ran just fine. :-)
> INFO: running: parted2fdisk -l 2>/dev/null | grep -i raid > /tmp/mondo.tmp.4v41Vd/mondo-run-prog-thing.tmp 2> /tmp/mondo.tmp.4v41Vd/mondo-run-prog-thing.err
> INFO: --------------------------------start of output-----------------------------
> INFO: --------------------------------end of output------------------------------
> INFO: ...ran with res=256
> INFO: Done.
> DBG1: [Main] libmondo-cli.c->process_switches#181: Loglevel forced to 99
> DBG20: [Main] libmondo-files.c->does_file_exist#188: /usr/bin/afio exists
> DBG4: [Main] libmondo-files.c->find_home_of_exe#349: find_home_of_exe --- Found afio at /usr/bin/afio

> ------------------------------------------------------------------------------
> New Year. New Location. New Benefits. New Data Center in Ashburn, VA.
> GigeNET is offering a free month of service with a new server in Ashburn.
> Choose from 2 high performing configs, both with 100TB of bandwidth.
> Higher redundancy.Lower latency.Increased capacity.Completely compliant.
> http://p.sf.net/sfu/gigenet

> _______________________________________________
> Mondo-devel mailing list
> [hidden email]
> https://lists.sourceforge.net/lists/listinfo/mondo-devel


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

------------------------------------------------------------------------------
Dive into the World of Parallel Programming. The Go Parallel Website,
sponsored by Intel and developed in partnership with Slashdot Media, is your
hub for all things parallel software development, from weekly thought
leadership blogs to news, videos, case studies, tutorials and more. Take a
look and join the conversation now. http://goparallel.sourceforge.net/
_______________________________________________
Mondo-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/mondo-devel
Reply | Threaded
Open this post in threaded view
|

Re: [Mondo-devel] Segmentation error running mondoarchive v3.2.0-r3332

Philippe Lefevre

Great !

Many thanks for your help and reply Bruno.

Next week-end I'm going to reinstall 3.2.0 and supress -I option and see
what happen.

One thing is strange anyway: in my tests after a mondoarchive
compilation, (pls, see my email dated on 17th january) I ran 3.2.0 with
-I option without any issue. The sigsegv was repructible when
mondoarchive was installed by the deb package ...

I used :
[phlsys]root:/home/phl/mondo-3.2.0# gdb -args mondoarchive -D -OV -i -N
-G -s 780M -p sys-D7.7-diff_150105212200 -T /graveur -S /graveur -d
/graveur -I "/|/|/opt/Zuma" -E
"/bases/sybase|/graveur|/home|/opt|/photos|/quemu|/Sauvegardes|/var/crash|/var/backups|/var/log|/var/mail|/var/spool|/vbox|/videos|/www"

and:
 ....
 Data archived OK.
 Mondoarchive ran OK.
 See /var/log/mondoarchive.log for details of backup run.
 Execution run ended; result=0
 Type 'less /var/log/mondoarchive.log' to see the output log [Inferior 1
(process 19382) exited normally]
 (gdb) quit


I'll let you know.
Kind regards,
Philippe



Le 26/01/2015 01:09, Bruno Cornec a écrit :

> Hello Philippe,
>
> This is now fixed as described in BR:
> http://trac.mondorescue.org/ticket/764#comment:2
>
> Bruno.
>
> Philippe Lefevre said on Mon, Jan 19, 2015 at 10:34:24PM +0100:
>
>> Hello Gaetagno,
>>
>> Regarding the two slashes, as I said, I used the same syntax to get into
>> the same bug situation.
>>
>>
>> I did a try with only one / in the -I option and got the same
>> segmentation violation exception.
>>
>>
>> Mindi launched alone as your example and it ran fine and the iso file
>> successfully built.
>> Please find attached the mindi.log file.
>>
>> [phlsys]root:/home/phl/Devel/mondo# ls -al /var/cache/mindi/mindi.iso
>> -rw-r----- 1 root root 98721792 janv. 19 22:09 /var/cache/mindi/mindi.iso
>>
>>
>>
>> Ran mondoarchive with -K99 option crashed again with the sigsegv signal.
>> Please find attached the mondoarchive.log file.
>> Unfortunately, I'm afraid it is not so verbose than we would ...
>> This time, the log ends with :
>>
>> DBG1: [Main] libmondo-cli.c->process_switches#181: Loglevel forced to 99
>> DBG20: [Main] libmondo-files.c->does_file_exist#188: /usr/bin/afio exists
>> DBG4: [Main] libmondo-files.c->find_home_of_exe#349: find_home_of_exe
>> --- Found afio at /usr/bin/afio
>>
>>
>>
>> Running mondo without - E option crashed in the same way and with same
>> mondoarchive.log file.
>> [phlsys]root:/home/phl/Devel/mondo# /usr/sbin/mondoarchive -K99 -D -OV
>> -i -N -G -s 780M -p sys-D7.7-diff_150105212200 -T /graveur -S /graveur
>> -d /graveur -I "/opt/zuma"
>> See /var/log/mondoarchive.log for details of backup run.
>> Checking sanity of your Linux distribution
>> Done.
>> Erreur de segmentation
>>
>>
>> Thank you for your time Gaetagno.
>> Kind regards,
>> Philippe
>>
>>
>>
>> Le 19/01/2015 12:17, Gattegno, Victor (GSD CSC / GCC) a écrit :
>>> Hi Philippe,
>>>
>>> You used again two time "/"  in the include :
>>> -I "/|/|/opt/Zuma"
>>>
>>> Your mondorachive.log file ends with :
>>> DBG4: [Main] libmondo-files.c->find_home_of_exe#349: find_home_of_exe --- Found afio at /usr/bin/afio
>>>
>>> You can try a few things :
>>>
>>> Try mindi alone :
>>> # mindi
>>> Do you want to use your own kernel to build the boot disk ([y]/n) ? y
>>>
>>> Try your mondoarchive command without -E, with only -I, and choice only one directory, example :
>>> -I "/opt/Zuma"
>>>
>>> Try your mondoarchive command with more debug, example with -K 5, or with -K 99 (which is full debug mode, be aware that the log file could grow from 200 Kb to 50 Mb).
>>>
>>> Rgds,
>>> Victor
>>>
>>> -----Original Message-----
>>> From: Philippe Lefevre [mailto:[hidden email]]
>>> Sent: samedi 17 janvier 2015 20:14
>>> To: Mondo mailing list
>>> Subject: Re: [Mondo-devel] Segmentation error running mondoarchive v3.2.0-r3332
>>>
>>> Hello list,
>>>
>>> sorry Gaetagno for the delay, I was not able to find some time long enought to go back into my issue.
>>>
>>> I did it today (without removing the two slashes in order to be in the same situation) and .... what I compiled worked fine with what I have compiled. (I noticed the -v bug, thanks  ;)  )
>>>
>>> Run mondoarchive via dbg:
>>> [phlsys]root:/home/phl/mondo-3.2.0# gdb -args mondoarchive -D -OV -i -N -G -s 780M -p sys-D7.7-diff_150105212200 -T /graveur -S /graveur -d /graveur -I "/|/|/opt/Zuma" -E "/bases/sybase|/graveur|/home|/opt|/photos|/quemu|/Sauvegardes|/var/crash|/var/backups|/var/log|/var/mail|/var/spool|/vbox|/videos|/www"
>>>
>>> and:
>>> ....
>>> Data archived OK.
>>> Mondoarchive ran OK.
>>> See /var/log/mondoarchive.log for details of backup run.
>>> Execution run ended; result=0
>>> Type 'less /var/log/mondoarchive.log' to see the output log [Inferior 1 (process 19382) exited normally]
>>> (gdb) quit
>>>
>>>
>>> So I reinstalled the official debian package:
>>>
>>> Sélection du paquet libmondorescue-perl précédemment désélectionné.
>>> (Lecture de la base de données... 279208 fichiers et répertoires déjà
>>> installés.)
>>> Dépaquetage de libmondorescue-perl (à partir de
>>> .../libmondorescue-perl_3.2.0-1_all.deb) ...
>>> Préparation du remplacement de mindi-busybox 1.18.5-3 (en utilisant
>>> .../mindi-busybox_1.21.1-1_amd64.deb) ...
>>> Dépaquetage de la mise à jour de mindi-busybox ...
>>> Préparation du remplacement de mindi 2.1.7-1 (en utilisant
>>> .../mindi_3.0.0-1_amd64.deb) ...
>>> Dépaquetage de la mise à jour de mindi ...
>>> Préparation du remplacement de mondo 3.0.4-1 (en utilisant
>>> .../mondo_3.2.0-1_amd64.deb) ...
>>> Dépaquetage de la mise à jour de mondo ...
>>> Traitement des actions différées (« triggers ») pour « man-db »...
>>> Paramétrage de libmondorescue-perl (3.2.0-1) ...
>>> Paramétrage de mindi-busybox (1.21.1-1) ...
>>> Paramétrage de mindi (3.0.0-1) ...
>>> Installation de la nouvelle version du fichier de configuration /etc/mindi/deplist.d/minimal.conf ...
>>> Installation de la nouvelle version du fichier de configuration /etc/mindi/deplist.d/udev.conf ...
>>> Installation de la nouvelle version du fichier de configuration /etc/mindi/deplist.d/ProLiant.conf ...
>>> Installation de la nouvelle version du fichier de configuration /etc/mindi/deplist.d/base.conf ...
>>> Installation de la nouvelle version du fichier de configuration /etc/mindi/deplist.d/lvm.conf ...
>>> Installation de la nouvelle version du fichier de configuration /etc/mindi/perl-scripts ...
>>> Paramétrage de mondo (3.2.0-1) ...
>>>
>>>
>>> but launched in the same way, it crashed again with a segmentation error:
>>>
>>> [phlsys]root:/home/phl/telechargements/mondo-3.2.0# mondoarchive -D -OV -i -N -G -s 780M -p sys-D7.7-diff_150105212200 -T /graveur -S /graveur -d /graveur -I "/|/|/opt/Zuma" -E "/bases/sybase|/graveur|/home|/opt|/photos|/quemu|/Sauvegardes|/var/crash|/var/backups|/var/log|/var/mail|/var/spool|/vbox|/videos|/www"
>>> See /var/log/mondoarchive.log for details of backup run.
>>> Checking sanity of your Linux distribution Done.
>>> Erreur de segmentation
>>>
>>>
>>>
>>> Please find attached the relevant mondoarchive.log file.
>>> It seems to be stopped before logging something about the fault.
>>> I franckly don't know what I could do more.
>>> Do you have an idea about what I could do to explore deeper this issue ?
>>> Something might be going wrong into the deb pkg ???
>>> I got it with apt using:
>>>    deb ftp://ftp.mondorescue.org//debian 7 contrib
>>>
>>>
>>> Thanks for your help.
>>> Regards,
>>> Philippe
>>>
>>>
>>>
>>>
>>>
>>> Le 06/01/2015 17:28, Gattegno, Victor (GSD CSC / GCC) a écrit :
>>>> Hello Philippe,
>>>>
>>>> From mondoarchive man : " When using the -I option with the -E option, the -E content should be subdirectories of those mentioned in the -I only, as -I takes precedence."
>>>>
>>>> But if your -I and -E combination works it's ok (check if /opt/zuma and /opt/calibre are well backuped and restored).
>>>>
>>>> Regards,
>>>> Victor
>>>>
>>>> -----Original Message-----
>>>> From: Philippe Lefevre [mailto:[hidden email]]
>>>> Sent: lundi 5 janvier 2015 21:42
>>>> To: [hidden email]
>>>> Subject: Re: [Mondo-devel] Segmentation error running mondoarchive
>>>> v3.2.0-r3332
>>>>
>>>> Thanks for your help and reply Victor,
>>>>
>>>> I should be able to replay with all of that before the end of the week and let you know.
>>>> Regarding the double /, it is due to my shell script which build the final request. I will also do a try without it.
>>>>
>>>> I believe I couldn't remove -I flag as in the exclude part there is /opt and I want to include only 2 directories /opt/zuma and /opt/calibre. At least, I should use -I "/opt/calibre|/opt/Zuma" right?
>>>>
>>>> PS: my system backup is run by root and ulimit is setted unlimited:
>>>>
>>>> # ulimit -a
>>>> core file size          (blocks, -c) 0
>>>> data seg size           (kbytes, -d) unlimited
>>>> scheduling priority             (-e) 0
>>>> file size               (blocks, -f) unlimited
>>>> pending signals                 (-i) 31106
>>>> max locked memory       (kbytes, -l) 64
>>>> max memory size         (kbytes, -m) unlimited
>>>> open files                      (-n) 1024
>>>> pipe size            (512 bytes, -p) 8
>>>> POSIX message queues     (bytes, -q) 819200
>>>> real-time priority              (-r) 0
>>>> stack size              (kbytes, -s) 8192
>>>> cpu time               (seconds, -t) unlimited
>>>> max user processes              (-u) 31106
>>>> virtual memory          (kbytes, -v) unlimited
>>>> file locks                      (-x) unlimited
>>>>
>>>>
>>>> Rgds,
>>>> Philippe
>>>>
>>>>
>>>> Le 05/01/2015 16:32, Gattegno, Victor (GSD CSC / GCC) a écrit :
>>>>> Hello Philippe,
>>>>>
>>>>> Good gdb work, but don't focus on "mondoarchive -v" segmentation fault, it's a known failing bug. It's better to debug mondoarchive with the options that you use.
>>>>>
>>>>>  In your 27/12/2014 test and post:
>>>>>  - did you posted too the associated /var/log/mondoarchive.log (compressed) ?
>>>>>  - you used -I (with / included twice) and -E options, it's better to use only -E option.
>>>>>
>>>>> What's the result of "ulimit -a" on your Debian ?
>>>>>
>>>>> I wish to you - and to all this mailig-list users - a nice year 2015.
>>>>>
>>>>> Rgds,
>>>>> Victor
>>>>>
>>>>> -----Original Message-----
>>>>> From: Philippe Lefevre [mailto:[hidden email]]
>>>>> Sent: samedi 3 janvier 2015 14:32
>>>>> To: [hidden email]
>>>>> Subject: Re: [Mondo-devel] Segmentation error running mondoarchive
>>>>> v3.2.0-r3332
>>>>>
>>>>> Hi list,
>>>>>
>>>>> Some more information about my issue.
>>>>>
>>>>> I can confirm that in my case it is related to this new release as a I did a downgrade and successfully built a new full backup.
>>>>>
>>>>> I uninstalled and purged
>>>>>   libmondorescue-perl_3.2.0-1_all.deb
>>>>>   mindi-busybox_1.21.1-1_amd64.deb
>>>>>   mindi_3.0.0-1_amd64.deb
>>>>>   mondo_3.2.0-1_amd64.deb
>>>>>
>>>>> and reinstalled the previous version
>>>>>   mindi-busybox 1.18.5-3
>>>>>   mindi 2.1.7-1
>>>>>   mondo 3.0.4-1
>>>>>
>>>>> I also compiled mondo 3.2.0 from sources and ran gdb against the simpliest command that raise the seg error. It shows :
>>>>>
>>>>> Starting program:
>>>>> /home/phl/telechargements/mondo-3.2.0/src/mondoarchive/mondoarchive -v [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
>>>>> mondoarchive v3.2.0-r3332
>>>>> See man page for help
>>>>>
>>>>> Program received signal SIGSEGV, Segmentation fault.
>>>>> 0x00007ffff76629aa in vfprintf () from
>>>>> /lib/x86_64-linux-gnu/libc.so.6
>>>>> (gdb) bt
>>>>> #0  0x00007ffff76629aa in vfprintf () from
>>>>> /lib/x86_64-linux-gnu/libc.so.6
>>>>> #1  0x00007ffff7688fca in vasprintf () from
>>>>> /lib/x86_64-linux-gnu/libc.so.6
>>>>> #2  0x00000000004367c4 in mr_asprintf_int (strp=strp@entry=0x7fffffffe0d0, line=line@entry=258, file=file@entry=0x44187f "libmondo-fork.c",
>>>>>     fmt=fmt@entry=0x441d38 "%s > %s/mondo-run-prog-thing.tmp 2>
>>>>> %s/mondo-run-prog-thing.err") at mr_mem.c:62
>>>>> #3  0x000000000041e0f0 in run_program_and_log_output
>>>>> (program=program@entry=0x43c4b4 "umount -d /mnt/cdrom",
>>>>> debug_level=debug_level@entry=0)
>>>>>     at libmondo-fork.c:258
>>>>> #4  0x000000000042ec19 in finish (signal=signal@entry=0) at
>>>>> newt-specific.c:388
>>>>> #5  0x0000000000403430 in main (argc=2, argv=0x7fffffffe668) at
>>>>> mondoarchive.c:176
>>>>> (gdb)
>>>>>
>>>>>
>>>>> function code exerpt
>>>>>
>>>>>    56 void mr_asprintf_int(char **strp, int line, const char *file, const char *fmt, ...) {
>>>>>    57
>>>>>    58 int res = 0;
>>>>>    59 va_list args;
>>>>>    60
>>>>>    61 va_start(args,fmt);
>>>>>    62 res = vasprintf(strp, fmt, args);
>>>>>    63 if (res == -1) {
>>>>>    64 mr_msg_int(1,line,file,"Unable to alloc memory in
>>>>> mr_asprintf\nExiting...");
>>>>>    65 mr_exit(-1,"Unable to alloc memory in mr_asprintf");
>>>>>    66 }
>>>>>    67 va_end(args);
>>>>>    68 }
>>>>>
>>>>>
>>>>> Breakpoint 1, mr_asprintf_int (strp=strp@entry=0x7fffffffe0d0, line=line@entry=258, file=file@entry=0x44187f "libmondo-fork.c",
>>>>>     fmt=fmt@entry=0x441d38 "%s > %s/mondo-run-prog-thing.tmp 2>
>>>>> %s/mondo-run-prog-thing.err") at mr_mem.c:56
>>>>> 56 void mr_asprintf_int(char **strp, int line, const char *file, const
>>>>> char *fmt, ...) {
>>>>> (gdb) s
>>>>> 61 va_start(args,fmt);
>>>>> (gdb) display fmt
>>>>> 1: fmt = 0x441d38 "%s > %s/mondo-run-prog-thing.tmp 2> %s/mondo-run-prog-thing.err"
>>>>> (gdb) display args
>>>>> 2: args = {{gp_offset = 4158558940, fp_offset = 32767,
>>>>> overflow_arg_area = 0x7ffff7fd5000, reg_save_area = 0x7ffff7ffd9d8}}
>>>>> (gdb) s
>>>>> 62 res = vasprintf(strp, fmt, args);
>>>>> 2: args = {{gp_offset = 4158558940, fp_offset = 32767,
>>>>> overflow_arg_area = 0x7ffff7fd5000, reg_save_area = 0x7ffff7ffd9d8}}
>>>>> 1: fmt = 0x441d38 "%s > %s/mondo-run-prog-thing.tmp 2> %s/mondo-run-prog-thing.err"
>>>>> (gdb) s
>>>>> 61 va_start(args,fmt);
>>>>> 2: args = {{gp_offset = 4158558940, fp_offset = 32767,
>>>>> overflow_arg_area = 0x7ffff7fd5000, reg_save_area = 0x7ffff7ffd9d8}}
>>>>> 1: fmt = 0x441d38 "%s > %s/mondo-run-prog-thing.tmp 2> %s/mondo-run-prog-thing.err"
>>>>> (gdb) s
>>>>> 62 res = vasprintf(strp, fmt, args);
>>>>> 2: args = {{gp_offset = 32, fp_offset = 48, overflow_arg_area =
>>>>> 0x7fffffffe0b0, reg_save_area = 0x7fffffffdfe0}}
>>>>> 1: fmt = 0x441d38 "%s > %s/mondo-run-prog-thing.tmp 2> %s/mondo-run-prog-thing.err"
>>>>> (gdb) display res
>>>>> 3: res = 0
>>>>> (gdb) s
>>>>>
>>>>> Program received signal SIGSEGV, Segmentation fault.
>>>>> 0x00007ffff76629aa in vfprintf () from
>>>>> /lib/x86_64-linux-gnu/libc.so.6
>>>>> (gdb)
>>>>>
>>>>>
>>>>> It seems there is an issue with mr_asprintf_int but sorry I don't feel strong enought to get more deeply into the mondo code and analyze it properly ...
>>>>>
>>>>> I hope this help ...
>>>>>
>>>>> Regards,
>>>>> Philippe
>>>>>
>>>>>
>>>>> Le 27/12/2014 11:17, [hidden email] a écrit :
>>>>>> Hi all,
>>>>>>
>>>>>> it seems that something goes wrong with mondo I could link to the
>>>>>> latest Debian version of MondoRescue.
>>>>>>
>>>>>> I updated my version last thursday and this morning (I have a
>>>>>> differential backup launched every friday night and one full a
>>>>>> month) it failed.
>>>>>> Unfortunately there are no much relevant informations in logs.
>>>>>>
>>>>>> The errors raised is :
>>>>>>
>>>>>>     # mondoarchive -D -OV -i -N -G -s 780M -p sys-D7.7-diff_141227100000
>>>>>>     -T /graveur -S /graveur -d
>>>>>>     /media/sauvegardes/phlsys/D7.7/sys/141227100000 -I
>>>>>>     "/|/|/opt/calibre|/opt/Zuma" -E
>>>>>>     "/bases/sybase|/graveur|/home|/opt|/photos|/quemu|/Sauvegardes|/var/crash|/var/backups|/var/log|/var/mail|/var/spool|/vbox|/videos|/www"
>>>>>>     See /var/log/mondoarchive.log for details of backup run.
>>>>>>     Checking sanity of your Linux distribution
>>>>>>     Done.
>>>>>>     Erreur de segmentation                /* Segmentation error */
>>>>>>
>>>>>> Please find attached the log files that seems to find out an issue
>>>>>> with LVM disks
>>>>>>
>>>>>>     INFO: Mindi v3.0.0-r3332
>>>>>>     INFO: Le disque /dev/mapper/data1vg-photoslv ne contient pas une
>>>>>>     table de partitions valable
>>>>>>              /* there is no valid partition table in
>>>>>>     /dev/mapper/data1vg-photoslv disk */
>>>>>>
>>>>>> I have no issues with my LVM disks. Please find on below my LVM
>>>>>> disks configuration
>>>>>>
>>>>>>     lvm> vgs
>>>>>>       VG      #PV #LV #SN Attr   VSize   VFree
>>>>>>       data1vg   1   7   0 wz--n- 931,51g 504,60g
>>>>>>       sysvg     1   1   0 wz--n-  95,12g  78,84g
>>>>>>
>>>>>>     lvm> lvs
>>>>>>       LV        VG      Attr     LSize   Pool Origin Data%  Move Log
>>>>>>     Copy%  Convert
>>>>>>       baseslv   data1vg -wi-ao--  
>>>>>>     1,86g                                          
>>>>>>       graveurlv data1vg -wi-ao--
>>>>>>     20,00g                                          
>>>>>>       homelv    data1vg -wi-ao--
>>>>>>     50,00g                                          
>>>>>>       photoslv  data1vg -wi-ao--
>>>>>>     70,00g                                          
>>>>>>       vboxlv    data1vg -wi-ao--
>>>>>>     130,39g                                          
>>>>>>       videoslv  data1vg -wi-ao--
>>>>>>     150,00g                                          
>>>>>>       wwwlv     data1vg -wi-ao--  
>>>>>>     4,66g                                          
>>>>>>       optlv     sysvg   -wi-ao--  16,28g
>>>>>>
>>>>>>     lvm> lvscan
>>>>>>       ACTIVE            '/dev/data1vg/photoslv' [70,00 GiB] inherit
>>>>>>       ACTIVE            '/dev/data1vg/videoslv' [150,00 GiB] inherit
>>>>>>       ACTIVE            '/dev/data1vg/homelv' [50,00 GiB] inherit
>>>>>>       ACTIVE            '/dev/data1vg/graveurlv' [20,00 GiB] inherit
>>>>>>       ACTIVE            '/dev/data1vg/wwwlv' [4,66 GiB] inherit
>>>>>>       ACTIVE            '/dev/data1vg/baseslv' [1,86 GiB] inherit
>>>>>>       ACTIVE            '/dev/data1vg/vboxlv' [130,39 GiB] inherit
>>>>>>       ACTIVE            '/dev/sysvg/optlv' [16,28 GiB] inherit
>>>>>>
>>>>>>     root@phlsys:/home/phl/Scripts# df -h
>>>>>>     Sys. fich.                                             Taille Util.
>>>>>>     Dispo Uti% Monté sur
>>>>>>     rootfs                                                    92G  
>>>>>>     11G   77G  12% /
>>>>>>     udev                                                      10M    
>>>>>>     0   10M   0% /dev
>>>>>>     tmpfs                                                    397M  968K
>>>>>>     396M   1% /run
>>>>>>     /dev/disk/by-uuid/4a5a9317-0b70-4796-a094-d61c01891c81    92G  
>>>>>>     11G   77G  12% /
>>>>>>     tmpfs                                                    5,0M     0
>>>>>>     5,0M   0% /run/lock
>>>>>>     tmpfs                                                    985M  324K
>>>>>>     985M   1% /run/shm
>>>>>>     /dev/mapper/sysvg-optlv                                   17G   15G
>>>>>>     845M  95% /opt
>>>>>>     /dev/mapper/data1vg-homelv                                50G   40G
>>>>>>     7,2G  85% /home
>>>>>>     /dev/mapper/data1vg-wwwlv                                4,6G  2,5G
>>>>>>     1,9G  58% /www
>>>>>>     /dev/mapper/data1vg-baseslv                              1,9G  720M
>>>>>>     1,1G  41% /bases
>>>>>>     /dev/mapper/data1vg-photoslv                              69G  
>>>>>>     43G   23G  66% /photos
>>>>>>     /dev/mapper/data1vg-videoslv                             148G
>>>>>>     104G   37G  74% /videos
>>>>>>     /dev/mapper/data1vg-vboxlv                               129G
>>>>>>     100G   23G  82% /vbox
>>>>>>     /dev/mapper/data1vg-graveurlv                             20G
>>>>>>     8,1G   11G  44% /graveur
>>>>>>
>>>>>>
>>>>>> The latest mondo upgrade dated of 25th of december was (it worked
>>>>>> fine before this upgrade)
>>>>>>
>>>>>>     Start-Date: 2014-12-25  18:55:08
>>>>>>     Commandline: /usr/sbin/synaptic
>>>>>>     Install: libprojectbuilder-perl:amd64 (0.12.6-1, automatic),
>>>>>>     libmondorescue-perl:amd64 (3.2.0-1, automatic)
>>>>>>     Upgrade: mindi:amd64 (2.1.7-1, 3.0.0-1), mondo:amd64 (3.0.4-1,
>>>>>>     3.2.0-1), mindi-busybox:amd64 (1.18.5-3, 1.21.1-1)
>>>>>>     End-Date: 2014-12-25  18:55:31
>>>>>>
>>>>>> The Debian distro used is
>>>>>>
>>>>>>     root@phlsys:/home/phl/Scripts# uname -a
>>>>>>     Linux phlsys 3.2.0-4-amd64 #1 SMP Debian 3.2.63-2+deb7u2 x86_64
>>>>>>     GNU/Linux
>>>>>>
>>>>>> Anyone have an idea to try to debug this.
>>>>>>
>>>>>> Thanks for any help.
>>>>>>
>>>>>> By the way, I whish you all an happy new year 2015 with all the best
>>>>>> in your lifes Kind regards, Philippe
>>>>>>
>>>>>>
>>>>>
>>>>>
>>>>>
>>>>> ---------------------------------------------------------------------
>>>>> -
>>>>> -------- Dive into the World of Parallel Programming! The Go Parallel
>>>>> Website, sponsored by Intel and developed in partnership with
>>>>> Slashdot Media, is your hub for all things parallel software
>>>>> development, from weekly thought leadership blogs to news, videos,
>>>>> case studies, tutorials and more. Take a look and join the conversation now.
>>>>> http://goparallel.sourceforge.net
>>>>> _______________________________________________
>>>>> Mondo-devel mailing list
>>>>> [hidden email]
>>>>> https://lists.sourceforge.net/lists/listinfo/mondo-devel
>>>>> ---------------------------------------------------------------------
>>>>> -
>>>>> -------- Dive into the World of Parallel Programming! The Go Parallel
>>>>> Website, sponsored by Intel and developed in partnership with
>>>>> Slashdot Media, is your hub for all things parallel software
>>>>> development, from weekly thought leadership blogs to news, videos,
>>>>> case studies, tutorials and more. Take a look and join the conversation now.
>>>>> http://goparallel.sourceforge.net
>>>>> _______________________________________________
>>>>> Mondo-devel mailing list
>>>>> [hidden email]
>>>>> https://lists.sourceforge.net/lists/listinfo/mondo-devel
>>>>>
>>>>
>>>>
>>>>
>>>> ----------------------------------------------------------------------
>>>> -------- Dive into the World of Parallel Programming! The Go Parallel
>>>> Website, sponsored by Intel and developed in partnership with Slashdot
>>>> Media, is your hub for all things parallel software development, from
>>>> weekly thought leadership blogs to news, videos, case studies,
>>>> tutorials and more. Take a look and join the conversation now.
>>>> http://goparallel.sourceforge.net 
>>>> _______________________________________________
>>>> Mondo-devel mailing list
>>>> [hidden email]
>>>> https://lists.sourceforge.net/lists/listinfo/mondo-devel
>>>> ----------------------------------------------------------------------
>>>> -------- Dive into the World of Parallel Programming! The Go Parallel
>>>> Website, sponsored by Intel and developed in partnership with Slashdot
>>>> Media, is your hub for all things parallel software development, from
>>>> weekly thought leadership blogs to news, videos, case studies,
>>>> tutorials and more. Take a look and join the conversation now.
>>>> http://goparallel.sourceforge.net 
>>>> _______________________________________________
>>>> Mondo-devel mailing list
>>>> [hidden email]
>>>> https://lists.sourceforge.net/lists/listinfo/mondo-devel
>>>>
>>>
>>>
>>> ------------------------------------------------------------------------------
>>> New Year. New Location. New Benefits. New Data Center in Ashburn, VA.
>>> GigeNET is offering a free month of service with a new server in Ashburn.
>>> Choose from 2 high performing configs, both with 100TB of bandwidth.
>>> Higher redundancy.Lower latency.Increased capacity.Completely compliant.
>>> http://p.sf.net/sfu/gigenet
>>> _______________________________________________
>>> Mondo-devel mailing list
>>> [hidden email]
>>> https://lists.sourceforge.net/lists/listinfo/mondo-devel
>>>
>>
>>
>
>> mindi v3.0.0-r3332
>> x86_64 architecture detected
>> mindi called with the following arguments:
>> --makemountlist /tmp/mondo.tmp.4v41Vd/mountlist.txt.test
>> Start date : lundi 19 janvier 2015, 22:16:43 (UTC+0100)
>> -----------------------------
>> MONDO_SHARE = /usr/share/mondo
>> MINDI_LIB = /usr/lib/mindi
>> MINDI_SBIN = /usr/sbin
>> MINDI_CONF = /etc/mindi
>> -----------------------------
>>  Mindi configuration file    
>> -----------------------------
>> -----------------------------
>> In Mindi
>> --------
>> EXTRA_SPACE = 120000
>> BOOT_SIZE = 65600
>> --------
>> INFO: Found isolinux.bin at /usr/lib/syslinux/isolinux.bin
>> INFO: LVM set to v2
>> ----------
>> mount result:
>> -------------
>> sysfs on /sys type sysfs (rw,nosuid,nodev,noexec,relatime)
>> proc on /proc type proc (rw,nosuid,nodev,noexec,relatime)
>> udev on /dev type devtmpfs (rw,relatime,size=10240k,nr_inodes=497709,mode=755)
>> devpts on /dev/pts type devpts (rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000)
>> tmpfs on /run type tmpfs (rw,nosuid,noexec,relatime,size=406288k,mode=755)
>> /dev/disk/by-uuid/4a5a9317-0b70-4796-a094-d61c01891c81 on / type ext4 (rw,relatime,errors=remount-ro,user_xattr,barrier=1,data=ordered)
>> tmpfs on /run/lock type tmpfs (rw,nosuid,nodev,noexec,relatime,size=5120k)
>> tmpfs on /run/shm type tmpfs (rw,nosuid,nodev,noexec,relatime,size=1008560k)
>> /dev/mapper/sysvg-optlv on /opt type ext4 (rw,relatime,errors=remount-ro,user_xattr,barrier=1,data=ordered)
>> /dev/mapper/data1vg-homelv on /home type ext4 (rw,relatime,errors=remount-ro,user_xattr,barrier=1,data=ordered)
>> /dev/mapper/data1vg-wwwlv on /www type ext4 (rw,relatime,errors=remount-ro,user_xattr,barrier=1,data=ordered)
>> /dev/mapper/data1vg-baseslv on /bases type ext4 (rw,relatime,errors=remount-ro,user_xattr,barrier=1,data=ordered)
>> /dev/mapper/data1vg-photoslv on /photos type ext4 (rw,relatime,errors=remount-ro,user_xattr,barrier=1,data=ordered)
>> /dev/mapper/data1vg-videoslv on /videos type ext4 (rw,relatime,errors=remount-ro,user_xattr,barrier=1,data=ordered)
>> /dev/mapper/data1vg-vboxlv on /vbox type ext4 (rw,relatime,errors=remount-ro,user_xattr,barrier=1,data=ordered)
>> /dev/mapper/data1vg-graveurlv on /graveur type ext4 (rw,relatime,errors=remount-ro,user_xattr,barrier=1,data=ordered)
>> rpc_pipefs on /var/lib/nfs/rpc_pipefs type rpc_pipefs (rw,relatime)
>> binfmt_misc on /proc/sys/fs/binfmt_misc type binfmt_misc (rw,nosuid,nodev,noexec,relatime)
>> No file /etc/raidtab
>> -------------
>> No file /etc/mdadm.conf
>> -------------
>> cat /proc/cmdline
>> -------------
>> BOOT_IMAGE=/boot/vmlinuz-3.2.0-4-amd64 root=UUID=4a5a9317-0b70-4796-a094-d61c01891c81 ro quiet
>> -------------
>> cat /proc/swaps:
>> -------------
>> Filename Type Size Used Priority
>> /dev/sda6                               partition 979928 11992 -1
>> -------------
>> cat /proc/mdstat:
>> -------------
>> Personalities : [linear] [raid0] [raid1] [raid6] [raid5] [raid4]
>> unused devices: <none>
>> -------------
>> cat /proc/partitions:
>> -------------
>> major minor  #blocks  name
>>
>>    8        0  312571224 sda
>>    8        1      56196 sda1
>>    8        2   10485760 sda2
>>    8        3  103643080 sda3
>>    8        4          1 sda4
>>    8        5   97659103 sda5
>>    8        6     979933 sda6
>>    8        7   99741696 sda7
>>   11        0    1048575 sr0
>>    8       16  976762584 sdb
>>    8       17  976761560 sdb1
>>  253        0   73400320 dm-0
>>  253        1  157286400 dm-1
>>  253        2   52428800 dm-2
>>  253        3   20971520 dm-3
>>  253        4    4886528 dm-4
>>  253        5    1953792 dm-5
>>  253        6  136720384 dm-6
>>  253        7   17072128 dm-7
>> -------------
>> cat /proc/filesystems:
>> -------------
>> nodev sysfs
>> nodev rootfs
>> nodev bdev
>> nodev proc
>> nodev cgroup
>> nodev cpuset
>> nodev tmpfs
>> nodev devtmpfs
>> nodev debugfs
>> nodev securityfs
>> nodev sockfs
>> nodev pipefs
>> nodev anon_inodefs
>> nodev devpts
>> nodev ramfs
>> nodev hugetlbfs
>> nodev pstore
>> nodev mqueue
>> nodev usbfs
>> ext4
>> nodev ecryptfs
>> nodev rpc_pipefs
>> nodev nfs
>> nodev nfs4
>> nodev nfsd
>> nodev binfmt_misc
>> msdos
>> vfat
>> iso9660
>> ext2
>> -------------
>> lsmod result:
>> -------------
>> Module                  Size  Used by
>> nls_utf8               12456  0
>> nls_cp437              16553  0
>> ext2                   59231  0
>> raid456                48453  0
>> async_raid6_recov      12574  1 raid456
>> async_memcpy           12387  2 async_raid6_recov,raid456
>> async_pq               12605  2 async_raid6_recov,raid456
>> raid6_pq               82624  2 async_pq,async_raid6_recov
>> async_xor              12422  3 async_pq,async_raid6_recov,raid456
>> xor                    12605  1 async_xor
>> async_tx               12604  5 async_xor,async_pq,async_memcpy,async_raid6_recov,raid456
>> raid1                  30714  0
>> raid0                  12904  0
>> linear                 12735  0
>> isofs                  35173  0
>> brd                    12772  0
>> vfat                   17316  0
>> msdos                  17077  0
>> fat                    45642  2 msdos,vfat
>> pci_stub               12429  1
>> vboxpci                19096  0
>> vboxnetadp             25443  0
>> vboxnetflt             23657  0
>> vboxdrv               304550  3 vboxnetflt,vboxnetadp,vboxpci
>> nfnetlink_log          17212  0
>> nfnetlink              12906  1 nfnetlink_log
>> parport_pc             22364  0
>> ppdev                  12763  0
>> lp                     17149  0
>> parport                31858  3 lp,ppdev,parport_pc
>> ip6t_REJECT            12512  2
>> xt_multiport           12548  2
>> xt_conntrack           12681  18
>> iptable_nat            12928  0
>> binfmt_misc            12957  1
>> iptable_mangle         12536  0
>> nfsd                  216181  2
>> nfs                   308353  0
>> nfs_acl                12511  2 nfs,nfsd
>> auth_rpcgss            37143  2 nfs,nfsd
>> fscache                36739  1 nfs
>> lockd                  67306  2 nfs,nfsd
>> sunrpc                173730  6 lockd,auth_rpcgss,nfs_acl,nfs,nfsd
>> ip6t_LOG               12609  4
>> xt_hl                  12449  6
>> ip6t_rt                12499  3
>> nf_conntrack_ipv6      13316  7
>> nf_defrag_ipv6         12832  1 nf_conntrack_ipv6
>> ipt_REJECT             12502  1
>> ipt_LOG                12605  12
>> xt_limit               12638  19
>> xt_tcpudp              12570  62
>> xt_addrtype            12557  4
>> xt_state               12503  21
>> ip6table_filter        12540  1
>> ip6_tables             22175  3 ip6table_filter,ip6t_rt,ip6t_LOG
>> nf_conntrack_netbios_ns    12445  0
>> nf_conntrack_broadcast    12365  1 nf_conntrack_netbios_ns
>> nf_nat_ftp             12460  0
>> nf_nat                 18242  2 nf_nat_ftp,iptable_nat
>> nf_conntrack_ipv4      14078  35 nf_nat,iptable_nat
>> nf_defrag_ipv4         12483  1 nf_conntrack_ipv4
>> nf_conntrack_ftp       12605  1 nf_nat_ftp
>> nf_conntrack           52720  10 nf_conntrack_ftp,nf_conntrack_ipv4,nf_nat,nf_nat_ftp,nf_conntrack_broadcast,nf_conntrack_netbios_ns,xt_state,nf_conntrack_ipv6,iptable_nat,xt_conntrack
>> iptable_filter         12536  1
>> ip_tables              22042  3 iptable_filter,iptable_mangle,iptable_nat
>> x_tables               19118  18 ip_tables,iptable_filter,ip6_tables,ip6table_filter,xt_state,xt_addrtype,xt_tcpudp,xt_limit,ipt_LOG,ipt_REJECT,ip6t_rt,xt_hl,ip6t_LOG,iptable_mangle,iptable_nat,xt_conntrack,xt_multiport,ip6t_REJECT
>> loop                   22641  0
>> ecryptfs               81507  0
>> dm_crypt               22586  0
>> snd_hda_codec_hdmi     30824  1
>> snd_usb_audio          89083  2
>> snd_usbmidi_lib        23369  1 snd_usb_audio
>> snd_seq_midi           12848  0
>> snd_seq_midi_event     13316  1 snd_seq_midi
>> snd_rawmidi            23060  2 snd_seq_midi,snd_usbmidi_lib
>> snd_hda_codec_idt      53792  1
>> tuner_simple           17175  1
>> tuner_types            16409  1 tuner_simple
>> wm8775                 12749  1
>> tda9887                12645  1
>> tda8290                17278  0
>> tuner                  17497  2
>> cx25840                39782  1
>> ivtv                  129010  0
>> cx2341x                21461  1 ivtv
>> snd_hda_intel          26259  2
>> snd_hda_codec          78031  3 snd_hda_intel,snd_hda_codec_idt,snd_hda_codec_hdmi
>> snd_hwdep              13186  2 snd_hda_codec,snd_usb_audio
>> snd_pcm                68083  4 snd_hda_codec,snd_hda_intel,snd_usb_audio,snd_hda_codec_hdmi
>> tveeprom               20593  1 ivtv
>> v4l2_common            13222  5 cx2341x,ivtv,cx25840,tuner,wm8775
>> videodev               70889  6 v4l2_common,cx2341x,ivtv,cx25840,tuner,wm8775
>> v4l2_compat_ioctl32    16655  1 videodev
>> media                  18148  1 videodev
>> nv_tco                 12914  0
>> i2c_algo_bit           12841  1 ivtv
>> snd_page_alloc         13003  2 snd_pcm,snd_hda_intel
>> snd_seq                45126  2 snd_seq_midi_event,snd_seq_midi
>> snd_seq_device         13176  3 snd_seq,snd_rawmidi,snd_seq_midi
>> i2c_nforce2            12584  0
>> dcdbas                 13307  0
>> edac_mce_amd           17103  0
>> edac_core              35258  0
>> evdev                  17562  18
>> powernow_k8            17618  1
>> mperf                  12453  1 powernow_k8
>> k8temp                 12647  0
>> psmouse                69265  0
>> snd_timer              22917  2 snd_seq,snd_pcm
>> i2c_core               23876  12 i2c_nforce2,i2c_algo_bit,videodev,v4l2_common,tveeprom,ivtv,cx25840,tuner,tda8290,tda9887,wm8775,tuner_simple
>> serio_raw              12931  0
>> fglrx                2634136  183
>> pcspkr                 12579  0
>> snd                    52893  20 snd_timer,snd_seq_device,snd_seq,snd_pcm,snd_hwdep,snd_hda_codec,snd_hda_intel,snd_hda_codec_idt,snd_rawmidi,snd_usbmidi_lib,snd_usb_audio,snd_hda_codec_hdmi
>> processor              28149  1 powernow_k8
>> button                 12937  1 fglrx
>> soundcore              13065  1 snd
>> thermal_sys            18040  1 processor
>> ext4                  350804  9
>> crc16                  12343  1 ext4
>> jbd2                   62115  1 ext4
>> mbcache                13114  2 ext4,ext2
>> dm_mod                 63645  29 dm_crypt
>> md_mod                 87742  4 linear,raid0,raid1,raid456
>> sg                     25874  0
>> sd_mod                 36136  6
>> sr_mod                 21899  0
>> cdrom                  35401  1 sr_mod
>> crc_t10dif             12348  1 sd_mod
>> usbhid                 36418  0
>> hid                    81372  1 usbhid
>> usb_storage            43870  0
>> ata_generic            12479  0
>> ohci_hcd               26563  0
>> sata_nv                26690  4
>> libata                140630  2 sata_nv,ata_generic
>> ehci_hcd               40249  0
>> b44                    27751  0
>> ssb                    44714  1 b44
>> mmc_core               68400  1 ssb
>> mii                    12675  1 b44
>> pcmcia                 32734  1 ssb
>> pcmcia_core            18294  1 pcmcia
>> scsi_mod              162321  5 libata,usb_storage,sr_mod,sd_mod,sg
>> usbcore               128741  7 ehci_hcd,ohci_hcd,usb_storage,usbhid,snd_usbmidi_lib,snd_usb_audio
>> usb_common             12354  1 usbcore
>> -------------
>> FORCE_MODS:
>> -------------
>>
>> -------------
>> DENY_MODS:
>> -------------
>> kqemu vxfen
>> -------------
>> df result:
>> ----------
>> Sys. fich.                                             Type        1K-blocks     Util. Disponible Uti% Mont?? sur
>> rootfs                                                 rootfs       96124904  10822540   80419412  12% /
>> sysfs                                                  sysfs               0         0          0    - /sys
>> proc                                                   proc                0         0          0    - /proc
>> udev                                                   devtmpfs        10240         0      10240   0% /dev
>> devpts                                                 devpts              0         0          0    - /dev/pts
>> tmpfs                                                  tmpfs          406288       944     405344   1% /run
>> /dev/disk/by-uuid/4a5a9317-0b70-4796-a094-d61c01891c81 ext4         96124904  10822540   80419412  12% /
>> tmpfs                                                  tmpfs            5120         0       5120   0% /run/lock
>> tmpfs                                                  tmpfs         1008560       276    1008284   1% /run/shm
>> /dev/mapper/sysvg-optlv                                ext4         16803708  15010400     939704  95% /opt
>> /dev/mapper/data1vg-homelv                             ext4         51606140  41866076    7119008  86% /home
>> /dev/mapper/data1vg-wwwlv                              ext4          4809704   2794384    1770996  62% /www
>> /dev/mapper/data1vg-baseslv                            ext4          1923084    737276    1088120  41% /bases
>> /dev/mapper/data1vg-photoslv                           ext4         72248648  45036992   23541896  66% /photos
>> /dev/mapper/data1vg-videoslv                           ext4        154818540 108302512   38651708  74% /videos
>> /dev/mapper/data1vg-vboxlv                             ext4        134573320 104068176   23669128  82% /vbox
>> /dev/mapper/data1vg-graveurlv                          ext4         20642428   8094972   11498880  42% /graveur
>> rpc_pipefs                                             rpc_pipefs          0         0          0    - /var/lib/nfs/rpc_pipefs
>> binfmt_misc                                            binfmt_misc         0         0          0    - /proc/sys/fs/binfmt_misc
>> -------------
>> df -i result:
>> ----------
>> Sys. fich.                                              Inodes IUtil.  ILibre IUti% Mont?? sur
>> rootfs                                                 6111232 313566 5797666    6% /
>> udev                                                    497709    610  497099    1% /dev
>> tmpfs                                                   507860    667  507193    1% /run
>> /dev/disk/by-uuid/4a5a9317-0b70-4796-a094-d61c01891c81 6111232 313566 5797666    6% /
>> tmpfs                                                   507860      3  507857    1% /run/lock
>> tmpfs                                                   507860     15  507845    1% /run/shm
>> /dev/mapper/sysvg-optlv                                1068960  54781 1014179    6% /opt
>> /dev/mapper/data1vg-homelv                             3276800  83092 3193708    3% /home
>> /dev/mapper/data1vg-wwwlv                               305824  43214  262610   15% /www
>> /dev/mapper/data1vg-baseslv                             122160   1213  120947    1% /bases
>> /dev/mapper/data1vg-photoslv                           4587520  23609 4563911    1% /photos
>> /dev/mapper/data1vg-videoslv                           9830400    180 9830220    1% /videos
>> /dev/mapper/data1vg-vboxlv                             8552448     91 8552357    1% /vbox
>> /dev/mapper/data1vg-graveurlv                          1310720     80 1310640    1% /graveur
>> -------------
>> -------------
>> INFO: /boot/grub/grub.cfg content
>> -------------
>> #
>> # DO NOT EDIT THIS FILE
>> #
>> # It is automatically generated by grub-mkconfig using templates
>> # from /etc/grub.d and settings from /etc/default/grub
>> #
>>
>> ### BEGIN /etc/grub.d/00_header ###
>> if [ -s $prefix/grubenv ]; then
>>   load_env
>> fi
>> set default="0"
>> if [ "${prev_saved_entry}" ]; then
>>   set saved_entry="${prev_saved_entry}"
>>   save_env saved_entry
>>   set prev_saved_entry=
>>   save_env prev_saved_entry
>>   set boot_once=true
>> fi
>>
>> function savedefault {
>>   if [ -z "${boot_once}" ]; then
>>     saved_entry="${chosen}"
>>     save_env saved_entry
>>   fi
>> }
>>
>> function load_video {
>>   insmod vbe
>>   insmod vga
>>   insmod video_bochs
>>   insmod video_cirrus
>> }
>>
>> insmod part_msdos
>> insmod ext2
>> set root='(hd0,msdos5)'
>> search --no-floppy --fs-uuid --set=root 4a5a9317-0b70-4796-a094-d61c01891c81
>> if loadfont /usr/share/grub/unicode.pf2 ; then
>>   set gfxmode=640x480
>>   load_video
>>   insmod gfxterm
>>   insmod part_msdos
>>   insmod ext2
>>   set root='(hd0,msdos5)'
>>   search --no-floppy --fs-uuid --set=root 4a5a9317-0b70-4796-a094-d61c01891c81
>>   set locale_dir=($root)/boot/grub/locale
>>   set lang=fr_FR
>>   insmod gettext
>> fi
>> terminal_output gfxterm
>> set timeout=5
>> ### END /etc/grub.d/00_header ###
>>
>> ### BEGIN /etc/grub.d/05_debian_theme ###
>> insmod part_msdos
>> insmod ext2
>> set root='(hd0,msdos5)'
>> search --no-floppy --fs-uuid --set=root 4a5a9317-0b70-4796-a094-d61c01891c81
>> insmod png
>> if background_image /usr/share/images/desktop-base/joy-grub.png; then
>>   set color_normal=white/black
>>   set color_highlight=black/white
>> else
>>   set menu_color_normal=cyan/blue
>>   set menu_color_highlight=white/blue
>> fi
>> ### END /etc/grub.d/05_debian_theme ###
>>
>> ### BEGIN /etc/grub.d/10_linux ###
>> menuentry 'Debian GNU/Linux, avec Linux 3.2.0-4-amd64' --class debian --class gnu-linux --class gnu --class os {
>> load_video
>> insmod gzio
>> insmod part_msdos
>> insmod ext2
>> set root='(hd0,msdos5)'
>> search --no-floppy --fs-uuid --set=root 4a5a9317-0b70-4796-a094-d61c01891c81
>> echo 'Chargement de Linux 3.2.0-4-amd64 ...'
>> linux /boot/vmlinuz-3.2.0-4-amd64 root=UUID=4a5a9317-0b70-4796-a094-d61c01891c81 ro  quiet
>> echo 'Chargement du disque m??moire initial ...'
>> initrd /boot/initrd.img-3.2.0-4-amd64
>> }
>> menuentry 'Debian GNU/Linux, avec Linux 3.2.0-4-amd64 (mode de d??pannage)' --class debian --class gnu-linux --class gnu --class os {
>> load_video
>> insmod gzio
>> insmod part_msdos
>> insmod ext2
>> set root='(hd0,msdos5)'
>> search --no-floppy --fs-uuid --set=root 4a5a9317-0b70-4796-a094-d61c01891c81
>> echo 'Chargement de Linux 3.2.0-4-amd64 ...'
>> linux /boot/vmlinuz-3.2.0-4-amd64 root=UUID=4a5a9317-0b70-4796-a094-d61c01891c81 ro single
>> echo 'Chargement du disque m??moire initial ...'
>> initrd /boot/initrd.img-3.2.0-4-amd64
>> }
>> ### END /etc/grub.d/10_linux ###
>>
>> ### BEGIN /etc/grub.d/20_linux_xen ###
>> ### END /etc/grub.d/20_linux_xen ###
>>
>> ### BEGIN /etc/grub.d/20_memtest86+ ###
>> menuentry "Memory test (memtest86+)" {
>> insmod part_msdos
>> insmod ext2
>> set root='(hd0,msdos5)'
>> search --no-floppy --fs-uuid --set=root 4a5a9317-0b70-4796-a094-d61c01891c81
>> linux16 /boot/memtest86+.bin
>> }
>> menuentry "Memory test (memtest86+, serial console 115200)" {
>> insmod part_msdos
>> insmod ext2
>> set root='(hd0,msdos5)'
>> search --no-floppy --fs-uuid --set=root 4a5a9317-0b70-4796-a094-d61c01891c81
>> linux16 /boot/memtest86+.bin console=ttyS0,115200n8
>> }
>> menuentry "Memory test (memtest86+, experimental multiboot)" {
>> insmod part_msdos
>> insmod ext2
>> set root='(hd0,msdos5)'
>> search --no-floppy --fs-uuid --set=root 4a5a9317-0b70-4796-a094-d61c01891c81
>> multiboot /boot/memtest86+_multiboot.bin
>> }
>> menuentry "Memory test (memtest86+, serial console 115200, experimental multiboot)" {
>> insmod part_msdos
>> insmod ext2
>> set root='(hd0,msdos5)'
>> search --no-floppy --fs-uuid --set=root 4a5a9317-0b70-4796-a094-d61c01891c81
>> multiboot /boot/memtest86+_multiboot.bin console=ttyS0,115200n8
>> }
>> ### END /etc/grub.d/20_memtest86+ ###
>>
>> ### BEGIN /etc/grub.d/30_os-prober ###
>> menuentry "Windows Vista (loader) (on /dev/sda3)" --class windows --class os {
>> insmod part_msdos
>> insmod ntfs
>> set root='(hd0,msdos3)'
>> search --no-floppy --fs-uuid --set=root 0C6CE0BA6CE0A026
>> chainloader +1
>> }
>> ### END /etc/grub.d/30_os-prober ###
>>
>> ### BEGIN /etc/grub.d/40_custom ###
>> # This file provides an easy way to add custom menu entries.  Simply type the
>> # menu entries you want to add after this comment.  Be careful not to change
>> # the 'exec tail' line above.
>> ### END /etc/grub.d/40_custom ###
>>
>> ### BEGIN /etc/grub.d/41_custom ###
>> if [ -f  $prefix/custom.cfg ]; then
>>   source $prefix/custom.cfg;
>> fi
>> ### END /etc/grub.d/41_custom ###
>> -------------
>> -------------
>> INFO: /boot/grub/device.map content
>> -------------
>> (hd0) /dev/disk/by-id/ata-ST3320620AS_5QF2VWM8
>> -------------
>> Full fdisk info
>> ---------------
>>
>> Disque /dev/sda??: 320.1??Go, 320072933376??octets
>> 255??t??tes, 63??secteurs/piste, 38913??cylindres, total 625142448??secteurs
>> Unit??s = secteurs de 1 * 512 = 512??octets
>> Taille de secteur (logique / physique)??: 512??octets / 512??octets
>> taille d'E/S (minimale / optimale)??: 512??octets / 512??octets
>> Identifiant de disque??: 0x58000000
>>
>> P??riph??rique Amorce  D??but        Fin      Blocs     Id  Syst??me
>> /dev/sda1              63      112454       56196   de  Dell Utility
>> /dev/sda2          112640    21084159    10485760    7  HPFS/NTFS/exFAT
>> /dev/sda3   *    21093345   228379505   103643080+   7  HPFS/NTFS/exFAT
>> /dev/sda4       228380101   625141759   198380829+   5  ??tendue
>> /dev/sda5       228380103   423698309    97659103+  83  Linux
>> /dev/sda6       423698373   425658239      979933+  82  partition d'??change Linux / Solaris
>> /dev/sda7       425658368   625141759    99741696   8e  LVM Linux
>>
>> Disque /dev/sdb??: 1000.2??Go, 1000204886016??octets
>> 81??t??tes, 63??secteurs/piste, 382818??cylindres, total 1953525168??secteurs
>> Unit??s = secteurs de 1 * 512 = 512??octets
>> Taille de secteur (logique / physique)??: 512??octets / 512??octets
>> taille d'E/S (minimale / optimale)??: 512??octets / 512??octets
>> Identifiant de disque??: 0x0003513f
>>
>> P??riph??rique Amorce  D??but        Fin      Blocs     Id  Syst??me
>> /dev/sdb1            2048  1953525167   976761560   8e  LVM Linux
>>
>> Disque /dev/mapper/data1vg-photoslv??: 75.2??Go, 75161927680??octets
>> 255??t??tes, 63??secteurs/piste, 9137??cylindres, total 146800640??secteurs
>> Unit??s = secteurs de 1 * 512 = 512??octets
>> Taille de secteur (logique / physique)??: 512??octets / 512??octets
>> taille d'E/S (minimale / optimale)??: 512??octets / 512??octets
>> Identifiant de disque??: 0x00000000
>>
>>
>> Disque /dev/mapper/data1vg-videoslv??: 161.1??Go, 161061273600??octets
>> 255??t??tes, 63??secteurs/piste, 19581??cylindres, total 314572800??secteurs
>> Unit??s = secteurs de 1 * 512 = 512??octets
>> Taille de secteur (logique / physique)??: 512??octets / 512??octets
>> taille d'E/S (minimale / optimale)??: 512??octets / 512??octets
>> Identifiant de disque??: 0x00000000
>>
>>
>> Disque /dev/mapper/data1vg-homelv??: 53.7??Go, 53687091200??octets
>> 255??t??tes, 63??secteurs/piste, 6527??cylindres, total 104857600??secteurs
>> Unit??s = secteurs de 1 * 512 = 512??octets
>> Taille de secteur (logique / physique)??: 512??octets / 512??octets
>> taille d'E/S (minimale / optimale)??: 512??octets / 512??octets
>> Identifiant de disque??: 0x00000000
>>
>>
>> Disque /dev/mapper/data1vg-graveurlv??: 21.5??Go, 21474836480??octets
>> 255??t??tes, 63??secteurs/piste, 2610??cylindres, total 41943040??secteurs
>> Unit??s = secteurs de 1 * 512 = 512??octets
>> Taille de secteur (logique / physique)??: 512??octets / 512??octets
>> taille d'E/S (minimale / optimale)??: 512??octets / 512??octets
>> Identifiant de disque??: 0x00000000
>>
>>
>> Disque /dev/mapper/data1vg-wwwlv??: 5003??Mo, 5003804672??octets
>> 255??t??tes, 63??secteurs/piste, 608??cylindres, total 9773056??secteurs
>> Unit??s = secteurs de 1 * 512 = 512??octets
>> Taille de secteur (logique / physique)??: 512??octets / 512??octets
>> taille d'E/S (minimale / optimale)??: 512??octets / 512??octets
>> Identifiant de disque??: 0x00000000
>>
>>
>> Disque /dev/mapper/data1vg-baseslv??: 2000??Mo, 2000683008??octets
>> 255??t??tes, 63??secteurs/piste, 243??cylindres, total 3907584??secteurs
>> Unit??s = secteurs de 1 * 512 = 512??octets
>> Taille de secteur (logique / physique)??: 512??octets / 512??octets
>> taille d'E/S (minimale / optimale)??: 512??octets / 512??octets
>> Identifiant de disque??: 0x00000000
>>
>>
>> Disque /dev/mapper/data1vg-vboxlv??: 140.0??Go, 140001673216??octets
>> 255??t??tes, 63??secteurs/piste, 17020??cylindres, total 273440768??secteurs
>> Unit??s = secteurs de 1 * 512 = 512??octets
>> Taille de secteur (logique / physique)??: 512??octets / 512??octets
>> taille d'E/S (minimale / optimale)??: 512??octets / 512??octets
>> Identifiant de disque??: 0x00000000
>>
>>
>> Disque /dev/mapper/sysvg-optlv??: 17.5??Go, 17481859072??octets
>> 255??t??tes, 63??secteurs/piste, 2125??cylindres, total 34144256??secteurs
>> Unit??s = secteurs de 1 * 512 = 512??octets
>> Taille de secteur (logique / physique)??: 512??octets / 512??octets
>> taille d'E/S (minimale / optimale)??: 512??octets / 512??octets
>> Identifiant de disque??: 0x00000000
>>
>> ----------------
>> ------------------------------------
>> Your raw fstab file looks like this:
>> ------------------------------------
>> # /etc/fstab: static file system information.
>> #
>> # Use 'blkid' to print the universally unique identifier for a
>> # device; this may be used with UUID= as a more robust way to name devices
>> # that works even if disks are added and removed. See fstab(5).
>> #
>> # <file system>        <mount point>     <type>      <options>                   <dump> <pass>
>> # / was on /dev/sda5 during installation
>> UUID=4a5a9317-0b70-4796-a094-d61c01891c81 /    ext4  errors=remount-ro           0      1
>> # swap was on /dev/sda6 during installation
>> UUID=b4d7e5c0-207b-4a67-8b58-20523c509b87 none swap  sw                          0      0
>>
>> /dev/sr0               /media/cdrom0     udf,iso9660 user,noauto                 0      0
>>
>> #/dev/sysvg/homelv      /home             ext4        relatime,errors=remount-ro  0      1
>> /dev/sysvg/optlv       /opt              ext4        relatime,errors=remount-ro  0      1
>>
>> /dev/data1vg/homelv    /home             ext4        relatime,errors=remount-ro  0      2
>> /dev/data1vg/wwwlv     /www              ext4        relatime,errors=remount-ro  0      2
>> /dev/data1vg/baseslv   /bases            ext4        relatime,errors=remount-ro  0      2
>> /dev/data1vg/photoslv  /photos           ext4        relatime,errors=remount-ro  0      2
>> /dev/data1vg/videoslv  /videos           ext4        relatime,errors=remount-ro  0      2
>> /dev/data1vg/vboxlv    /vbox             ext4        relatime,errors=remount-ro  0      2
>> /dev/data1vg/graveurlv /graveur          ext4        relatime,errors=remount-ro  0      2
>>
>> # /dev/data0vg/homelv    /data0vg/home     ext4        relatime,errors=remount-ro  0      2
>> # /dev/data0vg/wwwlv     /data0vg/www      ext4        relatime,errors=remount-ro  0      2
>> # /dev/data0vg/baseslv   /data0vg/bases    ext4        relatime,errors=remount-ro  0      2
>> # /dev/data0vg/photoslv  /data0vg/photos   ext4        relatime,errors=remount-ro  0      2
>> # /dev/data0vg/videoslv  /data0vg/videos   ext4        relatime,errors=remount-ro  0      2
>> # /dev/data0vg/vboxlv    /data0vg/vbox     ext4        relatime,errors=remount-ro  0      2
>>
>> # /dev/data2vg/homelv    /data2vg/home     ext4        relatime,errors=remount-ro  0      2
>> # /dev/data2vg/wwwlv     /data2vg/www      ext4        relatime,errors=remount-ro  0      2
>> # /dev/data2vg/baseslv   /data2vg/bases    ext4        relatime,errors=remount-ro  0      2
>> # /dev/data2vg/photoslv  /data2vg/photos   ext4        relatime,errors=remount-ro  0      2
>> # /dev/data2vg/videoslv  /data2vg/videos   ext4        relatime,errors=remount-ro  0      2
>> # /dev/data2vg/vboxlv    /data2vg/vbox     ext4        relatime,errors=remount-ro  0      2
>> -----------------------------------
>> Your mountlist will look like this:
>> -----------------------------------
>> INFO: Analyzing LVM...
>> DEVICE          MOUNTPOINT      FORMAT          SIZE MB       LABEL/UUID    
>> ------          ----------      ------          -------       ----------    
>> INFO: Examining /dev/sdb1 (mount=lvm fmt=lvm psz=976761560)
>> /dev/sdb1       lvm             lvm              953868 c9qZKK-bpqn-sY7P-fWH2-SBlo-YsXS-udCgP7
>> INFO: Examining /dev/sda7 (mount=lvm fmt=lvm psz=99741696)
>> /dev/sda7       lvm             lvm               97404 yuL0j7-wJtb-ANiO-Omxi-AuEE-wCkJ-pfhEWi
>> INFO: Examining /dev/sda5 (mount=/ fmt=ext4 psz=97659103)
>> /dev/sda5       /               ext4              95370 4a5a9317-0b70-4796-a094-d61c01891c81
>> INFO: Examining /dev/sda6 (mount=swap fmt=swap psz=979928)
>> /dev/sda6       swap            swap                956 b4d7e5c0-207b-4a67-8b58-20523c509b87
>> INFO: Examining /dev/sysvg/optlv (mount=/opt fmt=ext4 psz=lvm)
>> /dev/sysvg/optlv /opt            ext4                lvm f1c4b976-0101-47ac-9ff8-c5a9e567553b
>> INFO: Examining /dev/data1vg/homelv (mount=/home fmt=ext4 psz=lvm)
>> /dev/data1vg/homelv /home           ext4                lvm e063df74-3fff-45ac-927d-bc6a60bd2970
>> INFO: Examining /dev/data1vg/wwwlv (mount=/www fmt=ext4 psz=lvm)
>> /dev/data1vg/wwwlv /www            ext4                lvm 7942603b-20c8-483a-ab36-98ee20ab7700
>> INFO: Examining /dev/data1vg/baseslv (mount=/bases fmt=ext4 psz=lvm)
>> /dev/data1vg/baseslv /bases          ext4                lvm 09f40cc9-fc3b-4205-a466-df38e5774a59
>> INFO: Examining /dev/data1vg/photoslv (mount=/photos fmt=ext4 psz=lvm)
>> /dev/data1vg/photoslv /photos         ext4                lvm 11ff707f-da12-46a3-9218-87fcf38ddc2f
>> INFO: Examining /dev/data1vg/videoslv (mount=/videos fmt=ext4 psz=lvm)
>> /dev/data1vg/videoslv /videos         ext4                lvm 11e0f5ef-75e4-4b7b-b34e-c9112b731f57
>> INFO: Examining /dev/data1vg/vboxlv (mount=/vbox fmt=ext4 psz=lvm)
>> /dev/data1vg/vboxlv /vbox           ext4                lvm 69e8fcf6-9518-4c3c-9052-53096c873cc4
>> INFO: Examining /dev/data1vg/graveurlv (mount=/graveur fmt=ext4 psz=lvm)
>> /dev/data1vg/graveurlv /graveur        ext4                lvm a5d30c9b-d333-46a3-8c28-ef2c4c1d9185
>> -----------------------------------
>> Mindi 3.0.0-r3332 is exiting
>> End date : lundi 19 janvier 2015, 22:16:59 (UTC+0100)
>
>> INFO: Time started: Mon Jan 19 22:16:43 2015
>>
>> DBG2: [TH=22705] libmondo-tools.c->setup_tmpdir#715: bkpinfo->tmpdir is being set to /tmp/mondo.tmp.4v41Vd
>> DBG2: [TH=22705] libmondo-tools.c->setup_scratchdir#736: Purging old scratchdir /mondo.scratch.*
>> DBG2: [TH=22705] libmondo-tools.c->setup_scratchdir#757: bkpinfo->scratchdir is being set to /tmp/mondo.scratch.3mNp4N
>> INFO: root is mounted at /dev/disk/by-uuid/aa9317-0b70-4796-a094-d61c01891c81
>>
>> INFO: That doesn't mean /dev/disk/by-uuid/aa9317-0b70-4796-a094-d61c01891c81 is the root partition. It's just a debugging message. Relax. It's part of am_I_in_disaster_recovery_mode().
>> DBG1: [TH=22705] libmondo-devices.c->am_I_in_disaster_recovery_mode#163: Is this a ramdisk? result = FALSE
>> INFO: running: dmesg -n1 > /tmp/mondo.tmp.4v41Vd/mondo-run-prog-thing.tmp 2> /tmp/mondo.tmp.4v41Vd/mondo-run-prog-thing.err
>> INFO: --------------------------------start of output-----------------------------
>> INFO: --------------------------------end of output------------------------------
>> INFO: ...ran just fine. :-)
>> INFO: Mondo Archive v3.2.0-r3332 --- http://www.mondorescue.org
>> INFO: running x86_64 binaries
>> INFO: running on x86_64 architecture
>> INFO: -----------------------------------------------------------
>> INFO: NB: Mondo logs almost everything, so don't panic if you see
>> INFO: some error messages.  Please read them carefully before you
>> INFO: decide to break out in a cold sweat.    Despite (or perhaps
>> INFO: because of) the wealth of messages. some users are inclined
>> INFO: to stop reading this log. If Mondo stopped for some reason,
>> INFO: chances are it's detailed here.  More than likely there's a
>> INFO: message at the very end of this log that will tell you what
>> INFO: is wrong. Please read it!                          -Devteam
>> INFO: -----------------------------------------------------------
>> INFO: Zero...
>> DBG1: [Main] mondoarchive.c->welcome_to_mondoarchive#96: One...
>> DBG2: [Main] mondoarchive.c->welcome_to_mondoarchive#97: Two...
>> DBG3: [Main] mondoarchive.c->welcome_to_mondoarchive#98: Three...
>> DBG4: [Main] mondoarchive.c->welcome_to_mondoarchive#99: Four...
>> DBG2: [Main] mondoarchive.c->distro_specific_kludges_at_start_of_mondoarchive#114: Unmounting old ramdisks if necessary
>> INFO: running: mount | grep cdrom | grep super > /tmp/mondo.tmp.4v41Vd/mondo-run-prog-thing.tmp 2> /tmp/mondo.tmp.4v41Vd/mondo-run-prog-thing.err
>> INFO: --------------------------------start of output-----------------------------
>> INFO: --------------------------------end of output------------------------------
>> INFO: ...ran with res=256
>> INFO: running: mount | grep floppy | grep super > /tmp/mondo.tmp.4v41Vd/mondo-run-prog-thing.tmp 2> /tmp/mondo.tmp.4v41Vd/mondo-run-prog-thing.err
>> INFO: --------------------------------start of output-----------------------------
>> INFO: --------------------------------end of output------------------------------
>> INFO: ...ran with res=256
>> DBG1: [Main] libmondo-tools.c->mount_boot_if_necessary#1155: Started sub
>> DBG4: [Main] libmondo-tools.c->mount_boot_if_necessary#1156: About to set g_boot_mountpt[0] to '\0'
>> DBG4: [Main] libmondo-tools.c->mount_boot_if_necessary#1158: Done. Great. Seeting command to something
>> DBG4: [Main] libmondo-tools.c->mount_boot_if_necessary#1160: Cool. Command = 'grep -v ":" /etc/fstab | grep -vE '^#.*$' | grep -E "[ ]/boot[ ]" | tr -s ' ' ' ' | cut -f1 | head -n1'
>> DBG4: [Main] libmondo-tools.c->mount_boot_if_necessary#1164: tmp = ''
>> DBG2: [Main] libmondo-tools.c->mount_boot_if_necessary#1165: /boot is at  according to /etc/fstab
>> DBG3: [Main] libmondo-tools.c->mount_boot_if_necessary#1182: command = mount | grep -E '^'
>> DBG1: [Main] libmondo-tools.c->mount_boot_if_necessary#1205: Ended sub
>> DBG1: [Main] libmondo-tools.c->get_kernel_version#245: g_kernel_version = 3.200000
>> INFO: running: rm -Rf /var/cache/mondo/changed.files* > /tmp/mondo.tmp.4v41Vd/mondo-run-prog-thing.tmp 2> /tmp/mondo.tmp.4v41Vd/mondo-run-prog-thing.err
>> INFO: --------------------------------start of output-----------------------------
>> INFO: --------------------------------end of output------------------------------
>> INFO: ...ran just fine. :-)
>> INFO: Checking sanity of your Linux distribution
>> INFO: running: grep ramdisk /proc/devices > /tmp/mondo.tmp.4v41Vd/mondo-run-prog-thing.tmp 2> /tmp/mondo.tmp.4v41Vd/mondo-run-prog-thing.err
>> INFO: --------------------------------start of output-----------------------------
>> INFO: 1 ramdisk
>> INFO: --------------------------------end of output------------------------------
>> INFO: ...ran just fine. :-)
>> INFO: running: mount | grep -Ew 'vfat|fat|dos' | grep -vE "/dev/fd|nexdisk" > /tmp/mondo.tmp.4v41Vd/mondo-run-prog-thing.tmp 2> /tmp/mondo.tmp.4v41Vd/mondo-run-prog-thing.err
>> INFO: --------------------------------start of output-----------------------------
>> INFO: --------------------------------end of output------------------------------
>> INFO: ...ran with res=256
>> DBG4: [Main] libmondo-files.c->find_home_of_exe#349: find_home_of_exe --- Found cmp at /usr/bin/cmp
>> INFO: running: mindi -V > /tmp/mondo.tmp.4v41Vd/mondo-run-prog-thing.tmp 2> /tmp/mondo.tmp.4v41Vd/mondo-run-prog-thing.err
>> INFO: --------------------------------start of output-----------------------------
>> INFO: Mindi v3.0.0-r3332
>> INFO: Le disque /dev/mapper/data1vg-photoslv ne contient pas une table de partitions valable
>> INFO: Le disque /dev/mapper/data1vg-videoslv ne contient pas une table de partitions valable
>> INFO: Le disque /dev/mapper/data1vg-homelv ne contient pas une table de partitions valable
>> INFO: Le disque /dev/mapper/data1vg-graveurlv ne contient pas une table de partitions valable
>> INFO: Le disque /dev/mapper/data1vg-wwwlv ne contient pas une table de partitions valable
>> INFO: Le disque /dev/mapper/data1vg-baseslv ne contient pas une table de partitions valable
>> INFO: Le disque /dev/mapper/data1vg-vboxlv ne contient pas une table de partitions valable
>> INFO: Le disque /dev/mapper/sysvg-optlv ne contient pas une table de partitions valable
>> INFO: --------------------------------end of output------------------------------
>> INFO: ...ran just fine. :-)
>> INFO: running: parted2fdisk -l 2>/dev/null | grep -i raid > /tmp/mondo.tmp.4v41Vd/mondo-run-prog-thing.tmp 2> /tmp/mondo.tmp.4v41Vd/mondo-run-prog-thing.err
>> INFO: --------------------------------start of output-----------------------------
>> INFO: --------------------------------end of output------------------------------
>> INFO: ...ran with res=256
>> INFO: Done.
>> DBG1: [Main] libmondo-cli.c->process_switches#181: Loglevel forced to 99
>> DBG20: [Main] libmondo-files.c->does_file_exist#188: /usr/bin/afio exists
>> DBG4: [Main] libmondo-files.c->find_home_of_exe#349: find_home_of_exe --- Found afio at /usr/bin/afio
>
>> ------------------------------------------------------------------------------
>> New Year. New Location. New Benefits. New Data Center in Ashburn, VA.
>> GigeNET is offering a free month of service with a new server in Ashburn.
>> Choose from 2 high performing configs, both with 100TB of bandwidth.
>> Higher redundancy.Lower latency.Increased capacity.Completely compliant.
>> http://p.sf.net/sfu/gigenet
>
>> _______________________________________________
>> Mondo-devel mailing list
>> [hidden email]
>> https://lists.sourceforge.net/lists/listinfo/mondo-devel
>
>


--
         Philippe Lefèvre - PGP : 7552AC04
Adoptez un pingouin au lieu de jeter de l'argent par la fenêtre

------------------------------------------------------------------------------
Dive into the World of Parallel Programming. The Go Parallel Website,
sponsored by Intel and developed in partnership with Slashdot Media, is your
hub for all things parallel software development, from weekly thought
leadership blogs to news, videos, case studies, tutorials and more. Take a
look and join the conversation now. http://goparallel.sourceforge.net/
_______________________________________________
Mondo-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/mondo-devel
Reply | Threaded
Open this post in threaded view
|

Re: [Mondo-devel] Segmentation error running mondoarchive v3.2.0-r3332

Philippe Lefevre
Hello list,

I did again some tries with mondo 3.2.0
Right: without -I option it works.

I reran it from compiled sources but this time I also had the same
trouble with it and was not able to get the error.

I tried to understand what happen with this option and I believe it is
linked to the pointer bkpinfo->include_paths which is empty in
libmondo-cli.c:236
We can see that flag_val['I'] is well setted to the arg value and
flag_set['I'] is true in process_switches()

Sorry, I must stop now and I'm afraid I will not have time those next
days to grab into it again (may be next we ??) but I hope these traces
may help.

Please find attached some gdb steps.

Kind regards,
Philippe


Le 26/01/2015 22:10, Philippe Lefevre a écrit :

>
> Great !
>
> Many thanks for your help and reply Bruno.
>
> Next week-end I'm going to reinstall 3.2.0 and supress -I option and see
> what happen.
>
> One thing is strange anyway: in my tests after a mondoarchive
> compilation, (pls, see my email dated on 17th january) I ran 3.2.0 with
> -I option without any issue. The sigsegv was repructible when
> mondoarchive was installed by the deb package ...
>
> I used :
> [phlsys]root:/home/phl/mondo-3.2.0# gdb -args mondoarchive -D -OV -i -N
> -G -s 780M -p sys-D7.7-diff_150105212200 -T /graveur -S /graveur -d
> /graveur -I "/|/|/opt/Zuma" -E
> "/bases/sybase|/graveur|/home|/opt|/photos|/quemu|/Sauvegardes|/var/crash|/var/backups|/var/log|/var/mail|/var/spool|/vbox|/videos|/www"
>
> and:
>  ....
>  Data archived OK.
>  Mondoarchive ran OK.
>  See /var/log/mondoarchive.log for details of backup run.
>  Execution run ended; result=0
>  Type 'less /var/log/mondoarchive.log' to see the output log [Inferior 1
> (process 19382) exited normally]
>  (gdb) quit
>
>
> I'll let you know.
> Kind regards,
> Philippe
>
>
>
> Le 26/01/2015 01:09, Bruno Cornec a écrit :
>> Hello Philippe,
>>
>> This is now fixed as described in BR:
>> http://trac.mondorescue.org/ticket/764#comment:2
>>
>> Bruno.
>>
>> Philippe Lefevre said on Mon, Jan 19, 2015 at 10:34:24PM +0100:
>>
>>> Hello Gaetagno,
>>>
>>> Regarding the two slashes, as I said, I used the same syntax to get into
>>> the same bug situation.
>>>
>>>
>>> I did a try with only one / in the -I option and got the same
>>> segmentation violation exception.
>>>
>>>
>>> Mindi launched alone as your example and it ran fine and the iso file
>>> successfully built.
>>> Please find attached the mindi.log file.
>>>
>>> [phlsys]root:/home/phl/Devel/mondo# ls -al /var/cache/mindi/mindi.iso
>>> -rw-r----- 1 root root 98721792 janv. 19 22:09 /var/cache/mindi/mindi.iso
>>>
>>>
>>>
>>> Ran mondoarchive with -K99 option crashed again with the sigsegv signal.
>>> Please find attached the mondoarchive.log file.
>>> Unfortunately, I'm afraid it is not so verbose than we would ...
>>> This time, the log ends with :
>>>
>>> DBG1: [Main] libmondo-cli.c->process_switches#181: Loglevel forced to 99
>>> DBG20: [Main] libmondo-files.c->does_file_exist#188: /usr/bin/afio exists
>>> DBG4: [Main] libmondo-files.c->find_home_of_exe#349: find_home_of_exe
>>> --- Found afio at /usr/bin/afio
>>>
>>>
>>>
>>> Running mondo without - E option crashed in the same way and with same
>>> mondoarchive.log file.
>>> [phlsys]root:/home/phl/Devel/mondo# /usr/sbin/mondoarchive -K99 -D -OV
>>> -i -N -G -s 780M -p sys-D7.7-diff_150105212200 -T /graveur -S /graveur
>>> -d /graveur -I "/opt/zuma"
>>> See /var/log/mondoarchive.log for details of backup run.
>>> Checking sanity of your Linux distribution
>>> Done.
>>> Erreur de segmentation
>>>
>>>
>>> Thank you for your time Gaetagno.
>>> Kind regards,
>>> Philippe
>>>
>>>
>>>
>>> Le 19/01/2015 12:17, Gattegno, Victor (GSD CSC / GCC) a écrit :
>>>> Hi Philippe,
>>>>
>>>> You used again two time "/"  in the include :
>>>> -I "/|/|/opt/Zuma"
>>>>
>>>> Your mondorachive.log file ends with :
>>>> DBG4: [Main] libmondo-files.c->find_home_of_exe#349: find_home_of_exe --- Found afio at /usr/bin/afio
>>>>
>>>> You can try a few things :
>>>>
>>>> Try mindi alone :
>>>> # mindi
>>>> Do you want to use your own kernel to build the boot disk ([y]/n) ? y
>>>>
>>>> Try your mondoarchive command without -E, with only -I, and choice only one directory, example :
>>>> -I "/opt/Zuma"
>>>>
>>>> Try your mondoarchive command with more debug, example with -K 5, or with -K 99 (which is full debug mode, be aware that the log file could grow from 200 Kb to 50 Mb).
>>>>
>>>> Rgds,
>>>> Victor
>>>>
>>>> -----Original Message-----
>>>> From: Philippe Lefevre [mailto:[hidden email]]
>>>> Sent: samedi 17 janvier 2015 20:14
>>>> To: Mondo mailing list
>>>> Subject: Re: [Mondo-devel] Segmentation error running mondoarchive v3.2.0-r3332
>>>>
>>>> Hello list,
>>>>
>>>> sorry Gaetagno for the delay, I was not able to find some time long enought to go back into my issue.
>>>>
>>>> I did it today (without removing the two slashes in order to be in the same situation) and .... what I compiled worked fine with what I have compiled. (I noticed the -v bug, thanks  ;)  )
>>>>
>>>> Run mondoarchive via dbg:
>>>> [phlsys]root:/home/phl/mondo-3.2.0# gdb -args mondoarchive -D -OV -i -N -G -s 780M -p sys-D7.7-diff_150105212200 -T /graveur -S /graveur -d /graveur -I "/|/|/opt/Zuma" -E "/bases/sybase|/graveur|/home|/opt|/photos|/quemu|/Sauvegardes|/var/crash|/var/backups|/var/log|/var/mail|/var/spool|/vbox|/videos|/www"
>>>>
>>>> and:
>>>> ....
>>>> Data archived OK.
>>>> Mondoarchive ran OK.
>>>> See /var/log/mondoarchive.log for details of backup run.
>>>> Execution run ended; result=0
>>>> Type 'less /var/log/mondoarchive.log' to see the output log [Inferior 1 (process 19382) exited normally]
>>>> (gdb) quit
>>>>
>>>>
>>>> So I reinstalled the official debian package:
>>>>
>>>> Sélection du paquet libmondorescue-perl précédemment désélectionné.
>>>> (Lecture de la base de données... 279208 fichiers et répertoires déjà
>>>> installés.)
>>>> Dépaquetage de libmondorescue-perl (à partir de
>>>> .../libmondorescue-perl_3.2.0-1_all.deb) ...
>>>> Préparation du remplacement de mindi-busybox 1.18.5-3 (en utilisant
>>>> .../mindi-busybox_1.21.1-1_amd64.deb) ...
>>>> Dépaquetage de la mise à jour de mindi-busybox ...
>>>> Préparation du remplacement de mindi 2.1.7-1 (en utilisant
>>>> .../mindi_3.0.0-1_amd64.deb) ...
>>>> Dépaquetage de la mise à jour de mindi ...
>>>> Préparation du remplacement de mondo 3.0.4-1 (en utilisant
>>>> .../mondo_3.2.0-1_amd64.deb) ...
>>>> Dépaquetage de la mise à jour de mondo ...
>>>> Traitement des actions différées (« triggers ») pour « man-db »...
>>>> Paramétrage de libmondorescue-perl (3.2.0-1) ...
>>>> Paramétrage de mindi-busybox (1.21.1-1) ...
>>>> Paramétrage de mindi (3.0.0-1) ...
>>>> Installation de la nouvelle version du fichier de configuration /etc/mindi/deplist.d/minimal.conf ...
>>>> Installation de la nouvelle version du fichier de configuration /etc/mindi/deplist.d/udev.conf ...
>>>> Installation de la nouvelle version du fichier de configuration /etc/mindi/deplist.d/ProLiant.conf ...
>>>> Installation de la nouvelle version du fichier de configuration /etc/mindi/deplist.d/base.conf ...
>>>> Installation de la nouvelle version du fichier de configuration /etc/mindi/deplist.d/lvm.conf ...
>>>> Installation de la nouvelle version du fichier de configuration /etc/mindi/perl-scripts ...
>>>> Paramétrage de mondo (3.2.0-1) ...
>>>>
>>>>
>>>> but launched in the same way, it crashed again with a segmentation error:
>>>>
>>>> [phlsys]root:/home/phl/telechargements/mondo-3.2.0# mondoarchive -D -OV -i -N -G -s 780M -p sys-D7.7-diff_150105212200 -T /graveur -S /graveur -d /graveur -I "/|/|/opt/Zuma" -E "/bases/sybase|/graveur|/home|/opt|/photos|/quemu|/Sauvegardes|/var/crash|/var/backups|/var/log|/var/mail|/var/spool|/vbox|/videos|/www"
>>>> See /var/log/mondoarchive.log for details of backup run.
>>>> Checking sanity of your Linux distribution Done.
>>>> Erreur de segmentation
>>>>
>>>>
>>>>
>>>> Please find attached the relevant mondoarchive.log file.
>>>> It seems to be stopped before logging something about the fault.
>>>> I franckly don't know what I could do more.
>>>> Do you have an idea about what I could do to explore deeper this issue ?
>>>> Something might be going wrong into the deb pkg ???
>>>> I got it with apt using:
>>>>    deb ftp://ftp.mondorescue.org//debian 7 contrib
>>>>
>>>>
>>>> Thanks for your help.
>>>> Regards,
>>>> Philippe
>>>>
>>>>
>>>>
>>>>
>>>>
>>>> Le 06/01/2015 17:28, Gattegno, Victor (GSD CSC / GCC) a écrit :
>>>>> Hello Philippe,
>>>>>
>>>>> From mondoarchive man : " When using the -I option with the -E option, the -E content should be subdirectories of those mentioned in the -I only, as -I takes precedence."
>>>>>
>>>>> But if your -I and -E combination works it's ok (check if /opt/zuma and /opt/calibre are well backuped and restored).
>>>>>
>>>>> Regards,
>>>>> Victor
>>>>>
>>>>> -----Original Message-----
>>>>> From: Philippe Lefevre [mailto:[hidden email]]
>>>>> Sent: lundi 5 janvier 2015 21:42
>>>>> To: [hidden email]
>>>>> Subject: Re: [Mondo-devel] Segmentation error running mondoarchive
>>>>> v3.2.0-r3332
>>>>>
>>>>> Thanks for your help and reply Victor,
>>>>>
>>>>> I should be able to replay with all of that before the end of the week and let you know.
>>>>> Regarding the double /, it is due to my shell script which build the final request. I will also do a try without it.
>>>>>
>>>>> I believe I couldn't remove -I flag as in the exclude part there is /opt and I want to include only 2 directories /opt/zuma and /opt/calibre. At least, I should use -I "/opt/calibre|/opt/Zuma" right?
>>>>>
>>>>> PS: my system backup is run by root and ulimit is setted unlimited:
>>>>>
>>>>> # ulimit -a
>>>>> core file size          (blocks, -c) 0
>>>>> data seg size           (kbytes, -d) unlimited
>>>>> scheduling priority             (-e) 0
>>>>> file size               (blocks, -f) unlimited
>>>>> pending signals                 (-i) 31106
>>>>> max locked memory       (kbytes, -l) 64
>>>>> max memory size         (kbytes, -m) unlimited
>>>>> open files                      (-n) 1024
>>>>> pipe size            (512 bytes, -p) 8
>>>>> POSIX message queues     (bytes, -q) 819200
>>>>> real-time priority              (-r) 0
>>>>> stack size              (kbytes, -s) 8192
>>>>> cpu time               (seconds, -t) unlimited
>>>>> max user processes              (-u) 31106
>>>>> virtual memory          (kbytes, -v) unlimited
>>>>> file locks                      (-x) unlimited
>>>>>
>>>>>
>>>>> Rgds,
>>>>> Philippe
>>>>>
>>>>>
>>>>> Le 05/01/2015 16:32, Gattegno, Victor (GSD CSC / GCC) a écrit :
>>>>>> Hello Philippe,
>>>>>>
>>>>>> Good gdb work, but don't focus on "mondoarchive -v" segmentation fault, it's a known failing bug. It's better to debug mondoarchive with the options that you use.
>>>>>>
>>>>>>  In your 27/12/2014 test and post:
>>>>>>  - did you posted too the associated /var/log/mondoarchive.log (compressed) ?
>>>>>>  - you used -I (with / included twice) and -E options, it's better to use only -E option.
>>>>>>
>>>>>> What's the result of "ulimit -a" on your Debian ?
>>>>>>
>>>>>> I wish to you - and to all this mailig-list users - a nice year 2015.
>>>>>>
>>>>>> Rgds,
>>>>>> Victor
>>>>>>
>>>>>> -----Original Message-----
>>>>>> From: Philippe Lefevre [mailto:[hidden email]]
>>>>>> Sent: samedi 3 janvier 2015 14:32
>>>>>> To: [hidden email]
>>>>>> Subject: Re: [Mondo-devel] Segmentation error running mondoarchive
>>>>>> v3.2.0-r3332
>>>>>>
>>>>>> Hi list,
>>>>>>
>>>>>> Some more information about my issue.
>>>>>>
>>>>>> I can confirm that in my case it is related to this new release as a I did a downgrade and successfully built a new full backup.
>>>>>>
>>>>>> I uninstalled and purged
>>>>>>   libmondorescue-perl_3.2.0-1_all.deb
>>>>>>   mindi-busybox_1.21.1-1_amd64.deb
>>>>>>   mindi_3.0.0-1_amd64.deb
>>>>>>   mondo_3.2.0-1_amd64.deb
>>>>>>
>>>>>> and reinstalled the previous version
>>>>>>   mindi-busybox 1.18.5-3
>>>>>>   mindi 2.1.7-1
>>>>>>   mondo 3.0.4-1
>>>>>>
>>>>>> I also compiled mondo 3.2.0 from sources and ran gdb against the simpliest command that raise the seg error. It shows :
>>>>>>
>>>>>> Starting program:
>>>>>> /home/phl/telechargements/mondo-3.2.0/src/mondoarchive/mondoarchive -v [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
>>>>>> mondoarchive v3.2.0-r3332
>>>>>> See man page for help
>>>>>>
>>>>>> Program received signal SIGSEGV, Segmentation fault.
>>>>>> 0x00007ffff76629aa in vfprintf () from
>>>>>> /lib/x86_64-linux-gnu/libc.so.6
>>>>>> (gdb) bt
>>>>>> #0  0x00007ffff76629aa in vfprintf () from
>>>>>> /lib/x86_64-linux-gnu/libc.so.6
>>>>>> #1  0x00007ffff7688fca in vasprintf () from
>>>>>> /lib/x86_64-linux-gnu/libc.so.6
>>>>>> #2  0x00000000004367c4 in mr_asprintf_int (strp=strp@entry=0x7fffffffe0d0, line=line@entry=258, file=file@entry=0x44187f "libmondo-fork.c",
>>>>>>     fmt=fmt@entry=0x441d38 "%s > %s/mondo-run-prog-thing.tmp 2>
>>>>>> %s/mondo-run-prog-thing.err") at mr_mem.c:62
>>>>>> #3  0x000000000041e0f0 in run_program_and_log_output
>>>>>> (program=program@entry=0x43c4b4 "umount -d /mnt/cdrom",
>>>>>> debug_level=debug_level@entry=0)
>>>>>>     at libmondo-fork.c:258
>>>>>> #4  0x000000000042ec19 in finish (signal=signal@entry=0) at
>>>>>> newt-specific.c:388
>>>>>> #5  0x0000000000403430 in main (argc=2, argv=0x7fffffffe668) at
>>>>>> mondoarchive.c:176
>>>>>> (gdb)
>>>>>>
>>>>>>
>>>>>> function code exerpt
>>>>>>
>>>>>>    56 void mr_asprintf_int(char **strp, int line, const char *file, const char *fmt, ...) {
>>>>>>    57
>>>>>>    58 int res = 0;
>>>>>>    59 va_list args;
>>>>>>    60
>>>>>>    61 va_start(args,fmt);
>>>>>>    62 res = vasprintf(strp, fmt, args);
>>>>>>    63 if (res == -1) {
>>>>>>    64 mr_msg_int(1,line,file,"Unable to alloc memory in
>>>>>> mr_asprintf\nExiting...");
>>>>>>    65 mr_exit(-1,"Unable to alloc memory in mr_asprintf");
>>>>>>    66 }
>>>>>>    67 va_end(args);
>>>>>>    68 }
>>>>>>
>>>>>>
>>>>>> Breakpoint 1, mr_asprintf_int (strp=strp@entry=0x7fffffffe0d0, line=line@entry=258, file=file@entry=0x44187f "libmondo-fork.c",
>>>>>>     fmt=fmt@entry=0x441d38 "%s > %s/mondo-run-prog-thing.tmp 2>
>>>>>> %s/mondo-run-prog-thing.err") at mr_mem.c:56
>>>>>> 56 void mr_asprintf_int(char **strp, int line, const char *file, const
>>>>>> char *fmt, ...) {
>>>>>> (gdb) s
>>>>>> 61 va_start(args,fmt);
>>>>>> (gdb) display fmt
>>>>>> 1: fmt = 0x441d38 "%s > %s/mondo-run-prog-thing.tmp 2> %s/mondo-run-prog-thing.err"
>>>>>> (gdb) display args
>>>>>> 2: args = {{gp_offset = 4158558940, fp_offset = 32767,
>>>>>> overflow_arg_area = 0x7ffff7fd5000, reg_save_area = 0x7ffff7ffd9d8}}
>>>>>> (gdb) s
>>>>>> 62 res = vasprintf(strp, fmt, args);
>>>>>> 2: args = {{gp_offset = 4158558940, fp_offset = 32767,
>>>>>> overflow_arg_area = 0x7ffff7fd5000, reg_save_area = 0x7ffff7ffd9d8}}
>>>>>> 1: fmt = 0x441d38 "%s > %s/mondo-run-prog-thing.tmp 2> %s/mondo-run-prog-thing.err"
>>>>>> (gdb) s
>>>>>> 61 va_start(args,fmt);
>>>>>> 2: args = {{gp_offset = 4158558940, fp_offset = 32767,
>>>>>> overflow_arg_area = 0x7ffff7fd5000, reg_save_area = 0x7ffff7ffd9d8}}
>>>>>> 1: fmt = 0x441d38 "%s > %s/mondo-run-prog-thing.tmp 2> %s/mondo-run-prog-thing.err"
>>>>>> (gdb) s
>>>>>> 62 res = vasprintf(strp, fmt, args);
>>>>>> 2: args = {{gp_offset = 32, fp_offset = 48, overflow_arg_area =
>>>>>> 0x7fffffffe0b0, reg_save_area = 0x7fffffffdfe0}}
>>>>>> 1: fmt = 0x441d38 "%s > %s/mondo-run-prog-thing.tmp 2> %s/mondo-run-prog-thing.err"
>>>>>> (gdb) display res
>>>>>> 3: res = 0
>>>>>> (gdb) s
>>>>>>
>>>>>> Program received signal SIGSEGV, Segmentation fault.
>>>>>> 0x00007ffff76629aa in vfprintf () from
>>>>>> /lib/x86_64-linux-gnu/libc.so.6
>>>>>> (gdb)
>>>>>>
>>>>>>
>>>>>> It seems there is an issue with mr_asprintf_int but sorry I don't feel strong enought to get more deeply into the mondo code and analyze it properly ...
>>>>>>
>>>>>> I hope this help ...
>>>>>>
>>>>>> Regards,
>>>>>> Philippe
>>>>>>
>>>>>>
>>>>>> Le 27/12/2014 11:17, [hidden email] a écrit :
>>>>>>> Hi all,
>>>>>>>
>>>>>>> it seems that something goes wrong with mondo I could link to the
>>>>>>> latest Debian version of MondoRescue.
>>>>>>>
>>>>>>> I updated my version last thursday and this morning (I have a
>>>>>>> differential backup launched every friday night and one full a
>>>>>>> month) it failed.
>>>>>>> Unfortunately there are no much relevant informations in logs.
>>>>>>>
>>>>>>> The errors raised is :
>>>>>>>
>>>>>>>     # mondoarchive -D -OV -i -N -G -s 780M -p sys-D7.7-diff_141227100000
>>>>>>>     -T /graveur -S /graveur -d
>>>>>>>     /media/sauvegardes/phlsys/D7.7/sys/141227100000 -I
>>>>>>>     "/|/|/opt/calibre|/opt/Zuma" -E
>>>>>>>     "/bases/sybase|/graveur|/home|/opt|/photos|/quemu|/Sauvegardes|/var/crash|/var/backups|/var/log|/var/mail|/var/spool|/vbox|/videos|/www"
>>>>>>>     See /var/log/mondoarchive.log for details of backup run.
>>>>>>>     Checking sanity of your Linux distribution
>>>>>>>     Done.
>>>>>>>     Erreur de segmentation                /* Segmentation error */
>>>>>>>
>>>>>>> Please find attached the log files that seems to find out an issue
>>>>>>> with LVM disks
>>>>>>>
>>>>>>>     INFO: Mindi v3.0.0-r3332
>>>>>>>     INFO: Le disque /dev/mapper/data1vg-photoslv ne contient pas une
>>>>>>>     table de partitions valable
>>>>>>>              /* there is no valid partition table in
>>>>>>>     /dev/mapper/data1vg-photoslv disk */
>>>>>>>
>>>>>>> I have no issues with my LVM disks. Please find on below my LVM
>>>>>>> disks configuration
>>>>>>>
>>>>>>>     lvm> vgs
>>>>>>>       VG      #PV #LV #SN Attr   VSize   VFree
>>>>>>>       data1vg   1   7   0 wz--n- 931,51g 504,60g
>>>>>>>       sysvg     1   1   0 wz--n-  95,12g  78,84g
>>>>>>>
>>>>>>>     lvm> lvs
>>>>>>>       LV        VG      Attr     LSize   Pool Origin Data%  Move Log
>>>>>>>     Copy%  Convert
>>>>>>>       baseslv   data1vg -wi-ao--  
>>>>>>>     1,86g                                          
>>>>>>>       graveurlv data1vg -wi-ao--
>>>>>>>     20,00g                                          
>>>>>>>       homelv    data1vg -wi-ao--
>>>>>>>     50,00g                                          
>>>>>>>       photoslv  data1vg -wi-ao--
>>>>>>>     70,00g                                          
>>>>>>>       vboxlv    data1vg -wi-ao--
>>>>>>>     130,39g                                          
>>>>>>>       videoslv  data1vg -wi-ao--
>>>>>>>     150,00g                                          
>>>>>>>       wwwlv     data1vg -wi-ao--  
>>>>>>>     4,66g                                          
>>>>>>>       optlv     sysvg   -wi-ao--  16,28g
>>>>>>>
>>>>>>>     lvm> lvscan
>>>>>>>       ACTIVE            '/dev/data1vg/photoslv' [70,00 GiB] inherit
>>>>>>>       ACTIVE            '/dev/data1vg/videoslv' [150,00 GiB] inherit
>>>>>>>       ACTIVE            '/dev/data1vg/homelv' [50,00 GiB] inherit
>>>>>>>       ACTIVE            '/dev/data1vg/graveurlv' [20,00 GiB] inherit
>>>>>>>       ACTIVE            '/dev/data1vg/wwwlv' [4,66 GiB] inherit
>>>>>>>       ACTIVE            '/dev/data1vg/baseslv' [1,86 GiB] inherit
>>>>>>>       ACTIVE            '/dev/data1vg/vboxlv' [130,39 GiB] inherit
>>>>>>>       ACTIVE            '/dev/sysvg/optlv' [16,28 GiB] inherit
>>>>>>>
>>>>>>>     root@phlsys:/home/phl/Scripts# df -h
>>>>>>>     Sys. fich.                                             Taille Util.
>>>>>>>     Dispo Uti% Monté sur
>>>>>>>     rootfs                                                    92G  
>>>>>>>     11G   77G  12% /
>>>>>>>     udev                                                      10M    
>>>>>>>     0   10M   0% /dev
>>>>>>>     tmpfs                                                    397M  968K
>>>>>>>     396M   1% /run
>>>>>>>     /dev/disk/by-uuid/4a5a9317-0b70-4796-a094-d61c01891c81    92G  
>>>>>>>     11G   77G  12% /
>>>>>>>     tmpfs                                                    5,0M     0
>>>>>>>     5,0M   0% /run/lock
>>>>>>>     tmpfs                                                    985M  324K
>>>>>>>     985M   1% /run/shm
>>>>>>>     /dev/mapper/sysvg-optlv                                   17G   15G
>>>>>>>     845M  95% /opt
>>>>>>>     /dev/mapper/data1vg-homelv                                50G   40G
>>>>>>>     7,2G  85% /home
>>>>>>>     /dev/mapper/data1vg-wwwlv                                4,6G  2,5G
>>>>>>>     1,9G  58% /www
>>>>>>>     /dev/mapper/data1vg-baseslv                              1,9G  720M
>>>>>>>     1,1G  41% /bases
>>>>>>>     /dev/mapper/data1vg-photoslv                              69G  
>>>>>>>     43G   23G  66% /photos
>>>>>>>     /dev/mapper/data1vg-videoslv                             148G
>>>>>>>     104G   37G  74% /videos
>>>>>>>     /dev/mapper/data1vg-vboxlv                               129G
>>>>>>>     100G   23G  82% /vbox
>>>>>>>     /dev/mapper/data1vg-graveurlv                             20G
>>>>>>>     8,1G   11G  44% /graveur
>>>>>>>
>>>>>>>
>>>>>>> The latest mondo upgrade dated of 25th of december was (it worked
>>>>>>> fine before this upgrade)
>>>>>>>
>>>>>>>     Start-Date: 2014-12-25  18:55:08
>>>>>>>     Commandline: /usr/sbin/synaptic
>>>>>>>     Install: libprojectbuilder-perl:amd64 (0.12.6-1, automatic),
>>>>>>>     libmondorescue-perl:amd64 (3.2.0-1, automatic)
>>>>>>>     Upgrade: mindi:amd64 (2.1.7-1, 3.0.0-1), mondo:amd64 (3.0.4-1,
>>>>>>>     3.2.0-1), mindi-busybox:amd64 (1.18.5-3, 1.21.1-1)
>>>>>>>     End-Date: 2014-12-25  18:55:31
>>>>>>>
>>>>>>> The Debian distro used is
>>>>>>>
>>>>>>>     root@phlsys:/home/phl/Scripts# uname -a
>>>>>>>     Linux phlsys 3.2.0-4-amd64 #1 SMP Debian 3.2.63-2+deb7u2 x86_64
>>>>>>>     GNU/Linux
>>>>>>>
>>>>>>> Anyone have an idea to try to debug this.
>>>>>>>
>>>>>>> Thanks for any help.
>>>>>>>
>>>>>>> By the way, I whish you all an happy new year 2015 with all the best
>>>>>>> in your lifes Kind regards, Philippe
>>>>>>>
>>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> ---------------------------------------------------------------------
>>>>>> -
>>>>>> -------- Dive into the World of Parallel Programming! The Go Parallel
>>>>>> Website, sponsored by Intel and developed in partnership with
>>>>>> Slashdot Media, is your hub for all things parallel software
>>>>>> development, from weekly thought leadership blogs to news, videos,
>>>>>> case studies, tutorials and more. Take a look and join the conversation now.
>>>>>> http://goparallel.sourceforge.net
>>>>>> _______________________________________________
>>>>>> Mondo-devel mailing list
>>>>>> [hidden email]
>>>>>> https://lists.sourceforge.net/lists/listinfo/mondo-devel
>>>>>> ---------------------------------------------------------------------
>>>>>> -
>>>>>> -------- Dive into the World of Parallel Programming! The Go Parallel
>>>>>> Website, sponsored by Intel and developed in partnership with
>>>>>> Slashdot Media, is your hub for all things parallel software
>>>>>> development, from weekly thought leadership blogs to news, videos,
>>>>>> case studies, tutorials and more. Take a look and join the conversation now.
>>>>>> http://goparallel.sourceforge.net
>>>>>> _______________________________________________
>>>>>> Mondo-devel mailing list
>>>>>> [hidden email]
>>>>>> https://lists.sourceforge.net/lists/listinfo/mondo-devel
>>>>>>
>>>>>
>>>>>
>>>>>
>>>>> ----------------------------------------------------------------------
>>>>> -------- Dive into the World of Parallel Programming! The Go Parallel
>>>>> Website, sponsored by Intel and developed in partnership with Slashdot
>>>>> Media, is your hub for all things parallel software development, from
>>>>> weekly thought leadership blogs to news, videos, case studies,
>>>>> tutorials and more. Take a look and join the conversation now.
>>>>> http://goparallel.sourceforge.net 
>>>>> _______________________________________________
>>>>> Mondo-devel mailing list
>>>>> [hidden email]
>>>>> https://lists.sourceforge.net/lists/listinfo/mondo-devel
>>>>> ----------------------------------------------------------------------
>>>>> -------- Dive into the World of Parallel Programming! The Go Parallel
>>>>> Website, sponsored by Intel and developed in partnership with Slashdot
>>>>> Media, is your hub for all things parallel software development, from
>>>>> weekly thought leadership blogs to news, videos, case studies,
>>>>> tutorials and more. Take a look and join the conversation now.
>>>>> http://goparallel.sourceforge.net 
>>>>> _______________________________________________
>>>>> Mondo-devel mailing list
>>>>> [hidden email]
>>>>> https://lists.sourceforge.net/lists/listinfo/mondo-devel
>>>>>
>>>>
>>>>
>>>> ------------------------------------------------------------------------------
>>>> New Year. New Location. New Benefits. New Data Center in Ashburn, VA.
>>>> GigeNET is offering a free month of service with a new server in Ashburn.
>>>> Choose from 2 high performing configs, both with 100TB of bandwidth.
>>>> Higher redundancy.Lower latency.Increased capacity.Completely compliant.
>>>> http://p.sf.net/sfu/gigenet
>>>> _______________________________________________
>>>> Mondo-devel mailing list
>>>> [hidden email]
>>>> https://lists.sourceforge.net/lists/listinfo/mondo-devel
>>>>
>>>
>>>
>>
>>> mindi v3.0.0-r3332
>>> x86_64 architecture detected
>>> mindi called with the following arguments:
>>> --makemountlist /tmp/mondo.tmp.4v41Vd/mountlist.txt.test
>>> Start date : lundi 19 janvier 2015, 22:16:43 (UTC+0100)
>>> -----------------------------
>>> MONDO_SHARE = /usr/share/mondo
>>> MINDI_LIB = /usr/lib/mindi
>>> MINDI_SBIN = /usr/sbin
>>> MINDI_CONF = /etc/mindi
>>> -----------------------------
>>>  Mindi configuration file    
>>> -----------------------------
>>> -----------------------------
>>> In Mindi
>>> --------
>>> EXTRA_SPACE = 120000
>>> BOOT_SIZE = 65600
>>> --------
>>> INFO: Found isolinux.bin at /usr/lib/syslinux/isolinux.bin
>>> INFO: LVM set to v2
>>> ----------
>>> mount result:
>>> -------------
>>> sysfs on /sys type sysfs (rw,nosuid,nodev,noexec,relatime)
>>> proc on /proc type proc (rw,nosuid,nodev,noexec,relatime)
>>> udev on /dev type devtmpfs (rw,relatime,size=10240k,nr_inodes=497709,mode=755)
>>> devpts on /dev/pts type devpts (rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000)
>>> tmpfs on /run type tmpfs (rw,nosuid,noexec,relatime,size=406288k,mode=755)
>>> /dev/disk/by-uuid/4a5a9317-0b70-4796-a094-d61c01891c81 on / type ext4 (rw,relatime,errors=remount-ro,user_xattr,barrier=1,data=ordered)
>>> tmpfs on /run/lock type tmpfs (rw,nosuid,nodev,noexec,relatime,size=5120k)
>>> tmpfs on /run/shm type tmpfs (rw,nosuid,nodev,noexec,relatime,size=1008560k)
>>> /dev/mapper/sysvg-optlv on /opt type ext4 (rw,relatime,errors=remount-ro,user_xattr,barrier=1,data=ordered)
>>> /dev/mapper/data1vg-homelv on /home type ext4 (rw,relatime,errors=remount-ro,user_xattr,barrier=1,data=ordered)
>>> /dev/mapper/data1vg-wwwlv on /www type ext4 (rw,relatime,errors=remount-ro,user_xattr,barrier=1,data=ordered)
>>> /dev/mapper/data1vg-baseslv on /bases type ext4 (rw,relatime,errors=remount-ro,user_xattr,barrier=1,data=ordered)
>>> /dev/mapper/data1vg-photoslv on /photos type ext4 (rw,relatime,errors=remount-ro,user_xattr,barrier=1,data=ordered)
>>> /dev/mapper/data1vg-videoslv on /videos type ext4 (rw,relatime,errors=remount-ro,user_xattr,barrier=1,data=ordered)
>>> /dev/mapper/data1vg-vboxlv on /vbox type ext4 (rw,relatime,errors=remount-ro,user_xattr,barrier=1,data=ordered)
>>> /dev/mapper/data1vg-graveurlv on /graveur type ext4 (rw,relatime,errors=remount-ro,user_xattr,barrier=1,data=ordered)
>>> rpc_pipefs on /var/lib/nfs/rpc_pipefs type rpc_pipefs (rw,relatime)
>>> binfmt_misc on /proc/sys/fs/binfmt_misc type binfmt_misc (rw,nosuid,nodev,noexec,relatime)
>>> No file /etc/raidtab
>>> -------------
>>> No file /etc/mdadm.conf
>>> -------------
>>> cat /proc/cmdline
>>> -------------
>>> BOOT_IMAGE=/boot/vmlinuz-3.2.0-4-amd64 root=UUID=4a5a9317-0b70-4796-a094-d61c01891c81 ro quiet
>>> -------------
>>> cat /proc/swaps:
>>> -------------
>>> Filename Type Size Used Priority
>>> /dev/sda6                               partition 979928 11992 -1
>>> -------------
>>> cat /proc/mdstat:
>>> -------------
>>> Personalities : [linear] [raid0] [raid1] [raid6] [raid5] [raid4]
>>> unused devices: <none>
>>> -------------
>>> cat /proc/partitions:
>>> -------------
>>> major minor  #blocks  name
>>>
>>>    8        0  312571224 sda
>>>    8        1      56196 sda1
>>>    8        2   10485760 sda2
>>>    8        3  103643080 sda3
>>>    8        4          1 sda4
>>>    8        5   97659103 sda5
>>>    8        6     979933 sda6
>>>    8        7   99741696 sda7
>>>   11        0    1048575 sr0
>>>    8       16  976762584 sdb
>>>    8       17  976761560 sdb1
>>>  253        0   73400320 dm-0
>>>  253        1  157286400 dm-1
>>>  253        2   52428800 dm-2
>>>  253        3   20971520 dm-3
>>>  253        4    4886528 dm-4
>>>  253        5    1953792 dm-5
>>>  253        6  136720384 dm-6
>>>  253        7   17072128 dm-7
>>> -------------
>>> cat /proc/filesystems:
>>> -------------
>>> nodev sysfs
>>> nodev rootfs
>>> nodev bdev
>>> nodev proc
>>> nodev cgroup
>>> nodev cpuset
>>> nodev tmpfs
>>> nodev devtmpfs
>>> nodev debugfs
>>> nodev securityfs
>>> nodev sockfs
>>> nodev pipefs
>>> nodev anon_inodefs
>>> nodev devpts
>>> nodev ramfs
>>> nodev hugetlbfs
>>> nodev pstore
>>> nodev mqueue
>>> nodev usbfs
>>> ext4
>>> nodev ecryptfs
>>> nodev rpc_pipefs
>>> nodev nfs
>>> nodev nfs4
>>> nodev nfsd
>>> nodev binfmt_misc
>>> msdos
>>> vfat
>>> iso9660
>>> ext2
>>> -------------
>>> lsmod result:
>>> -------------
>>> Module                  Size  Used by
>>> nls_utf8               12456  0
>>> nls_cp437              16553  0
>>> ext2                   59231  0
>>> raid456                48453  0
>>> async_raid6_recov      12574  1 raid456
>>> async_memcpy           12387  2 async_raid6_recov,raid456
>>> async_pq               12605  2 async_raid6_recov,raid456
>>> raid6_pq               82624  2 async_pq,async_raid6_recov
>>> async_xor              12422  3 async_pq,async_raid6_recov,raid456
>>> xor                    12605  1 async_xor
>>> async_tx               12604  5 async_xor,async_pq,async_memcpy,async_raid6_recov,raid456
>>> raid1                  30714  0
>>> raid0                  12904  0
>>> linear                 12735  0
>>> isofs                  35173  0
>>> brd                    12772  0
>>> vfat                   17316  0
>>> msdos                  17077  0
>>> fat                    45642  2 msdos,vfat
>>> pci_stub               12429  1
>>> vboxpci                19096  0
>>> vboxnetadp             25443  0
>>> vboxnetflt             23657  0
>>> vboxdrv               304550  3 vboxnetflt,vboxnetadp,vboxpci
>>> nfnetlink_log          17212  0
>>> nfnetlink              12906  1 nfnetlink_log
>>> parport_pc             22364  0
>>> ppdev                  12763  0
>>> lp                     17149  0
>>> parport                31858  3 lp,ppdev,parport_pc
>>> ip6t_REJECT            12512  2
>>> xt_multiport           12548  2
>>> xt_conntrack           12681  18
>>> iptable_nat            12928  0
>>> binfmt_misc            12957  1
>>> iptable_mangle         12536  0
>>> nfsd                  216181  2
>>> nfs                   308353  0
>>> nfs_acl                12511  2 nfs,nfsd
>>> auth_rpcgss            37143  2 nfs,nfsd
>>> fscache                36739  1 nfs
>>> lockd                  67306  2 nfs,nfsd
>>> sunrpc                173730  6 lockd,auth_rpcgss,nfs_acl,nfs,nfsd
>>> ip6t_LOG               12609  4
>>> xt_hl                  12449  6
>>> ip6t_rt                12499  3
>>> nf_conntrack_ipv6      13316  7
>>> nf_defrag_ipv6         12832  1 nf_conntrack_ipv6
>>> ipt_REJECT             12502  1
>>> ipt_LOG                12605  12
>>> xt_limit               12638  19
>>> xt_tcpudp              12570  62
>>> xt_addrtype            12557  4
>>> xt_state               12503  21
>>> ip6table_filter        12540  1
>>> ip6_tables             22175  3 ip6table_filter,ip6t_rt,ip6t_LOG
>>> nf_conntrack_netbios_ns    12445  0
>>> nf_conntrack_broadcast    12365  1 nf_conntrack_netbios_ns
>>> nf_nat_ftp             12460  0
>>> nf_nat                 18242  2 nf_nat_ftp,iptable_nat
>>> nf_conntrack_ipv4      14078  35 nf_nat,iptable_nat
>>> nf_defrag_ipv4         12483  1 nf_conntrack_ipv4
>>> nf_conntrack_ftp       12605  1 nf_nat_ftp
>>> nf_conntrack           52720  10 nf_conntrack_ftp,nf_conntrack_ipv4,nf_nat,nf_nat_ftp,nf_conntrack_broadcast,nf_conntrack_netbios_ns,xt_state,nf_conntrack_ipv6,iptable_nat,xt_conntrack
>>> iptable_filter         12536  1
>>> ip_tables              22042  3 iptable_filter,iptable_mangle,iptable_nat
>>> x_tables               19118  18 ip_tables,iptable_filter,ip6_tables,ip6table_filter,xt_state,xt_addrtype,xt_tcpudp,xt_limit,ipt_LOG,ipt_REJECT,ip6t_rt,xt_hl,ip6t_LOG,iptable_mangle,iptable_nat,xt_conntrack,xt_multiport,ip6t_REJECT
>>> loop                   22641  0
>>> ecryptfs               81507  0
>>> dm_crypt               22586  0
>>> snd_hda_codec_hdmi     30824  1
>>> snd_usb_audio          89083  2
>>> snd_usbmidi_lib        23369  1 snd_usb_audio
>>> snd_seq_midi           12848  0
>>> snd_seq_midi_event     13316  1 snd_seq_midi
>>> snd_rawmidi            23060  2 snd_seq_midi,snd_usbmidi_lib
>>> snd_hda_codec_idt      53792  1
>>> tuner_simple           17175  1
>>> tuner_types            16409  1 tuner_simple
>>> wm8775                 12749  1
>>> tda9887                12645  1
>>> tda8290                17278  0
>>> tuner                  17497  2
>>> cx25840                39782  1
>>> ivtv                  129010  0
>>> cx2341x                21461  1 ivtv
>>> snd_hda_intel          26259  2
>>> snd_hda_codec          78031  3 snd_hda_intel,snd_hda_codec_idt,snd_hda_codec_hdmi
>>> snd_hwdep              13186  2 snd_hda_codec,snd_usb_audio
>>> snd_pcm                68083  4 snd_hda_codec,snd_hda_intel,snd_usb_audio,snd_hda_codec_hdmi
>>> tveeprom               20593  1 ivtv
>>> v4l2_common            13222  5 cx2341x,ivtv,cx25840,tuner,wm8775
>>> videodev               70889  6 v4l2_common,cx2341x,ivtv,cx25840,tuner,wm8775
>>> v4l2_compat_ioctl32    16655  1 videodev
>>> media                  18148  1 videodev
>>> nv_tco                 12914  0
>>> i2c_algo_bit           12841  1 ivtv
>>> snd_page_alloc         13003  2 snd_pcm,snd_hda_intel
>>> snd_seq                45126  2 snd_seq_midi_event,snd_seq_midi
>>> snd_seq_device         13176  3 snd_seq,snd_rawmidi,snd_seq_midi
>>> i2c_nforce2            12584  0
>>> dcdbas                 13307  0
>>> edac_mce_amd           17103  0
>>> edac_core              35258  0
>>> evdev                  17562  18
>>> powernow_k8            17618  1
>>> mperf                  12453  1 powernow_k8
>>> k8temp                 12647  0
>>> psmouse                69265  0
>>> snd_timer              22917  2 snd_seq,snd_pcm
>>> i2c_core               23876  12 i2c_nforce2,i2c_algo_bit,videodev,v4l2_common,tveeprom,ivtv,cx25840,tuner,tda8290,tda9887,wm8775,tuner_simple
>>> serio_raw              12931  0
>>> fglrx                2634136  183
>>> pcspkr                 12579  0
>>> snd                    52893  20 snd_timer,snd_seq_device,snd_seq,snd_pcm,snd_hwdep,snd_hda_codec,snd_hda_intel,snd_hda_codec_idt,snd_rawmidi,snd_usbmidi_lib,snd_usb_audio,snd_hda_codec_hdmi
>>> processor              28149  1 powernow_k8
>>> button                 12937  1 fglrx
>>> soundcore              13065  1 snd
>>> thermal_sys            18040  1 processor
>>> ext4                  350804  9
>>> crc16                  12343  1 ext4
>>> jbd2                   62115  1 ext4
>>> mbcache                13114  2 ext4,ext2
>>> dm_mod                 63645  29 dm_crypt
>>> md_mod                 87742  4 linear,raid0,raid1,raid456
>>> sg                     25874  0
>>> sd_mod                 36136  6
>>> sr_mod                 21899  0
>>> cdrom                  35401  1 sr_mod
>>> crc_t10dif             12348  1 sd_mod
>>> usbhid                 36418  0
>>> hid                    81372  1 usbhid
>>> usb_storage            43870  0
>>> ata_generic            12479  0
>>> ohci_hcd               26563  0
>>> sata_nv                26690  4
>>> libata                140630  2 sata_nv,ata_generic
>>> ehci_hcd               40249  0
>>> b44                    27751  0
>>> ssb                    44714  1 b44
>>> mmc_core               68400  1 ssb
>>> mii                    12675  1 b44
>>> pcmcia                 32734  1 ssb
>>> pcmcia_core            18294  1 pcmcia
>>> scsi_mod              162321  5 libata,usb_storage,sr_mod,sd_mod,sg
>>> usbcore               128741  7 ehci_hcd,ohci_hcd,usb_storage,usbhid,snd_usbmidi_lib,snd_usb_audio
>>> usb_common             12354  1 usbcore
>>> -------------
>>> FORCE_MODS:
>>> -------------
>>>
>>> -------------
>>> DENY_MODS:
>>> -------------
>>> kqemu vxfen
>>> -------------
>>> df result:
>>> ----------
>>> Sys. fich.                                             Type        1K-blocks     Util. Disponible Uti% Mont?? sur
>>> rootfs                                                 rootfs       96124904  10822540   80419412  12% /
>>> sysfs                                                  sysfs               0         0          0    - /sys
>>> proc                                                   proc                0         0          0    - /proc
>>> udev                                                   devtmpfs        10240         0      10240   0% /dev
>>> devpts                                                 devpts              0         0          0    - /dev/pts
>>> tmpfs                                                  tmpfs          406288       944     405344   1% /run
>>> /dev/disk/by-uuid/4a5a9317-0b70-4796-a094-d61c01891c81 ext4         96124904  10822540   80419412  12% /
>>> tmpfs                                                  tmpfs            5120         0       5120   0% /run/lock
>>> tmpfs                                                  tmpfs         1008560       276    1008284   1% /run/shm
>>> /dev/mapper/sysvg-optlv                                ext4         16803708  15010400     939704  95% /opt
>>> /dev/mapper/data1vg-homelv                             ext4         51606140  41866076    7119008  86% /home
>>> /dev/mapper/data1vg-wwwlv                              ext4          4809704   2794384    1770996  62% /www
>>> /dev/mapper/data1vg-baseslv                            ext4          1923084    737276    1088120  41% /bases
>>> /dev/mapper/data1vg-photoslv                           ext4         72248648  45036992   23541896  66% /photos
>>> /dev/mapper/data1vg-videoslv                           ext4        154818540 108302512   38651708  74% /videos
>>> /dev/mapper/data1vg-vboxlv                             ext4        134573320 104068176   23669128  82% /vbox
>>> /dev/mapper/data1vg-graveurlv                          ext4         20642428   8094972   11498880  42% /graveur
>>> rpc_pipefs                                             rpc_pipefs          0         0          0    - /var/lib/nfs/rpc_pipefs
>>> binfmt_misc                                            binfmt_misc         0         0          0    - /proc/sys/fs/binfmt_misc
>>> -------------
>>> df -i result:
>>> ----------
>>> Sys. fich.                                              Inodes IUtil.  ILibre IUti% Mont?? sur
>>> rootfs                                                 6111232 313566 5797666    6% /
>>> udev                                                    497709    610  497099    1% /dev
>>> tmpfs                                                   507860    667  507193    1% /run
>>> /dev/disk/by-uuid/4a5a9317-0b70-4796-a094-d61c01891c81 6111232 313566 5797666    6% /
>>> tmpfs                                                   507860      3  507857    1% /run/lock
>>> tmpfs                                                   507860     15  507845    1% /run/shm
>>> /dev/mapper/sysvg-optlv                                1068960  54781 1014179    6% /opt
>>> /dev/mapper/data1vg-homelv                             3276800  83092 3193708    3% /home
>>> /dev/mapper/data1vg-wwwlv                               305824  43214  262610   15% /www
>>> /dev/mapper/data1vg-baseslv                             122160   1213  120947    1% /bases
>>> /dev/mapper/data1vg-photoslv                           4587520  23609 4563911    1% /photos
>>> /dev/mapper/data1vg-videoslv                           9830400    180 9830220    1% /videos
>>> /dev/mapper/data1vg-vboxlv                             8552448     91 8552357    1% /vbox
>>> /dev/mapper/data1vg-graveurlv                          1310720     80 1310640    1% /graveur
>>> -------------
>>> -------------
>>> INFO: /boot/grub/grub.cfg content
>>> -------------
>>> #
>>> # DO NOT EDIT THIS FILE
>>> #
>>> # It is automatically generated by grub-mkconfig using templates
>>> # from /etc/grub.d and settings from /etc/default/grub
>>> #
>>>
>>> ### BEGIN /etc/grub.d/00_header ###
>>> if [ -s $prefix/grubenv ]; then
>>>   load_env
>>> fi
>>> set default="0"
>>> if [ "${prev_saved_entry}" ]; then
>>>   set saved_entry="${prev_saved_entry}"
>>>   save_env saved_entry
>>>   set prev_saved_entry=
>>>   save_env prev_saved_entry
>>>   set boot_once=true
>>> fi
>>>
>>> function savedefault {
>>>   if [ -z "${boot_once}" ]; then
>>>     saved_entry="${chosen}"
>>>     save_env saved_entry
>>>   fi
>>> }
>>>
>>> function load_video {
>>>   insmod vbe
>>>   insmod vga
>>>   insmod video_bochs
>>>   insmod video_cirrus
>>> }
>>>
>>> insmod part_msdos
>>> insmod ext2
>>> set root='(hd0,msdos5)'
>>> search --no-floppy --fs-uuid --set=root 4a5a9317-0b70-4796-a094-d61c01891c81
>>> if loadfont /usr/share/grub/unicode.pf2 ; then
>>>   set gfxmode=640x480
>>>   load_video
>>>   insmod gfxterm
>>>   insmod part_msdos
>>>   insmod ext2
>>>   set root='(hd0,msdos5)'
>>>   search --no-floppy --fs-uuid --set=root 4a5a9317-0b70-4796-a094-d61c01891c81
>>>   set locale_dir=($root)/boot/grub/locale
>>>   set lang=fr_FR
>>>   insmod gettext
>>> fi
>>> terminal_output gfxterm
>>> set timeout=5
>>> ### END /etc/grub.d/00_header ###
>>>
>>> ### BEGIN /etc/grub.d/05_debian_theme ###
>>> insmod part_msdos
>>> insmod ext2
>>> set root='(hd0,msdos5)'
>>> search --no-floppy --fs-uuid --set=root 4a5a9317-0b70-4796-a094-d61c01891c81
>>> insmod png
>>> if background_image /usr/share/images/desktop-base/joy-grub.png; then
>>>   set color_normal=white/black
>>>   set color_highlight=black/white
>>> else
>>>   set menu_color_normal=cyan/blue
>>>   set menu_color_highlight=white/blue
>>> fi
>>> ### END /etc/grub.d/05_debian_theme ###
>>>
>>> ### BEGIN /etc/grub.d/10_linux ###
>>> menuentry 'Debian GNU/Linux, avec Linux 3.2.0-4-amd64' --class debian --class gnu-linux --class gnu --class os {
>>> load_video
>>> insmod gzio
>>> insmod part_msdos
>>> insmod ext2
>>> set root='(hd0,msdos5)'
>>> search --no-floppy --fs-uuid --set=root 4a5a9317-0b70-4796-a094-d61c01891c81
>>> echo 'Chargement de Linux 3.2.0-4-amd64 ...'
>>> linux /boot/vmlinuz-3.2.0-4-amd64 root=UUID=4a5a9317-0b70-4796-a094-d61c01891c81 ro  quiet
>>> echo 'Chargement du disque m??moire initial ...'
>>> initrd /boot/initrd.img-3.2.0-4-amd64
>>> }
>>> menuentry 'Debian GNU/Linux, avec Linux 3.2.0-4-amd64 (mode de d??pannage)' --class debian --class gnu-linux --class gnu --class os {
>>> load_video
>>> insmod gzio
>>> insmod part_msdos
>>> insmod ext2
>>> set root='(hd0,msdos5)'
>>> search --no-floppy --fs-uuid --set=root 4a5a9317-0b70-4796-a094-d61c01891c81
>>> echo 'Chargement de Linux 3.2.0-4-amd64 ...'
>>> linux /boot/vmlinuz-3.2.0-4-amd64 root=UUID=4a5a9317-0b70-4796-a094-d61c01891c81 ro single
>>> echo 'Chargement du disque m??moire initial ...'
>>> initrd /boot/initrd.img-3.2.0-4-amd64
>>> }
>>> ### END /etc/grub.d/10_linux ###
>>>
>>> ### BEGIN /etc/grub.d/20_linux_xen ###
>>> ### END /etc/grub.d/20_linux_xen ###
>>>
>>> ### BEGIN /etc/grub.d/20_memtest86+ ###
>>> menuentry "Memory test (memtest86+)" {
>>> insmod part_msdos
>>> insmod ext2
>>> set root='(hd0,msdos5)'
>>> search --no-floppy --fs-uuid --set=root 4a5a9317-0b70-4796-a094-d61c01891c81
>>> linux16 /boot/memtest86+.bin
>>> }
>>> menuentry "Memory test (memtest86+, serial console 115200)" {
>>> insmod part_msdos
>>> insmod ext2
>>> set root='(hd0,msdos5)'
>>> search --no-floppy --fs-uuid --set=root 4a5a9317-0b70-4796-a094-d61c01891c81
>>> linux16 /boot/memtest86+.bin console=ttyS0,115200n8
>>> }
>>> menuentry "Memory test (memtest86+, experimental multiboot)" {
>>> insmod part_msdos
>>> insmod ext2
>>> set root='(hd0,msdos5)'
>>> search --no-floppy --fs-uuid --set=root 4a5a9317-0b70-4796-a094-d61c01891c81
>>> multiboot /boot/memtest86+_multiboot.bin
>>> }
>>> menuentry "Memory test (memtest86+, serial console 115200, experimental multiboot)" {
>>> insmod part_msdos
>>> insmod ext2
>>> set root='(hd0,msdos5)'
>>> search --no-floppy --fs-uuid --set=root 4a5a9317-0b70-4796-a094-d61c01891c81
>>> multiboot /boot/memtest86+_multiboot.bin console=ttyS0,115200n8
>>> }
>>> ### END /etc/grub.d/20_memtest86+ ###
>>>
>>> ### BEGIN /etc/grub.d/30_os-prober ###
>>> menuentry "Windows Vista (loader) (on /dev/sda3)" --class windows --class os {
>>> insmod part_msdos
>>> insmod ntfs
>>> set root='(hd0,msdos3)'
>>> search --no-floppy --fs-uuid --set=root 0C6CE0BA6CE0A026
>>> chainloader +1
>>> }
>>> ### END /etc/grub.d/30_os-prober ###
>>>
>>> ### BEGIN /etc/grub.d/40_custom ###
>>> # This file provides an easy way to add custom menu entries.  Simply type the
>>> # menu entries you want to add after this comment.  Be careful not to change
>>> # the 'exec tail' line above.
>>> ### END /etc/grub.d/40_custom ###
>>>
>>> ### BEGIN /etc/grub.d/41_custom ###
>>> if [ -f  $prefix/custom.cfg ]; then
>>>   source $prefix/custom.cfg;
>>> fi
>>> ### END /etc/grub.d/41_custom ###
>>> -------------
>>> -------------
>>> INFO: /boot/grub/device.map content
>>> -------------
>>> (hd0) /dev/disk/by-id/ata-ST3320620AS_5QF2VWM8
>>> -------------
>>> Full fdisk info
>>> ---------------
>>>
>>> Disque /dev/sda??: 320.1??Go, 320072933376??octets
>>> 255??t??tes, 63??secteurs/piste, 38913??cylindres, total 625142448??secteurs
>>> Unit??s = secteurs de 1 * 512 = 512??octets
>>> Taille de secteur (logique / physique)??: 512??octets / 512??octets
>>> taille d'E/S (minimale / optimale)??: 512??octets / 512??octets
>>> Identifiant de disque??: 0x58000000
>>>
>>> P??riph??rique Amorce  D??but        Fin      Blocs     Id  Syst??me
>>> /dev/sda1              63      112454       56196   de  Dell Utility
>>> /dev/sda2          112640    21084159    10485760    7  HPFS/NTFS/exFAT
>>> /dev/sda3   *    21093345   228379505   103643080+   7  HPFS/NTFS/exFAT
>>> /dev/sda4       228380101   625141759   198380829+   5  ??tendue
>>> /dev/sda5       228380103   423698309    97659103+  83  Linux
>>> /dev/sda6       423698373   425658239      979933+  82  partition d'??change Linux / Solaris
>>> /dev/sda7       425658368   625141759    99741696   8e  LVM Linux
>>>
>>> Disque /dev/sdb??: 1000.2??Go, 1000204886016??octets
>>> 81??t??tes, 63??secteurs/piste, 382818??cylindres, total 1953525168??secteurs
>>> Unit??s = secteurs de 1 * 512 = 512??octets
>>> Taille de secteur (logique / physique)??: 512??octets / 512??octets
>>> taille d'E/S (minimale / optimale)??: 512??octets / 512??octets
>>> Identifiant de disque??: 0x0003513f
>>>
>>> P??riph??rique Amorce  D??but        Fin      Blocs     Id  Syst??me
>>> /dev/sdb1            2048  1953525167   976761560   8e  LVM Linux
>>>
>>> Disque /dev/mapper/data1vg-photoslv??: 75.2??Go, 75161927680??octets
>>> 255??t??tes, 63??secteurs/piste, 9137??cylindres, total 146800640??secteurs
>>> Unit??s = secteurs de 1 * 512 = 512??octets
>>> Taille de secteur (logique / physique)??: 512??octets / 512??octets
>>> taille d'E/S (minimale / optimale)??: 512??octets / 512??octets
>>> Identifiant de disque??: 0x00000000
>>>
>>>
>>> Disque /dev/mapper/data1vg-videoslv??: 161.1??Go, 161061273600??octets
>>> 255??t??tes, 63??secteurs/piste, 19581??cylindres, total 314572800??secteurs
>>> Unit??s = secteurs de 1 * 512 = 512??octets
>>> Taille de secteur (logique / physique)??: 512??octets / 512??octets
>>> taille d'E/S (minimale / optimale)??: 512??octets / 512??octets
>>> Identifiant de disque??: 0x00000000
>>>
>>>
>>> Disque /dev/mapper/data1vg-homelv??: 53.7??Go, 53687091200??octets
>>> 255??t??tes, 63??secteurs/piste, 6527??cylindres, total 104857600??secteurs
>>> Unit??s = secteurs de 1 * 512 = 512??octets
>>> Taille de secteur (logique / physique)??: 512??octets / 512??octets
>>> taille d'E/S (minimale / optimale)??: 512??octets / 512??octets
>>> Identifiant de disque??: 0x00000000
>>>
>>>
>>> Disque /dev/mapper/data1vg-graveurlv??: 21.5??Go, 21474836480??octets
>>> 255??t??tes, 63??secteurs/piste, 2610??cylindres, total 41943040??secteurs
>>> Unit??s = secteurs de 1 * 512 = 512??octets
>>> Taille de secteur (logique / physique)??: 512??octets / 512??octets
>>> taille d'E/S (minimale / optimale)??: 512??octets / 512??octets
>>> Identifiant de disque??: 0x00000000
>>>
>>>
>>> Disque /dev/mapper/data1vg-wwwlv??: 5003??Mo, 5003804672??octets
>>> 255??t??tes, 63??secteurs/piste, 608??cylindres, total 9773056??secteurs
>>> Unit??s = secteurs de 1 * 512 = 512??octets
>>> Taille de secteur (logique / physique)??: 512??octets / 512??octets
>>> taille d'E/S (minimale / optimale)??: 512??octets / 512??octets
>>> Identifiant de disque??: 0x00000000
>>>
>>>
>>> Disque /dev/mapper/data1vg-baseslv??: 2000??Mo, 2000683008??octets
>>> 255??t??tes, 63??secteurs/piste, 243??cylindres, total 3907584??secteurs
>>> Unit??s = secteurs de 1 * 512 = 512??octets
>>> Taille de secteur (logique / physique)??: 512??octets / 512??octets
>>> taille d'E/S (minimale / optimale)??: 512??octets / 512??octets
>>> Identifiant de disque??: 0x00000000
>>>
>>>
>>> Disque /dev/mapper/data1vg-vboxlv??: 140.0??Go, 140001673216??octets
>>> 255??t??tes, 63??secteurs/piste, 17020??cylindres, total 273440768??secteurs
>>> Unit??s = secteurs de 1 * 512 = 512??octets
>>> Taille de secteur (logique / physique)??: 512??octets / 512??octets
>>> taille d'E/S (minimale / optimale)??: 512??octets / 512??octets
>>> Identifiant de disque??: 0x00000000
>>>
>>>
>>> Disque /dev/mapper/sysvg-optlv??: 17.5??Go, 17481859072??octets
>>> 255??t??tes, 63??secteurs/piste, 2125??cylindres, total 34144256??secteurs
>>> Unit??s = secteurs de 1 * 512 = 512??octets
>>> Taille de secteur (logique / physique)??: 512??octets / 512??octets
>>> taille d'E/S (minimale / optimale)??: 512??octets / 512??octets
>>> Identifiant de disque??: 0x00000000
>>>
>>> ----------------
>>> ------------------------------------
>>> Your raw fstab file looks like this:
>>> ------------------------------------
>>> # /etc/fstab: static file system information.
>>> #
>>> # Use 'blkid' to print the universally unique identifier for a
>>> # device; this may be used with UUID= as a more robust way to name devices
>>> # that works even if disks are added and removed. See fstab(5).
>>> #
>>> # <file system>        <mount point>     <type>      <options>                   <dump> <pass>
>>> # / was on /dev/sda5 during installation
>>> UUID=4a5a9317-0b70-4796-a094-d61c01891c81 /    ext4  errors=remount-ro           0      1
>>> # swap was on /dev/sda6 during installation
>>> UUID=b4d7e5c0-207b-4a67-8b58-20523c509b87 none swap  sw                          0      0
>>>
>>> /dev/sr0               /media/cdrom0     udf,iso9660 user,noauto                 0      0
>>>
>>> #/dev/sysvg/homelv      /home             ext4        relatime,errors=remount-ro  0      1
>>> /dev/sysvg/optlv       /opt              ext4        relatime,errors=remount-ro  0      1
>>>
>>> /dev/data1vg/homelv    /home             ext4        relatime,errors=remount-ro  0      2
>>> /dev/data1vg/wwwlv     /www              ext4        relatime,errors=remount-ro  0      2
>>> /dev/data1vg/baseslv   /bases            ext4        relatime,errors=remount-ro  0      2
>>> /dev/data1vg/photoslv  /photos           ext4        relatime,errors=remount-ro  0      2
>>> /dev/data1vg/videoslv  /videos           ext4        relatime,errors=remount-ro  0      2
>>> /dev/data1vg/vboxlv    /vbox             ext4        relatime,errors=remount-ro  0      2
>>> /dev/data1vg/graveurlv /graveur          ext4        relatime,errors=remount-ro  0      2
>>>
>>> # /dev/data0vg/homelv    /data0vg/home     ext4        relatime,errors=remount-ro  0      2
>>> # /dev/data0vg/wwwlv     /data0vg/www      ext4        relatime,errors=remount-ro  0      2
>>> # /dev/data0vg/baseslv   /data0vg/bases    ext4        relatime,errors=remount-ro  0      2
>>> # /dev/data0vg/photoslv  /data0vg/photos   ext4        relatime,errors=remount-ro  0      2
>>> # /dev/data0vg/videoslv  /data0vg/videos   ext4        relatime,errors=remount-ro  0      2
>>> # /dev/data0vg/vboxlv    /data0vg/vbox     ext4        relatime,errors=remount-ro  0      2
>>>
>>> # /dev/data2vg/homelv    /data2vg/home     ext4        relatime,errors=remount-ro  0      2
>>> # /dev/data2vg/wwwlv     /data2vg/www      ext4        relatime,errors=remount-ro  0      2
>>> # /dev/data2vg/baseslv   /data2vg/bases    ext4        relatime,errors=remount-ro  0      2
>>> # /dev/data2vg/photoslv  /data2vg/photos   ext4        relatime,errors=remount-ro  0      2
>>> # /dev/data2vg/videoslv  /data2vg/videos   ext4        relatime,errors=remount-ro  0      2
>>> # /dev/data2vg/vboxlv    /data2vg/vbox     ext4        relatime,errors=remount-ro  0      2
>>> -----------------------------------
>>> Your mountlist will look like this:
>>> -----------------------------------
>>> INFO: Analyzing LVM...
>>> DEVICE          MOUNTPOINT      FORMAT          SIZE MB       LABEL/UUID    
>>> ------          ----------      ------          -------       ----------    
>>> INFO: Examining /dev/sdb1 (mount=lvm fmt=lvm psz=976761560)
>>> /dev/sdb1       lvm             lvm              953868 c9qZKK-bpqn-sY7P-fWH2-SBlo-YsXS-udCgP7
>>> INFO: Examining /dev/sda7 (mount=lvm fmt=lvm psz=99741696)
>>> /dev/sda7       lvm             lvm               97404 yuL0j7-wJtb-ANiO-Omxi-AuEE-wCkJ-pfhEWi
>>> INFO: Examining /dev/sda5 (mount=/ fmt=ext4 psz=97659103)
>>> /dev/sda5       /               ext4              95370 4a5a9317-0b70-4796-a094-d61c01891c81
>>> INFO: Examining /dev/sda6 (mount=swap fmt=swap psz=979928)
>>> /dev/sda6       swap            swap                956 b4d7e5c0-207b-4a67-8b58-20523c509b87
>>> INFO: Examining /dev/sysvg/optlv (mount=/opt fmt=ext4 psz=lvm)
>>> /dev/sysvg/optlv /opt            ext4                lvm f1c4b976-0101-47ac-9ff8-c5a9e567553b
>>> INFO: Examining /dev/data1vg/homelv (mount=/home fmt=ext4 psz=lvm)
>>> /dev/data1vg/homelv /home           ext4                lvm e063df74-3fff-45ac-927d-bc6a60bd2970
>>> INFO: Examining /dev/data1vg/wwwlv (mount=/www fmt=ext4 psz=lvm)
>>> /dev/data1vg/wwwlv /www            ext4                lvm 7942603b-20c8-483a-ab36-98ee20ab7700
>>> INFO: Examining /dev/data1vg/baseslv (mount=/bases fmt=ext4 psz=lvm)
>>> /dev/data1vg/baseslv /bases          ext4                lvm 09f40cc9-fc3b-4205-a466-df38e5774a59
>>> INFO: Examining /dev/data1vg/photoslv (mount=/photos fmt=ext4 psz=lvm)
>>> /dev/data1vg/photoslv /photos         ext4                lvm 11ff707f-da12-46a3-9218-87fcf38ddc2f
>>> INFO: Examining /dev/data1vg/videoslv (mount=/videos fmt=ext4 psz=lvm)
>>> /dev/data1vg/videoslv /videos         ext4                lvm 11e0f5ef-75e4-4b7b-b34e-c9112b731f57
>>> INFO: Examining /dev/data1vg/vboxlv (mount=/vbox fmt=ext4 psz=lvm)
>>> /dev/data1vg/vboxlv /vbox           ext4                lvm 69e8fcf6-9518-4c3c-9052-53096c873cc4
>>> INFO: Examining /dev/data1vg/graveurlv (mount=/graveur fmt=ext4 psz=lvm)
>>> /dev/data1vg/graveurlv /graveur        ext4                lvm a5d30c9b-d333-46a3-8c28-ef2c4c1d9185
>>> -----------------------------------
>>> Mindi 3.0.0-r3332 is exiting
>>> End date : lundi 19 janvier 2015, 22:16:59 (UTC+0100)
>>
>>> INFO: Time started: Mon Jan 19 22:16:43 2015
>>>
>>> DBG2: [TH=22705] libmondo-tools.c->setup_tmpdir#715: bkpinfo->tmpdir is being set to /tmp/mondo.tmp.4v41Vd
>>> DBG2: [TH=22705] libmondo-tools.c->setup_scratchdir#736: Purging old scratchdir /mondo.scratch.*
>>> DBG2: [TH=22705] libmondo-tools.c->setup_scratchdir#757: bkpinfo->scratchdir is being set to /tmp/mondo.scratch.3mNp4N
>>> INFO: root is mounted at /dev/disk/by-uuid/aa9317-0b70-4796-a094-d61c01891c81
>>>
>>> INFO: That doesn't mean /dev/disk/by-uuid/aa9317-0b70-4796-a094-d61c01891c81 is the root partition. It's just a debugging message. Relax. It's part of am_I_in_disaster_recovery_mode().
>>> DBG1: [TH=22705] libmondo-devices.c->am_I_in_disaster_recovery_mode#163: Is this a ramdisk? result = FALSE
>>> INFO: running: dmesg -n1 > /tmp/mondo.tmp.4v41Vd/mondo-run-prog-thing.tmp 2> /tmp/mondo.tmp.4v41Vd/mondo-run-prog-thing.err
>>> INFO: --------------------------------start of output-----------------------------
>>> INFO: --------------------------------end of output------------------------------
>>> INFO: ...ran just fine. :-)
>>> INFO: Mondo Archive v3.2.0-r3332 --- http://www.mondorescue.org
>>> INFO: running x86_64 binaries
>>> INFO: running on x86_64 architecture
>>> INFO: -----------------------------------------------------------
>>> INFO: NB: Mondo logs almost everything, so don't panic if you see
>>> INFO: some error messages.  Please read them carefully before you
>>> INFO: decide to break out in a cold sweat.    Despite (or perhaps
>>> INFO: because of) the wealth of messages. some users are inclined
>>> INFO: to stop reading this log. If Mondo stopped for some reason,
>>> INFO: chances are it's detailed here.  More than likely there's a
>>> INFO: message at the very end of this log that will tell you what
>>> INFO: is wrong. Please read it!                          -Devteam
>>> INFO: -----------------------------------------------------------
>>> INFO: Zero...
>>> DBG1: [Main] mondoarchive.c->welcome_to_mondoarchive#96: One...
>>> DBG2: [Main] mondoarchive.c->welcome_to_mondoarchive#97: Two...
>>> DBG3: [Main] mondoarchive.c->welcome_to_mondoarchive#98: Three...
>>> DBG4: [Main] mondoarchive.c->welcome_to_mondoarchive#99: Four...
>>> DBG2: [Main] mondoarchive.c->distro_specific_kludges_at_start_of_mondoarchive#114: Unmounting old ramdisks if necessary
>>> INFO: running: mount | grep cdrom | grep super > /tmp/mondo.tmp.4v41Vd/mondo-run-prog-thing.tmp 2> /tmp/mondo.tmp.4v41Vd/mondo-run-prog-thing.err
>>> INFO: --------------------------------start of output-----------------------------
>>> INFO: --------------------------------end of output------------------------------
>>> INFO: ...ran with res=256
>>> INFO: running: mount | grep floppy | grep super > /tmp/mondo.tmp.4v41Vd/mondo-run-prog-thing.tmp 2> /tmp/mondo.tmp.4v41Vd/mondo-run-prog-thing.err
>>> INFO: --------------------------------start of output-----------------------------
>>> INFO: --------------------------------end of output------------------------------
>>> INFO: ...ran with res=256
>>> DBG1: [Main] libmondo-tools.c->mount_boot_if_necessary#1155: Started sub
>>> DBG4: [Main] libmondo-tools.c->mount_boot_if_necessary#1156: About to set g_boot_mountpt[0] to '\0'
>>> DBG4: [Main] libmondo-tools.c->mount_boot_if_necessary#1158: Done. Great. Seeting command to something
>>> DBG4: [Main] libmondo-tools.c->mount_boot_if_necessary#1160: Cool. Command = 'grep -v ":" /etc/fstab | grep -vE '^#.*$' | grep -E "[ ]/boot[ ]" | tr -s ' ' ' ' | cut -f1 | head -n1'
>>> DBG4: [Main] libmondo-tools.c->mount_boot_if_necessary#1164: tmp = ''
>>> DBG2: [Main] libmondo-tools.c->mount_boot_if_necessary#1165: /boot is at  according to /etc/fstab
>>> DBG3: [Main] libmondo-tools.c->mount_boot_if_necessary#1182: command = mount | grep -E '^'
>>> DBG1: [Main] libmondo-tools.c->mount_boot_if_necessary#1205: Ended sub
>>> DBG1: [Main] libmondo-tools.c->get_kernel_version#245: g_kernel_version = 3.200000
>>> INFO: running: rm -Rf /var/cache/mondo/changed.files* > /tmp/mondo.tmp.4v41Vd/mondo-run-prog-thing.tmp 2> /tmp/mondo.tmp.4v41Vd/mondo-run-prog-thing.err
>>> INFO: --------------------------------start of output-----------------------------
>>> INFO: --------------------------------end of output------------------------------
>>> INFO: ...ran just fine. :-)
>>> INFO: Checking sanity of your Linux distribution
>>> INFO: running: grep ramdisk /proc/devices > /tmp/mondo.tmp.4v41Vd/mondo-run-prog-thing.tmp 2> /tmp/mondo.tmp.4v41Vd/mondo-run-prog-thing.err
>>> INFO: --------------------------------start of output-----------------------------
>>> INFO: 1 ramdisk
>>> INFO: --------------------------------end of output------------------------------
>>> INFO: ...ran just fine. :-)
>>> INFO: running: mount | grep -Ew 'vfat|fat|dos' | grep -vE "/dev/fd|nexdisk" > /tmp/mondo.tmp.4v41Vd/mondo-run-prog-thing.tmp 2> /tmp/mondo.tmp.4v41Vd/mondo-run-prog-thing.err
>>> INFO: --------------------------------start of output-----------------------------
>>> INFO: --------------------------------end of output------------------------------
>>> INFO: ...ran with res=256
>>> DBG4: [Main] libmondo-files.c->find_home_of_exe#349: find_home_of_exe --- Found cmp at /usr/bin/cmp
>>> INFO: running: mindi -V > /tmp/mondo.tmp.4v41Vd/mondo-run-prog-thing.tmp 2> /tmp/mondo.tmp.4v41Vd/mondo-run-prog-thing.err
>>> INFO: --------------------------------start of output-----------------------------
>>> INFO: Mindi v3.0.0-r3332
>>> INFO: Le disque /dev/mapper/data1vg-photoslv ne contient pas une table de partitions valable
>>> INFO: Le disque /dev/mapper/data1vg-videoslv ne contient pas une table de partitions valable
>>> INFO: Le disque /dev/mapper/data1vg-homelv ne contient pas une table de partitions valable
>>> INFO: Le disque /dev/mapper/data1vg-graveurlv ne contient pas une table de partitions valable
>>> INFO: Le disque /dev/mapper/data1vg-wwwlv ne contient pas une table de partitions valable
>>> INFO: Le disque /dev/mapper/data1vg-baseslv ne contient pas une table de partitions valable
>>> INFO: Le disque /dev/mapper/data1vg-vboxlv ne contient pas une table de partitions valable
>>> INFO: Le disque /dev/mapper/sysvg-optlv ne contient pas une table de partitions valable
>>> INFO: --------------------------------end of output------------------------------
>>> INFO: ...ran just fine. :-)
>>> INFO: running: parted2fdisk -l 2>/dev/null | grep -i raid > /tmp/mondo.tmp.4v41Vd/mondo-run-prog-thing.tmp 2> /tmp/mondo.tmp.4v41Vd/mondo-run-prog-thing.err
>>> INFO: --------------------------------start of output-----------------------------
>>> INFO: --------------------------------end of output------------------------------
>>> INFO: ...ran with res=256
>>> INFO: Done.
>>> DBG1: [Main] libmondo-cli.c->process_switches#181: Loglevel forced to 99
>>> DBG20: [Main] libmondo-files.c->does_file_exist#188: /usr/bin/afio exists
>>> DBG4: [Main] libmondo-files.c->find_home_of_exe#349: find_home_of_exe --- Found afio at /usr/bin/afio
>>
>>> ------------------------------------------------------------------------------
>>> New Year. New Location. New Benefits. New Data Center in Ashburn, VA.
>>> GigeNET is offering a free month of service with a new server in Ashburn.
>>> Choose from 2 high performing configs, both with 100TB of bandwidth.
>>> Higher redundancy.Lower latency.Increased capacity.Completely compliant.
>>> http://p.sf.net/sfu/gigenet
>>
>>> _______________________________________________
>>> Mondo-devel mailing list
>>> [hidden email]
>>> https://lists.sourceforge.net/lists/listinfo/mondo-devel
>>
>>
>
>


------------------------------------------------------------------------------
Dive into the World of Parallel Programming. The Go Parallel Website,
sponsored by Intel and developed in partnership with Slashdot Media, is your
hub for all things parallel software development, from weekly thought
leadership blogs to news, videos, case studies, tutorials and more. Take a
look and join the conversation now. http://goparallel.sourceforge.net/
_______________________________________________
Mondo-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/mondo-devel

mondo_trc_I.txt (1K) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Re: [Mondo-devel] Segmentation error running mondoarchive v3.2.0-r3332

Philippe Lefevre
OOPS !

In my latest email:
> I reran it from compiled sources but this time I also had the same
> trouble with it and was not able to get the error.

I meant "I was unable to get it work well again as I described in my
email dated of 17th of januray"

Kind Rgds,
Philippe

Le 01/02/2015 23:17, Philippe Lefevre a écrit :

> Hello list,
>
> I did again some tries with mondo 3.2.0
> Right: without -I option it works.
>
> I reran it from compiled sources but this time I also had the same
> trouble with it and was not able to get the error.
>
> I tried to understand what happen with this option and I believe it is
> linked to the pointer bkpinfo->include_paths which is empty in
> libmondo-cli.c:236
> We can see that flag_val['I'] is well setted to the arg value and
> flag_set['I'] is true in process_switches()
>
> Sorry, I must stop now and I'm afraid I will not have time those next
> days to grab into it again (may be next we ??) but I hope these traces
> may help.
>
> Please find attached some gdb steps.
>
> Kind regards,
> Philippe
>
>
> Le 26/01/2015 22:10, Philippe Lefevre a écrit :
>>
>> Great !
>>
>> Many thanks for your help and reply Bruno.
>>
>> Next week-end I'm going to reinstall 3.2.0 and supress -I option and see
>> what happen.
>>
>> One thing is strange anyway: in my tests after a mondoarchive
>> compilation, (pls, see my email dated on 17th january) I ran 3.2.0 with
>> -I option without any issue. The sigsegv was repructible when
>> mondoarchive was installed by the deb package ...
>>
>> I used :
>> [phlsys]root:/home/phl/mondo-3.2.0# gdb -args mondoarchive -D -OV -i -N
>> -G -s 780M -p sys-D7.7-diff_150105212200 -T /graveur -S /graveur -d
>> /graveur -I "/|/|/opt/Zuma" -E
>> "/bases/sybase|/graveur|/home|/opt|/photos|/quemu|/Sauvegardes|/var/crash|/var/backups|/var/log|/var/mail|/var/spool|/vbox|/videos|/www"
>>
>> and:
>>  ....
>>  Data archived OK.
>>  Mondoarchive ran OK.
>>  See /var/log/mondoarchive.log for details of backup run.
>>  Execution run ended; result=0
>>  Type 'less /var/log/mondoarchive.log' to see the output log [Inferior 1
>> (process 19382) exited normally]
>>  (gdb) quit
>>
>>
>> I'll let you know.
>> Kind regards,
>> Philippe
>>
>>
>>
>> Le 26/01/2015 01:09, Bruno Cornec a écrit :
>>> Hello Philippe,
>>>
>>> This is now fixed as described in BR:
>>> http://trac.mondorescue.org/ticket/764#comment:2
>>>
>>> Bruno.
>>>
>>> Philippe Lefevre said on Mon, Jan 19, 2015 at 10:34:24PM +0100:
>>>
>>>> Hello Gaetagno,
>>>>
>>>> Regarding the two slashes, as I said, I used the same syntax to get into
>>>> the same bug situation.
>>>>
>>>>
>>>> I did a try with only one / in the -I option and got the same
>>>> segmentation violation exception.
>>>>
>>>>
>>>> Mindi launched alone as your example and it ran fine and the iso file
>>>> successfully built.
>>>> Please find attached the mindi.log file.
>>>>
>>>> [phlsys]root:/home/phl/Devel/mondo# ls -al /var/cache/mindi/mindi.iso
>>>> -rw-r----- 1 root root 98721792 janv. 19 22:09 /var/cache/mindi/mindi.iso
>>>>
>>>>
>>>>
>>>> Ran mondoarchive with -K99 option crashed again with the sigsegv signal.
>>>> Please find attached the mondoarchive.log file.
>>>> Unfortunately, I'm afraid it is not so verbose than we would ...
>>>> This time, the log ends with :
>>>>
>>>> DBG1: [Main] libmondo-cli.c->process_switches#181: Loglevel forced to 99
>>>> DBG20: [Main] libmondo-files.c->does_file_exist#188: /usr/bin/afio exists
>>>> DBG4: [Main] libmondo-files.c->find_home_of_exe#349: find_home_of_exe
>>>> --- Found afio at /usr/bin/afio
>>>>
>>>>
>>>>
>>>> Running mondo without - E option crashed in the same way and with same
>>>> mondoarchive.log file.
>>>> [phlsys]root:/home/phl/Devel/mondo# /usr/sbin/mondoarchive -K99 -D -OV
>>>> -i -N -G -s 780M -p sys-D7.7-diff_150105212200 -T /graveur -S /graveur
>>>> -d /graveur -I "/opt/zuma"
>>>> See /var/log/mondoarchive.log for details of backup run.
>>>> Checking sanity of your Linux distribution
>>>> Done.
>>>> Erreur de segmentation
>>>>
>>>>
>>>> Thank you for your time Gaetagno.
>>>> Kind regards,
>>>> Philippe
>>>>
>>>>
>>>>
>>>> Le 19/01/2015 12:17, Gattegno, Victor (GSD CSC / GCC) a écrit :
>>>>> Hi Philippe,
>>>>>
>>>>> You used again two time "/"  in the include :
>>>>> -I "/|/|/opt/Zuma"
>>>>>
>>>>> Your mondorachive.log file ends with :
>>>>> DBG4: [Main] libmondo-files.c->find_home_of_exe#349: find_home_of_exe --- Found afio at /usr/bin/afio
>>>>>
>>>>> You can try a few things :
>>>>>
>>>>> Try mindi alone :
>>>>> # mindi
>>>>> Do you want to use your own kernel to build the boot disk ([y]/n) ? y
>>>>>
>>>>> Try your mondoarchive command without -E, with only -I, and choice only one directory, example :
>>>>> -I "/opt/Zuma"
>>>>>
>>>>> Try your mondoarchive command with more debug, example with -K 5, or with -K 99 (which is full debug mode, be aware that the log file could grow from 200 Kb to 50 Mb).
>>>>>
>>>>> Rgds,
>>>>> Victor
>>>>>
>>>>> -----Original Message-----
>>>>> From: Philippe Lefevre [mailto:[hidden email]]
>>>>> Sent: samedi 17 janvier 2015 20:14
>>>>> To: Mondo mailing list
>>>>> Subject: Re: [Mondo-devel] Segmentation error running mondoarchive v3.2.0-r3332
>>>>>
>>>>> Hello list,
>>>>>
>>>>> sorry Gaetagno for the delay, I was not able to find some time long enought to go back into my issue.
>>>>>
>>>>> I did it today (without removing the two slashes in order to be in the same situation) and .... what I compiled worked fine with what I have compiled. (I noticed the -v bug, thanks  ;)  )
>>>>>
>>>>> Run mondoarchive via dbg:
>>>>> [phlsys]root:/home/phl/mondo-3.2.0# gdb -args mondoarchive -D -OV -i -N -G -s 780M -p sys-D7.7-diff_150105212200 -T /graveur -S /graveur -d /graveur -I "/|/|/opt/Zuma" -E "/bases/sybase|/graveur|/home|/opt|/photos|/quemu|/Sauvegardes|/var/crash|/var/backups|/var/log|/var/mail|/var/spool|/vbox|/videos|/www"
>>>>>
>>>>> and:
>>>>> ....
>>>>> Data archived OK.
>>>>> Mondoarchive ran OK.
>>>>> See /var/log/mondoarchive.log for details of backup run.
>>>>> Execution run ended; result=0
>>>>> Type 'less /var/log/mondoarchive.log' to see the output log [Inferior 1 (process 19382) exited normally]
>>>>> (gdb) quit
>>>>>
>>>>>
>>>>> So I reinstalled the official debian package:
>>>>>
>>>>> Sélection du paquet libmondorescue-perl précédemment désélectionné.
>>>>> (Lecture de la base de données... 279208 fichiers et répertoires déjà
>>>>> installés.)
>>>>> Dépaquetage de libmondorescue-perl (à partir de
>>>>> .../libmondorescue-perl_3.2.0-1_all.deb) ...
>>>>> Préparation du remplacement de mindi-busybox 1.18.5-3 (en utilisant
>>>>> .../mindi-busybox_1.21.1-1_amd64.deb) ...
>>>>> Dépaquetage de la mise à jour de mindi-busybox ...
>>>>> Préparation du remplacement de mindi 2.1.7-1 (en utilisant
>>>>> .../mindi_3.0.0-1_amd64.deb) ...
>>>>> Dépaquetage de la mise à jour de mindi ...
>>>>> Préparation du remplacement de mondo 3.0.4-1 (en utilisant
>>>>> .../mondo_3.2.0-1_amd64.deb) ...
>>>>> Dépaquetage de la mise à jour de mondo ...
>>>>> Traitement des actions différées (« triggers ») pour « man-db »...
>>>>> Paramétrage de libmondorescue-perl (3.2.0-1) ...
>>>>> Paramétrage de mindi-busybox (1.21.1-1) ...
>>>>> Paramétrage de mindi (3.0.0-1) ...
>>>>> Installation de la nouvelle version du fichier de configuration /etc/mindi/deplist.d/minimal.conf ...
>>>>> Installation de la nouvelle version du fichier de configuration /etc/mindi/deplist.d/udev.conf ...
>>>>> Installation de la nouvelle version du fichier de configuration /etc/mindi/deplist.d/ProLiant.conf ...
>>>>> Installation de la nouvelle version du fichier de configuration /etc/mindi/deplist.d/base.conf ...
>>>>> Installation de la nouvelle version du fichier de configuration /etc/mindi/deplist.d/lvm.conf ...
>>>>> Installation de la nouvelle version du fichier de configuration /etc/mindi/perl-scripts ...
>>>>> Paramétrage de mondo (3.2.0-1) ...
>>>>>
>>>>>
>>>>> but launched in the same way, it crashed again with a segmentation error:
>>>>>
>>>>> [phlsys]root:/home/phl/telechargements/mondo-3.2.0# mondoarchive -D -OV -i -N -G -s 780M -p sys-D7.7-diff_150105212200 -T /graveur -S /graveur -d /graveur -I "/|/|/opt/Zuma" -E "/bases/sybase|/graveur|/home|/opt|/photos|/quemu|/Sauvegardes|/var/crash|/var/backups|/var/log|/var/mail|/var/spool|/vbox|/videos|/www"
>>>>> See /var/log/mondoarchive.log for details of backup run.
>>>>> Checking sanity of your Linux distribution Done.
>>>>> Erreur de segmentation
>>>>>
>>>>>
>>>>>
>>>>> Please find attached the relevant mondoarchive.log file.
>>>>> It seems to be stopped before logging something about the fault.
>>>>> I franckly don't know what I could do more.
>>>>> Do you have an idea about what I could do to explore deeper this issue ?
>>>>> Something might be going wrong into the deb pkg ???
>>>>> I got it with apt using:
>>>>>    deb ftp://ftp.mondorescue.org//debian 7 contrib
>>>>>
>>>>>
>>>>> Thanks for your help.
>>>>> Regards,
>>>>> Philippe
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> Le 06/01/2015 17:28, Gattegno, Victor (GSD CSC / GCC) a écrit :
>>>>>> Hello Philippe,
>>>>>>
>>>>>> From mondoarchive man : " When using the -I option with the -E option, the -E content should be subdirectories of those mentioned in the -I only, as -I takes precedence."
>>>>>>
>>>>>> But if your -I and -E combination works it's ok (check if /opt/zuma and /opt/calibre are well backuped and restored).
>>>>>>
>>>>>> Regards,
>>>>>> Victor
>>>>>>
>>>>>> -----Original Message-----
>>>>>> From: Philippe Lefevre [mailto:[hidden email]]
>>>>>> Sent: lundi 5 janvier 2015 21:42
>>>>>> To: [hidden email]
>>>>>> Subject: Re: [Mondo-devel] Segmentation error running mondoarchive
>>>>>> v3.2.0-r3332
>>>>>>
>>>>>> Thanks for your help and reply Victor,
>>>>>>
>>>>>> I should be able to replay with all of that before the end of the week and let you know.
>>>>>> Regarding the double /, it is due to my shell script which build the final request. I will also do a try without it.
>>>>>>
>>>>>> I believe I couldn't remove -I flag as in the exclude part there is /opt and I want to include only 2 directories /opt/zuma and /opt/calibre. At least, I should use -I "/opt/calibre|/opt/Zuma" right?
>>>>>>
>>>>>> PS: my system backup is run by root and ulimit is setted unlimited:
>>>>>>
>>>>>> # ulimit -a
>>>>>> core file size          (blocks, -c) 0
>>>>>> data seg size           (kbytes, -d) unlimited
>>>>>> scheduling priority             (-e) 0
>>>>>> file size               (blocks, -f) unlimited
>>>>>> pending signals                 (-i) 31106
>>>>>> max locked memory       (kbytes, -l) 64
>>>>>> max memory size         (kbytes, -m) unlimited
>>>>>> open files                      (-n) 1024
>>>>>> pipe size            (512 bytes, -p) 8
>>>>>> POSIX message queues     (bytes, -q) 819200
>>>>>> real-time priority              (-r) 0
>>>>>> stack size              (kbytes, -s) 8192
>>>>>> cpu time               (seconds, -t) unlimited
>>>>>> max user processes              (-u) 31106
>>>>>> virtual memory          (kbytes, -v) unlimited
>>>>>> file locks                      (-x) unlimited
>>>>>>
>>>>>>
>>>>>> Rgds,
>>>>>> Philippe
>>>>>>
>>>>>>
>>>>>> Le 05/01/2015 16:32, Gattegno, Victor (GSD CSC / GCC) a écrit :
>>>>>>> Hello Philippe,
>>>>>>>
>>>>>>> Good gdb work, but don't focus on "mondoarchive -v" segmentation fault, it's a known failing bug. It's better to debug mondoarchive with the options that you use.
>>>>>>>
>>>>>>>  In your 27/12/2014 test and post:
>>>>>>>  - did you posted too the associated /var/log/mondoarchive.log (compressed) ?
>>>>>>>  - you used -I (with / included twice) and -E options, it's better to use only -E option.
>>>>>>>
>>>>>>> What's the result of "ulimit -a" on your Debian ?
>>>>>>>
>>>>>>> I wish to you - and to all this mailig-list users - a nice year 2015.
>>>>>>>
>>>>>>> Rgds,
>>>>>>> Victor
>>>>>>>
>>>>>>> -----Original Message-----
>>>>>>> From: Philippe Lefevre [mailto:[hidden email]]
>>>>>>> Sent: samedi 3 janvier 2015 14:32
>>>>>>> To: [hidden email]
>>>>>>> Subject: Re: [Mondo-devel] Segmentation error running mondoarchive
>>>>>>> v3.2.0-r3332
>>>>>>>
>>>>>>> Hi list,
>>>>>>>
>>>>>>> Some more information about my issue.
>>>>>>>
>>>>>>> I can confirm that in my case it is related to this new release as a I did a downgrade and successfully built a new full backup.
>>>>>>>
>>>>>>> I uninstalled and purged
>>>>>>>   libmondorescue-perl_3.2.0-1_all.deb
>>>>>>>   mindi-busybox_1.21.1-1_amd64.deb
>>>>>>>   mindi_3.0.0-1_amd64.deb
>>>>>>>   mondo_3.2.0-1_amd64.deb
>>>>>>>
>>>>>>> and reinstalled the previous version
>>>>>>>   mindi-busybox 1.18.5-3
>>>>>>>   mindi 2.1.7-1
>>>>>>>   mondo 3.0.4-1
>>>>>>>
>>>>>>> I also compiled mondo 3.2.0 from sources and ran gdb against the simpliest command that raise the seg error. It shows :
>>>>>>>
>>>>>>> Starting program:
>>>>>>> /home/phl/telechargements/mondo-3.2.0/src/mondoarchive/mondoarchive -v [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
>>>>>>> mondoarchive v3.2.0-r3332
>>>>>>> See man page for help
>>>>>>>
>>>>>>> Program received signal SIGSEGV, Segmentation fault.
>>>>>>> 0x00007ffff76629aa in vfprintf () from
>>>>>>> /lib/x86_64-linux-gnu/libc.so.6
>>>>>>> (gdb) bt
>>>>>>> #0  0x00007ffff76629aa in vfprintf () from
>>>>>>> /lib/x86_64-linux-gnu/libc.so.6
>>>>>>> #1  0x00007ffff7688fca in vasprintf () from
>>>>>>> /lib/x86_64-linux-gnu/libc.so.6
>>>>>>> #2  0x00000000004367c4 in mr_asprintf_int (strp=strp@entry=0x7fffffffe0d0, line=line@entry=258, file=file@entry=0x44187f "libmondo-fork.c",
>>>>>>>     fmt=fmt@entry=0x441d38 "%s > %s/mondo-run-prog-thing.tmp 2>
>>>>>>> %s/mondo-run-prog-thing.err") at mr_mem.c:62
>>>>>>> #3  0x000000000041e0f0 in run_program_and_log_output
>>>>>>> (program=program@entry=0x43c4b4 "umount -d /mnt/cdrom",
>>>>>>> debug_level=debug_level@entry=0)
>>>>>>>     at libmondo-fork.c:258
>>>>>>> #4  0x000000000042ec19 in finish (signal=signal@entry=0) at
>>>>>>> newt-specific.c:388
>>>>>>> #5  0x0000000000403430 in main (argc=2, argv=0x7fffffffe668) at
>>>>>>> mondoarchive.c:176
>>>>>>> (gdb)
>>>>>>>
>>>>>>>
>>>>>>> function code exerpt
>>>>>>>
>>>>>>>    56 void mr_asprintf_int(char **strp, int line, const char *file, const char *fmt, ...) {
>>>>>>>    57
>>>>>>>    58 int res = 0;
>>>>>>>    59 va_list args;
>>>>>>>    60
>>>>>>>    61 va_start(args,fmt);
>>>>>>>    62 res = vasprintf(strp, fmt, args);
>>>>>>>    63 if (res == -1) {
>>>>>>>    64 mr_msg_int(1,line,file,"Unable to alloc memory in
>>>>>>> mr_asprintf\nExiting...");
>>>>>>>    65 mr_exit(-1,"Unable to alloc memory in mr_asprintf");
>>>>>>>    66 }
>>>>>>>    67 va_end(args);
>>>>>>>    68 }
>>>>>>>
>>>>>>>
>>>>>>> Breakpoint 1, mr_asprintf_int (strp=strp@entry=0x7fffffffe0d0, line=line@entry=258, file=file@entry=0x44187f "libmondo-fork.c",
>>>>>>>     fmt=fmt@entry=0x441d38 "%s > %s/mondo-run-prog-thing.tmp 2>
>>>>>>> %s/mondo-run-prog-thing.err") at mr_mem.c:56
>>>>>>> 56 void mr_asprintf_int(char **strp, int line, const char *file, const
>>>>>>> char *fmt, ...) {
>>>>>>> (gdb) s
>>>>>>> 61 va_start(args,fmt);
>>>>>>> (gdb) display fmt
>>>>>>> 1: fmt = 0x441d38 "%s > %s/mondo-run-prog-thing.tmp 2> %s/mondo-run-prog-thing.err"
>>>>>>> (gdb) display args
>>>>>>> 2: args = {{gp_offset = 4158558940, fp_offset = 32767,
>>>>>>> overflow_arg_area = 0x7ffff7fd5000, reg_save_area = 0x7ffff7ffd9d8}}
>>>>>>> (gdb) s
>>>>>>> 62 res = vasprintf(strp, fmt, args);
>>>>>>> 2: args = {{gp_offset = 4158558940, fp_offset = 32767,
>>>>>>> overflow_arg_area = 0x7ffff7fd5000, reg_save_area = 0x7ffff7ffd9d8}}
>>>>>>> 1: fmt = 0x441d38 "%s > %s/mondo-run-prog-thing.tmp 2> %s/mondo-run-prog-thing.err"
>>>>>>> (gdb) s
>>>>>>> 61 va_start(args,fmt);
>>>>>>> 2: args = {{gp_offset = 4158558940, fp_offset = 32767,
>>>>>>> overflow_arg_area = 0x7ffff7fd5000, reg_save_area = 0x7ffff7ffd9d8}}
>>>>>>> 1: fmt = 0x441d38 "%s > %s/mondo-run-prog-thing.tmp 2> %s/mondo-run-prog-thing.err"
>>>>>>> (gdb) s
>>>>>>> 62 res = vasprintf(strp, fmt, args);
>>>>>>> 2: args = {{gp_offset = 32, fp_offset = 48, overflow_arg_area =
>>>>>>> 0x7fffffffe0b0, reg_save_area = 0x7fffffffdfe0}}
>>>>>>> 1: fmt = 0x441d38 "%s > %s/mondo-run-prog-thing.tmp 2> %s/mondo-run-prog-thing.err"
>>>>>>> (gdb) display res
>>>>>>> 3: res = 0
>>>>>>> (gdb) s
>>>>>>>
>>>>>>> Program received signal SIGSEGV, Segmentation fault.
>>>>>>> 0x00007ffff76629aa in vfprintf () from
>>>>>>> /lib/x86_64-linux-gnu/libc.so.6
>>>>>>> (gdb)
>>>>>>>
>>>>>>>
>>>>>>> It seems there is an issue with mr_asprintf_int but sorry I don't feel strong enought to get more deeply into the mondo code and analyze it properly ...
>>>>>>>
>>>>>>> I hope this help ...
>>>>>>>
>>>>>>> Regards,
>>>>>>> Philippe
>>>>>>>
>>>>>>>
>>>>>>> Le 27/12/2014 11:17, [hidden email] a écrit :
>>>>>>>> Hi all,
>>>>>>>>
>>>>>>>> it seems that something goes wrong with mondo I could link to the
>>>>>>>> latest Debian version of MondoRescue.
>>>>>>>>
>>>>>>>> I updated my version last thursday and this morning (I have a
>>>>>>>> differential backup launched every friday night and one full a
>>>>>>>> month) it failed.
>>>>>>>> Unfortunately there are no much relevant informations in logs.
>>>>>>>>
>>>>>>>> The errors raised is :
>>>>>>>>
>>>>>>>>     # mondoarchive -D -OV -i -N -G -s 780M -p sys-D7.7-diff_141227100000
>>>>>>>>     -T /graveur -S /graveur -d
>>>>>>>>     /media/sauvegardes/phlsys/D7.7/sys/141227100000 -I
>>>>>>>>     "/|/|/opt/calibre|/opt/Zuma" -E
>>>>>>>>     "/bases/sybase|/graveur|/home|/opt|/photos|/quemu|/Sauvegardes|/var/crash|/var/backups|/var/log|/var/mail|/var/spool|/vbox|/videos|/www"
>>>>>>>>     See /var/log/mondoarchive.log for details of backup run.
>>>>>>>>     Checking sanity of your Linux distribution
>>>>>>>>     Done.
>>>>>>>>     Erreur de segmentation                /* Segmentation error */
>>>>>>>>
>>>>>>>> Please find attached the log files that seems to find out an issue
>>>>>>>> with LVM disks
>>>>>>>>
>>>>>>>>     INFO: Mindi v3.0.0-r3332
>>>>>>>>     INFO: Le disque /dev/mapper/data1vg-photoslv ne contient pas une
>>>>>>>>     table de partitions valable
>>>>>>>>              /* there is no valid partition table in
>>>>>>>>     /dev/mapper/data1vg-photoslv disk */
>>>>>>>>
>>>>>>>> I have no issues with my LVM disks. Please find on below my LVM
>>>>>>>> disks configuration
>>>>>>>>
>>>>>>>>     lvm> vgs
>>>>>>>>       VG      #PV #LV #SN Attr   VSize   VFree
>>>>>>>>       data1vg   1   7   0 wz--n- 931,51g 504,60g
>>>>>>>>       sysvg     1   1   0 wz--n-  95,12g  78,84g
>>>>>>>>
>>>>>>>>     lvm> lvs
>>>>>>>>       LV        VG      Attr     LSize   Pool Origin Data%  Move Log
>>>>>>>>     Copy%  Convert
>>>>>>>>       baseslv   data1vg -wi-ao--  
>>>>>>>>     1,86g                                          
>>>>>>>>       graveurlv data1vg -wi-ao--
>>>>>>>>     20,00g                                          
>>>>>>>>       homelv    data1vg -wi-ao--
>>>>>>>>     50,00g                                          
>>>>>>>>       photoslv  data1vg -wi-ao--
>>>>>>>>     70,00g                                          
>>>>>>>>       vboxlv    data1vg -wi-ao--
>>>>>>>>     130,39g                                          
>>>>>>>>       videoslv  data1vg -wi-ao--
>>>>>>>>     150,00g                                          
>>>>>>>>       wwwlv     data1vg -wi-ao--  
>>>>>>>>     4,66g                                          
>>>>>>>>       optlv     sysvg   -wi-ao--  16,28g
>>>>>>>>
>>>>>>>>     lvm> lvscan
>>>>>>>>       ACTIVE            '/dev/data1vg/photoslv' [70,00 GiB] inherit
>>>>>>>>       ACTIVE            '/dev/data1vg/videoslv' [150,00 GiB] inherit
>>>>>>>>       ACTIVE            '/dev/data1vg/homelv' [50,00 GiB] inherit
>>>>>>>>       ACTIVE            '/dev/data1vg/graveurlv' [20,00 GiB] inherit
>>>>>>>>       ACTIVE            '/dev/data1vg/wwwlv' [4,66 GiB] inherit
>>>>>>>>       ACTIVE            '/dev/data1vg/baseslv' [1,86 GiB] inherit
>>>>>>>>       ACTIVE            '/dev/data1vg/vboxlv' [130,39 GiB] inherit
>>>>>>>>       ACTIVE            '/dev/sysvg/optlv' [16,28 GiB] inherit
>>>>>>>>
>>>>>>>>     root@phlsys:/home/phl/Scripts# df -h
>>>>>>>>     Sys. fich.                                             Taille Util.
>>>>>>>>     Dispo Uti% Monté sur
>>>>>>>>     rootfs                                                    92G  
>>>>>>>>     11G   77G  12% /
>>>>>>>>     udev                                                      10M    
>>>>>>>>     0   10M   0% /dev
>>>>>>>>     tmpfs                                                    397M  968K
>>>>>>>>     396M   1% /run
>>>>>>>>     /dev/disk/by-uuid/4a5a9317-0b70-4796-a094-d61c01891c81    92G  
>>>>>>>>     11G   77G  12% /
>>>>>>>>     tmpfs                                                    5,0M     0
>>>>>>>>     5,0M   0% /run/lock
>>>>>>>>     tmpfs                                                    985M  324K
>>>>>>>>     985M   1% /run/shm
>>>>>>>>     /dev/mapper/sysvg-optlv                                   17G   15G
>>>>>>>>     845M  95% /opt
>>>>>>>>     /dev/mapper/data1vg-homelv                                50G   40G
>>>>>>>>     7,2G  85% /home
>>>>>>>>     /dev/mapper/data1vg-wwwlv                                4,6G  2,5G
>>>>>>>>     1,9G  58% /www
>>>>>>>>     /dev/mapper/data1vg-baseslv                              1,9G  720M
>>>>>>>>     1,1G  41% /bases
>>>>>>>>     /dev/mapper/data1vg-photoslv                              69G  
>>>>>>>>     43G   23G  66% /photos
>>>>>>>>     /dev/mapper/data1vg-videoslv                             148G
>>>>>>>>     104G   37G  74% /videos
>>>>>>>>     /dev/mapper/data1vg-vboxlv                               129G
>>>>>>>>     100G   23G  82% /vbox
>>>>>>>>     /dev/mapper/data1vg-graveurlv                             20G
>>>>>>>>     8,1G   11G  44% /graveur
>>>>>>>>
>>>>>>>>
>>>>>>>> The latest mondo upgrade dated of 25th of december was (it worked
>>>>>>>> fine before this upgrade)
>>>>>>>>
>>>>>>>>     Start-Date: 2014-12-25  18:55:08
>>>>>>>>     Commandline: /usr/sbin/synaptic
>>>>>>>>     Install: libprojectbuilder-perl:amd64 (0.12.6-1, automatic),
>>>>>>>>     libmondorescue-perl:amd64 (3.2.0-1, automatic)
>>>>>>>>     Upgrade: mindi:amd64 (2.1.7-1, 3.0.0-1), mondo:amd64 (3.0.4-1,
>>>>>>>>     3.2.0-1), mindi-busybox:amd64 (1.18.5-3, 1.21.1-1)
>>>>>>>>     End-Date: 2014-12-25  18:55:31
>>>>>>>>
>>>>>>>> The Debian distro used is
>>>>>>>>
>>>>>>>>     root@phlsys:/home/phl/Scripts# uname -a
>>>>>>>>     Linux phlsys 3.2.0-4-amd64 #1 SMP Debian 3.2.63-2+deb7u2 x86_64
>>>>>>>>     GNU/Linux
>>>>>>>>
>>>>>>>> Anyone have an idea to try to debug this.
>>>>>>>>
>>>>>>>> Thanks for any help.
>>>>>>>>
>>>>>>>> By the way, I whish you all an happy new year 2015 with all the best
>>>>>>>> in your lifes Kind regards, Philippe
>>>>>>>>
>>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> ---------------------------------------------------------------------
>>>>>>> -
>>>>>>> -------- Dive into the World of Parallel Programming! The Go Parallel
>>>>>>> Website, sponsored by Intel and developed in partnership with
>>>>>>> Slashdot Media, is your hub for all things parallel software
>>>>>>> development, from weekly thought leadership blogs to news, videos,
>>>>>>> case studies, tutorials and more. Take a look and join the conversation now.
>>>>>>> http://goparallel.sourceforge.net
>>>>>>> _______________________________________________
>>>>>>> Mondo-devel mailing list
>>>>>>> [hidden email]
>>>>>>> https://lists.sourceforge.net/lists/listinfo/mondo-devel
>>>>>>> ---------------------------------------------------------------------
>>>>>>> -
>>>>>>> -------- Dive into the World of Parallel Programming! The Go Parallel
>>>>>>> Website, sponsored by Intel and developed in partnership with
>>>>>>> Slashdot Media, is your hub for all things parallel software
>>>>>>> development, from weekly thought leadership blogs to news, videos,
>>>>>>> case studies, tutorials and more. Take a look and join the conversation now.
>>>>>>> http://goparallel.sourceforge.net
>>>>>>> _______________________________________________
>>>>>>> Mondo-devel mailing list
>>>>>>> [hidden email]
>>>>>>> https://lists.sourceforge.net/lists/listinfo/mondo-devel
>>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> ----------------------------------------------------------------------
>>>>>> -------- Dive into the World of Parallel Programming! The Go Parallel
>>>>>> Website, sponsored by Intel and developed in partnership with Slashdot
>>>>>> Media, is your hub for all things parallel software development, from
>>>>>> weekly thought leadership blogs to news, videos, case studies,
>>>>>> tutorials and more. Take a look and join the conversation now.
>>>>>> http://goparallel.sourceforge.net 
>>>>>> _______________________________________________
>>>>>> Mondo-devel mailing list
>>>>>> [hidden email]
>>>>>> https://lists.sourceforge.net/lists/listinfo/mondo-devel
>>>>>> ----------------------------------------------------------------------
>>>>>> -------- Dive into the World of Parallel Programming! The Go Parallel
>>>>>> Website, sponsored by Intel and developed in partnership with Slashdot
>>>>>> Media, is your hub for all things parallel software development, from
>>>>>> weekly thought leadership blogs to news, videos, case studies,
>>>>>> tutorials and more. Take a look and join the conversation now.
>>>>>> http://goparallel.sourceforge.net 
>>>>>> _______________________________________________
>>>>>> Mondo-devel mailing list
>>>>>> [hidden email]
>>>>>> https://lists.sourceforge.net/lists/listinfo/mondo-devel
>>>>>>
>>>>>
>>>>>
>>>>> ------------------------------------------------------------------------------
>>>>> New Year. New Location. New Benefits. New Data Center in Ashburn, VA.
>>>>> GigeNET is offering a free month of service with a new server in Ashburn.
>>>>> Choose from 2 high performing configs, both with 100TB of bandwidth.
>>>>> Higher redundancy.Lower latency.Increased capacity.Completely compliant.
>>>>> http://p.sf.net/sfu/gigenet
>>>>> _______________________________________________
>>>>> Mondo-devel mailing list
>>>>> [hidden email]
>>>>> https://lists.sourceforge.net/lists/listinfo/mondo-devel
>>>>>
>>>>
>>>>
>>>
>>>> mindi v3.0.0-r3332
>>>> x86_64 architecture detected
>>>> mindi called with the following arguments:
>>>> --makemountlist /tmp/mondo.tmp.4v41Vd/mountlist.txt.test
>>>> Start date : lundi 19 janvier 2015, 22:16:43 (UTC+0100)
>>>> -----------------------------
>>>> MONDO_SHARE = /usr/share/mondo
>>>> MINDI_LIB = /usr/lib/mindi
>>>> MINDI_SBIN = /usr/sbin
>>>> MINDI_CONF = /etc/mindi
>>>> -----------------------------
>>>>  Mindi configuration file    
>>>> -----------------------------
>>>> -----------------------------
>>>> In Mindi
>>>> --------
>>>> EXTRA_SPACE = 120000
>>>> BOOT_SIZE = 65600
>>>> --------
>>>> INFO: Found isolinux.bin at /usr/lib/syslinux/isolinux.bin
>>>> INFO: LVM set to v2
>>>> ----------
>>>> mount result:
>>>> -------------
>>>> sysfs on /sys type sysfs (rw,nosuid,nodev,noexec,relatime)
>>>> proc on /proc type proc (rw,nosuid,nodev,noexec,relatime)
>>>> udev on /dev type devtmpfs (rw,relatime,size=10240k,nr_inodes=497709,mode=755)
>>>> devpts on /dev/pts type devpts (rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000)
>>>> tmpfs on /run type tmpfs (rw,nosuid,noexec,relatime,size=406288k,mode=755)
>>>> /dev/disk/by-uuid/4a5a9317-0b70-4796-a094-d61c01891c81 on / type ext4 (rw,relatime,errors=remount-ro,user_xattr,barrier=1,data=ordered)
>>>> tmpfs on /run/lock type tmpfs (rw,nosuid,nodev,noexec,relatime,size=5120k)
>>>> tmpfs on /run/shm type tmpfs (rw,nosuid,nodev,noexec,relatime,size=1008560k)
>>>> /dev/mapper/sysvg-optlv on /opt type ext4 (rw,relatime,errors=remount-ro,user_xattr,barrier=1,data=ordered)
>>>> /dev/mapper/data1vg-homelv on /home type ext4 (rw,relatime,errors=remount-ro,user_xattr,barrier=1,data=ordered)
>>>> /dev/mapper/data1vg-wwwlv on /www type ext4 (rw,relatime,errors=remount-ro,user_xattr,barrier=1,data=ordered)
>>>> /dev/mapper/data1vg-baseslv on /bases type ext4 (rw,relatime,errors=remount-ro,user_xattr,barrier=1,data=ordered)
>>>> /dev/mapper/data1vg-photoslv on /photos type ext4 (rw,relatime,errors=remount-ro,user_xattr,barrier=1,data=ordered)
>>>> /dev/mapper/data1vg-videoslv on /videos type ext4 (rw,relatime,errors=remount-ro,user_xattr,barrier=1,data=ordered)
>>>> /dev/mapper/data1vg-vboxlv on /vbox type ext4 (rw,relatime,errors=remount-ro,user_xattr,barrier=1,data=ordered)
>>>> /dev/mapper/data1vg-graveurlv on /graveur type ext4 (rw,relatime,errors=remount-ro,user_xattr,barrier=1,data=ordered)
>>>> rpc_pipefs on /var/lib/nfs/rpc_pipefs type rpc_pipefs (rw,relatime)
>>>> binfmt_misc on /proc/sys/fs/binfmt_misc type binfmt_misc (rw,nosuid,nodev,noexec,relatime)
>>>> No file /etc/raidtab
>>>> -------------
>>>> No file /etc/mdadm.conf
>>>> -------------
>>>> cat /proc/cmdline
>>>> -------------
>>>> BOOT_IMAGE=/boot/vmlinuz-3.2.0-4-amd64 root=UUID=4a5a9317-0b70-4796-a094-d61c01891c81 ro quiet
>>>> -------------
>>>> cat /proc/swaps:
>>>> -------------
>>>> Filename Type Size Used Priority
>>>> /dev/sda6                               partition 979928 11992 -1
>>>> -------------
>>>> cat /proc/mdstat:
>>>> -------------
>>>> Personalities : [linear] [raid0] [raid1] [raid6] [raid5] [raid4]
>>>> unused devices: <none>
>>>> -------------
>>>> cat /proc/partitions:
>>>> -------------
>>>> major minor  #blocks  name
>>>>
>>>>    8        0  312571224 sda
>>>>    8        1      56196 sda1
>>>>    8        2   10485760 sda2
>>>>    8        3  103643080 sda3
>>>>    8        4          1 sda4
>>>>    8        5   97659103 sda5
>>>>    8        6     979933 sda6
>>>>    8        7   99741696 sda7
>>>>   11        0    1048575 sr0
>>>>    8       16  976762584 sdb
>>>>    8       17  976761560 sdb1
>>>>  253        0   73400320 dm-0
>>>>  253        1  157286400 dm-1
>>>>  253        2   52428800 dm-2
>>>>  253        3   20971520 dm-3
>>>>  253        4    4886528 dm-4
>>>>  253        5    1953792 dm-5
>>>>  253        6  136720384 dm-6
>>>>  253        7   17072128 dm-7
>>>> -------------
>>>> cat /proc/filesystems:
>>>> -------------
>>>> nodev sysfs
>>>> nodev rootfs
>>>> nodev bdev
>>>> nodev proc
>>>> nodev cgroup
>>>> nodev cpuset
>>>> nodev tmpfs
>>>> nodev devtmpfs
>>>> nodev debugfs
>>>> nodev securityfs
>>>> nodev sockfs
>>>> nodev pipefs
>>>> nodev anon_inodefs
>>>> nodev devpts
>>>> nodev ramfs
>>>> nodev hugetlbfs
>>>> nodev pstore
>>>> nodev mqueue
>>>> nodev usbfs
>>>> ext4
>>>> nodev ecryptfs
>>>> nodev rpc_pipefs
>>>> nodev nfs
>>>> nodev nfs4
>>>> nodev nfsd
>>>> nodev binfmt_misc
>>>> msdos
>>>> vfat
>>>> iso9660
>>>> ext2
>>>> -------------
>>>> lsmod result:
>>>> -------------
>>>> Module                  Size  Used by
>>>> nls_utf8               12456  0
>>>> nls_cp437              16553  0
>>>> ext2                   59231  0
>>>> raid456                48453  0
>>>> async_raid6_recov      12574  1 raid456
>>>> async_memcpy           12387  2 async_raid6_recov,raid456
>>>> async_pq               12605  2 async_raid6_recov,raid456
>>>> raid6_pq               82624  2 async_pq,async_raid6_recov
>>>> async_xor              12422  3 async_pq,async_raid6_recov,raid456
>>>> xor                    12605  1 async_xor
>>>> async_tx               12604  5 async_xor,async_pq,async_memcpy,async_raid6_recov,raid456
>>>> raid1                  30714  0
>>>> raid0                  12904  0
>>>> linear                 12735  0
>>>> isofs                  35173  0
>>>> brd                    12772  0
>>>> vfat                   17316  0
>>>> msdos                  17077  0
>>>> fat                    45642  2 msdos,vfat
>>>> pci_stub               12429  1
>>>> vboxpci                19096  0
>>>> vboxnetadp             25443  0
>>>> vboxnetflt             23657  0
>>>> vboxdrv               304550  3 vboxnetflt,vboxnetadp,vboxpci
>>>> nfnetlink_log          17212  0
>>>> nfnetlink              12906  1 nfnetlink_log
>>>> parport_pc             22364  0
>>>> ppdev                  12763  0
>>>> lp                     17149  0
>>>> parport                31858  3 lp,ppdev,parport_pc
>>>> ip6t_REJECT            12512  2
>>>> xt_multiport           12548  2
>>>> xt_conntrack           12681  18
>>>> iptable_nat            12928  0
>>>> binfmt_misc            12957  1
>>>> iptable_mangle         12536  0
>>>> nfsd                  216181  2
>>>> nfs                   308353  0
>>>> nfs_acl                12511  2 nfs,nfsd
>>>> auth_rpcgss            37143  2 nfs,nfsd
>>>> fscache                36739  1 nfs
>>>> lockd                  67306  2 nfs,nfsd
>>>> sunrpc                173730  6 lockd,auth_rpcgss,nfs_acl,nfs,nfsd
>>>> ip6t_LOG               12609  4
>>>> xt_hl                  12449  6
>>>> ip6t_rt                12499  3
>>>> nf_conntrack_ipv6      13316  7
>>>> nf_defrag_ipv6         12832  1 nf_conntrack_ipv6
>>>> ipt_REJECT             12502  1
>>>> ipt_LOG                12605  12
>>>> xt_limit               12638  19
>>>> xt_tcpudp              12570  62
>>>> xt_addrtype            12557  4
>>>> xt_state               12503  21
>>>> ip6table_filter        12540  1
>>>> ip6_tables             22175  3 ip6table_filter,ip6t_rt,ip6t_LOG
>>>> nf_conntrack_netbios_ns    12445  0
>>>> nf_conntrack_broadcast    12365  1 nf_conntrack_netbios_ns
>>>> nf_nat_ftp             12460  0
>>>> nf_nat                 18242  2 nf_nat_ftp,iptable_nat
>>>> nf_conntrack_ipv4      14078  35 nf_nat,iptable_nat
>>>> nf_defrag_ipv4         12483  1 nf_conntrack_ipv4
>>>> nf_conntrack_ftp       12605  1 nf_nat_ftp
>>>> nf_conntrack           52720  10 nf_conntrack_ftp,nf_conntrack_ipv4,nf_nat,nf_nat_ftp,nf_conntrack_broadcast,nf_conntrack_netbios_ns,xt_state,nf_conntrack_ipv6,iptable_nat,xt_conntrack
>>>> iptable_filter         12536  1
>>>> ip_tables              22042  3 iptable_filter,iptable_mangle,iptable_nat
>>>> x_tables               19118  18 ip_tables,iptable_filter,ip6_tables,ip6table_filter,xt_state,xt_addrtype,xt_tcpudp,xt_limit,ipt_LOG,ipt_REJECT,ip6t_rt,xt_hl,ip6t_LOG,iptable_mangle,iptable_nat,xt_conntrack,xt_multiport,ip6t_REJECT
>>>> loop                   22641  0
>>>> ecryptfs               81507  0
>>>> dm_crypt               22586  0
>>>> snd_hda_codec_hdmi     30824  1
>>>> snd_usb_audio          89083  2
>>>> snd_usbmidi_lib        23369  1 snd_usb_audio
>>>> snd_seq_midi           12848  0
>>>> snd_seq_midi_event     13316  1 snd_seq_midi
>>>> snd_rawmidi            23060  2 snd_seq_midi,snd_usbmidi_lib
>>>> snd_hda_codec_idt      53792  1
>>>> tuner_simple           17175  1
>>>> tuner_types            16409  1 tuner_simple
>>>> wm8775                 12749  1
>>>> tda9887                12645  1
>>>> tda8290                17278  0
>>>> tuner                  17497  2
>>>> cx25840                39782  1
>>>> ivtv                  129010  0
>>>> cx2341x                21461  1 ivtv
>>>> snd_hda_intel          26259  2
>>>> snd_hda_codec          78031  3 snd_hda_intel,snd_hda_codec_idt,snd_hda_codec_hdmi
>>>> snd_hwdep              13186  2 snd_hda_codec,snd_usb_audio
>>>> snd_pcm                68083  4 snd_hda_codec,snd_hda_intel,snd_usb_audio,snd_hda_codec_hdmi
>>>> tveeprom               20593  1 ivtv
>>>> v4l2_common            13222  5 cx2341x,ivtv,cx25840,tuner,wm8775
>>>> videodev               70889  6 v4l2_common,cx2341x,ivtv,cx25840,tuner,wm8775
>>>> v4l2_compat_ioctl32    16655  1 videodev
>>>> media                  18148  1 videodev
>>>> nv_tco                 12914  0
>>>> i2c_algo_bit           12841  1 ivtv
>>>> snd_page_alloc         13003  2 snd_pcm,snd_hda_intel
>>>> snd_seq                45126  2 snd_seq_midi_event,snd_seq_midi
>>>> snd_seq_device         13176  3 snd_seq,snd_rawmidi,snd_seq_midi
>>>> i2c_nforce2            12584  0
>>>> dcdbas                 13307  0
>>>> edac_mce_amd           17103  0
>>>> edac_core              35258  0
>>>> evdev                  17562  18
>>>> powernow_k8            17618  1
>>>> mperf                  12453  1 powernow_k8
>>>> k8temp                 12647  0
>>>> psmouse                69265  0
>>>> snd_timer              22917  2 snd_seq,snd_pcm
>>>> i2c_core               23876  12 i2c_nforce2,i2c_algo_bit,videodev,v4l2_common,tveeprom,ivtv,cx25840,tuner,tda8290,tda9887,wm8775,tuner_simple
>>>> serio_raw              12931  0
>>>> fglrx                2634136  183
>>>> pcspkr                 12579  0
>>>> snd                    52893  20 snd_timer,snd_seq_device,snd_seq,snd_pcm,snd_hwdep,snd_hda_codec,snd_hda_intel,snd_hda_codec_idt,snd_rawmidi,snd_usbmidi_lib,snd_usb_audio,snd_hda_codec_hdmi
>>>> processor              28149  1 powernow_k8
>>>> button                 12937  1 fglrx
>>>> soundcore              13065  1 snd
>>>> thermal_sys            18040  1 processor
>>>> ext4                  350804  9
>>>> crc16                  12343  1 ext4
>>>> jbd2                   62115  1 ext4
>>>> mbcache                13114  2 ext4,ext2
>>>> dm_mod                 63645  29 dm_crypt
>>>> md_mod                 87742  4 linear,raid0,raid1,raid456
>>>> sg                     25874  0
>>>> sd_mod                 36136  6
>>>> sr_mod                 21899  0
>>>> cdrom                  35401  1 sr_mod
>>>> crc_t10dif             12348  1 sd_mod
>>>> usbhid                 36418  0
>>>> hid                    81372  1 usbhid
>>>> usb_storage            43870  0
>>>> ata_generic            12479  0
>>>> ohci_hcd               26563  0
>>>> sata_nv                26690  4
>>>> libata                140630  2 sata_nv,ata_generic
>>>> ehci_hcd               40249  0
>>>> b44                    27751  0
>>>> ssb                    44714  1 b44
>>>> mmc_core               68400  1 ssb
>>>> mii                    12675  1 b44
>>>> pcmcia                 32734  1 ssb
>>>> pcmcia_core            18294  1 pcmcia
>>>> scsi_mod              162321  5 libata,usb_storage,sr_mod,sd_mod,sg
>>>> usbcore               128741  7 ehci_hcd,ohci_hcd,usb_storage,usbhid,snd_usbmidi_lib,snd_usb_audio
>>>> usb_common             12354  1 usbcore
>>>> -------------
>>>> FORCE_MODS:
>>>> -------------
>>>>
>>>> -------------
>>>> DENY_MODS:
>>>> -------------
>>>> kqemu vxfen
>>>> -------------
>>>> df result:
>>>> ----------
>>>> Sys. fich.                                             Type        1K-blocks     Util. Disponible Uti% Mont?? sur
>>>> rootfs                                                 rootfs       96124904  10822540   80419412  12% /
>>>> sysfs                                                  sysfs               0         0          0    - /sys
>>>> proc                                                   proc                0         0          0    - /proc
>>>> udev                                                   devtmpfs        10240         0      10240   0% /dev
>>>> devpts                                                 devpts              0         0          0    - /dev/pts
>>>> tmpfs                                                  tmpfs          406288       944     405344   1% /run
>>>> /dev/disk/by-uuid/4a5a9317-0b70-4796-a094-d61c01891c81 ext4         96124904  10822540   80419412  12% /
>>>> tmpfs                                                  tmpfs            5120         0       5120   0% /run/lock
>>>> tmpfs                                                  tmpfs         1008560       276    1008284   1% /run/shm
>>>> /dev/mapper/sysvg-optlv                                ext4         16803708  15010400     939704  95% /opt
>>>> /dev/mapper/data1vg-homelv                             ext4         51606140  41866076    7119008  86% /home
>>>> /dev/mapper/data1vg-wwwlv                              ext4          4809704   2794384    1770996  62% /www
>>>> /dev/mapper/data1vg-baseslv                            ext4          1923084    737276    1088120  41% /bases
>>>> /dev/mapper/data1vg-photoslv                           ext4         72248648  45036992   23541896  66% /photos
>>>> /dev/mapper/data1vg-videoslv                           ext4        154818540 108302512   38651708  74% /videos
>>>> /dev/mapper/data1vg-vboxlv                             ext4        134573320 104068176   23669128  82% /vbox
>>>> /dev/mapper/data1vg-graveurlv                          ext4         20642428   8094972   11498880  42% /graveur
>>>> rpc_pipefs                                             rpc_pipefs          0         0          0    - /var/lib/nfs/rpc_pipefs
>>>> binfmt_misc                                            binfmt_misc         0         0          0    - /proc/sys/fs/binfmt_misc
>>>> -------------
>>>> df -i result:
>>>> ----------
>>>> Sys. fich.                                              Inodes IUtil.  ILibre IUti% Mont?? sur
>>>> rootfs                                                 6111232 313566 5797666    6% /
>>>> udev                                                    497709    610  497099    1% /dev
>>>> tmpfs                                                   507860    667  507193    1% /run
>>>> /dev/disk/by-uuid/4a5a9317-0b70-4796-a094-d61c01891c81 6111232 313566 5797666    6% /
>>>> tmpfs                                                   507860      3  507857    1% /run/lock
>>>> tmpfs                                                   507860     15  507845    1% /run/shm
>>>> /dev/mapper/sysvg-optlv                                1068960  54781 1014179    6% /opt
>>>> /dev/mapper/data1vg-homelv                             3276800  83092 3193708    3% /home
>>>> /dev/mapper/data1vg-wwwlv                               305824  43214  262610   15% /www
>>>> /dev/mapper/data1vg-baseslv                             122160   1213  120947    1% /bases
>>>> /dev/mapper/data1vg-photoslv                           4587520  23609 4563911    1% /photos
>>>> /dev/mapper/data1vg-videoslv                           9830400    180 9830220    1% /videos
>>>> /dev/mapper/data1vg-vboxlv                             8552448     91 8552357    1% /vbox
>>>> /dev/mapper/data1vg-graveurlv                          1310720     80 1310640    1% /graveur
>>>> -------------
>>>> -------------
>>>> INFO: /boot/grub/grub.cfg content
>>>> -------------
>>>> #
>>>> # DO NOT EDIT THIS FILE
>>>> #
>>>> # It is automatically generated by grub-mkconfig using templates
>>>> # from /etc/grub.d and settings from /etc/default/grub
>>>> #
>>>>
>>>> ### BEGIN /etc/grub.d/00_header ###
>>>> if [ -s $prefix/grubenv ]; then
>>>>   load_env
>>>> fi
>>>> set default="0"
>>>> if [ "${prev_saved_entry}" ]; then
>>>>   set saved_entry="${prev_saved_entry}"
>>>>   save_env saved_entry
>>>>   set prev_saved_entry=
>>>>   save_env prev_saved_entry
>>>>   set boot_once=true
>>>> fi
>>>>
>>>> function savedefault {
>>>>   if [ -z "${boot_once}" ]; then
>>>>     saved_entry="${chosen}"
>>>>     save_env saved_entry
>>>>   fi
>>>> }
>>>>
>>>> function load_video {
>>>>   insmod vbe
>>>>   insmod vga
>>>>   insmod video_bochs
>>>>   insmod video_cirrus
>>>> }
>>>>
>>>> insmod part_msdos
>>>> insmod ext2
>>>> set root='(hd0,msdos5)'
>>>> search --no-floppy --fs-uuid --set=root 4a5a9317-0b70-4796-a094-d61c01891c81
>>>> if loadfont /usr/share/grub/unicode.pf2 ; then
>>>>   set gfxmode=640x480
>>>>   load_video
>>>>   insmod gfxterm
>>>>   insmod part_msdos
>>>>   insmod ext2
>>>>   set root='(hd0,msdos5)'
>>>>   search --no-floppy --fs-uuid --set=root 4a5a9317-0b70-4796-a094-d61c01891c81
>>>>   set locale_dir=($root)/boot/grub/locale
>>>>   set lang=fr_FR
>>>>   insmod gettext
>>>> fi
>>>> terminal_output gfxterm
>>>> set timeout=5
>>>> ### END /etc/grub.d/00_header ###
>>>>
>>>> ### BEGIN /etc/grub.d/05_debian_theme ###
>>>> insmod part_msdos
>>>> insmod ext2
>>>> set root='(hd0,msdos5)'
>>>> search --no-floppy --fs-uuid --set=root 4a5a9317-0b70-4796-a094-d61c01891c81
>>>> insmod png
>>>> if background_image /usr/share/images/desktop-base/joy-grub.png; then
>>>>   set color_normal=white/black
>>>>   set color_highlight=black/white
>>>> else
>>>>   set menu_color_normal=cyan/blue
>>>>   set menu_color_highlight=white/blue
>>>> fi
>>>> ### END /etc/grub.d/05_debian_theme ###
>>>>
>>>> ### BEGIN /etc/grub.d/10_linux ###
>>>> menuentry 'Debian GNU/Linux, avec Linux 3.2.0-4-amd64' --class debian --class gnu-linux --class gnu --class os {
>>>> load_video
>>>> insmod gzio
>>>> insmod part_msdos
>>>> insmod ext2
>>>> set root='(hd0,msdos5)'
>>>> search --no-floppy --fs-uuid --set=root 4a5a9317-0b70-4796-a094-d61c01891c81
>>>> echo 'Chargement de Linux 3.2.0-4-amd64 ...'
>>>> linux /boot/vmlinuz-3.2.0-4-amd64 root=UUID=4a5a9317-0b70-4796-a094-d61c01891c81 ro  quiet
>>>> echo 'Chargement du disque m??moire initial ...'
>>>> initrd /boot/initrd.img-3.2.0-4-amd64
>>>> }
>>>> menuentry 'Debian GNU/Linux, avec Linux 3.2.0-4-amd64 (mode de d??pannage)' --class debian --class gnu-linux --class gnu --class os {
>>>> load_video
>>>> insmod gzio
>>>> insmod part_msdos
>>>> insmod ext2
>>>> set root='(hd0,msdos5)'
>>>> search --no-floppy --fs-uuid --set=root 4a5a9317-0b70-4796-a094-d61c01891c81
>>>> echo 'Chargement de Linux 3.2.0-4-amd64 ...'
>>>> linux /boot/vmlinuz-3.2.0-4-amd64 root=UUID=4a5a9317-0b70-4796-a094-d61c01891c81 ro single
>>>> echo 'Chargement du disque m??moire initial ...'
>>>> initrd /boot/initrd.img-3.2.0-4-amd64
>>>> }
>>>> ### END /etc/grub.d/10_linux ###
>>>>
>>>> ### BEGIN /etc/grub.d/20_linux_xen ###
>>>> ### END /etc/grub.d/20_linux_xen ###
>>>>
>>>> ### BEGIN /etc/grub.d/20_memtest86+ ###
>>>> menuentry "Memory test (memtest86+)" {
>>>> insmod part_msdos
>>>> insmod ext2
>>>> set root='(hd0,msdos5)'
>>>> search --no-floppy --fs-uuid --set=root 4a5a9317-0b70-4796-a094-d61c01891c81
>>>> linux16 /boot/memtest86+.bin
>>>> }
>>>> menuentry "Memory test (memtest86+, serial console 115200)" {
>>>> insmod part_msdos
>>>> insmod ext2
>>>> set root='(hd0,msdos5)'
>>>> search --no-floppy --fs-uuid --set=root 4a5a9317-0b70-4796-a094-d61c01891c81
>>>> linux16 /boot/memtest86+.bin console=ttyS0,115200n8
>>>> }
>>>> menuentry "Memory test (memtest86+, experimental multiboot)" {
>>>> insmod part_msdos
>>>> insmod ext2
>>>> set root='(hd0,msdos5)'
>>>> search --no-floppy --fs-uuid --set=root 4a5a9317-0b70-4796-a094-d61c01891c81
>>>> multiboot /boot/memtest86+_multiboot.bin
>>>> }
>>>> menuentry "Memory test (memtest86+, serial console 115200, experimental multiboot)" {
>>>> insmod part_msdos
>>>> insmod ext2
>>>> set root='(hd0,msdos5)'
>>>> search --no-floppy --fs-uuid --set=root 4a5a9317-0b70-4796-a094-d61c01891c81
>>>> multiboot /boot/memtest86+_multiboot.bin console=ttyS0,115200n8
>>>> }
>>>> ### END /etc/grub.d/20_memtest86+ ###
>>>>
>>>> ### BEGIN /etc/grub.d/30_os-prober ###
>>>> menuentry "Windows Vista (loader) (on /dev/sda3)" --class windows --class os {
>>>> insmod part_msdos
>>>> insmod ntfs
>>>> set root='(hd0,msdos3)'
>>>> search --no-floppy --fs-uuid --set=root 0C6CE0BA6CE0A026
>>>> chainloader +1
>>>> }
>>>> ### END /etc/grub.d/30_os-prober ###
>>>>
>>>> ### BEGIN /etc/grub.d/40_custom ###
>>>> # This file provides an easy way to add custom menu entries.  Simply type the
>>>> # menu entries you want to add after this comment.  Be careful not to change
>>>> # the 'exec tail' line above.
>>>> ### END /etc/grub.d/40_custom ###
>>>>
>>>> ### BEGIN /etc/grub.d/41_custom ###
>>>> if [ -f  $prefix/custom.cfg ]; then
>>>>   source $prefix/custom.cfg;
>>>> fi
>>>> ### END /etc/grub.d/41_custom ###
>>>> -------------
>>>> -------------
>>>> INFO: /boot/grub/device.map content
>>>> -------------
>>>> (hd0) /dev/disk/by-id/ata-ST3320620AS_5QF2VWM8
>>>> -------------
>>>> Full fdisk info
>>>> ---------------
>>>>
>>>> Disque /dev/sda??: 320.1??Go, 320072933376??octets
>>>> 255??t??tes, 63??secteurs/piste, 38913??cylindres, total 625142448??secteurs
>>>> Unit??s = secteurs de 1 * 512 = 512??octets
>>>> Taille de secteur (logique / physique)??: 512??octets / 512??octets
>>>> taille d'E/S (minimale / optimale)??: 512??octets / 512??octets
>>>> Identifiant de disque??: 0x58000000
>>>>
>>>> P??riph??rique Amorce  D??but        Fin      Blocs     Id  Syst??me
>>>> /dev/sda1              63      112454       56196   de  Dell Utility
>>>> /dev/sda2          112640    21084159    10485760    7  HPFS/NTFS/exFAT
>>>> /dev/sda3   *    21093345   228379505   103643080+   7  HPFS/NTFS/exFAT
>>>> /dev/sda4       228380101   625141759   198380829+   5  ??tendue
>>>> /dev/sda5       228380103   423698309    97659103+  83  Linux
>>>> /dev/sda6       423698373   425658239      979933+  82  partition d'??change Linux / Solaris
>>>> /dev/sda7       425658368   625141759    99741696   8e  LVM Linux
>>>>
>>>> Disque /dev/sdb??: 1000.2??Go, 1000204886016??octets
>>>> 81??t??tes, 63??secteurs/piste, 382818??cylindres, total 1953525168??secteurs
>>>> Unit??s = secteurs de 1 * 512 = 512??octets
>>>> Taille de secteur (logique / physique)??: 512??octets / 512??octets
>>>> taille d'E/S (minimale / optimale)??: 512??octets / 512??octets
>>>> Identifiant de disque??: 0x0003513f
>>>>
>>>> P??riph??rique Amorce  D??but        Fin      Blocs     Id  Syst??me
>>>> /dev/sdb1            2048  1953525167   976761560   8e  LVM Linux
>>>>
>>>> Disque /dev/mapper/data1vg-photoslv??: 75.2??Go, 75161927680??octets
>>>> 255??t??tes, 63??secteurs/piste, 9137??cylindres, total 146800640??secteurs
>>>> Unit??s = secteurs de 1 * 512 = 512??octets
>>>> Taille de secteur (logique / physique)??: 512??octets / 512??octets
>>>> taille d'E/S (minimale / optimale)??: 512??octets / 512??octets
>>>> Identifiant de disque??: 0x00000000
>>>>
>>>>
>>>> Disque /dev/mapper/data1vg-videoslv??: 161.1??Go, 161061273600??octets
>>>> 255??t??tes, 63??secteurs/piste, 19581??cylindres, total 314572800??secteurs
>>>> Unit??s = secteurs de 1 * 512 = 512??octets
>>>> Taille de secteur (logique / physique)??: 512??octets / 512??octets
>>>> taille d'E/S (minimale / optimale)??: 512??octets / 512??octets
>>>> Identifiant de disque??: 0x00000000
>>>>
>>>>
>>>> Disque /dev/mapper/data1vg-homelv??: 53.7??Go, 53687091200??octets
>>>> 255??t??tes, 63??secteurs/piste, 6527??cylindres, total 104857600??secteurs
>>>> Unit??s = secteurs de 1 * 512 = 512??octets
>>>> Taille de secteur (logique / physique)??: 512??octets / 512??octets
>>>> taille d'E/S (minimale / optimale)??: 512??octets / 512??octets
>>>> Identifiant de disque??: 0x00000000
>>>>
>>>>
>>>> Disque /dev/mapper/data1vg-graveurlv??: 21.5??Go, 21474836480??octets
>>>> 255??t??tes, 63??secteurs/piste, 2610??cylindres, total 41943040??secteurs
>>>> Unit??s = secteurs de 1 * 512 = 512??octets
>>>> Taille de secteur (logique / physique)??: 512??octets / 512??octets
>>>> taille d'E/S (minimale / optimale)??: 512??octets / 512??octets
>>>> Identifiant de disque??: 0x00000000
>>>>
>>>>
>>>> Disque /dev/mapper/data1vg-wwwlv??: 5003??Mo, 5003804672??octets
>>>> 255??t??tes, 63??secteurs/piste, 608??cylindres, total 9773056??secteurs
>>>> Unit??s = secteurs de 1 * 512 = 512??octets
>>>> Taille de secteur (logique / physique)??: 512??octets / 512??octets
>>>> taille d'E/S (minimale / optimale)??: 512??octets / 512??octets
>>>> Identifiant de disque??: 0x00000000
>>>>
>>>>
>>>> Disque /dev/mapper/data1vg-baseslv??: 2000??Mo, 2000683008??octets
>>>> 255??t??tes, 63??secteurs/piste, 243??cylindres, total 3907584??secteurs
>>>> Unit??s = secteurs de 1 * 512 = 512??octets
>>>> Taille de secteur (logique / physique)??: 512??octets / 512??octets
>>>> taille d'E/S (minimale / optimale)??: 512??octets / 512??octets
>>>> Identifiant de disque??: 0x00000000
>>>>
>>>>
>>>> Disque /dev/mapper/data1vg-vboxlv??: 140.0??Go, 140001673216??octets
>>>> 255??t??tes, 63??secteurs/piste, 17020??cylindres, total 273440768??secteurs
>>>> Unit??s = secteurs de 1 * 512 = 512??octets
>>>> Taille de secteur (logique / physique)??: 512??octets / 512??octets
>>>> taille d'E/S (minimale / optimale)??: 512??octets / 512??octets
>>>> Identifiant de disque??: 0x00000000
>>>>
>>>>
>>>> Disque /dev/mapper/sysvg-optlv??: 17.5??Go, 17481859072??octets
>>>> 255??t??tes, 63??secteurs/piste, 2125??cylindres, total 34144256??secteurs
>>>> Unit??s = secteurs de 1 * 512 = 512??octets
>>>> Taille de secteur (logique / physique)??: 512??octets / 512??octets
>>>> taille d'E/S (minimale / optimale)??: 512??octets / 512??octets
>>>> Identifiant de disque??: 0x00000000
>>>>
>>>> ----------------
>>>> ------------------------------------
>>>> Your raw fstab file looks like this:
>>>> ------------------------------------
>>>> # /etc/fstab: static file system information.
>>>> #
>>>> # Use 'blkid' to print the universally unique identifier for a
>>>> # device; this may be used with UUID= as a more robust way to name devices
>>>> # that works even if disks are added and removed. See fstab(5).
>>>> #
>>>> # <file system>        <mount point>     <type>      <options>                   <dump> <pass>
>>>> # / was on /dev/sda5 during installation
>>>> UUID=4a5a9317-0b70-4796-a094-d61c01891c81 /    ext4  errors=remount-ro           0      1
>>>> # swap was on /dev/sda6 during installation
>>>> UUID=b4d7e5c0-207b-4a67-8b58-20523c509b87 none swap  sw                          0      0
>>>>
>>>> /dev/sr0               /media/cdrom0     udf,iso9660 user,noauto                 0      0
>>>>
>>>> #/dev/sysvg/homelv      /home             ext4        relatime,errors=remount-ro  0      1
>>>> /dev/sysvg/optlv       /opt              ext4        relatime,errors=remount-ro  0      1
>>>>
>>>> /dev/data1vg/homelv    /home             ext4        relatime,errors=remount-ro  0      2
>>>> /dev/data1vg/wwwlv     /www              ext4        relatime,errors=remount-ro  0      2
>>>> /dev/data1vg/baseslv   /bases            ext4        relatime,errors=remount-ro  0      2
>>>> /dev/data1vg/photoslv  /photos           ext4        relatime,errors=remount-ro  0      2
>>>> /dev/data1vg/videoslv  /videos           ext4        relatime,errors=remount-ro  0      2
>>>> /dev/data1vg/vboxlv    /vbox             ext4        relatime,errors=remount-ro  0      2
>>>> /dev/data1vg/graveurlv /graveur          ext4        relatime,errors=remount-ro  0      2
>>>>
>>>> # /dev/data0vg/homelv    /data0vg/home     ext4        relatime,errors=remount-ro  0      2
>>>> # /dev/data0vg/wwwlv     /data0vg/www      ext4        relatime,errors=remount-ro  0      2
>>>> # /dev/data0vg/baseslv   /data0vg/bases    ext4        relatime,errors=remount-ro  0      2
>>>> # /dev/data0vg/photoslv  /data0vg/photos   ext4        relatime,errors=remount-ro  0      2
>>>> # /dev/data0vg/videoslv  /data0vg/videos   ext4        relatime,errors=remount-ro  0      2
>>>> # /dev/data0vg/vboxlv    /data0vg/vbox     ext4        relatime,errors=remount-ro  0      2
>>>>
>>>> # /dev/data2vg/homelv    /data2vg/home     ext4        relatime,errors=remount-ro  0      2
>>>> # /dev/data2vg/wwwlv     /data2vg/www      ext4        relatime,errors=remount-ro  0      2
>>>> # /dev/data2vg/baseslv   /data2vg/bases    ext4        relatime,errors=remount-ro  0      2
>>>> # /dev/data2vg/photoslv  /data2vg/photos   ext4        relatime,errors=remount-ro  0      2
>>>> # /dev/data2vg/videoslv  /data2vg/videos   ext4        relatime,errors=remount-ro  0      2
>>>> # /dev/data2vg/vboxlv    /data2vg/vbox     ext4        relatime,errors=remount-ro  0      2
>>>> -----------------------------------
>>>> Your mountlist will look like this:
>>>> -----------------------------------
>>>> INFO: Analyzing LVM...
>>>> DEVICE          MOUNTPOINT      FORMAT          SIZE MB       LABEL/UUID    
>>>> ------          ----------      ------          -------       ----------    
>>>> INFO: Examining /dev/sdb1 (mount=lvm fmt=lvm psz=976761560)
>>>> /dev/sdb1       lvm             lvm              953868 c9qZKK-bpqn-sY7P-fWH2-SBlo-YsXS-udCgP7
>>>> INFO: Examining /dev/sda7 (mount=lvm fmt=lvm psz=99741696)
>>>> /dev/sda7       lvm             lvm               97404 yuL0j7-wJtb-ANiO-Omxi-AuEE-wCkJ-pfhEWi
>>>> INFO: Examining /dev/sda5 (mount=/ fmt=ext4 psz=97659103)
>>>> /dev/sda5       /               ext4              95370 4a5a9317-0b70-4796-a094-d61c01891c81
>>>> INFO: Examining /dev/sda6 (mount=swap fmt=swap psz=979928)
>>>> /dev/sda6       swap            swap                956 b4d7e5c0-207b-4a67-8b58-20523c509b87
>>>> INFO: Examining /dev/sysvg/optlv (mount=/opt fmt=ext4 psz=lvm)
>>>> /dev/sysvg/optlv /opt            ext4                lvm f1c4b976-0101-47ac-9ff8-c5a9e567553b
>>>> INFO: Examining /dev/data1vg/homelv (mount=/home fmt=ext4 psz=lvm)
>>>> /dev/data1vg/homelv /home           ext4                lvm e063df74-3fff-45ac-927d-bc6a60bd2970
>>>> INFO: Examining /dev/data1vg/wwwlv (mount=/www fmt=ext4 psz=lvm)
>>>> /dev/data1vg/wwwlv /www            ext4                lvm 7942603b-20c8-483a-ab36-98ee20ab7700
>>>> INFO: Examining /dev/data1vg/baseslv (mount=/bases fmt=ext4 psz=lvm)
>>>> /dev/data1vg/baseslv /bases          ext4                lvm 09f40cc9-fc3b-4205-a466-df38e5774a59
>>>> INFO: Examining /dev/data1vg/photoslv (mount=/photos fmt=ext4 psz=lvm)
>>>> /dev/data1vg/photoslv /photos         ext4                lvm 11ff707f-da12-46a3-9218-87fcf38ddc2f
>>>> INFO: Examining /dev/data1vg/videoslv (mount=/videos fmt=ext4 psz=lvm)
>>>> /dev/data1vg/videoslv /videos         ext4                lvm 11e0f5ef-75e4-4b7b-b34e-c9112b731f57
>>>> INFO: Examining /dev/data1vg/vboxlv (mount=/vbox fmt=ext4 psz=lvm)
>>>> /dev/data1vg/vboxlv /vbox           ext4                lvm 69e8fcf6-9518-4c3c-9052-53096c873cc4
>>>> INFO: Examining /dev/data1vg/graveurlv (mount=/graveur fmt=ext4 psz=lvm)
>>>> /dev/data1vg/graveurlv /graveur        ext4                lvm a5d30c9b-d333-46a3-8c28-ef2c4c1d9185
>>>> -----------------------------------
>>>> Mindi 3.0.0-r3332 is exiting
>>>> End date : lundi 19 janvier 2015, 22:16:59 (UTC+0100)
>>>
>>>> INFO: Time started: Mon Jan 19 22:16:43 2015
>>>>
>>>> DBG2: [TH=22705] libmondo-tools.c->setup_tmpdir#715: bkpinfo->tmpdir is being set to /tmp/mondo.tmp.4v41Vd
>>>> DBG2: [TH=22705] libmondo-tools.c->setup_scratchdir#736: Purging old scratchdir /mondo.scratch.*
>>>> DBG2: [TH=22705] libmondo-tools.c->setup_scratchdir#757: bkpinfo->scratchdir is being set to /tmp/mondo.scratch.3mNp4N
>>>> INFO: root is mounted at /dev/disk/by-uuid/aa9317-0b70-4796-a094-d61c01891c81
>>>>
>>>> INFO: That doesn't mean /dev/disk/by-uuid/aa9317-0b70-4796-a094-d61c01891c81 is the root partition. It's just a debugging message. Relax. It's part of am_I_in_disaster_recovery_mode().
>>>> DBG1: [TH=22705] libmondo-devices.c->am_I_in_disaster_recovery_mode#163: Is this a ramdisk? result = FALSE
>>>> INFO: running: dmesg -n1 > /tmp/mondo.tmp.4v41Vd/mondo-run-prog-thing.tmp 2> /tmp/mondo.tmp.4v41Vd/mondo-run-prog-thing.err
>>>> INFO: --------------------------------start of output-----------------------------
>>>> INFO: --------------------------------end of output------------------------------
>>>> INFO: ...ran just fine. :-)
>>>> INFO: Mondo Archive v3.2.0-r3332 --- http://www.mondorescue.org
>>>> INFO: running x86_64 binaries
>>>> INFO: running on x86_64 architecture
>>>> INFO: -----------------------------------------------------------
>>>> INFO: NB: Mondo logs almost everything, so don't panic if you see
>>>> INFO: some error messages.  Please read them carefully before you
>>>> INFO: decide to break out in a cold sweat.    Despite (or perhaps
>>>> INFO: because of) the wealth of messages. some users are inclined
>>>> INFO: to stop reading this log. If Mondo stopped for some reason,
>>>> INFO: chances are it's detailed here.  More than likely there's a
>>>> INFO: message at the very end of this log that will tell you what
>>>> INFO: is wrong. Please read it!                          -Devteam
>>>> INFO: -----------------------------------------------------------
>>>> INFO: Zero...
>>>> DBG1: [Main] mondoarchive.c->welcome_to_mondoarchive#96: One...
>>>> DBG2: [Main] mondoarchive.c->welcome_to_mondoarchive#97: Two...
>>>> DBG3: [Main] mondoarchive.c->welcome_to_mondoarchive#98: Three...
>>>> DBG4: [Main] mondoarchive.c->welcome_to_mondoarchive#99: Four...
>>>> DBG2: [Main] mondoarchive.c->distro_specific_kludges_at_start_of_mondoarchive#114: Unmounting old ramdisks if necessary
>>>> INFO: running: mount | grep cdrom | grep super > /tmp/mondo.tmp.4v41Vd/mondo-run-prog-thing.tmp 2> /tmp/mondo.tmp.4v41Vd/mondo-run-prog-thing.err
>>>> INFO: --------------------------------start of output-----------------------------
>>>> INFO: --------------------------------end of output------------------------------
>>>> INFO: ...ran with res=256
>>>> INFO: running: mount | grep floppy | grep super > /tmp/mondo.tmp.4v41Vd/mondo-run-prog-thing.tmp 2> /tmp/mondo.tmp.4v41Vd/mondo-run-prog-thing.err
>>>> INFO: --------------------------------start of output-----------------------------
>>>> INFO: --------------------------------end of output------------------------------
>>>> INFO: ...ran with res=256
>>>> DBG1: [Main] libmondo-tools.c->mount_boot_if_necessary#1155: Started sub
>>>> DBG4: [Main] libmondo-tools.c->mount_boot_if_necessary#1156: About to set g_boot_mountpt[0] to '\0'
>>>> DBG4: [Main] libmondo-tools.c->mount_boot_if_necessary#1158: Done. Great. Seeting command to something
>>>> DBG4: [Main] libmondo-tools.c->mount_boot_if_necessary#1160: Cool. Command = 'grep -v ":" /etc/fstab | grep -vE '^#.*$' | grep -E "[ ]/boot[ ]" | tr -s ' ' ' ' | cut -f1 | head -n1'
>>>> DBG4: [Main] libmondo-tools.c->mount_boot_if_necessary#1164: tmp = ''
>>>> DBG2: [Main] libmondo-tools.c->mount_boot_if_necessary#1165: /boot is at  according to /etc/fstab
>>>> DBG3: [Main] libmondo-tools.c->mount_boot_if_necessary#1182: command = mount | grep -E '^'
>>>> DBG1: [Main] libmondo-tools.c->mount_boot_if_necessary#1205: Ended sub
>>>> DBG1: [Main] libmondo-tools.c->get_kernel_version#245: g_kernel_version = 3.200000
>>>> INFO: running: rm -Rf /var/cache/mondo/changed.files* > /tmp/mondo.tmp.4v41Vd/mondo-run-prog-thing.tmp 2> /tmp/mondo.tmp.4v41Vd/mondo-run-prog-thing.err
>>>> INFO: --------------------------------start of output-----------------------------
>>>> INFO: --------------------------------end of output------------------------------
>>>> INFO: ...ran just fine. :-)
>>>> INFO: Checking sanity of your Linux distribution
>>>> INFO: running: grep ramdisk /proc/devices > /tmp/mondo.tmp.4v41Vd/mondo-run-prog-thing.tmp 2> /tmp/mondo.tmp.4v41Vd/mondo-run-prog-thing.err
>>>> INFO: --------------------------------start of output-----------------------------
>>>> INFO: 1 ramdisk
>>>> INFO: --------------------------------end of output------------------------------
>>>> INFO: ...ran just fine. :-)
>>>> INFO: running: mount | grep -Ew 'vfat|fat|dos' | grep -vE "/dev/fd|nexdisk" > /tmp/mondo.tmp.4v41Vd/mondo-run-prog-thing.tmp 2> /tmp/mondo.tmp.4v41Vd/mondo-run-prog-thing.err
>>>> INFO: --------------------------------start of output-----------------------------
>>>> INFO: --------------------------------end of output------------------------------
>>>> INFO: ...ran with res=256
>>>> DBG4: [Main] libmondo-files.c->find_home_of_exe#349: find_home_of_exe --- Found cmp at /usr/bin/cmp
>>>> INFO: running: mindi -V > /tmp/mondo.tmp.4v41Vd/mondo-run-prog-thing.tmp 2> /tmp/mondo.tmp.4v41Vd/mondo-run-prog-thing.err
>>>> INFO: --------------------------------start of output-----------------------------
>>>> INFO: Mindi v3.0.0-r3332
>>>> INFO: Le disque /dev/mapper/data1vg-photoslv ne contient pas une table de partitions valable
>>>> INFO: Le disque /dev/mapper/data1vg-videoslv ne contient pas une table de partitions valable
>>>> INFO: Le disque /dev/mapper/data1vg-homelv ne contient pas une table de partitions valable
>>>> INFO: Le disque /dev/mapper/data1vg-graveurlv ne contient pas une table de partitions valable
>>>> INFO: Le disque /dev/mapper/data1vg-wwwlv ne contient pas une table de partitions valable
>>>> INFO: Le disque /dev/mapper/data1vg-baseslv ne contient pas une table de partitions valable
>>>> INFO: Le disque /dev/mapper/data1vg-vboxlv ne contient pas une table de partitions valable
>>>> INFO: Le disque /dev/mapper/sysvg-optlv ne contient pas une table de partitions valable
>>>> INFO: --------------------------------end of output------------------------------
>>>> INFO: ...ran just fine. :-)
>>>> INFO: running: parted2fdisk -l 2>/dev/null | grep -i raid > /tmp/mondo.tmp.4v41Vd/mondo-run-prog-thing.tmp 2> /tmp/mondo.tmp.4v41Vd/mondo-run-prog-thing.err
>>>> INFO: --------------------------------start of output-----------------------------
>>>> INFO: --------------------------------end of output------------------------------
>>>> INFO: ...ran with res=256
>>>> INFO: Done.
>>>> DBG1: [Main] libmondo-cli.c->process_switches#181: Loglevel forced to 99
>>>> DBG20: [Main] libmondo-files.c->does_file_exist#188: /usr/bin/afio exists
>>>> DBG4: [Main] libmondo-files.c->find_home_of_exe#349: find_home_of_exe --- Found afio at /usr/bin/afio
>>>
>>>> ------------------------------------------------------------------------------
>>>> New Year. New Location. New Benefits. New Data Center in Ashburn, VA.
>>>> GigeNET is offering a free month of service with a new server in Ashburn.
>>>> Choose from 2 high performing configs, both with 100TB of bandwidth.
>>>> Higher redundancy.Lower latency.Increased capacity.Completely compliant.
>>>> http://p.sf.net/sfu/gigenet
>>>
>>>> _______________________________________________
>>>> Mondo-devel mailing list
>>>> [hidden email]
>>>> https://lists.sourceforge.net/lists/listinfo/mondo-devel
>>>
>>>
>>
>>
>
>
>
>
> ------------------------------------------------------------------------------
> Dive into the World of Parallel Programming. The Go Parallel Website,
> sponsored by Intel and developed in partnership with Slashdot Media, is your
> hub for all things parallel software development, from weekly thought
> leadership blogs to news, videos, case studies, tutorials and more. Take a
> look and join the conversation now. http://goparallel.sourceforge.net/
>
>
>
> _______________________________________________
> Mondo-devel mailing list
> [hidden email]
> https://lists.sourceforge.net/lists/listinfo/mondo-devel
>



------------------------------------------------------------------------------
Dive into the World of Parallel Programming. The Go Parallel Website,
sponsored by Intel and developed in partnership with Slashdot Media, is your
hub for all things parallel software development, from weekly thought
leadership blogs to news, videos, case studies, tutorials and more. Take a
look and join the conversation now. http://goparallel.sourceforge.net/
_______________________________________________
Mondo-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/mondo-devel
Reply | Threaded
Open this post in threaded view
|

Re: [Mondo-devel] Segmentation error running mondoarchive v3.2.0-r3332

Philippe Lefevre
Hi list,

I believe I found where the issue with -I is.

In fact, the structure bkpinfo is well built with an include_paths entry
initialized to NULL, but there is no malloc that would allow to store
any string.

I compared how is parsed the -E and -I options and supposed they should
work in quite the same way.

It seems to me that there is some code missing in libmondo-cli.c. So I
made the following changes and that seems to work.

================================================
libmondo-cli.c
231:if (flag_set['I']) {
      if (bkpinfo->include_paths && bkpinfo->include_paths[0] == '-'){
        retval++;
        log_to_screen("Please supply a sensible value with '-I'\n");
        }

// Added
mr_asprintf(tmp1, "%s", flag_val['I']);
p = tmp1;
q = tmp1;
// End add

// Modified
if (!strcmp(tmp1, "/")) {
// End modif
                        log_msg(2, "'/' is pleonastic.");
                        mr_free(bkpinfo->include_paths);  // Not sure
this is needed
                }
// Modified
if (tmp1[0]) {
// End modif
                        mr_strcat(bkpinfo->include_paths, "|");
                }

249 :   /* Cut the flag_val['I'] in parts containing all paths to test
them */
================================================



I hope this help :)

Kind regards,
Philippe



Le 02/02/2015 21:00, Philippe Lefevre a écrit :

> OOPS !
>
> In my latest email:
>> I reran it from compiled sources but this time I also had the same
>> trouble with it and was not able to get the error.
>
> I meant "I was unable to get it work well again as I described in my
> email dated of 17th of januray"
>
> Kind Rgds,
> Philippe
>
> Le 01/02/2015 23:17, Philippe Lefevre a écrit :
>> Hello list,
>>
>> I did again some tries with mondo 3.2.0
>> Right: without -I option it works.
>>
>> I reran it from compiled sources but this time I also had the same
>> trouble with it and was not able to get the error.
>>
>> I tried to understand what happen with this option and I believe it is
>> linked to the pointer bkpinfo->include_paths which is empty in
>> libmondo-cli.c:236
>> We can see that flag_val['I'] is well setted to the arg value and
>> flag_set['I'] is true in process_switches()
>>
>> Sorry, I must stop now and I'm afraid I will not have time those next
>> days to grab into it again (may be next we ??) but I hope these traces
>> may help.
>>
>> Please find attached some gdb steps.
>>
>> Kind regards,
>> Philippe
>>
>>
>> Le 26/01/2015 22:10, Philippe Lefevre a écrit :
>>>
>>> Great !
>>>
>>> Many thanks for your help and reply Bruno.
>>>
>>> Next week-end I'm going to reinstall 3.2.0 and supress -I option and see
>>> what happen.
>>>
>>> One thing is strange anyway: in my tests after a mondoarchive
>>> compilation, (pls, see my email dated on 17th january) I ran 3.2.0 with
>>> -I option without any issue. The sigsegv was repructible when
>>> mondoarchive was installed by the deb package ...
>>>
>>> I used :
>>> [phlsys]root:/home/phl/mondo-3.2.0# gdb -args mondoarchive -D -OV -i -N
>>> -G -s 780M -p sys-D7.7-diff_150105212200 -T /graveur -S /graveur -d
>>> /graveur -I "/|/|/opt/Zuma" -E
>>> "/bases/sybase|/graveur|/home|/opt|/photos|/quemu|/Sauvegardes|/var/crash|/var/backups|/var/log|/var/mail|/var/spool|/vbox|/videos|/www"
>>>
>>> and:
>>>  ....
>>>  Data archived OK.
>>>  Mondoarchive ran OK.
>>>  See /var/log/mondoarchive.log for details of backup run.
>>>  Execution run ended; result=0
>>>  Type 'less /var/log/mondoarchive.log' to see the output log [Inferior 1
>>> (process 19382) exited normally]
>>>  (gdb) quit
>>>
>>>
>>> I'll let you know.
>>> Kind regards,
>>> Philippe
>>>
>>>
>>>
>>> Le 26/01/2015 01:09, Bruno Cornec a écrit :
>>>> Hello Philippe,
>>>>
>>>> This is now fixed as described in BR:
>>>> http://trac.mondorescue.org/ticket/764#comment:2
>>>>
>>>> Bruno.
>>>>
>>>> Philippe Lefevre said on Mon, Jan 19, 2015 at 10:34:24PM +0100:
>>>>
>>>>> Hello Gaetagno,
>>>>>
>>>>> Regarding the two slashes, as I said, I used the same syntax to get into
>>>>> the same bug situation.
>>>>>
>>>>>
>>>>> I did a try with only one / in the -I option and got the same
>>>>> segmentation violation exception.
>>>>>
>>>>>
>>>>> Mindi launched alone as your example and it ran fine and the iso file
>>>>> successfully built.
>>>>> Please find attached the mindi.log file.
>>>>>
>>>>> [phlsys]root:/home/phl/Devel/mondo# ls -al /var/cache/mindi/mindi.iso
>>>>> -rw-r----- 1 root root 98721792 janv. 19 22:09 /var/cache/mindi/mindi.iso
>>>>>
>>>>>
>>>>>
>>>>> Ran mondoarchive with -K99 option crashed again with the sigsegv signal.
>>>>> Please find attached the mondoarchive.log file.
>>>>> Unfortunately, I'm afraid it is not so verbose than we would ...
>>>>> This time, the log ends with :
>>>>>
>>>>> DBG1: [Main] libmondo-cli.c->process_switches#181: Loglevel forced to 99
>>>>> DBG20: [Main] libmondo-files.c->does_file_exist#188: /usr/bin/afio exists
>>>>> DBG4: [Main] libmondo-files.c->find_home_of_exe#349: find_home_of_exe
>>>>> --- Found afio at /usr/bin/afio
>>>>>
>>>>>
>>>>>
>>>>> Running mondo without - E option crashed in the same way and with same
>>>>> mondoarchive.log file.
>>>>> [phlsys]root:/home/phl/Devel/mondo# /usr/sbin/mondoarchive -K99 -D -OV
>>>>> -i -N -G -s 780M -p sys-D7.7-diff_150105212200 -T /graveur -S /graveur
>>>>> -d /graveur -I "/opt/zuma"
>>>>> See /var/log/mondoarchive.log for details of backup run.
>>>>> Checking sanity of your Linux distribution
>>>>> Done.
>>>>> Erreur de segmentation
>>>>>
>>>>>
>>>>> Thank you for your time Gaetagno.
>>>>> Kind regards,
>>>>> Philippe
>>>>>
>>>>>
>>>>>
>>>>> Le 19/01/2015 12:17, Gattegno, Victor (GSD CSC / GCC) a écrit :
>>>>>> Hi Philippe,
>>>>>>
>>>>>> You used again two time "/"  in the include :
>>>>>> -I "/|/|/opt/Zuma"
>>>>>>
>>>>>> Your mondorachive.log file ends with :
>>>>>> DBG4: [Main] libmondo-files.c->find_home_of_exe#349: find_home_of_exe --- Found afio at /usr/bin/afio
>>>>>>
>>>>>> You can try a few things :
>>>>>>
>>>>>> Try mindi alone :
>>>>>> # mindi
>>>>>> Do you want to use your own kernel to build the boot disk ([y]/n) ? y
>>>>>>
>>>>>> Try your mondoarchive command without -E, with only -I, and choice only one directory, example :
>>>>>> -I "/opt/Zuma"
>>>>>>
>>>>>> Try your mondoarchive command with more debug, example with -K 5, or with -K 99 (which is full debug mode, be aware that the log file could grow from 200 Kb to 50 Mb).
>>>>>>
>>>>>> Rgds,
>>>>>> Victor
>>>>>>
>>>>>> -----Original Message-----
>>>>>> From: Philippe Lefevre [mailto:[hidden email]]
>>>>>> Sent: samedi 17 janvier 2015 20:14
>>>>>> To: Mondo mailing list
>>>>>> Subject: Re: [Mondo-devel] Segmentation error running mondoarchive v3.2.0-r3332
>>>>>>
>>>>>> Hello list,
>>>>>>
>>>>>> sorry Gaetagno for the delay, I was not able to find some time long enought to go back into my issue.
>>>>>>
>>>>>> I did it today (without removing the two slashes in order to be in the same situation) and .... what I compiled worked fine with what I have compiled. (I noticed the -v bug, thanks  ;)  )
>>>>>>
>>>>>> Run mondoarchive via dbg:
>>>>>> [phlsys]root:/home/phl/mondo-3.2.0# gdb -args mondoarchive -D -OV -i -N -G -s 780M -p sys-D7.7-diff_150105212200 -T /graveur -S /graveur -d /graveur -I "/|/|/opt/Zuma" -E "/bases/sybase|/graveur|/home|/opt|/photos|/quemu|/Sauvegardes|/var/crash|/var/backups|/var/log|/var/mail|/var/spool|/vbox|/videos|/www"
>>>>>>
>>>>>> and:
>>>>>> ....
>>>>>> Data archived OK.
>>>>>> Mondoarchive ran OK.
>>>>>> See /var/log/mondoarchive.log for details of backup run.
>>>>>> Execution run ended; result=0
>>>>>> Type 'less /var/log/mondoarchive.log' to see the output log [Inferior 1 (process 19382) exited normally]
>>>>>> (gdb) quit
>>>>>>
>>>>>>
>>>>>> So I reinstalled the official debian package:
>>>>>>
>>>>>> Sélection du paquet libmondorescue-perl précédemment désélectionné.
>>>>>> (Lecture de la base de données... 279208 fichiers et répertoires déjà
>>>>>> installés.)
>>>>>> Dépaquetage de libmondorescue-perl (à partir de
>>>>>> .../libmondorescue-perl_3.2.0-1_all.deb) ...
>>>>>> Préparation du remplacement de mindi-busybox 1.18.5-3 (en utilisant
>>>>>> .../mindi-busybox_1.21.1-1_amd64.deb) ...
>>>>>> Dépaquetage de la mise à jour de mindi-busybox ...
>>>>>> Préparation du remplacement de mindi 2.1.7-1 (en utilisant
>>>>>> .../mindi_3.0.0-1_amd64.deb) ...
>>>>>> Dépaquetage de la mise à jour de mindi ...
>>>>>> Préparation du remplacement de mondo 3.0.4-1 (en utilisant
>>>>>> .../mondo_3.2.0-1_amd64.deb) ...
>>>>>> Dépaquetage de la mise à jour de mondo ...
>>>>>> Traitement des actions différées (« triggers ») pour « man-db »...
>>>>>> Paramétrage de libmondorescue-perl (3.2.0-1) ...
>>>>>> Paramétrage de mindi-busybox (1.21.1-1) ...
>>>>>> Paramétrage de mindi (3.0.0-1) ...
>>>>>> Installation de la nouvelle version du fichier de configuration /etc/mindi/deplist.d/minimal.conf ...
>>>>>> Installation de la nouvelle version du fichier de configuration /etc/mindi/deplist.d/udev.conf ...
>>>>>> Installation de la nouvelle version du fichier de configuration /etc/mindi/deplist.d/ProLiant.conf ...
>>>>>> Installation de la nouvelle version du fichier de configuration /etc/mindi/deplist.d/base.conf ...
>>>>>> Installation de la nouvelle version du fichier de configuration /etc/mindi/deplist.d/lvm.conf ...
>>>>>> Installation de la nouvelle version du fichier de configuration /etc/mindi/perl-scripts ...
>>>>>> Paramétrage de mondo (3.2.0-1) ...
>>>>>>
>>>>>>
>>>>>> but launched in the same way, it crashed again with a segmentation error:
>>>>>>
>>>>>> [phlsys]root:/home/phl/telechargements/mondo-3.2.0# mondoarchive -D -OV -i -N -G -s 780M -p sys-D7.7-diff_150105212200 -T /graveur -S /graveur -d /graveur -I "/|/|/opt/Zuma" -E "/bases/sybase|/graveur|/home|/opt|/photos|/quemu|/Sauvegardes|/var/crash|/var/backups|/var/log|/var/mail|/var/spool|/vbox|/videos|/www"
>>>>>> See /var/log/mondoarchive.log for details of backup run.
>>>>>> Checking sanity of your Linux distribution Done.
>>>>>> Erreur de segmentation
>>>>>>
>>>>>>
>>>>>>
>>>>>> Please find attached the relevant mondoarchive.log file.
>>>>>> It seems to be stopped before logging something about the fault.
>>>>>> I franckly don't know what I could do more.
>>>>>> Do you have an idea about what I could do to explore deeper this issue ?
>>>>>> Something might be going wrong into the deb pkg ???
>>>>>> I got it with apt using:
>>>>>>    deb ftp://ftp.mondorescue.org//debian 7 contrib
>>>>>>
>>>>>>
>>>>>> Thanks for your help.
>>>>>> Regards,
>>>>>> Philippe
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> Le 06/01/2015 17:28, Gattegno, Victor (GSD CSC / GCC) a écrit :
>>>>>>> Hello Philippe,
>>>>>>>
>>>>>>> From mondoarchive man : " When using the -I option with the -E option, the -E content should be subdirectories of those mentioned in the -I only, as -I takes precedence."
>>>>>>>
>>>>>>> But if your -I and -E combination works it's ok (check if /opt/zuma and /opt/calibre are well backuped and restored).
>>>>>>>
>>>>>>> Regards,
>>>>>>> Victor
>>>>>>>
>>>>>>> -----Original Message-----
>>>>>>> From: Philippe Lefevre [mailto:[hidden email]]
>>>>>>> Sent: lundi 5 janvier 2015 21:42
>>>>>>> To: [hidden email]
>>>>>>> Subject: Re: [Mondo-devel] Segmentation error running mondoarchive
>>>>>>> v3.2.0-r3332
>>>>>>>
>>>>>>> Thanks for your help and reply Victor,
>>>>>>>
>>>>>>> I should be able to replay with all of that before the end of the week and let you know.
>>>>>>> Regarding the double /, it is due to my shell script which build the final request. I will also do a try without it.
>>>>>>>
>>>>>>> I believe I couldn't remove -I flag as in the exclude part there is /opt and I want to include only 2 directories /opt/zuma and /opt/calibre. At least, I should use -I "/opt/calibre|/opt/Zuma" right?
>>>>>>>
>>>>>>> PS: my system backup is run by root and ulimit is setted unlimited:
>>>>>>>
>>>>>>> # ulimit -a
>>>>>>> core file size          (blocks, -c) 0
>>>>>>> data seg size           (kbytes, -d) unlimited
>>>>>>> scheduling priority             (-e) 0
>>>>>>> file size               (blocks, -f) unlimited
>>>>>>> pending signals                 (-i) 31106
>>>>>>> max locked memory       (kbytes, -l) 64
>>>>>>> max memory size         (kbytes, -m) unlimited
>>>>>>> open files                      (-n) 1024
>>>>>>> pipe size            (512 bytes, -p) 8
>>>>>>> POSIX message queues     (bytes, -q) 819200
>>>>>>> real-time priority              (-r) 0
>>>>>>> stack size              (kbytes, -s) 8192
>>>>>>> cpu time               (seconds, -t) unlimited
>>>>>>> max user processes              (-u) 31106
>>>>>>> virtual memory          (kbytes, -v) unlimited
>>>>>>> file locks                      (-x) unlimited
>>>>>>>
>>>>>>>
>>>>>>> Rgds,
>>>>>>> Philippe
>>>>>>>
>>>>>>>
>>>>>>> Le 05/01/2015 16:32, Gattegno, Victor (GSD CSC / GCC) a écrit :
>>>>>>>> Hello Philippe,
>>>>>>>>
>>>>>>>> Good gdb work, but don't focus on "mondoarchive -v" segmentation fault, it's a known failing bug. It's better to debug mondoarchive with the options that you use.
>>>>>>>>
>>>>>>>>  In your 27/12/2014 test and post:
>>>>>>>>  - did you posted too the associated /var/log/mondoarchive.log (compressed) ?
>>>>>>>>  - you used -I (with / included twice) and -E options, it's better to use only -E option.
>>>>>>>>
>>>>>>>> What's the result of "ulimit -a" on your Debian ?
>>>>>>>>
>>>>>>>> I wish to you - and to all this mailig-list users - a nice year 2015.
>>>>>>>>
>>>>>>>> Rgds,
>>>>>>>> Victor
>>>>>>>>
>>>>>>>> -----Original Message-----
>>>>>>>> From: Philippe Lefevre [mailto:[hidden email]]
>>>>>>>> Sent: samedi 3 janvier 2015 14:32
>>>>>>>> To: [hidden email]
>>>>>>>> Subject: Re: [Mondo-devel] Segmentation error running mondoarchive
>>>>>>>> v3.2.0-r3332
>>>>>>>>
>>>>>>>> Hi list,
>>>>>>>>
>>>>>>>> Some more information about my issue.
>>>>>>>>
>>>>>>>> I can confirm that in my case it is related to this new release as a I did a downgrade and successfully built a new full backup.
>>>>>>>>
>>>>>>>> I uninstalled and purged
>>>>>>>>   libmondorescue-perl_3.2.0-1_all.deb
>>>>>>>>   mindi-busybox_1.21.1-1_amd64.deb
>>>>>>>>   mindi_3.0.0-1_amd64.deb
>>>>>>>>   mondo_3.2.0-1_amd64.deb
>>>>>>>>
>>>>>>>> and reinstalled the previous version
>>>>>>>>   mindi-busybox 1.18.5-3
>>>>>>>>   mindi 2.1.7-1
>>>>>>>>   mondo 3.0.4-1
>>>>>>>>
>>>>>>>> I also compiled mondo 3.2.0 from sources and ran gdb against the simpliest command that raise the seg error. It shows :
>>>>>>>>
>>>>>>>> Starting program:
>>>>>>>> /home/phl/telechargements/mondo-3.2.0/src/mondoarchive/mondoarchive -v [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
>>>>>>>> mondoarchive v3.2.0-r3332
>>>>>>>> See man page for help
>>>>>>>>
>>>>>>>> Program received signal SIGSEGV, Segmentation fault.
>>>>>>>> 0x00007ffff76629aa in vfprintf () from
>>>>>>>> /lib/x86_64-linux-gnu/libc.so.6
>>>>>>>> (gdb) bt
>>>>>>>> #0  0x00007ffff76629aa in vfprintf () from
>>>>>>>> /lib/x86_64-linux-gnu/libc.so.6
>>>>>>>> #1  0x00007ffff7688fca in vasprintf () from
>>>>>>>> /lib/x86_64-linux-gnu/libc.so.6
>>>>>>>> #2  0x00000000004367c4 in mr_asprintf_int (strp=strp@entry=0x7fffffffe0d0, line=line@entry=258, file=file@entry=0x44187f "libmondo-fork.c",
>>>>>>>>     fmt=fmt@entry=0x441d38 "%s > %s/mondo-run-prog-thing.tmp 2>
>>>>>>>> %s/mondo-run-prog-thing.err") at mr_mem.c:62
>>>>>>>> #3  0x000000000041e0f0 in run_program_and_log_output
>>>>>>>> (program=program@entry=0x43c4b4 "umount -d /mnt/cdrom",
>>>>>>>> debug_level=debug_level@entry=0)
>>>>>>>>     at libmondo-fork.c:258
>>>>>>>> #4  0x000000000042ec19 in finish (signal=signal@entry=0) at
>>>>>>>> newt-specific.c:388
>>>>>>>> #5  0x0000000000403430 in main (argc=2, argv=0x7fffffffe668) at
>>>>>>>> mondoarchive.c:176
>>>>>>>> (gdb)
>>>>>>>>
>>>>>>>>
>>>>>>>> function code exerpt
>>>>>>>>
>>>>>>>>    56 void mr_asprintf_int(char **strp, int line, const char *file, const char *fmt, ...) {
>>>>>>>>    57
>>>>>>>>    58 int res = 0;
>>>>>>>>    59 va_list args;
>>>>>>>>    60
>>>>>>>>    61 va_start(args,fmt);
>>>>>>>>    62 res = vasprintf(strp, fmt, args);
>>>>>>>>    63 if (res == -1) {
>>>>>>>>    64 mr_msg_int(1,line,file,"Unable to alloc memory in
>>>>>>>> mr_asprintf\nExiting...");
>>>>>>>>    65 mr_exit(-1,"Unable to alloc memory in mr_asprintf");
>>>>>>>>    66 }
>>>>>>>>    67 va_end(args);
>>>>>>>>    68 }
>>>>>>>>
>>>>>>>>
>>>>>>>> Breakpoint 1, mr_asprintf_int (strp=strp@entry=0x7fffffffe0d0, line=line@entry=258, file=file@entry=0x44187f "libmondo-fork.c",
>>>>>>>>     fmt=fmt@entry=0x441d38 "%s > %s/mondo-run-prog-thing.tmp 2>
>>>>>>>> %s/mondo-run-prog-thing.err") at mr_mem.c:56
>>>>>>>> 56 void mr_asprintf_int(char **strp, int line, const char *file, const
>>>>>>>> char *fmt, ...) {
>>>>>>>> (gdb) s
>>>>>>>> 61 va_start(args,fmt);
>>>>>>>> (gdb) display fmt
>>>>>>>> 1: fmt = 0x441d38 "%s > %s/mondo-run-prog-thing.tmp 2> %s/mondo-run-prog-thing.err"
>>>>>>>> (gdb) display args
>>>>>>>> 2: args = {{gp_offset = 4158558940, fp_offset = 32767,
>>>>>>>> overflow_arg_area = 0x7ffff7fd5000, reg_save_area = 0x7ffff7ffd9d8}}
>>>>>>>> (gdb) s
>>>>>>>> 62 res = vasprintf(strp, fmt, args);
>>>>>>>> 2: args = {{gp_offset = 4158558940, fp_offset = 32767,
>>>>>>>> overflow_arg_area = 0x7ffff7fd5000, reg_save_area = 0x7ffff7ffd9d8}}
>>>>>>>> 1: fmt = 0x441d38 "%s > %s/mondo-run-prog-thing.tmp 2> %s/mondo-run-prog-thing.err"
>>>>>>>> (gdb) s
>>>>>>>> 61 va_start(args,fmt);
>>>>>>>> 2: args = {{gp_offset = 4158558940, fp_offset = 32767,
>>>>>>>> overflow_arg_area = 0x7ffff7fd5000, reg_save_area = 0x7ffff7ffd9d8}}
>>>>>>>> 1: fmt = 0x441d38 "%s > %s/mondo-run-prog-thing.tmp 2> %s/mondo-run-prog-thing.err"
>>>>>>>> (gdb) s
>>>>>>>> 62 res = vasprintf(strp, fmt, args);
>>>>>>>> 2: args = {{gp_offset = 32, fp_offset = 48, overflow_arg_area =
>>>>>>>> 0x7fffffffe0b0, reg_save_area = 0x7fffffffdfe0}}
>>>>>>>> 1: fmt = 0x441d38 "%s > %s/mondo-run-prog-thing.tmp 2> %s/mondo-run-prog-thing.err"
>>>>>>>> (gdb) display res
>>>>>>>> 3: res = 0
>>>>>>>> (gdb) s
>>>>>>>>
>>>>>>>> Program received signal SIGSEGV, Segmentation fault.
>>>>>>>> 0x00007ffff76629aa in vfprintf () from
>>>>>>>> /lib/x86_64-linux-gnu/libc.so.6
>>>>>>>> (gdb)
>>>>>>>>
>>>>>>>>
>>>>>>>> It seems there is an issue with mr_asprintf_int but sorry I don't feel strong enought to get more deeply into the mondo code and analyze it properly ...
>>>>>>>>
>>>>>>>> I hope this help ...
>>>>>>>>
>>>>>>>> Regards,
>>>>>>>> Philippe
>>>>>>>>
>>>>>>>>
>>>>>>>> Le 27/12/2014 11:17, [hidden email] a écrit :
>>>>>>>>> Hi all,
>>>>>>>>>
>>>>>>>>> it seems that something goes wrong with mondo I could link to the
>>>>>>>>> latest Debian version of MondoRescue.
>>>>>>>>>
>>>>>>>>> I updated my version last thursday and this morning (I have a
>>>>>>>>> differential backup launched every friday night and one full a
>>>>>>>>> month) it failed.
>>>>>>>>> Unfortunately there are no much relevant informations in logs.
>>>>>>>>>
>>>>>>>>> The errors raised is :
>>>>>>>>>
>>>>>>>>>     # mondoarchive -D -OV -i -N -G -s 780M -p sys-D7.7-diff_141227100000
>>>>>>>>>     -T /graveur -S /graveur -d
>>>>>>>>>     /media/sauvegardes/phlsys/D7.7/sys/141227100000 -I
>>>>>>>>>     "/|/|/opt/calibre|/opt/Zuma" -E
>>>>>>>>>     "/bases/sybase|/graveur|/home|/opt|/photos|/quemu|/Sauvegardes|/var/crash|/var/backups|/var/log|/var/mail|/var/spool|/vbox|/videos|/www"
>>>>>>>>>     See /var/log/mondoarchive.log for details of backup run.
>>>>>>>>>     Checking sanity of your Linux distribution
>>>>>>>>>     Done.
>>>>>>>>>     Erreur de segmentation                /* Segmentation error */
>>>>>>>>>
>>>>>>>>> Please find attached the log files that seems to find out an issue
>>>>>>>>> with LVM disks
>>>>>>>>>
>>>>>>>>>     INFO: Mindi v3.0.0-r3332
>>>>>>>>>     INFO: Le disque /dev/mapper/data1vg-photoslv ne contient pas une
>>>>>>>>>     table de partitions valable
>>>>>>>>>              /* there is no valid partition table in
>>>>>>>>>     /dev/mapper/data1vg-photoslv disk */
>>>>>>>>>
>>>>>>>>> I have no issues with my LVM disks. Please find on below my LVM
>>>>>>>>> disks configuration
>>>>>>>>>
>>>>>>>>>     lvm> vgs
>>>>>>>>>       VG      #PV #LV #SN Attr   VSize   VFree
>>>>>>>>>       data1vg   1   7   0 wz--n- 931,51g 504,60g
>>>>>>>>>       sysvg     1   1   0 wz--n-  95,12g  78,84g
>>>>>>>>>
>>>>>>>>>     lvm> lvs
>>>>>>>>>       LV        VG      Attr     LSize   Pool Origin Data%  Move Log
>>>>>>>>>     Copy%  Convert
>>>>>>>>>       baseslv   data1vg -wi-ao--  
>>>>>>>>>     1,86g                                          
>>>>>>>>>       graveurlv data1vg -wi-ao--
>>>>>>>>>     20,00g                                          
>>>>>>>>>       homelv    data1vg -wi-ao--
>>>>>>>>>     50,00g                                          
>>>>>>>>>       photoslv  data1vg -wi-ao--
>>>>>>>>>     70,00g                                          
>>>>>>>>>       vboxlv    data1vg -wi-ao--
>>>>>>>>>     130,39g                                          
>>>>>>>>>       videoslv  data1vg -wi-ao--
>>>>>>>>>     150,00g                                          
>>>>>>>>>       wwwlv     data1vg -wi-ao--  
>>>>>>>>>     4,66g                                          
>>>>>>>>>       optlv     sysvg   -wi-ao--  16,28g
>>>>>>>>>
>>>>>>>>>     lvm> lvscan
>>>>>>>>>       ACTIVE            '/dev/data1vg/photoslv' [70,00 GiB] inherit
>>>>>>>>>       ACTIVE            '/dev/data1vg/videoslv' [150,00 GiB] inherit
>>>>>>>>>       ACTIVE            '/dev/data1vg/homelv' [50,00 GiB] inherit
>>>>>>>>>       ACTIVE            '/dev/data1vg/graveurlv' [20,00 GiB] inherit
>>>>>>>>>       ACTIVE            '/dev/data1vg/wwwlv' [4,66 GiB] inherit
>>>>>>>>>       ACTIVE            '/dev/data1vg/baseslv' [1,86 GiB] inherit
>>>>>>>>>       ACTIVE            '/dev/data1vg/vboxlv' [130,39 GiB] inherit
>>>>>>>>>       ACTIVE            '/dev/sysvg/optlv' [16,28 GiB] inherit
>>>>>>>>>
>>>>>>>>>     root@phlsys:/home/phl/Scripts# df -h
>>>>>>>>>     Sys. fich.                                             Taille Util.
>>>>>>>>>     Dispo Uti% Monté sur
>>>>>>>>>     rootfs                                                    92G  
>>>>>>>>>     11G   77G  12% /
>>>>>>>>>     udev                                                      10M    
>>>>>>>>>     0   10M   0% /dev
>>>>>>>>>     tmpfs                                                    397M  968K
>>>>>>>>>     396M   1% /run
>>>>>>>>>     /dev/disk/by-uuid/4a5a9317-0b70-4796-a094-d61c01891c81    92G  
>>>>>>>>>     11G   77G  12% /
>>>>>>>>>     tmpfs                                                    5,0M     0
>>>>>>>>>     5,0M   0% /run/lock
>>>>>>>>>     tmpfs                                                    985M  324K
>>>>>>>>>     985M   1% /run/shm
>>>>>>>>>     /dev/mapper/sysvg-optlv                                   17G   15G
>>>>>>>>>     845M  95% /opt
>>>>>>>>>     /dev/mapper/data1vg-homelv                                50G   40G
>>>>>>>>>     7,2G  85% /home
>>>>>>>>>     /dev/mapper/data1vg-wwwlv                                4,6G  2,5G
>>>>>>>>>     1,9G  58% /www
>>>>>>>>>     /dev/mapper/data1vg-baseslv                              1,9G  720M
>>>>>>>>>     1,1G  41% /bases
>>>>>>>>>     /dev/mapper/data1vg-photoslv                              69G  
>>>>>>>>>     43G   23G  66% /photos
>>>>>>>>>     /dev/mapper/data1vg-videoslv                             148G
>>>>>>>>>     104G   37G  74% /videos
>>>>>>>>>     /dev/mapper/data1vg-vboxlv                               129G
>>>>>>>>>     100G   23G  82% /vbox
>>>>>>>>>     /dev/mapper/data1vg-graveurlv                             20G
>>>>>>>>>     8,1G   11G  44% /graveur
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> The latest mondo upgrade dated of 25th of december was (it worked
>>>>>>>>> fine before this upgrade)
>>>>>>>>>
>>>>>>>>>     Start-Date: 2014-12-25  18:55:08
>>>>>>>>>     Commandline: /usr/sbin/synaptic
>>>>>>>>>     Install: libprojectbuilder-perl:amd64 (0.12.6-1, automatic),
>>>>>>>>>     libmondorescue-perl:amd64 (3.2.0-1, automatic)
>>>>>>>>>     Upgrade: mindi:amd64 (2.1.7-1, 3.0.0-1), mondo:amd64 (3.0.4-1,
>>>>>>>>>     3.2.0-1), mindi-busybox:amd64 (1.18.5-3, 1.21.1-1)
>>>>>>>>>     End-Date: 2014-12-25  18:55:31
>>>>>>>>>
>>>>>>>>> The Debian distro used is
>>>>>>>>>
>>>>>>>>>     root@phlsys:/home/phl/Scripts# uname -a
>>>>>>>>>     Linux phlsys 3.2.0-4-amd64 #1 SMP Debian 3.2.63-2+deb7u2 x86_64
>>>>>>>>>     GNU/Linux
>>>>>>>>>
>>>>>>>>> Anyone have an idea to try to debug this.
>>>>>>>>>
>>>>>>>>> Thanks for any help.
>>>>>>>>>
>>>>>>>>> By the way, I whish you all an happy new year 2015 with all the best
>>>>>>>>> in your lifes Kind regards, Philippe
>>>>>>>>>
>>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> ---------------------------------------------------------------------
>>>>>>>> -
>>>>>>>> -------- Dive into the World of Parallel Programming! The Go Parallel
>>>>>>>> Website, sponsored by Intel and developed in partnership with
>>>>>>>> Slashdot Media, is your hub for all things parallel software
>>>>>>>> development, from weekly thought leadership blogs to news, videos,
>>>>>>>> case studies, tutorials and more. Take a look and join the conversation now.
>>>>>>>> http://goparallel.sourceforge.net
>>>>>>>> _______________________________________________
>>>>>>>> Mondo-devel mailing list
>>>>>>>> [hidden email]
>>>>>>>> https://lists.sourceforge.net/lists/listinfo/mondo-devel
>>>>>>>> ---------------------------------------------------------------------
>>>>>>>> -
>>>>>>>> -------- Dive into the World of Parallel Programming! The Go Parallel
>>>>>>>> Website, sponsored by Intel and developed in partnership with
>>>>>>>> Slashdot Media, is your hub for all things parallel software
>>>>>>>> development, from weekly thought leadership blogs to news, videos,
>>>>>>>> case studies, tutorials and more. Take a look and join the conversation now.
>>>>>>>> http://goparallel.sourceforge.net
>>>>>>>> _______________________________________________
>>>>>>>> Mondo-devel mailing list
>>>>>>>> [hidden email]
>>>>>>>> https://lists.sourceforge.net/lists/listinfo/mondo-devel
>>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> ----------------------------------------------------------------------
>>>>>>> -------- Dive into the World of Parallel Programming! The Go Parallel
>>>>>>> Website, sponsored by Intel and developed in partnership with Slashdot
>>>>>>> Media, is your hub for all things parallel software development, from
>>>>>>> weekly thought leadership blogs to news, videos, case studies,
>>>>>>> tutorials and more. Take a look and join the conversation now.
>>>>>>> http://goparallel.sourceforge.net 
>>>>>>> _______________________________________________
>>>>>>> Mondo-devel mailing list
>>>>>>> [hidden email]
>>>>>>> https://lists.sourceforge.net/lists/listinfo/mondo-devel
>>>>>>> ----------------------------------------------------------------------
>>>>>>> -------- Dive into the World of Parallel Programming! The Go Parallel
>>>>>>> Website, sponsored by Intel and developed in partnership with Slashdot
>>>>>>> Media, is your hub for all things parallel software development, from
>>>>>>> weekly thought leadership blogs to news, videos, case studies,
>>>>>>> tutorials and more. Take a look and join the conversation now.
>>>>>>> http://goparallel.sourceforge.net 
>>>>>>> _______________________________________________
>>>>>>> Mondo-devel mailing list
>>>>>>> [hidden email]
>>>>>>> https://lists.sourceforge.net/lists/listinfo/mondo-devel
>>>>>>>
>>>>>>
>>>>>>
>>>>>> ------------------------------------------------------------------------------
>>>>>> New Year. New Location. New Benefits. New Data Center in Ashburn, VA.
>>>>>> GigeNET is offering a free month of service with a new server in Ashburn.
>>>>>> Choose from 2 high performing configs, both with 100TB of bandwidth.
>>>>>> Higher redundancy.Lower latency.Increased capacity.Completely compliant.
>>>>>> http://p.sf.net/sfu/gigenet
>>>>>> _______________________________________________
>>>>>> Mondo-devel mailing list
>>>>>> [hidden email]
>>>>>> https://lists.sourceforge.net/lists/listinfo/mondo-devel
>>>>>>
>>>>>
>>>>>
>>>>
>>>>> mindi v3.0.0-r3332
>>>>> x86_64 architecture detected
>>>>> mindi called with the following arguments:
>>>>> --makemountlist /tmp/mondo.tmp.4v41Vd/mountlist.txt.test
>>>>> Start date : lundi 19 janvier 2015, 22:16:43 (UTC+0100)
>>>>> -----------------------------
>>>>> MONDO_SHARE = /usr/share/mondo
>>>>> MINDI_LIB = /usr/lib/mindi
>>>>> MINDI_SBIN = /usr/sbin
>>>>> MINDI_CONF = /etc/mindi
>>>>> -----------------------------
>>>>>  Mindi configuration file    
>>>>> -----------------------------
>>>>> -----------------------------
>>>>> In Mindi
>>>>> --------
>>>>> EXTRA_SPACE = 120000
>>>>> BOOT_SIZE = 65600
>>>>> --------
>>>>> INFO: Found isolinux.bin at /usr/lib/syslinux/isolinux.bin
>>>>> INFO: LVM set to v2
>>>>> ----------
>>>>> mount result:
>>>>> -------------
>>>>> sysfs on /sys type sysfs (rw,nosuid,nodev,noexec,relatime)
>>>>> proc on /proc type proc (rw,nosuid,nodev,noexec,relatime)
>>>>> udev on /dev type devtmpfs (rw,relatime,size=10240k,nr_inodes=497709,mode=755)
>>>>> devpts on /dev/pts type devpts (rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000)
>>>>> tmpfs on /run type tmpfs (rw,nosuid,noexec,relatime,size=406288k,mode=755)
>>>>> /dev/disk/by-uuid/4a5a9317-0b70-4796-a094-d61c01891c81 on / type ext4 (rw,relatime,errors=remount-ro,user_xattr,barrier=1,data=ordered)
>>>>> tmpfs on /run/lock type tmpfs (rw,nosuid,nodev,noexec,relatime,size=5120k)
>>>>> tmpfs on /run/shm type tmpfs (rw,nosuid,nodev,noexec,relatime,size=1008560k)
>>>>> /dev/mapper/sysvg-optlv on /opt type ext4 (rw,relatime,errors=remount-ro,user_xattr,barrier=1,data=ordered)
>>>>> /dev/mapper/data1vg-homelv on /home type ext4 (rw,relatime,errors=remount-ro,user_xattr,barrier=1,data=ordered)
>>>>> /dev/mapper/data1vg-wwwlv on /www type ext4 (rw,relatime,errors=remount-ro,user_xattr,barrier=1,data=ordered)
>>>>> /dev/mapper/data1vg-baseslv on /bases type ext4 (rw,relatime,errors=remount-ro,user_xattr,barrier=1,data=ordered)
>>>>> /dev/mapper/data1vg-photoslv on /photos type ext4 (rw,relatime,errors=remount-ro,user_xattr,barrier=1,data=ordered)
>>>>> /dev/mapper/data1vg-videoslv on /videos type ext4 (rw,relatime,errors=remount-ro,user_xattr,barrier=1,data=ordered)
>>>>> /dev/mapper/data1vg-vboxlv on /vbox type ext4 (rw,relatime,errors=remount-ro,user_xattr,barrier=1,data=ordered)
>>>>> /dev/mapper/data1vg-graveurlv on /graveur type ext4 (rw,relatime,errors=remount-ro,user_xattr,barrier=1,data=ordered)
>>>>> rpc_pipefs on /var/lib/nfs/rpc_pipefs type rpc_pipefs (rw,relatime)
>>>>> binfmt_misc on /proc/sys/fs/binfmt_misc type binfmt_misc (rw,nosuid,nodev,noexec,relatime)
>>>>> No file /etc/raidtab
>>>>> -------------
>>>>> No file /etc/mdadm.conf
>>>>> -------------
>>>>> cat /proc/cmdline
>>>>> -------------
>>>>> BOOT_IMAGE=/boot/vmlinuz-3.2.0-4-amd64 root=UUID=4a5a9317-0b70-4796-a094-d61c01891c81 ro quiet
>>>>> -------------
>>>>> cat /proc/swaps:
>>>>> -------------
>>>>> Filename Type Size Used Priority
>>>>> /dev/sda6                               partition 979928 11992 -1
>>>>> -------------
>>>>> cat /proc/mdstat:
>>>>> -------------
>>>>> Personalities : [linear] [raid0] [raid1] [raid6] [raid5] [raid4]
>>>>> unused devices: <none>
>>>>> -------------
>>>>> cat /proc/partitions:
>>>>> -------------
>>>>> major minor  #blocks  name
>>>>>
>>>>>    8        0  312571224 sda
>>>>>    8        1      56196 sda1
>>>>>    8        2   10485760 sda2
>>>>>    8        3  103643080 sda3
>>>>>    8        4          1 sda4
>>>>>    8        5   97659103 sda5
>>>>>    8        6     979933 sda6
>>>>>    8        7   99741696 sda7
>>>>>   11        0    1048575 sr0
>>>>>    8       16  976762584 sdb
>>>>>    8       17  976761560 sdb1
>>>>>  253        0   73400320 dm-0
>>>>>  253        1  157286400 dm-1
>>>>>  253        2   52428800 dm-2
>>>>>  253        3   20971520 dm-3
>>>>>  253        4    4886528 dm-4
>>>>>  253        5    1953792 dm-5
>>>>>  253        6  136720384 dm-6
>>>>>  253        7   17072128 dm-7
>>>>> -------------
>>>>> cat /proc/filesystems:
>>>>> -------------
>>>>> nodev sysfs
>>>>> nodev rootfs
>>>>> nodev bdev
>>>>> nodev proc
>>>>> nodev cgroup
>>>>> nodev cpuset
>>>>> nodev tmpfs
>>>>> nodev devtmpfs
>>>>> nodev debugfs
>>>>> nodev securityfs
>>>>> nodev sockfs
>>>>> nodev pipefs
>>>>> nodev anon_inodefs
>>>>> nodev devpts
>>>>> nodev ramfs
>>>>> nodev hugetlbfs
>>>>> nodev pstore
>>>>> nodev mqueue
>>>>> nodev usbfs
>>>>> ext4
>>>>> nodev ecryptfs
>>>>> nodev rpc_pipefs
>>>>> nodev nfs
>>>>> nodev nfs4
>>>>> nodev nfsd
>>>>> nodev binfmt_misc
>>>>> msdos
>>>>> vfat
>>>>> iso9660
>>>>> ext2
>>>>> -------------
>>>>> lsmod result:
>>>>> -------------
>>>>> Module                  Size  Used by
>>>>> nls_utf8               12456  0
>>>>> nls_cp437              16553  0
>>>>> ext2                   59231  0
>>>>> raid456                48453  0
>>>>> async_raid6_recov      12574  1 raid456
>>>>> async_memcpy           12387  2 async_raid6_recov,raid456
>>>>> async_pq               12605  2 async_raid6_recov,raid456
>>>>> raid6_pq               82624  2 async_pq,async_raid6_recov
>>>>> async_xor              12422  3 async_pq,async_raid6_recov,raid456
>>>>> xor                    12605  1 async_xor
>>>>> async_tx               12604  5 async_xor,async_pq,async_memcpy,async_raid6_recov,raid456
>>>>> raid1                  30714  0
>>>>> raid0                  12904  0
>>>>> linear                 12735  0
>>>>> isofs                  35173  0
>>>>> brd                    12772  0
>>>>> vfat                   17316  0
>>>>> msdos                  17077  0
>>>>> fat                    45642  2 msdos,vfat
>>>>> pci_stub               12429  1
>>>>> vboxpci                19096  0
>>>>> vboxnetadp             25443  0
>>>>> vboxnetflt             23657  0
>>>>> vboxdrv               304550  3 vboxnetflt,vboxnetadp,vboxpci
>>>>> nfnetlink_log          17212  0
>>>>> nfnetlink              12906  1 nfnetlink_log
>>>>> parport_pc             22364  0
>>>>> ppdev                  12763  0
>>>>> lp                     17149  0
>>>>> parport                31858  3 lp,ppdev,parport_pc
>>>>> ip6t_REJECT            12512  2
>>>>> xt_multiport           12548  2
>>>>> xt_conntrack           12681  18
>>>>> iptable_nat            12928  0
>>>>> binfmt_misc            12957  1
>>>>> iptable_mangle         12536  0
>>>>> nfsd                  216181  2
>>>>> nfs                   308353  0
>>>>> nfs_acl                12511  2 nfs,nfsd
>>>>> auth_rpcgss            37143  2 nfs,nfsd
>>>>> fscache                36739  1 nfs
>>>>> lockd                  67306  2 nfs,nfsd
>>>>> sunrpc                173730  6 lockd,auth_rpcgss,nfs_acl,nfs,nfsd
>>>>> ip6t_LOG               12609  4
>>>>> xt_hl                  12449  6
>>>>> ip6t_rt                12499  3
>>>>> nf_conntrack_ipv6      13316  7
>>>>> nf_defrag_ipv6         12832  1 nf_conntrack_ipv6
>>>>> ipt_REJECT             12502  1
>>>>> ipt_LOG                12605  12
>>>>> xt_limit               12638  19
>>>>> xt_tcpudp              12570  62
>>>>> xt_addrtype            12557  4
>>>>> xt_state               12503  21
>>>>> ip6table_filter        12540  1
>>>>> ip6_tables             22175  3 ip6table_filter,ip6t_rt,ip6t_LOG
>>>>> nf_conntrack_netbios_ns    12445  0
>>>>> nf_conntrack_broadcast    12365  1 nf_conntrack_netbios_ns
>>>>> nf_nat_ftp             12460  0
>>>>> nf_nat                 18242  2 nf_nat_ftp,iptable_nat
>>>>> nf_conntrack_ipv4      14078  35 nf_nat,iptable_nat
>>>>> nf_defrag_ipv4         12483  1 nf_conntrack_ipv4
>>>>> nf_conntrack_ftp       12605  1 nf_nat_ftp
>>>>> nf_conntrack           52720  10 nf_conntrack_ftp,nf_conntrack_ipv4,nf_nat,nf_nat_ftp,nf_conntrack_broadcast,nf_conntrack_netbios_ns,xt_state,nf_conntrack_ipv6,iptable_nat,xt_conntrack
>>>>> iptable_filter         12536  1
>>>>> ip_tables              22042  3 iptable_filter,iptable_mangle,iptable_nat
>>>>> x_tables               19118  18 ip_tables,iptable_filter,ip6_tables,ip6table_filter,xt_state,xt_addrtype,xt_tcpudp,xt_limit,ipt_LOG,ipt_REJECT,ip6t_rt,xt_hl,ip6t_LOG,iptable_mangle,iptable_nat,xt_conntrack,xt_multiport,ip6t_REJECT
>>>>> loop                   22641  0
>>>>> ecryptfs               81507  0
>>>>> dm_crypt               22586  0
>>>>> snd_hda_codec_hdmi     30824  1
>>>>> snd_usb_audio          89083  2
>>>>> snd_usbmidi_lib        23369  1 snd_usb_audio
>>>>> snd_seq_midi           12848  0
>>>>> snd_seq_midi_event     13316  1 snd_seq_midi
>>>>> snd_rawmidi            23060  2 snd_seq_midi,snd_usbmidi_lib
>>>>> snd_hda_codec_idt      53792  1
>>>>> tuner_simple           17175  1
>>>>> tuner_types            16409  1 tuner_simple
>>>>> wm8775                 12749  1
>>>>> tda9887                12645  1
>>>>> tda8290                17278  0
>>>>> tuner                  17497  2
>>>>> cx25840                39782  1
>>>>> ivtv                  129010  0
>>>>> cx2341x                21461  1 ivtv
>>>>> snd_hda_intel          26259  2
>>>>> snd_hda_codec          78031  3 snd_hda_intel,snd_hda_codec_idt,snd_hda_codec_hdmi
>>>>> snd_hwdep              13186  2 snd_hda_codec,snd_usb_audio
>>>>> snd_pcm                68083  4 snd_hda_codec,snd_hda_intel,snd_usb_audio,snd_hda_codec_hdmi
>>>>> tveeprom               20593  1 ivtv
>>>>> v4l2_common            13222  5 cx2341x,ivtv,cx25840,tuner,wm8775
>>>>> videodev               70889  6 v4l2_common,cx2341x,ivtv,cx25840,tuner,wm8775
>>>>> v4l2_compat_ioctl32    16655  1 videodev
>>>>> media                  18148  1 videodev
>>>>> nv_tco                 12914  0
>>>>> i2c_algo_bit           12841  1 ivtv
>>>>> snd_page_alloc         13003  2 snd_pcm,snd_hda_intel
>>>>> snd_seq                45126  2 snd_seq_midi_event,snd_seq_midi
>>>>> snd_seq_device         13176  3 snd_seq,snd_rawmidi,snd_seq_midi
>>>>> i2c_nforce2            12584  0
>>>>> dcdbas                 13307  0
>>>>> edac_mce_amd           17103  0
>>>>> edac_core              35258  0
>>>>> evdev                  17562  18
>>>>> powernow_k8            17618  1
>>>>> mperf                  12453  1 powernow_k8
>>>>> k8temp                 12647  0
>>>>> psmouse                69265  0
>>>>> snd_timer              22917  2 snd_seq,snd_pcm
>>>>> i2c_core               23876  12 i2c_nforce2,i2c_algo_bit,videodev,v4l2_common,tveeprom,ivtv,cx25840,tuner,tda8290,tda9887,wm8775,tuner_simple
>>>>> serio_raw              12931  0
>>>>> fglrx                2634136  183
>>>>> pcspkr                 12579  0
>>>>> snd                    52893  20 snd_timer,snd_seq_device,snd_seq,snd_pcm,snd_hwdep,snd_hda_codec,snd_hda_intel,snd_hda_codec_idt,snd_rawmidi,snd_usbmidi_lib,snd_usb_audio,snd_hda_codec_hdmi
>>>>> processor              28149  1 powernow_k8
>>>>> button                 12937  1 fglrx
>>>>> soundcore              13065  1 snd
>>>>> thermal_sys            18040  1 processor
>>>>> ext4                  350804  9
>>>>> crc16                  12343  1 ext4
>>>>> jbd2                   62115  1 ext4
>>>>> mbcache                13114  2 ext4,ext2
>>>>> dm_mod                 63645  29 dm_crypt
>>>>> md_mod                 87742  4 linear,raid0,raid1,raid456
>>>>> sg                     25874  0
>>>>> sd_mod                 36136  6
>>>>> sr_mod                 21899  0
>>>>> cdrom                  35401  1 sr_mod
>>>>> crc_t10dif             12348  1 sd_mod
>>>>> usbhid                 36418  0
>>>>> hid                    81372  1 usbhid
>>>>> usb_storage            43870  0
>>>>> ata_generic            12479  0
>>>>> ohci_hcd               26563  0
>>>>> sata_nv                26690  4
>>>>> libata                140630  2 sata_nv,ata_generic
>>>>> ehci_hcd               40249  0
>>>>> b44                    27751  0
>>>>> ssb                    44714  1 b44
>>>>> mmc_core               68400  1 ssb
>>>>> mii                    12675  1 b44
>>>>> pcmcia                 32734  1 ssb
>>>>> pcmcia_core            18294  1 pcmcia
>>>>> scsi_mod              162321  5 libata,usb_storage,sr_mod,sd_mod,sg
>>>>> usbcore               128741  7 ehci_hcd,ohci_hcd,usb_storage,usbhid,snd_usbmidi_lib,snd_usb_audio
>>>>> usb_common             12354  1 usbcore
>>>>> -------------
>>>>> FORCE_MODS:
>>>>> -------------
>>>>>
>>>>> -------------
>>>>> DENY_MODS:
>>>>> -------------
>>>>> kqemu vxfen
>>>>> -------------
>>>>> df result:
>>>>> ----------
>>>>> Sys. fich.                                             Type        1K-blocks     Util. Disponible Uti% Mont?? sur
>>>>> rootfs                                                 rootfs       96124904  10822540   80419412  12% /
>>>>> sysfs                                                  sysfs               0         0          0    - /sys
>>>>> proc                                                   proc                0         0          0    - /proc
>>>>> udev                                                   devtmpfs        10240         0      10240   0% /dev
>>>>> devpts                                                 devpts              0         0          0    - /dev/pts
>>>>> tmpfs                                                  tmpfs          406288       944     405344   1% /run
>>>>> /dev/disk/by-uuid/4a5a9317-0b70-4796-a094-d61c01891c81 ext4         96124904  10822540   80419412  12% /
>>>>> tmpfs                                                  tmpfs            5120         0       5120   0% /run/lock
>>>>> tmpfs                                                  tmpfs         1008560       276    1008284   1% /run/shm
>>>>> /dev/mapper/sysvg-optlv                                ext4         16803708  15010400     939704  95% /opt
>>>>> /dev/mapper/data1vg-homelv                             ext4         51606140  41866076    7119008  86% /home
>>>>> /dev/mapper/data1vg-wwwlv                              ext4          4809704   2794384    1770996  62% /www
>>>>> /dev/mapper/data1vg-baseslv                            ext4          1923084    737276    1088120  41% /bases
>>>>> /dev/mapper/data1vg-photoslv                           ext4         72248648  45036992   23541896  66% /photos
>>>>> /dev/mapper/data1vg-videoslv                           ext4        154818540 108302512   38651708  74% /videos
>>>>> /dev/mapper/data1vg-vboxlv                             ext4        134573320 104068176   23669128  82% /vbox
>>>>> /dev/mapper/data1vg-graveurlv                          ext4         20642428   8094972   11498880  42% /graveur
>>>>> rpc_pipefs                                             rpc_pipefs          0         0          0    - /var/lib/nfs/rpc_pipefs
>>>>> binfmt_misc                                            binfmt_misc         0         0          0    - /proc/sys/fs/binfmt_misc
>>>>> -------------
>>>>> df -i result:
>>>>> ----------
>>>>> Sys. fich.                                              Inodes IUtil.  ILibre IUti% Mont?? sur
>>>>> rootfs                                                 6111232 313566 5797666    6% /
>>>>> udev                                                    497709    610  497099    1% /dev
>>>>> tmpfs                                                   507860    667  507193    1% /run
>>>>> /dev/disk/by-uuid/4a5a9317-0b70-4796-a094-d61c01891c81 6111232 313566 5797666    6% /
>>>>> tmpfs                                                   507860      3  507857    1% /run/lock
>>>>> tmpfs                                                   507860     15  507845    1% /run/shm
>>>>> /dev/mapper/sysvg-optlv                                1068960  54781 1014179    6% /opt
>>>>> /dev/mapper/data1vg-homelv                             3276800  83092 3193708    3% /home
>>>>> /dev/mapper/data1vg-wwwlv                               305824  43214  262610   15% /www
>>>>> /dev/mapper/data1vg-baseslv                             122160   1213  120947    1% /bases
>>>>> /dev/mapper/data1vg-photoslv                           4587520  23609 4563911    1% /photos
>>>>> /dev/mapper/data1vg-videoslv                           9830400    180 9830220    1% /videos
>>>>> /dev/mapper/data1vg-vboxlv                             8552448     91 8552357    1% /vbox
>>>>> /dev/mapper/data1vg-graveurlv                          1310720     80 1310640    1% /graveur
>>>>> -------------
>>>>> -------------
>>>>> INFO: /boot/grub/grub.cfg content
>>>>> -------------
>>>>> #
>>>>> # DO NOT EDIT THIS FILE
>>>>> #
>>>>> # It is automatically generated by grub-mkconfig using templates
>>>>> # from /etc/grub.d and settings from /etc/default/grub
>>>>> #
>>>>>
>>>>> ### BEGIN /etc/grub.d/00_header ###
>>>>> if [ -s $prefix/grubenv ]; then
>>>>>   load_env
>>>>> fi
>>>>> set default="0"
>>>>> if [ "${prev_saved_entry}" ]; then
>>>>>   set saved_entry="${prev_saved_entry}"
>>>>>   save_env saved_entry
>>>>>   set prev_saved_entry=
>>>>>   save_env prev_saved_entry
>>>>>   set boot_once=true
>>>>> fi
>>>>>
>>>>> function savedefault {
>>>>>   if [ -z "${boot_once}" ]; then
>>>>>     saved_entry="${chosen}"
>>>>>     save_env saved_entry
>>>>>   fi
>>>>> }
>>>>>
>>>>> function load_video {
>>>>>   insmod vbe
>>>>>   insmod vga
>>>>>   insmod video_bochs
>>>>>   insmod video_cirrus
>>>>> }
>>>>>
>>>>> insmod part_msdos
>>>>> insmod ext2
>>>>> set root='(hd0,msdos5)'
>>>>> search --no-floppy --fs-uuid --set=root 4a5a9317-0b70-4796-a094-d61c01891c81
>>>>> if loadfont /usr/share/grub/unicode.pf2 ; then
>>>>>   set gfxmode=640x480
>>>>>   load_video
>>>>>   insmod gfxterm
>>>>>   insmod part_msdos
>>>>>   insmod ext2
>>>>>   set root='(hd0,msdos5)'
>>>>>   search --no-floppy --fs-uuid --set=root 4a5a9317-0b70-4796-a094-d61c01891c81
>>>>>   set locale_dir=($root)/boot/grub/locale
>>>>>   set lang=fr_FR
>>>>>   insmod gettext
>>>>> fi
>>>>> terminal_output gfxterm
>>>>> set timeout=5
>>>>> ### END /etc/grub.d/00_header ###
>>>>>
>>>>> ### BEGIN /etc/grub.d/05_debian_theme ###
>>>>> insmod part_msdos
>>>>> insmod ext2
>>>>> set root='(hd0,msdos5)'
>>>>> search --no-floppy --fs-uuid --set=root 4a5a9317-0b70-4796-a094-d61c01891c81
>>>>> insmod png
>>>>> if background_image /usr/share/images/desktop-base/joy-grub.png; then
>>>>>   set color_normal=white/black
>>>>>   set color_highlight=black/white
>>>>> else
>>>>>   set menu_color_normal=cyan/blue
>>>>>   set menu_color_highlight=white/blue
>>>>> fi
>>>>> ### END /etc/grub.d/05_debian_theme ###
>>>>>
>>>>> ### BEGIN /etc/grub.d/10_linux ###
>>>>> menuentry 'Debian GNU/Linux, avec Linux 3.2.0-4-amd64' --class debian --class gnu-linux --class gnu --class os {
>>>>> load_video
>>>>> insmod gzio
>>>>> insmod part_msdos
>>>>> insmod ext2
>>>>> set root='(hd0,msdos5)'
>>>>> search --no-floppy --fs-uuid --set=root 4a5a9317-0b70-4796-a094-d61c01891c81
>>>>> echo 'Chargement de Linux 3.2.0-4-amd64 ...'
>>>>> linux /boot/vmlinuz-3.2.0-4-amd64 root=UUID=4a5a9317-0b70-4796-a094-d61c01891c81 ro  quiet
>>>>> echo 'Chargement du disque m??moire initial ...'
>>>>> initrd /boot/initrd.img-3.2.0-4-amd64
>>>>> }
>>>>> menuentry 'Debian GNU/Linux, avec Linux 3.2.0-4-amd64 (mode de d??pannage)' --class debian --class gnu-linux --class gnu --class os {
>>>>> load_video
>>>>> insmod gzio
>>>>> insmod part_msdos
>>>>> insmod ext2
>>>>> set root='(hd0,msdos5)'
>>>>> search --no-floppy --fs-uuid --set=root 4a5a9317-0b70-4796-a094-d61c01891c81
>>>>> echo 'Chargement de Linux 3.2.0-4-amd64 ...'
>>>>> linux /boot/vmlinuz-3.2.0-4-amd64 root=UUID=4a5a9317-0b70-4796-a094-d61c01891c81 ro single
>>>>> echo 'Chargement du disque m??moire initial ...'
>>>>> initrd /boot/initrd.img-3.2.0-4-amd64
>>>>> }
>>>>> ### END /etc/grub.d/10_linux ###
>>>>>
>>>>> ### BEGIN /etc/grub.d/20_linux_xen ###
>>>>> ### END /etc/grub.d/20_linux_xen ###
>>>>>
>>>>> ### BEGIN /etc/grub.d/20_memtest86+ ###
>>>>> menuentry "Memory test (memtest86+)" {
>>>>> insmod part_msdos
>>>>> insmod ext2
>>>>> set root='(hd0,msdos5)'
>>>>> search --no-floppy --fs-uuid --set=root 4a5a9317-0b70-4796-a094-d61c01891c81
>>>>> linux16 /boot/memtest86+.bin
>>>>> }
>>>>> menuentry "Memory test (memtest86+, serial console 115200)" {
>>>>> insmod part_msdos
>>>>> insmod ext2
>>>>> set root='(hd0,msdos5)'
>>>>> search --no-floppy --fs-uuid --set=root 4a5a9317-0b70-4796-a094-d61c01891c81
>>>>> linux16 /boot/memtest86+.bin console=ttyS0,115200n8
>>>>> }
>>>>> menuentry "Memory test (memtest86+, experimental multiboot)" {
>>>>> insmod part_msdos
>>>>> insmod ext2
>>>>> set root='(hd0,msdos5)'
>>>>> search --no-floppy --fs-uuid --set=root 4a5a9317-0b70-4796-a094-d61c01891c81
>>>>> multiboot /boot/memtest86+_multiboot.bin
>>>>> }
>>>>> menuentry "Memory test (memtest86+, serial console 115200, experimental multiboot)" {
>>>>> insmod part_msdos
>>>>> insmod ext2
>>>>> set root='(hd0,msdos5)'
>>>>> search --no-floppy --fs-uuid --set=root 4a5a9317-0b70-4796-a094-d61c01891c81
>>>>> multiboot /boot/memtest86+_multiboot.bin console=ttyS0,115200n8
>>>>> }
>>>>> ### END /etc/grub.d/20_memtest86+ ###
>>>>>
>>>>> ### BEGIN /etc/grub.d/30_os-prober ###
>>>>> menuentry "Windows Vista (loader) (on /dev/sda3)" --class windows --class os {
>>>>> insmod part_msdos
>>>>> insmod ntfs
>>>>> set root='(hd0,msdos3)'
>>>>> search --no-floppy --fs-uuid --set=root 0C6CE0BA6CE0A026
>>>>> chainloader +1
>>>>> }
>>>>> ### END /etc/grub.d/30_os-prober ###
>>>>>
>>>>> ### BEGIN /etc/grub.d/40_custom ###
>>>>> # This file provides an easy way to add custom menu entries.  Simply type the
>>>>> # menu entries you want to add after this comment.  Be careful not to change
>>>>> # the 'exec tail' line above.
>>>>> ### END /etc/grub.d/40_custom ###
>>>>>
>>>>> ### BEGIN /etc/grub.d/41_custom ###
>>>>> if [ -f  $prefix/custom.cfg ]; then
>>>>>   source $prefix/custom.cfg;
>>>>> fi
>>>>> ### END /etc/grub.d/41_custom ###
>>>>> -------------
>>>>> -------------
>>>>> INFO: /boot/grub/device.map content
>>>>> -------------
>>>>> (hd0) /dev/disk/by-id/ata-ST3320620AS_5QF2VWM8
>>>>> -------------
>>>>> Full fdisk info
>>>>> ---------------
>>>>>
>>>>> Disque /dev/sda??: 320.1??Go, 320072933376??octets
>>>>> 255??t??tes, 63??secteurs/piste, 38913??cylindres, total 625142448??secteurs
>>>>> Unit??s = secteurs de 1 * 512 = 512??octets
>>>>> Taille de secteur (logique / physique)??: 512??octets / 512??octets
>>>>> taille d'E/S (minimale / optimale)??: 512??octets / 512??octets
>>>>> Identifiant de disque??: 0x58000000
>>>>>
>>>>> P??riph??rique Amorce  D??but        Fin      Blocs     Id  Syst??me
>>>>> /dev/sda1              63      112454       56196   de  Dell Utility
>>>>> /dev/sda2          112640    21084159    10485760    7  HPFS/NTFS/exFAT
>>>>> /dev/sda3   *    21093345   228379505   103643080+   7  HPFS/NTFS/exFAT
>>>>> /dev/sda4       228380101   625141759   198380829+   5  ??tendue
>>>>> /dev/sda5       228380103   423698309    97659103+  83  Linux
>>>>> /dev/sda6       423698373   425658239      979933+  82  partition d'??change Linux / Solaris
>>>>> /dev/sda7       425658368   625141759    99741696   8e  LVM Linux
>>>>>
>>>>> Disque /dev/sdb??: 1000.2??Go, 1000204886016??octets
>>>>> 81??t??tes, 63??secteurs/piste, 382818??cylindres, total 1953525168??secteurs
>>>>> Unit??s = secteurs de 1 * 512 = 512??octets
>>>>> Taille de secteur (logique / physique)??: 512??octets / 512??octets
>>>>> taille d'E/S (minimale / optimale)??: 512??octets / 512??octets
>>>>> Identifiant de disque??: 0x0003513f
>>>>>
>>>>> P??riph??rique Amorce  D??but        Fin      Blocs     Id  Syst??me
>>>>> /dev/sdb1            2048  1953525167   976761560   8e  LVM Linux
>>>>>
>>>>> Disque /dev/mapper/data1vg-photoslv??: 75.2??Go, 75161927680??octets
>>>>> 255??t??tes, 63??secteurs/piste, 9137??cylindres, total 146800640??secteurs
>>>>> Unit??s = secteurs de 1 * 512 = 512??octets
>>>>> Taille de secteur (logique / physique)??: 512??octets / 512??octets
>>>>> taille d'E/S (minimale / optimale)??: 512??octets / 512??octets
>>>>> Identifiant de disque??: 0x00000000
>>>>>
>>>>>
>>>>> Disque /dev/mapper/data1vg-videoslv??: 161.1??Go, 161061273600??octets
>>>>> 255??t??tes, 63??secteurs/piste, 19581??cylindres, total 314572800??secteurs
>>>>> Unit??s = secteurs de 1 * 512 = 512??octets
>>>>> Taille de secteur (logique / physique)??: 512??octets / 512??octets
>>>>> taille d'E/S (minimale / optimale)??: 512??octets / 512??octets
>>>>> Identifiant de disque??: 0x00000000
>>>>>
>>>>>
>>>>> Disque /dev/mapper/data1vg-homelv??: 53.7??Go, 53687091200??octets
>>>>> 255??t??tes, 63??secteurs/piste, 6527??cylindres, total 104857600??secteurs
>>>>> Unit??s = secteurs de 1 * 512 = 512??octets
>>>>> Taille de secteur (logique / physique)??: 512??octets / 512??octets
>>>>> taille d'E/S (minimale / optimale)??: 512??octets / 512??octets
>>>>> Identifiant de disque??: 0x00000000
>>>>>
>>>>>
>>>>> Disque /dev/mapper/data1vg-graveurlv??: 21.5??Go, 21474836480??octets
>>>>> 255??t??tes, 63??secteurs/piste, 2610??cylindres, total 41943040??secteurs
>>>>> Unit??s = secteurs de 1 * 512 = 512??octets
>>>>> Taille de secteur (logique / physique)??: 512??octets / 512??octets
>>>>> taille d'E/S (minimale / optimale)??: 512??octets / 512??octets
>>>>> Identifiant de disque??: 0x00000000
>>>>>
>>>>>
>>>>> Disque /dev/mapper/data1vg-wwwlv??: 5003??Mo, 5003804672??octets
>>>>> 255??t??tes, 63??secteurs/piste, 608??cylindres, total 9773056??secteurs
>>>>> Unit??s = secteurs de 1 * 512 = 512??octets
>>>>> Taille de secteur (logique / physique)??: 512??octets / 512??octets
>>>>> taille d'E/S (minimale / optimale)??: 512??octets / 512??octets
>>>>> Identifiant de disque??: 0x00000000
>>>>>
>>>>>
>>>>> Disque /dev/mapper/data1vg-baseslv??: 2000??Mo, 2000683008??octets
>>>>> 255??t??tes, 63??secteurs/piste, 243??cylindres, total 3907584??secteurs
>>>>> Unit??s = secteurs de 1 * 512 = 512??octets
>>>>> Taille de secteur (logique / physique)??: 512??octets / 512??octets
>>>>> taille d'E/S (minimale / optimale)??: 512??octets / 512??octets
>>>>> Identifiant de disque??: 0x00000000
>>>>>
>>>>>
>>>>> Disque /dev/mapper/data1vg-vboxlv??: 140.0??Go, 140001673216??octets
>>>>> 255??t??tes, 63??secteurs/piste, 17020??cylindres, total 273440768??secteurs
>>>>> Unit??s = secteurs de 1 * 512 = 512??octets
>>>>> Taille de secteur (logique / physique)??: 512??octets / 512??octets
>>>>> taille d'E/S (minimale / optimale)??: 512??octets / 512??octets
>>>>> Identifiant de disque??: 0x00000000
>>>>>
>>>>>
>>>>> Disque /dev/mapper/sysvg-optlv??: 17.5??Go, 17481859072??octets
>>>>> 255??t??tes, 63??secteurs/piste, 2125??cylindres, total 34144256??secteurs
>>>>> Unit??s = secteurs de 1 * 512 = 512??octets
>>>>> Taille de secteur (logique / physique)??: 512??octets / 512??octets
>>>>> taille d'E/S (minimale / optimale)??: 512??octets / 512??octets
>>>>> Identifiant de disque??: 0x00000000
>>>>>
>>>>> ----------------
>>>>> ------------------------------------
>>>>> Your raw fstab file looks like this:
>>>>> ------------------------------------
>>>>> # /etc/fstab: static file system information.
>>>>> #
>>>>> # Use 'blkid' to print the universally unique identifier for a
>>>>> # device; this may be used with UUID= as a more robust way to name devices
>>>>> # that works even if disks are added and removed. See fstab(5).
>>>>> #
>>>>> # <file system>        <mount point>     <type>      <options>                   <dump> <pass>
>>>>> # / was on /dev/sda5 during installation
>>>>> UUID=4a5a9317-0b70-4796-a094-d61c01891c81 /    ext4  errors=remount-ro           0      1
>>>>> # swap was on /dev/sda6 during installation
>>>>> UUID=b4d7e5c0-207b-4a67-8b58-20523c509b87 none swap  sw                          0      0
>>>>>
>>>>> /dev/sr0               /media/cdrom0     udf,iso9660 user,noauto                 0      0
>>>>>
>>>>> #/dev/sysvg/homelv      /home             ext4        relatime,errors=remount-ro  0      1
>>>>> /dev/sysvg/optlv       /opt              ext4        relatime,errors=remount-ro  0      1
>>>>>
>>>>> /dev/data1vg/homelv    /home             ext4        relatime,errors=remount-ro  0      2
>>>>> /dev/data1vg/wwwlv     /www              ext4        relatime,errors=remount-ro  0      2
>>>>> /dev/data1vg/baseslv   /bases            ext4        relatime,errors=remount-ro  0      2
>>>>> /dev/data1vg/photoslv  /photos           ext4        relatime,errors=remount-ro  0      2
>>>>> /dev/data1vg/videoslv  /videos           ext4        relatime,errors=remount-ro  0      2
>>>>> /dev/data1vg/vboxlv    /vbox             ext4        relatime,errors=remount-ro  0      2
>>>>> /dev/data1vg/graveurlv /graveur          ext4        relatime,errors=remount-ro  0      2
>>>>>
>>>>> # /dev/data0vg/homelv    /data0vg/home     ext4        relatime,errors=remount-ro  0      2
>>>>> # /dev/data0vg/wwwlv     /data0vg/www      ext4        relatime,errors=remount-ro  0      2
>>>>> # /dev/data0vg/baseslv   /data0vg/bases    ext4        relatime,errors=remount-ro  0      2
>>>>> # /dev/data0vg/photoslv  /data0vg/photos   ext4        relatime,errors=remount-ro  0      2
>>>>> # /dev/data0vg/videoslv  /data0vg/videos   ext4        relatime,errors=remount-ro  0      2
>>>>> # /dev/data0vg/vboxlv    /data0vg/vbox     ext4        relatime,errors=remount-ro  0      2
>>>>>
>>>>> # /dev/data2vg/homelv    /data2vg/home     ext4        relatime,errors=remount-ro  0      2
>>>>> # /dev/data2vg/wwwlv     /data2vg/www      ext4        relatime,errors=remount-ro  0      2
>>>>> # /dev/data2vg/baseslv   /data2vg/bases    ext4        relatime,errors=remount-ro  0      2
>>>>> # /dev/data2vg/photoslv  /data2vg/photos   ext4        relatime,errors=remount-ro  0      2
>>>>> # /dev/data2vg/videoslv  /data2vg/videos   ext4        relatime,errors=remount-ro  0      2
>>>>> # /dev/data2vg/vboxlv    /data2vg/vbox     ext4        relatime,errors=remount-ro  0      2
>>>>> -----------------------------------
>>>>> Your mountlist will look like this:
>>>>> -----------------------------------
>>>>> INFO: Analyzing LVM...
>>>>> DEVICE          MOUNTPOINT      FORMAT          SIZE MB       LABEL/UUID    
>>>>> ------          ----------      ------          -------       ----------    
>>>>> INFO: Examining /dev/sdb1 (mount=lvm fmt=lvm psz=976761560)
>>>>> /dev/sdb1       lvm             lvm              953868 c9qZKK-bpqn-sY7P-fWH2-SBlo-YsXS-udCgP7
>>>>> INFO: Examining /dev/sda7 (mount=lvm fmt=lvm psz=99741696)
>>>>> /dev/sda7       lvm             lvm               97404 yuL0j7-wJtb-ANiO-Omxi-AuEE-wCkJ-pfhEWi
>>>>> INFO: Examining /dev/sda5 (mount=/ fmt=ext4 psz=97659103)
>>>>> /dev/sda5       /               ext4              95370 4a5a9317-0b70-4796-a094-d61c01891c81
>>>>> INFO: Examining /dev/sda6 (mount=swap fmt=swap psz=979928)
>>>>> /dev/sda6       swap            swap                956 b4d7e5c0-207b-4a67-8b58-20523c509b87
>>>>> INFO: Examining /dev/sysvg/optlv (mount=/opt fmt=ext4 psz=lvm)
>>>>> /dev/sysvg/optlv /opt            ext4                lvm f1c4b976-0101-47ac-9ff8-c5a9e567553b
>>>>> INFO: Examining /dev/data1vg/homelv (mount=/home fmt=ext4 psz=lvm)
>>>>> /dev/data1vg/homelv /home           ext4                lvm e063df74-3fff-45ac-927d-bc6a60bd2970
>>>>> INFO: Examining /dev/data1vg/wwwlv (mount=/www fmt=ext4 psz=lvm)
>>>>> /dev/data1vg/wwwlv /www            ext4                lvm 7942603b-20c8-483a-ab36-98ee20ab7700
>>>>> INFO: Examining /dev/data1vg/baseslv (mount=/bases fmt=ext4 psz=lvm)
>>>>> /dev/data1vg/baseslv /bases          ext4                lvm 09f40cc9-fc3b-4205-a466-df38e5774a59
>>>>> INFO: Examining /dev/data1vg/photoslv (mount=/photos fmt=ext4 psz=lvm)
>>>>> /dev/data1vg/photoslv /photos         ext4                lvm 11ff707f-da12-46a3-9218-87fcf38ddc2f
>>>>> INFO: Examining /dev/data1vg/videoslv (mount=/videos fmt=ext4 psz=lvm)
>>>>> /dev/data1vg/videoslv /videos         ext4                lvm 11e0f5ef-75e4-4b7b-b34e-c9112b731f57
>>>>> INFO: Examining /dev/data1vg/vboxlv (mount=/vbox fmt=ext4 psz=lvm)
>>>>> /dev/data1vg/vboxlv /vbox           ext4                lvm 69e8fcf6-9518-4c3c-9052-53096c873cc4
>>>>> INFO: Examining /dev/data1vg/graveurlv (mount=/graveur fmt=ext4 psz=lvm)
>>>>> /dev/data1vg/graveurlv /graveur        ext4                lvm a5d30c9b-d333-46a3-8c28-ef2c4c1d9185
>>>>> -----------------------------------
>>>>> Mindi 3.0.0-r3332 is exiting
>>>>> End date : lundi 19 janvier 2015, 22:16:59 (UTC+0100)
>>>>
>>>>> INFO: Time started: Mon Jan 19 22:16:43 2015
>>>>>
>>>>> DBG2: [TH=22705] libmondo-tools.c->setup_tmpdir#715: bkpinfo->tmpdir is being set to /tmp/mondo.tmp.4v41Vd
>>>>> DBG2: [TH=22705] libmondo-tools.c->setup_scratchdir#736: Purging old scratchdir /mondo.scratch.*
>>>>> DBG2: [TH=22705] libmondo-tools.c->setup_scratchdir#757: bkpinfo->scratchdir is being set to /tmp/mondo.scratch.3mNp4N
>>>>> INFO: root is mounted at /dev/disk/by-uuid/aa9317-0b70-4796-a094-d61c01891c81
>>>>>
>>>>> INFO: That doesn't mean /dev/disk/by-uuid/aa9317-0b70-4796-a094-d61c01891c81 is the root partition. It's just a debugging message. Relax. It's part of am_I_in_disaster_recovery_mode().
>>>>> DBG1: [TH=22705] libmondo-devices.c->am_I_in_disaster_recovery_mode#163: Is this a ramdisk? result = FALSE
>>>>> INFO: running: dmesg -n1 > /tmp/mondo.tmp.4v41Vd/mondo-run-prog-thing.tmp 2> /tmp/mondo.tmp.4v41Vd/mondo-run-prog-thing.err
>>>>> INFO: --------------------------------start of output-----------------------------
>>>>> INFO: --------------------------------end of output------------------------------
>>>>> INFO: ...ran just fine. :-)
>>>>> INFO: Mondo Archive v3.2.0-r3332 --- http://www.mondorescue.org
>>>>> INFO: running x86_64 binaries
>>>>> INFO: running on x86_64 architecture
>>>>> INFO: -----------------------------------------------------------
>>>>> INFO: NB: Mondo logs almost everything, so don't panic if you see
>>>>> INFO: some error messages.  Please read them carefully before you
>>>>> INFO: decide to break out in a cold sweat.    Despite (or perhaps
>>>>> INFO: because of) the wealth of messages. some users are inclined
>>>>> INFO: to stop reading this log. If Mondo stopped for some reason,
>>>>> INFO: chances are it's detailed here.  More than likely there's a
>>>>> INFO: message at the very end of this log that will tell you what
>>>>> INFO: is wrong. Please read it!                          -Devteam
>>>>> INFO: -----------------------------------------------------------
>>>>> INFO: Zero...
>>>>> DBG1: [Main] mondoarchive.c->welcome_to_mondoarchive#96: One...
>>>>> DBG2: [Main] mondoarchive.c->welcome_to_mondoarchive#97: Two...
>>>>> DBG3: [Main] mondoarchive.c->welcome_to_mondoarchive#98: Three...
>>>>> DBG4: [Main] mondoarchive.c->welcome_to_mondoarchive#99: Four...
>>>>> DBG2: [Main] mondoarchive.c->distro_specific_kludges_at_start_of_mondoarchive#114: Unmounting old ramdisks if necessary
>>>>> INFO: running: mount | grep cdrom | grep super > /tmp/mondo.tmp.4v41Vd/mondo-run-prog-thing.tmp 2> /tmp/mondo.tmp.4v41Vd/mondo-run-prog-thing.err
>>>>> INFO: --------------------------------start of output-----------------------------
>>>>> INFO: --------------------------------end of output------------------------------
>>>>> INFO: ...ran with res=256
>>>>> INFO: running: mount | grep floppy | grep super > /tmp/mondo.tmp.4v41Vd/mondo-run-prog-thing.tmp 2> /tmp/mondo.tmp.4v41Vd/mondo-run-prog-thing.err
>>>>> INFO: --------------------------------start of output-----------------------------
>>>>> INFO: --------------------------------end of output------------------------------
>>>>> INFO: ...ran with res=256
>>>>> DBG1: [Main] libmondo-tools.c->mount_boot_if_necessary#1155: Started sub
>>>>> DBG4: [Main] libmondo-tools.c->mount_boot_if_necessary#1156: About to set g_boot_mountpt[0] to '\0'
>>>>> DBG4: [Main] libmondo-tools.c->mount_boot_if_necessary#1158: Done. Great. Seeting command to something
>>>>> DBG4: [Main] libmondo-tools.c->mount_boot_if_necessary#1160: Cool. Command = 'grep -v ":" /etc/fstab | grep -vE '^#.*$' | grep -E "[ ]/boot[ ]" | tr -s ' ' ' ' | cut -f1 | head -n1'
>>>>> DBG4: [Main] libmondo-tools.c->mount_boot_if_necessary#1164: tmp = ''
>>>>> DBG2: [Main] libmondo-tools.c->mount_boot_if_necessary#1165: /boot is at  according to /etc/fstab
>>>>> DBG3: [Main] libmondo-tools.c->mount_boot_if_necessary#1182: command = mount | grep -E '^'
>>>>> DBG1: [Main] libmondo-tools.c->mount_boot_if_necessary#1205: Ended sub
>>>>> DBG1: [Main] libmondo-tools.c->get_kernel_version#245: g_kernel_version = 3.200000
>>>>> INFO: running: rm -Rf /var/cache/mondo/changed.files* > /tmp/mondo.tmp.4v41Vd/mondo-run-prog-thing.tmp 2> /tmp/mondo.tmp.4v41Vd/mondo-run-prog-thing.err
>>>>> INFO: --------------------------------start of output-----------------------------
>>>>> INFO: --------------------------------end of output------------------------------
>>>>> INFO: ...ran just fine. :-)
>>>>> INFO: Checking sanity of your Linux distribution
>>>>> INFO: running: grep ramdisk /proc/devices > /tmp/mondo.tmp.4v41Vd/mondo-run-prog-thing.tmp 2> /tmp/mondo.tmp.4v41Vd/mondo-run-prog-thing.err
>>>>> INFO: --------------------------------start of output-----------------------------
>>>>> INFO: 1 ramdisk
>>>>> INFO: --------------------------------end of output------------------------------
>>>>> INFO: ...ran just fine. :-)
>>>>> INFO: running: mount | grep -Ew 'vfat|fat|dos' | grep -vE "/dev/fd|nexdisk" > /tmp/mondo.tmp.4v41Vd/mondo-run-prog-thing.tmp 2> /tmp/mondo.tmp.4v41Vd/mondo-run-prog-thing.err
>>>>> INFO: --------------------------------start of output-----------------------------
>>>>> INFO: --------------------------------end of output------------------------------
>>>>> INFO: ...ran with res=256
>>>>> DBG4: [Main] libmondo-files.c->find_home_of_exe#349: find_home_of_exe --- Found cmp at /usr/bin/cmp
>>>>> INFO: running: mindi -V > /tmp/mondo.tmp.4v41Vd/mondo-run-prog-thing.tmp 2> /tmp/mondo.tmp.4v41Vd/mondo-run-prog-thing.err
>>>>> INFO: --------------------------------start of output-----------------------------
>>>>> INFO: Mindi v3.0.0-r3332
>>>>> INFO: Le disque /dev/mapper/data1vg-photoslv ne contient pas une table de partitions valable
>>>>> INFO: Le disque /dev/mapper/data1vg-videoslv ne contient pas une table de partitions valable
>>>>> INFO: Le disque /dev/mapper/data1vg-homelv ne contient pas une table de partitions valable
>>>>> INFO: Le disque /dev/mapper/data1vg-graveurlv ne contient pas une table de partitions valable
>>>>> INFO: Le disque /dev/mapper/data1vg-wwwlv ne contient pas une table de partitions valable
>>>>> INFO: Le disque /dev/mapper/data1vg-baseslv ne contient pas une table de partitions valable
>>>>> INFO: Le disque /dev/mapper/data1vg-vboxlv ne contient pas une table de partitions valable
>>>>> INFO: Le disque /dev/mapper/sysvg-optlv ne contient pas une table de partitions valable
>>>>> INFO: --------------------------------end of output------------------------------
>>>>> INFO: ...ran just fine. :-)
>>>>> INFO: running: parted2fdisk -l 2>/dev/null | grep -i raid > /tmp/mondo.tmp.4v41Vd/mondo-run-prog-thing.tmp 2> /tmp/mondo.tmp.4v41Vd/mondo-run-prog-thing.err
>>>>> INFO: --------------------------------start of output-----------------------------
>>>>> INFO: --------------------------------end of output------------------------------
>>>>> INFO: ...ran with res=256
>>>>> INFO: Done.
>>>>> DBG1: [Main] libmondo-cli.c->process_switches#181: Loglevel forced to 99
>>>>> DBG20: [Main] libmondo-files.c->does_file_exist#188: /usr/bin/afio exists
>>>>> DBG4: [Main] libmondo-files.c->find_home_of_exe#349: find_home_of_exe --- Found afio at /usr/bin/afio
>>>>
>>>>> ------------------------------------------------------------------------------
>>>>> New Year. New Location. New Benefits. New Data Center in Ashburn, VA.
>>>>> GigeNET is offering a free month of service with a new server in Ashburn.
>>>>> Choose from 2 high performing configs, both with 100TB of bandwidth.
>>>>> Higher redundancy.Lower latency.Increased capacity.Completely compliant.
>>>>> http://p.sf.net/sfu/gigenet
>>>>
>>>>> _______________________________________________
>>>>> Mondo-devel mailing list
>>>>> [hidden email]
>>>>> https://lists.sourceforge.net/lists/listinfo/mondo-devel
>>>>
>>>>
>>>
>>>
>>
>>
>>
>>
>> ------------------------------------------------------------------------------
>> Dive into the World of Parallel Programming. The Go Parallel Website,
>> sponsored by Intel and developed in partnership with Slashdot Media, is your
>> hub for all things parallel software development, from weekly thought
>> leadership blogs to news, videos, case studies, tutorials and more. Take a
>> look and join the conversation now. http://goparallel.sourceforge.net/
>>
>>
>>
>> _______________________________________________
>> Mondo-devel mailing list
>> [hidden email]
>> https://lists.sourceforge.net/lists/listinfo/mondo-devel
>>
>
>
>
> ------------------------------------------------------------------------------
> Dive into the World of Parallel Programming. The Go Parallel Website,
> sponsored by Intel and developed in partnership with Slashdot Media, is your
> hub for all things parallel software development, from weekly thought
> leadership blogs to news, videos, case studies, tutorials and more. Take a
> look and join the conversation now. http://goparallel.sourceforge.net/
> _______________________________________________
> Mondo-devel mailing list
> [hidden email]
> https://lists.sourceforge.net/lists/listinfo/mondo-devel
>
>



------------------------------------------------------------------------------
Dive into the World of Parallel Programming. The Go Parallel Website,
sponsored by Intel and developed in partnership with Slashdot Media, is your
hub for all things parallel software development, from weekly thought
leadership blogs to news, videos, case studies, tutorials and more. Take a
look and join the conversation now. http://goparallel.sourceforge.net/
_______________________________________________
Mondo-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/mondo-devel
Reply | Threaded
Open this post in threaded view
|

Re: [Mondo-devel] Segmentation error running mondoarchive v3.2.0-r3332

Philippe Lefevre
Hello list,

I performed an entire backup test this morning with my fix.
That seems to be ok.
Please find attached the libmondo-cli.c fixed and a log trace from
mondoarchive.

Kind regards,
Philippe



Le 06/02/2015 21:53, Philippe Lefevre a écrit :

> Hi list,
>
> I believe I found where the issue with -I is.
>
> In fact, the structure bkpinfo is well built with an include_paths entry
> initialized to NULL, but there is no malloc that would allow to store
> any string.
>
> I compared how is parsed the -E and -I options and supposed they should
> work in quite the same way.
>
> It seems to me that there is some code missing in libmondo-cli.c. So I
> made the following changes and that seems to work.
>
> ================================================
> libmondo-cli.c
> 231:if (flag_set['I']) {
>       if (bkpinfo->include_paths && bkpinfo->include_paths[0] == '-'){
>         retval++;
>         log_to_screen("Please supply a sensible value with '-I'\n");
>         }
>
> // Added
> mr_asprintf(tmp1, "%s", flag_val['I']);
> p = tmp1;
> q = tmp1;
> // End add
>
> // Modified
> if (!strcmp(tmp1, "/")) {
> // End modif
>                         log_msg(2, "'/' is pleonastic.");
>                         mr_free(bkpinfo->include_paths);  // Not sure
> this is needed
>                 }
> // Modified
> if (tmp1[0]) {
> // End modif
>                         mr_strcat(bkpinfo->include_paths, "|");
>                 }
>
> 249 :   /* Cut the flag_val['I'] in parts containing all paths to test
> them */
> ================================================
>
>
>
> I hope this help :)
>
> Kind regards,
> Philippe
>
>
>
> Le 02/02/2015 21:00, Philippe Lefevre a écrit :
>> OOPS !
>>
>> In my latest email:
>>> I reran it from compiled sources but this time I also had the same
>>> trouble with it and was not able to get the error.
>>
>> I meant "I was unable to get it work well again as I described in my
>> email dated of 17th of januray"
>>
>> Kind Rgds,
>> Philippe
>>
>> Le 01/02/2015 23:17, Philippe Lefevre a écrit :
>>> Hello list,
>>>
>>> I did again some tries with mondo 3.2.0
>>> Right: without -I option it works.
>>>
>>> I reran it from compiled sources but this time I also had the same
>>> trouble with it and was not able to get the error.
>>>
>>> I tried to understand what happen with this option and I believe it is
>>> linked to the pointer bkpinfo->include_paths which is empty in
>>> libmondo-cli.c:236
>>> We can see that flag_val['I'] is well setted to the arg value and
>>> flag_set['I'] is true in process_switches()
>>>
>>> Sorry, I must stop now and I'm afraid I will not have time those next
>>> days to grab into it again (may be next we ??) but I hope these traces
>>> may help.
>>>
>>> Please find attached some gdb steps.
>>>
>>> Kind regards,
>>> Philippe
>>>
>>>
>>> Le 26/01/2015 22:10, Philippe Lefevre a écrit :
>>>>
>>>> Great !
>>>>
>>>> Many thanks for your help and reply Bruno.
>>>>
>>>> Next week-end I'm going to reinstall 3.2.0 and supress -I option and see
>>>> what happen.
>>>>
>>>> One thing is strange anyway: in my tests after a mondoarchive
>>>> compilation, (pls, see my email dated on 17th january) I ran 3.2.0 with
>>>> -I option without any issue. The sigsegv was repructible when
>>>> mondoarchive was installed by the deb package ...
>>>>
>>>> I used :
>>>> [phlsys]root:/home/phl/mondo-3.2.0# gdb -args mondoarchive -D -OV -i -N
>>>> -G -s 780M -p sys-D7.7-diff_150105212200 -T /graveur -S /graveur -d
>>>> /graveur -I "/|/|/opt/Zuma" -E
>>>> "/bases/sybase|/graveur|/home|/opt|/photos|/quemu|/Sauvegardes|/var/crash|/var/backups|/var/log|/var/mail|/var/spool|/vbox|/videos|/www"
>>>>
>>>> and:
>>>>  ....
>>>>  Data archived OK.
>>>>  Mondoarchive ran OK.
>>>>  See /var/log/mondoarchive.log for details of backup run.
>>>>  Execution run ended; result=0
>>>>  Type 'less /var/log/mondoarchive.log' to see the output log [Inferior 1
>>>> (process 19382) exited normally]
>>>>  (gdb) quit
>>>>
>>>>
>>>> I'll let you know.
>>>> Kind regards,
>>>> Philippe
>>>>
>>>>
>>>>
>>>> Le 26/01/2015 01:09, Bruno Cornec a écrit :
>>>>> Hello Philippe,
>>>>>
>>>>> This is now fixed as described in BR:
>>>>> http://trac.mondorescue.org/ticket/764#comment:2
>>>>>
>>>>> Bruno.
>>>>>
>>>>> Philippe Lefevre said on Mon, Jan 19, 2015 at 10:34:24PM +0100:
>>>>>
>>>>>> Hello Gaetagno,
>>>>>>
>>>>>> Regarding the two slashes, as I said, I used the same syntax to get into
>>>>>> the same bug situation.
>>>>>>
>>>>>>
>>>>>> I did a try with only one / in the -I option and got the same
>>>>>> segmentation violation exception.
>>>>>>
>>>>>>
>>>>>> Mindi launched alone as your example and it ran fine and the iso file
>>>>>> successfully built.
>>>>>> Please find attached the mindi.log file.
>>>>>>
>>>>>> [phlsys]root:/home/phl/Devel/mondo# ls -al /var/cache/mindi/mindi.iso
>>>>>> -rw-r----- 1 root root 98721792 janv. 19 22:09 /var/cache/mindi/mindi.iso
>>>>>>
>>>>>>
>>>>>>
>>>>>> Ran mondoarchive with -K99 option crashed again with the sigsegv signal.
>>>>>> Please find attached the mondoarchive.log file.
>>>>>> Unfortunately, I'm afraid it is not so verbose than we would ...
>>>>>> This time, the log ends with :
>>>>>>
>>>>>> DBG1: [Main] libmondo-cli.c->process_switches#181: Loglevel forced to 99
>>>>>> DBG20: [Main] libmondo-files.c->does_file_exist#188: /usr/bin/afio exists
>>>>>> DBG4: [Main] libmondo-files.c->find_home_of_exe#349: find_home_of_exe
>>>>>> --- Found afio at /usr/bin/afio
>>>>>>
>>>>>>
>>>>>>
>>>>>> Running mondo without - E option crashed in the same way and with same
>>>>>> mondoarchive.log file.
>>>>>> [phlsys]root:/home/phl/Devel/mondo# /usr/sbin/mondoarchive -K99 -D -OV
>>>>>> -i -N -G -s 780M -p sys-D7.7-diff_150105212200 -T /graveur -S /graveur
>>>>>> -d /graveur -I "/opt/zuma"
>>>>>> See /var/log/mondoarchive.log for details of backup run.
>>>>>> Checking sanity of your Linux distribution
>>>>>> Done.
>>>>>> Erreur de segmentation
>>>>>>
>>>>>>
>>>>>> Thank you for your time Gaetagno.
>>>>>> Kind regards,
>>>>>> Philippe
>>>>>>
>>>>>>
>>>>>>
>>>>>> Le 19/01/2015 12:17, Gattegno, Victor (GSD CSC / GCC) a écrit :
>>>>>>> Hi Philippe,
>>>>>>>
>>>>>>> You used again two time "/"  in the include :
>>>>>>> -I "/|/|/opt/Zuma"
>>>>>>>
>>>>>>> Your mondorachive.log file ends with :
>>>>>>> DBG4: [Main] libmondo-files.c->find_home_of_exe#349: find_home_of_exe --- Found afio at /usr/bin/afio
>>>>>>>
>>>>>>> You can try a few things :
>>>>>>>
>>>>>>> Try mindi alone :
>>>>>>> # mindi
>>>>>>> Do you want to use your own kernel to build the boot disk ([y]/n) ? y
>>>>>>>
>>>>>>> Try your mondoarchive command without -E, with only -I, and choice only one directory, example :
>>>>>>> -I "/opt/Zuma"
>>>>>>>
>>>>>>> Try your mondoarchive command with more debug, example with -K 5, or with -K 99 (which is full debug mode, be aware that the log file could grow from 200 Kb to 50 Mb).
>>>>>>>
>>>>>>> Rgds,
>>>>>>> Victor
>>>>>>>
>>>>>>> -----Original Message-----
>>>>>>> From: Philippe Lefevre [mailto:[hidden email]]
>>>>>>> Sent: samedi 17 janvier 2015 20:14
>>>>>>> To: Mondo mailing list
>>>>>>> Subject: Re: [Mondo-devel] Segmentation error running mondoarchive v3.2.0-r3332
>>>>>>>
>>>>>>> Hello list,
>>>>>>>
>>>>>>> sorry Gaetagno for the delay, I was not able to find some time long enought to go back into my issue.
>>>>>>>
>>>>>>> I did it today (without removing the two slashes in order to be in the same situation) and .... what I compiled worked fine with what I have compiled. (I noticed the -v bug, thanks  ;)  )
>>>>>>>
>>>>>>> Run mondoarchive via dbg:
>>>>>>> [phlsys]root:/home/phl/mondo-3.2.0# gdb -args mondoarchive -D -OV -i -N -G -s 780M -p sys-D7.7-diff_150105212200 -T /graveur -S /graveur -d /graveur -I "/|/|/opt/Zuma" -E "/bases/sybase|/graveur|/home|/opt|/photos|/quemu|/Sauvegardes|/var/crash|/var/backups|/var/log|/var/mail|/var/spool|/vbox|/videos|/www"
>>>>>>>
>>>>>>> and:
>>>>>>> ....
>>>>>>> Data archived OK.
>>>>>>> Mondoarchive ran OK.
>>>>>>> See /var/log/mondoarchive.log for details of backup run.
>>>>>>> Execution run ended; result=0
>>>>>>> Type 'less /var/log/mondoarchive.log' to see the output log [Inferior 1 (process 19382) exited normally]
>>>>>>> (gdb) quit
>>>>>>>
>>>>>>>
>>>>>>> So I reinstalled the official debian package:
>>>>>>>
>>>>>>> Sélection du paquet libmondorescue-perl précédemment désélectionné.
>>>>>>> (Lecture de la base de données... 279208 fichiers et répertoires déjà
>>>>>>> installés.)
>>>>>>> Dépaquetage de libmondorescue-perl (à partir de
>>>>>>> .../libmondorescue-perl_3.2.0-1_all.deb) ...
>>>>>>> Préparation du remplacement de mindi-busybox 1.18.5-3 (en utilisant
>>>>>>> .../mindi-busybox_1.21.1-1_amd64.deb) ...
>>>>>>> Dépaquetage de la mise à jour de mindi-busybox ...
>>>>>>> Préparation du remplacement de mindi 2.1.7-1 (en utilisant
>>>>>>> .../mindi_3.0.0-1_amd64.deb) ...
>>>>>>> Dépaquetage de la mise à jour de mindi ...
>>>>>>> Préparation du remplacement de mondo 3.0.4-1 (en utilisant
>>>>>>> .../mondo_3.2.0-1_amd64.deb) ...
>>>>>>> Dépaquetage de la mise à jour de mondo ...
>>>>>>> Traitement des actions différées (« triggers ») pour « man-db »...
>>>>>>> Paramétrage de libmondorescue-perl (3.2.0-1) ...
>>>>>>> Paramétrage de mindi-busybox (1.21.1-1) ...
>>>>>>> Paramétrage de mindi (3.0.0-1) ...
>>>>>>> Installation de la nouvelle version du fichier de configuration /etc/mindi/deplist.d/minimal.conf ...
>>>>>>> Installation de la nouvelle version du fichier de configuration /etc/mindi/deplist.d/udev.conf ...
>>>>>>> Installation de la nouvelle version du fichier de configuration /etc/mindi/deplist.d/ProLiant.conf ...
>>>>>>> Installation de la nouvelle version du fichier de configuration /etc/mindi/deplist.d/base.conf ...
>>>>>>> Installation de la nouvelle version du fichier de configuration /etc/mindi/deplist.d/lvm.conf ...
>>>>>>> Installation de la nouvelle version du fichier de configuration /etc/mindi/perl-scripts ...
>>>>>>> Paramétrage de mondo (3.2.0-1) ...
>>>>>>>
>>>>>>>
>>>>>>> but launched in the same way, it crashed again with a segmentation error:
>>>>>>>
>>>>>>> [phlsys]root:/home/phl/telechargements/mondo-3.2.0# mondoarchive -D -OV -i -N -G -s 780M -p sys-D7.7-diff_150105212200 -T /graveur -S /graveur -d /graveur -I "/|/|/opt/Zuma" -E "/bases/sybase|/graveur|/home|/opt|/photos|/quemu|/Sauvegardes|/var/crash|/var/backups|/var/log|/var/mail|/var/spool|/vbox|/videos|/www"
>>>>>>> See /var/log/mondoarchive.log for details of backup run.
>>>>>>> Checking sanity of your Linux distribution Done.
>>>>>>> Erreur de segmentation
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> Please find attached the relevant mondoarchive.log file.
>>>>>>> It seems to be stopped before logging something about the fault.
>>>>>>> I franckly don't know what I could do more.
>>>>>>> Do you have an idea about what I could do to explore deeper this issue ?
>>>>>>> Something might be going wrong into the deb pkg ???
>>>>>>> I got it with apt using:
>>>>>>>    deb ftp://ftp.mondorescue.org//debian 7 contrib
>>>>>>>
>>>>>>>
>>>>>>> Thanks for your help.
>>>>>>> Regards,
>>>>>>> Philippe
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> Le 06/01/2015 17:28, Gattegno, Victor (GSD CSC / GCC) a écrit :
>>>>>>>> Hello Philippe,
>>>>>>>>
>>>>>>>> From mondoarchive man : " When using the -I option with the -E option, the -E content should be subdirectories of those mentioned in the -I only, as -I takes precedence."
>>>>>>>>
>>>>>>>> But if your -I and -E combination works it's ok (check if /opt/zuma and /opt/calibre are well backuped and restored).
>>>>>>>>
>>>>>>>> Regards,
>>>>>>>> Victor
>>>>>>>>
>>>>>>>> -----Original Message-----
>>>>>>>> From: Philippe Lefevre [mailto:[hidden email]]
>>>>>>>> Sent: lundi 5 janvier 2015 21:42
>>>>>>>> To: [hidden email]
>>>>>>>> Subject: Re: [Mondo-devel] Segmentation error running mondoarchive
>>>>>>>> v3.2.0-r3332
>>>>>>>>
>>>>>>>> Thanks for your help and reply Victor,
>>>>>>>>
>>>>>>>> I should be able to replay with all of that before the end of the week and let you know.
>>>>>>>> Regarding the double /, it is due to my shell script which build the final request. I will also do a try without it.
>>>>>>>>
>>>>>>>> I believe I couldn't remove -I flag as in the exclude part there is /opt and I want to include only 2 directories /opt/zuma and /opt/calibre. At least, I should use -I "/opt/calibre|/opt/Zuma" right?
>>>>>>>>
>>>>>>>> PS: my system backup is run by root and ulimit is setted unlimited:
>>>>>>>>
>>>>>>>> # ulimit -a
>>>>>>>> core file size          (blocks, -c) 0
>>>>>>>> data seg size           (kbytes, -d) unlimited
>>>>>>>> scheduling priority             (-e) 0
>>>>>>>> file size               (blocks, -f) unlimited
>>>>>>>> pending signals                 (-i) 31106
>>>>>>>> max locked memory       (kbytes, -l) 64
>>>>>>>> max memory size         (kbytes, -m) unlimited
>>>>>>>> open files                      (-n) 1024
>>>>>>>> pipe size            (512 bytes, -p) 8
>>>>>>>> POSIX message queues     (bytes, -q) 819200
>>>>>>>> real-time priority              (-r) 0
>>>>>>>> stack size              (kbytes, -s) 8192
>>>>>>>> cpu time               (seconds, -t) unlimited
>>>>>>>> max user processes              (-u) 31106
>>>>>>>> virtual memory          (kbytes, -v) unlimited
>>>>>>>> file locks                      (-x) unlimited
>>>>>>>>
>>>>>>>>
>>>>>>>> Rgds,
>>>>>>>> Philippe
>>>>>>>>
>>>>>>>>
>>>>>>>> Le 05/01/2015 16:32, Gattegno, Victor (GSD CSC / GCC) a écrit :
>>>>>>>>> Hello Philippe,
>>>>>>>>>
>>>>>>>>> Good gdb work, but don't focus on "mondoarchive -v" segmentation fault, it's a known failing bug. It's better to debug mondoarchive with the options that you use.
>>>>>>>>>
>>>>>>>>>  In your 27/12/2014 test and post:
>>>>>>>>>  - did you posted too the associated /var/log/mondoarchive.log (compressed) ?
>>>>>>>>>  - you used -I (with / included twice) and -E options, it's better to use only -E option.
>>>>>>>>>
>>>>>>>>> What's the result of "ulimit -a" on your Debian ?
>>>>>>>>>
>>>>>>>>> I wish to you - and to all this mailig-list users - a nice year 2015.
>>>>>>>>>
>>>>>>>>> Rgds,
>>>>>>>>> Victor
>>>>>>>>>
>>>>>>>>> -----Original Message-----
>>>>>>>>> From: Philippe Lefevre [mailto:[hidden email]]
>>>>>>>>> Sent: samedi 3 janvier 2015 14:32
>>>>>>>>> To: [hidden email]
>>>>>>>>> Subject: Re: [Mondo-devel] Segmentation error running mondoarchive
>>>>>>>>> v3.2.0-r3332
>>>>>>>>>
>>>>>>>>> Hi list,
>>>>>>>>>
>>>>>>>>> Some more information about my issue.
>>>>>>>>>
>>>>>>>>> I can confirm that in my case it is related to this new release as a I did a downgrade and successfully built a new full backup.
>>>>>>>>>
>>>>>>>>> I uninstalled and purged
>>>>>>>>>   libmondorescue-perl_3.2.0-1_all.deb
>>>>>>>>>   mindi-busybox_1.21.1-1_amd64.deb
>>>>>>>>>   mindi_3.0.0-1_amd64.deb
>>>>>>>>>   mondo_3.2.0-1_amd64.deb
>>>>>>>>>
>>>>>>>>> and reinstalled the previous version
>>>>>>>>>   mindi-busybox 1.18.5-3
>>>>>>>>>   mindi 2.1.7-1
>>>>>>>>>   mondo 3.0.4-1
>>>>>>>>>
>>>>>>>>> I also compiled mondo 3.2.0 from sources and ran gdb against the simpliest command that raise the seg error. It shows :
>>>>>>>>>
>>>>>>>>> Starting program:
>>>>>>>>> /home/phl/telechargements/mondo-3.2.0/src/mondoarchive/mondoarchive -v [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
>>>>>>>>> mondoarchive v3.2.0-r3332
>>>>>>>>> See man page for help
>>>>>>>>>
>>>>>>>>> Program received signal SIGSEGV, Segmentation fault.
>>>>>>>>> 0x00007ffff76629aa in vfprintf () from
>>>>>>>>> /lib/x86_64-linux-gnu/libc.so.6
>>>>>>>>> (gdb) bt
>>>>>>>>> #0  0x00007ffff76629aa in vfprintf () from
>>>>>>>>> /lib/x86_64-linux-gnu/libc.so.6
>>>>>>>>> #1  0x00007ffff7688fca in vasprintf () from
>>>>>>>>> /lib/x86_64-linux-gnu/libc.so.6
>>>>>>>>> #2  0x00000000004367c4 in mr_asprintf_int (strp=strp@entry=0x7fffffffe0d0, line=line@entry=258, file=file@entry=0x44187f "libmondo-fork.c",
>>>>>>>>>     fmt=fmt@entry=0x441d38 "%s > %s/mondo-run-prog-thing.tmp 2>
>>>>>>>>> %s/mondo-run-prog-thing.err") at mr_mem.c:62
>>>>>>>>> #3  0x000000000041e0f0 in run_program_and_log_output
>>>>>>>>> (program=program@entry=0x43c4b4 "umount -d /mnt/cdrom",
>>>>>>>>> debug_level=debug_level@entry=0)
>>>>>>>>>     at libmondo-fork.c:258
>>>>>>>>> #4  0x000000000042ec19 in finish (signal=signal@entry=0) at
>>>>>>>>> newt-specific.c:388
>>>>>>>>> #5  0x0000000000403430 in main (argc=2, argv=0x7fffffffe668) at
>>>>>>>>> mondoarchive.c:176
>>>>>>>>> (gdb)
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> function code exerpt
>>>>>>>>>
>>>>>>>>>    56 void mr_asprintf_int(char **strp, int line, const char *file, const char *fmt, ...) {
>>>>>>>>>    57
>>>>>>>>>    58 int res = 0;
>>>>>>>>>    59 va_list args;
>>>>>>>>>    60
>>>>>>>>>    61 va_start(args,fmt);
>>>>>>>>>    62 res = vasprintf(strp, fmt, args);
>>>>>>>>>    63 if (res == -1) {
>>>>>>>>>    64 mr_msg_int(1,line,file,"Unable to alloc memory in
>>>>>>>>> mr_asprintf\nExiting...");
>>>>>>>>>    65 mr_exit(-1,"Unable to alloc memory in mr_asprintf");
>>>>>>>>>    66 }
>>>>>>>>>    67 va_end(args);
>>>>>>>>>    68 }
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> Breakpoint 1, mr_asprintf_int (strp=strp@entry=0x7fffffffe0d0, line=line@entry=258, file=file@entry=0x44187f "libmondo-fork.c",
>>>>>>>>>     fmt=fmt@entry=0x441d38 "%s > %s/mondo-run-prog-thing.tmp 2>
>>>>>>>>> %s/mondo-run-prog-thing.err") at mr_mem.c:56
>>>>>>>>> 56 void mr_asprintf_int(char **strp, int line, const char *file, const
>>>>>>>>> char *fmt, ...) {
>>>>>>>>> (gdb) s
>>>>>>>>> 61 va_start(args,fmt);
>>>>>>>>> (gdb) display fmt
>>>>>>>>> 1: fmt = 0x441d38 "%s > %s/mondo-run-prog-thing.tmp 2> %s/mondo-run-prog-thing.err"
>>>>>>>>> (gdb) display args
>>>>>>>>> 2: args = {{gp_offset = 4158558940, fp_offset = 32767,
>>>>>>>>> overflow_arg_area = 0x7ffff7fd5000, reg_save_area = 0x7ffff7ffd9d8}}
>>>>>>>>> (gdb) s
>>>>>>>>> 62 res = vasprintf(strp, fmt, args);
>>>>>>>>> 2: args = {{gp_offset = 4158558940, fp_offset = 32767,
>>>>>>>>> overflow_arg_area = 0x7ffff7fd5000, reg_save_area = 0x7ffff7ffd9d8}}
>>>>>>>>> 1: fmt = 0x441d38 "%s > %s/mondo-run-prog-thing.tmp 2> %s/mondo-run-prog-thing.err"
>>>>>>>>> (gdb) s
>>>>>>>>> 61 va_start(args,fmt);
>>>>>>>>> 2: args = {{gp_offset = 4158558940, fp_offset = 32767,
>>>>>>>>> overflow_arg_area = 0x7ffff7fd5000, reg_save_area = 0x7ffff7ffd9d8}}
>>>>>>>>> 1: fmt = 0x441d38 "%s > %s/mondo-run-prog-thing.tmp 2> %s/mondo-run-prog-thing.err"
>>>>>>>>> (gdb) s
>>>>>>>>> 62 res = vasprintf(strp, fmt, args);
>>>>>>>>> 2: args = {{gp_offset = 32, fp_offset = 48, overflow_arg_area =
>>>>>>>>> 0x7fffffffe0b0, reg_save_area = 0x7fffffffdfe0}}
>>>>>>>>> 1: fmt = 0x441d38 "%s > %s/mondo-run-prog-thing.tmp 2> %s/mondo-run-prog-thing.err"
>>>>>>>>> (gdb) display res
>>>>>>>>> 3: res = 0
>>>>>>>>> (gdb) s
>>>>>>>>>
>>>>>>>>> Program received signal SIGSEGV, Segmentation fault.
>>>>>>>>> 0x00007ffff76629aa in vfprintf () from
>>>>>>>>> /lib/x86_64-linux-gnu/libc.so.6
>>>>>>>>> (gdb)
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> It seems there is an issue with mr_asprintf_int but sorry I don't feel strong enought to get more deeply into the mondo code and analyze it properly ...
>>>>>>>>>
>>>>>>>>> I hope this help ...
>>>>>>>>>
>>>>>>>>> Regards,
>>>>>>>>> Philippe
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> Le 27/12/2014 11:17, [hidden email] a écrit :
>>>>>>>>>> Hi all,
>>>>>>>>>>
>>>>>>>>>> it seems that something goes wrong with mondo I could link to the
>>>>>>>>>> latest Debian version of MondoRescue.
>>>>>>>>>>
>>>>>>>>>> I updated my version last thursday and this morning (I have a
>>>>>>>>>> differential backup launched every friday night and one full a
>>>>>>>>>> month) it failed.
>>>>>>>>>> Unfortunately there are no much relevant informations in logs.
>>>>>>>>>>
>>>>>>>>>> The errors raised is :
>>>>>>>>>>
>>>>>>>>>>     # mondoarchive -D -OV -i -N -G -s 780M -p sys-D7.7-diff_141227100000
>>>>>>>>>>     -T /graveur -S /graveur -d
>>>>>>>>>>     /media/sauvegardes/phlsys/D7.7/sys/141227100000 -I
>>>>>>>>>>     "/|/|/opt/calibre|/opt/Zuma" -E
>>>>>>>>>>     "/bases/sybase|/graveur|/home|/opt|/photos|/quemu|/Sauvegardes|/var/crash|/var/backups|/var/log|/var/mail|/var/spool|/vbox|/videos|/www"
>>>>>>>>>>     See /var/log/mondoarchive.log for details of backup run.
>>>>>>>>>>     Checking sanity of your Linux distribution
>>>>>>>>>>     Done.
>>>>>>>>>>     Erreur de segmentation                /* Segmentation error */
>>>>>>>>>>
>>>>>>>>>> Please find attached the log files that seems to find out an issue
>>>>>>>>>> with LVM disks
>>>>>>>>>>
>>>>>>>>>>     INFO: Mindi v3.0.0-r3332
>>>>>>>>>>     INFO: Le disque /dev/mapper/data1vg-photoslv ne contient pas une
>>>>>>>>>>     table de partitions valable
>>>>>>>>>>              /* there is no valid partition table in
>>>>>>>>>>     /dev/mapper/data1vg-photoslv disk */
>>>>>>>>>>
>>>>>>>>>> I have no issues with my LVM disks. Please find on below my LVM
>>>>>>>>>> disks configuration
>>>>>>>>>>
>>>>>>>>>>     lvm> vgs
>>>>>>>>>>       VG      #PV #LV #SN Attr   VSize   VFree
>>>>>>>>>>       data1vg   1   7   0 wz--n- 931,51g 504,60g
>>>>>>>>>>       sysvg     1   1   0 wz--n-  95,12g  78,84g
>>>>>>>>>>
>>>>>>>>>>     lvm> lvs
>>>>>>>>>>       LV        VG      Attr     LSize   Pool Origin Data%  Move Log
>>>>>>>>>>     Copy%  Convert
>>>>>>>>>>       baseslv   data1vg -wi-ao--  
>>>>>>>>>>     1,86g                                          
>>>>>>>>>>       graveurlv data1vg -wi-ao--
>>>>>>>>>>     20,00g                                          
>>>>>>>>>>       homelv    data1vg -wi-ao--
>>>>>>>>>>     50,00g                                          
>>>>>>>>>>       photoslv  data1vg -wi-ao--
>>>>>>>>>>     70,00g                                          
>>>>>>>>>>       vboxlv    data1vg -wi-ao--
>>>>>>>>>>     130,39g                                          
>>>>>>>>>>       videoslv  data1vg -wi-ao--
>>>>>>>>>>     150,00g                                          
>>>>>>>>>>       wwwlv     data1vg -wi-ao--  
>>>>>>>>>>     4,66g                                          
>>>>>>>>>>       optlv     sysvg   -wi-ao--  16,28g
>>>>>>>>>>
>>>>>>>>>>     lvm> lvscan
>>>>>>>>>>       ACTIVE            '/dev/data1vg/photoslv' [70,00 GiB] inherit
>>>>>>>>>>       ACTIVE            '/dev/data1vg/videoslv' [150,00 GiB] inherit
>>>>>>>>>>       ACTIVE            '/dev/data1vg/homelv' [50,00 GiB] inherit
>>>>>>>>>>       ACTIVE            '/dev/data1vg/graveurlv' [20,00 GiB] inherit
>>>>>>>>>>       ACTIVE            '/dev/data1vg/wwwlv' [4,66 GiB] inherit
>>>>>>>>>>       ACTIVE            '/dev/data1vg/baseslv' [1,86 GiB] inherit
>>>>>>>>>>       ACTIVE            '/dev/data1vg/vboxlv' [130,39 GiB] inherit
>>>>>>>>>>       ACTIVE            '/dev/sysvg/optlv' [16,28 GiB] inherit
>>>>>>>>>>
>>>>>>>>>>     root@phlsys:/home/phl/Scripts# df -h
>>>>>>>>>>     Sys. fich.                                             Taille Util.
>>>>>>>>>>     Dispo Uti% Monté sur
>>>>>>>>>>     rootfs                                                    92G  
>>>>>>>>>>     11G   77G  12% /
>>>>>>>>>>     udev                                                      10M    
>>>>>>>>>>     0   10M   0% /dev
>>>>>>>>>>     tmpfs                                                    397M  968K
>>>>>>>>>>     396M   1% /run
>>>>>>>>>>     /dev/disk/by-uuid/4a5a9317-0b70-4796-a094-d61c01891c81    92G  
>>>>>>>>>>     11G   77G  12% /
>>>>>>>>>>     tmpfs                                                    5,0M     0
>>>>>>>>>>     5,0M   0% /run/lock
>>>>>>>>>>     tmpfs                                                    985M  324K
>>>>>>>>>>     985M   1% /run/shm
>>>>>>>>>>     /dev/mapper/sysvg-optlv                                   17G   15G
>>>>>>>>>>     845M  95% /opt
>>>>>>>>>>     /dev/mapper/data1vg-homelv                                50G   40G
>>>>>>>>>>     7,2G  85% /home
>>>>>>>>>>     /dev/mapper/data1vg-wwwlv                                4,6G  2,5G
>>>>>>>>>>     1,9G  58% /www
>>>>>>>>>>     /dev/mapper/data1vg-baseslv                              1,9G  720M
>>>>>>>>>>     1,1G  41% /bases
>>>>>>>>>>     /dev/mapper/data1vg-photoslv                              69G  
>>>>>>>>>>     43G   23G  66% /photos
>>>>>>>>>>     /dev/mapper/data1vg-videoslv                             148G
>>>>>>>>>>     104G   37G  74% /videos
>>>>>>>>>>     /dev/mapper/data1vg-vboxlv                               129G
>>>>>>>>>>     100G   23G  82% /vbox
>>>>>>>>>>     /dev/mapper/data1vg-graveurlv                             20G
>>>>>>>>>>     8,1G   11G  44% /graveur
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> The latest mondo upgrade dated of 25th of december was (it worked
>>>>>>>>>> fine before this upgrade)
>>>>>>>>>>
>>>>>>>>>>     Start-Date: 2014-12-25  18:55:08
>>>>>>>>>>     Commandline: /usr/sbin/synaptic
>>>>>>>>>>     Install: libprojectbuilder-perl:amd64 (0.12.6-1, automatic),
>>>>>>>>>>     libmondorescue-perl:amd64 (3.2.0-1, automatic)
>>>>>>>>>>     Upgrade: mindi:amd64 (2.1.7-1, 3.0.0-1), mondo:amd64 (3.0.4-1,
>>>>>>>>>>     3.2.0-1), mindi-busybox:amd64 (1.18.5-3, 1.21.1-1)
>>>>>>>>>>     End-Date: 2014-12-25  18:55:31
>>>>>>>>>>
>>>>>>>>>> The Debian distro used is
>>>>>>>>>>
>>>>>>>>>>     root@phlsys:/home/phl/Scripts# uname -a
>>>>>>>>>>     Linux phlsys 3.2.0-4-amd64 #1 SMP Debian 3.2.63-2+deb7u2 x86_64
>>>>>>>>>>     GNU/Linux
>>>>>>>>>>
>>>>>>>>>> Anyone have an idea to try to debug this.
>>>>>>>>>>
>>>>>>>>>> Thanks for any help.
>>>>>>>>>>
>>>>>>>>>> By the way, I whish you all an happy new year 2015 with all the best
>>>>>>>>>> in your lifes Kind regards, Philippe
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> ---------------------------------------------------------------------
>>>>>>>>> -
>>>>>>>>> -------- Dive into the World of Parallel Programming! The Go Parallel
>>>>>>>>> Website, sponsored by Intel and developed in partnership with
>>>>>>>>> Slashdot Media, is your hub for all things parallel software
>>>>>>>>> development, from weekly thought leadership blogs to news, videos,
>>>>>>>>> case studies, tutorials and more. Take a look and join the conversation now.
>>>>>>>>> http://goparallel.sourceforge.net
>>>>>>>>> _______________________________________________
>>>>>>>>> Mondo-devel mailing list
>>>>>>>>> [hidden email]
>>>>>>>>> https://lists.sourceforge.net/lists/listinfo/mondo-devel
>>>>>>>>> ---------------------------------------------------------------------
>>>>>>>>> -
>>>>>>>>> -------- Dive into the World of Parallel Programming! The Go Parallel
>>>>>>>>> Website, sponsored by Intel and developed in partnership with
>>>>>>>>> Slashdot Media, is your hub for all things parallel software
>>>>>>>>> development, from weekly thought leadership blogs to news, videos,
>>>>>>>>> case studies, tutorials and more. Take a look and join the conversation now.
>>>>>>>>> http://goparallel.sourceforge.net
>>>>>>>>> _______________________________________________
>>>>>>>>> Mondo-devel mailing list
>>>>>>>>> [hidden email]
>>>>>>>>> https://lists.sourceforge.net/lists/listinfo/mondo-devel
>>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> ----------------------------------------------------------------------
>>>>>>>> -------- Dive into the World of Parallel Programming! The Go Parallel
>>>>>>>> Website, sponsored by Intel and developed in partnership with Slashdot
>>>>>>>> Media, is your hub for all things parallel software development, from
>>>>>>>> weekly thought leadership blogs to news, videos, case studies,
>>>>>>>> tutorials and more. Take a look and join the conversation now.
>>>>>>>> http://goparallel.sourceforge.net 
>>>>>>>> _______________________________________________
>>>>>>>> Mondo-devel mailing list
>>>>>>>> [hidden email]
>>>>>>>> https://lists.sourceforge.net/lists/listinfo/mondo-devel
>>>>>>>> ----------------------------------------------------------------------
>>>>>>>> -------- Dive into the World of Parallel Programming! The Go Parallel
>>>>>>>> Website, sponsored by Intel and developed in partnership with Slashdot
>>>>>>>> Media, is your hub for all things parallel software development, from
>>>>>>>> weekly thought leadership blogs to news, videos, case studies,
>>>>>>>> tutorials and more. Take a look and join the conversation now.
>>>>>>>> http://goparallel.sourceforge.net 
>>>>>>>> _______________________________________________
>>>>>>>> Mondo-devel mailing list
>>>>>>>> [hidden email]
>>>>>>>> https://lists.sourceforge.net/lists/listinfo/mondo-devel
>>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> ------------------------------------------------------------------------------
>>>>>>> New Year. New Location. New Benefits. New Data Center in Ashburn, VA.
>>>>>>> GigeNET is offering a free month of service with a new server in Ashburn.
>>>>>>> Choose from 2 high performing configs, both with 100TB of bandwidth.
>>>>>>> Higher redundancy.Lower latency.Increased capacity.Completely compliant.
>>>>>>> http://p.sf.net/sfu/gigenet
>>>>>>> _______________________________________________
>>>>>>> Mondo-devel mailing list
>>>>>>> [hidden email]
>>>>>>> https://lists.sourceforge.net/lists/listinfo/mondo-devel
>>>>>>>
>>>>>>
>>>>>>
>>>>>
>>>>>> mindi v3.0.0-r3332
>>>>>> x86_64 architecture detected
>>>>>> mindi called with the following arguments:
>>>>>> --makemountlist /tmp/mondo.tmp.4v41Vd/mountlist.txt.test
>>>>>> Start date : lundi 19 janvier 2015, 22:16:43 (UTC+0100)
>>>>>> -----------------------------
>>>>>> MONDO_SHARE = /usr/share/mondo
>>>>>> MINDI_LIB = /usr/lib/mindi
>>>>>> MINDI_SBIN = /usr/sbin
>>>>>> MINDI_CONF = /etc/mindi
>>>>>> -----------------------------
>>>>>>  Mindi configuration file    
>>>>>> -----------------------------
>>>>>> -----------------------------
>>>>>> In Mindi
>>>>>> --------
>>>>>> EXTRA_SPACE = 120000
>>>>>> BOOT_SIZE = 65600
>>>>>> --------
>>>>>> INFO: Found isolinux.bin at /usr/lib/syslinux/isolinux.bin
>>>>>> INFO: LVM set to v2
>>>>>> ----------
>>>>>> mount result:
>>>>>> -------------
>>>>>> sysfs on /sys type sysfs (rw,nosuid,nodev,noexec,relatime)
>>>>>> proc on /proc type proc (rw,nosuid,nodev,noexec,relatime)
>>>>>> udev on /dev type devtmpfs (rw,relatime,size=10240k,nr_inodes=497709,mode=755)
>>>>>> devpts on /dev/pts type devpts (rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000)
>>>>>> tmpfs on /run type tmpfs (rw,nosuid,noexec,relatime,size=406288k,mode=755)
>>>>>> /dev/disk/by-uuid/4a5a9317-0b70-4796-a094-d61c01891c81 on / type ext4 (rw,relatime,errors=remount-ro,user_xattr,barrier=1,data=ordered)
>>>>>> tmpfs on /run/lock type tmpfs (rw,nosuid,nodev,noexec,relatime,size=5120k)
>>>>>> tmpfs on /run/shm type tmpfs (rw,nosuid,nodev,noexec,relatime,size=1008560k)
>>>>>> /dev/mapper/sysvg-optlv on /opt type ext4 (rw,relatime,errors=remount-ro,user_xattr,barrier=1,data=ordered)
>>>>>> /dev/mapper/data1vg-homelv on /home type ext4 (rw,relatime,errors=remount-ro,user_xattr,barrier=1,data=ordered)
>>>>>> /dev/mapper/data1vg-wwwlv on /www type ext4 (rw,relatime,errors=remount-ro,user_xattr,barrier=1,data=ordered)
>>>>>> /dev/mapper/data1vg-baseslv on /bases type ext4 (rw,relatime,errors=remount-ro,user_xattr,barrier=1,data=ordered)
>>>>>> /dev/mapper/data1vg-photoslv on /photos type ext4 (rw,relatime,errors=remount-ro,user_xattr,barrier=1,data=ordered)
>>>>>> /dev/mapper/data1vg-videoslv on /videos type ext4 (rw,relatime,errors=remount-ro,user_xattr,barrier=1,data=ordered)
>>>>>> /dev/mapper/data1vg-vboxlv on /vbox type ext4 (rw,relatime,errors=remount-ro,user_xattr,barrier=1,data=ordered)
>>>>>> /dev/mapper/data1vg-graveurlv on /graveur type ext4 (rw,relatime,errors=remount-ro,user_xattr,barrier=1,data=ordered)
>>>>>> rpc_pipefs on /var/lib/nfs/rpc_pipefs type rpc_pipefs (rw,relatime)
>>>>>> binfmt_misc on /proc/sys/fs/binfmt_misc type binfmt_misc (rw,nosuid,nodev,noexec,relatime)
>>>>>> No file /etc/raidtab
>>>>>> -------------
>>>>>> No file /etc/mdadm.conf
>>>>>> -------------
>>>>>> cat /proc/cmdline
>>>>>> -------------
>>>>>> BOOT_IMAGE=/boot/vmlinuz-3.2.0-4-amd64 root=UUID=4a5a9317-0b70-4796-a094-d61c01891c81 ro quiet
>>>>>> -------------
>>>>>> cat /proc/swaps:
>>>>>> -------------
>>>>>> Filename Type Size Used Priority
>>>>>> /dev/sda6                               partition 979928 11992 -1
>>>>>> -------------
>>>>>> cat /proc/mdstat:
>>>>>> -------------
>>>>>> Personalities : [linear] [raid0] [raid1] [raid6] [raid5] [raid4]
>>>>>> unused devices: <none>
>>>>>> -------------
>>>>>> cat /proc/partitions:
>>>>>> -------------
>>>>>> major minor  #blocks  name
>>>>>>
>>>>>>    8        0  312571224 sda
>>>>>>    8        1      56196 sda1
>>>>>>    8        2   10485760 sda2
>>>>>>    8        3  103643080 sda3
>>>>>>    8        4          1 sda4
>>>>>>    8        5   97659103 sda5
>>>>>>    8        6     979933 sda6
>>>>>>    8        7   99741696 sda7
>>>>>>   11        0    1048575 sr0
>>>>>>    8       16  976762584 sdb
>>>>>>    8       17  976761560 sdb1
>>>>>>  253        0   73400320 dm-0
>>>>>>  253        1  157286400 dm-1
>>>>>>  253        2   52428800 dm-2
>>>>>>  253        3   20971520 dm-3
>>>>>>  253        4    4886528 dm-4
>>>>>>  253        5    1953792 dm-5
>>>>>>  253        6  136720384 dm-6
>>>>>>  253        7   17072128 dm-7
>>>>>> -------------
>>>>>> cat /proc/filesystems:
>>>>>> -------------
>>>>>> nodev sysfs
>>>>>> nodev rootfs
>>>>>> nodev bdev
>>>>>> nodev proc
>>>>>> nodev cgroup
>>>>>> nodev cpuset
>>>>>> nodev tmpfs
>>>>>> nodev devtmpfs
>>>>>> nodev debugfs
>>>>>> nodev securityfs
>>>>>> nodev sockfs
>>>>>> nodev pipefs
>>>>>> nodev anon_inodefs
>>>>>> nodev devpts
>>>>>> nodev ramfs
>>>>>> nodev hugetlbfs
>>>>>> nodev pstore
>>>>>> nodev mqueue
>>>>>> nodev usbfs
>>>>>> ext4
>>>>>> nodev ecryptfs
>>>>>> nodev rpc_pipefs
>>>>>> nodev nfs
>>>>>> nodev nfs4
>>>>>> nodev nfsd
>>>>>> nodev binfmt_misc
>>>>>> msdos
>>>>>> vfat
>>>>>> iso9660
>>>>>> ext2
>>>>>> -------------
>>>>>> lsmod result:
>>>>>> -------------
>>>>>> Module                  Size  Used by
>>>>>> nls_utf8               12456  0
>>>>>> nls_cp437              16553  0
>>>>>> ext2                   59231  0
>>>>>> raid456                48453  0
>>>>>> async_raid6_recov      12574  1 raid456
>>>>>> async_memcpy           12387  2 async_raid6_recov,raid456
>>>>>> async_pq               12605  2 async_raid6_recov,raid456
>>>>>> raid6_pq               82624  2 async_pq,async_raid6_recov
>>>>>> async_xor              12422  3 async_pq,async_raid6_recov,raid456
>>>>>> xor                    12605  1 async_xor
>>>>>> async_tx               12604  5 async_xor,async_pq,async_memcpy,async_raid6_recov,raid456
>>>>>> raid1                  30714  0
>>>>>> raid0                  12904  0
>>>>>> linear                 12735  0
>>>>>> isofs                  35173  0
>>>>>> brd                    12772  0
>>>>>> vfat                   17316  0
>>>>>> msdos                  17077  0
>>>>>> fat                    45642  2 msdos,vfat
>>>>>> pci_stub               12429  1
>>>>>> vboxpci                19096  0
>>>>>> vboxnetadp             25443  0
>>>>>> vboxnetflt             23657  0
>>>>>> vboxdrv               304550  3 vboxnetflt,vboxnetadp,vboxpci
>>>>>> nfnetlink_log          17212  0
>>>>>> nfnetlink              12906  1 nfnetlink_log
>>>>>> parport_pc             22364  0
>>>>>> ppdev                  12763  0
>>>>>> lp                     17149  0
>>>>>> parport                31858  3 lp,ppdev,parport_pc
>>>>>> ip6t_REJECT            12512  2
>>>>>> xt_multiport           12548  2
>>>>>> xt_conntrack           12681  18
>>>>>> iptable_nat            12928  0
>>>>>> binfmt_misc            12957  1
>>>>>> iptable_mangle         12536  0
>>>>>> nfsd                  216181  2
>>>>>> nfs                   308353  0
>>>>>> nfs_acl                12511  2 nfs,nfsd
>>>>>> auth_rpcgss            37143  2 nfs,nfsd
>>>>>> fscache                36739  1 nfs
>>>>>> lockd                  67306  2 nfs,nfsd
>>>>>> sunrpc                173730  6 lockd,auth_rpcgss,nfs_acl,nfs,nfsd
>>>>>> ip6t_LOG               12609  4
>>>>>> xt_hl                  12449  6
>>>>>> ip6t_rt                12499  3
>>>>>> nf_conntrack_ipv6      13316  7
>>>>>> nf_defrag_ipv6         12832  1 nf_conntrack_ipv6
>>>>>> ipt_REJECT             12502  1
>>>>>> ipt_LOG                12605  12
>>>>>> xt_limit               12638  19
>>>>>> xt_tcpudp              12570  62
>>>>>> xt_addrtype            12557  4
>>>>>> xt_state               12503  21
>>>>>> ip6table_filter        12540  1
>>>>>> ip6_tables             22175  3 ip6table_filter,ip6t_rt,ip6t_LOG
>>>>>> nf_conntrack_netbios_ns    12445  0
>>>>>> nf_conntrack_broadcast    12365  1 nf_conntrack_netbios_ns
>>>>>> nf_nat_ftp             12460  0
>>>>>> nf_nat                 18242  2 nf_nat_ftp,iptable_nat
>>>>>> nf_conntrack_ipv4      14078  35 nf_nat,iptable_nat
>>>>>> nf_defrag_ipv4         12483  1 nf_conntrack_ipv4
>>>>>> nf_conntrack_ftp       12605  1 nf_nat_ftp
>>>>>> nf_conntrack           52720  10 nf_conntrack_ftp,nf_conntrack_ipv4,nf_nat,nf_nat_ftp,nf_conntrack_broadcast,nf_conntrack_netbios_ns,xt_state,nf_conntrack_ipv6,iptable_nat,xt_conntrack
>>>>>> iptable_filter         12536  1
>>>>>> ip_tables              22042  3 iptable_filter,iptable_mangle,iptable_nat
>>>>>> x_tables               19118  18 ip_tables,iptable_filter,ip6_tables,ip6table_filter,xt_state,xt_addrtype,xt_tcpudp,xt_limit,ipt_LOG,ipt_REJECT,ip6t_rt,xt_hl,ip6t_LOG,iptable_mangle,iptable_nat,xt_conntrack,xt_multiport,ip6t_REJECT
>>>>>> loop                   22641  0
>>>>>> ecryptfs               81507  0
>>>>>> dm_crypt               22586  0
>>>>>> snd_hda_codec_hdmi     30824  1
>>>>>> snd_usb_audio          89083  2
>>>>>> snd_usbmidi_lib        23369  1 snd_usb_audio
>>>>>> snd_seq_midi           12848  0
>>>>>> snd_seq_midi_event     13316  1 snd_seq_midi
>>>>>> snd_rawmidi            23060  2 snd_seq_midi,snd_usbmidi_lib
>>>>>> snd_hda_codec_idt      53792  1
>>>>>> tuner_simple           17175  1
>>>>>> tuner_types            16409  1 tuner_simple
>>>>>> wm8775                 12749  1
>>>>>> tda9887                12645  1
>>>>>> tda8290                17278  0
>>>>>> tuner                  17497  2
>>>>>> cx25840                39782  1
>>>>>> ivtv                  129010  0
>>>>>> cx2341x                21461  1 ivtv
>>>>>> snd_hda_intel          26259  2
>>>>>> snd_hda_codec          78031  3 snd_hda_intel,snd_hda_codec_idt,snd_hda_codec_hdmi
>>>>>> snd_hwdep              13186  2 snd_hda_codec,snd_usb_audio
>>>>>> snd_pcm                68083  4 snd_hda_codec,snd_hda_intel,snd_usb_audio,snd_hda_codec_hdmi
>>>>>> tveeprom               20593  1 ivtv
>>>>>> v4l2_common            13222  5 cx2341x,ivtv,cx25840,tuner,wm8775
>>>>>> videodev               70889  6 v4l2_common,cx2341x,ivtv,cx25840,tuner,wm8775
>>>>>> v4l2_compat_ioctl32    16655  1 videodev
>>>>>> media                  18148  1 videodev
>>>>>> nv_tco                 12914  0
>>>>>> i2c_algo_bit           12841  1 ivtv
>>>>>> snd_page_alloc         13003  2 snd_pcm,snd_hda_intel
>>>>>> snd_seq                45126  2 snd_seq_midi_event,snd_seq_midi
>>>>>> snd_seq_device         13176  3 snd_seq,snd_rawmidi,snd_seq_midi
>>>>>> i2c_nforce2            12584  0
>>>>>> dcdbas                 13307  0
>>>>>> edac_mce_amd           17103  0
>>>>>> edac_core              35258  0
>>>>>> evdev                  17562  18
>>>>>> powernow_k8            17618  1
>>>>>> mperf                  12453  1 powernow_k8
>>>>>> k8temp                 12647  0
>>>>>> psmouse                69265  0
>>>>>> snd_timer              22917  2 snd_seq,snd_pcm
>>>>>> i2c_core               23876  12 i2c_nforce2,i2c_algo_bit,videodev,v4l2_common,tveeprom,ivtv,cx25840,tuner,tda8290,tda9887,wm8775,tuner_simple
>>>>>> serio_raw              12931  0
>>>>>> fglrx                2634136  183
>>>>>> pcspkr                 12579  0
>>>>>> snd                    52893  20 snd_timer,snd_seq_device,snd_seq,snd_pcm,snd_hwdep,snd_hda_codec,snd_hda_intel,snd_hda_codec_idt,snd_rawmidi,snd_usbmidi_lib,snd_usb_audio,snd_hda_codec_hdmi
>>>>>> processor              28149  1 powernow_k8
>>>>>> button                 12937  1 fglrx
>>>>>> soundcore              13065  1 snd
>>>>>> thermal_sys            18040  1 processor
>>>>>> ext4                  350804  9
>>>>>> crc16                  12343  1 ext4
>>>>>> jbd2                   62115  1 ext4
>>>>>> mbcache                13114  2 ext4,ext2
>>>>>> dm_mod                 63645  29 dm_crypt
>>>>>> md_mod                 87742  4 linear,raid0,raid1,raid456
>>>>>> sg                     25874  0
>>>>>> sd_mod                 36136  6
>>>>>> sr_mod                 21899  0
>>>>>> cdrom                  35401  1 sr_mod
>>>>>> crc_t10dif             12348  1 sd_mod
>>>>>> usbhid                 36418  0
>>>>>> hid                    81372  1 usbhid
>>>>>> usb_storage            43870  0
>>>>>> ata_generic            12479  0
>>>>>> ohci_hcd               26563  0
>>>>>> sata_nv                26690  4
>>>>>> libata                140630  2 sata_nv,ata_generic
>>>>>> ehci_hcd               40249  0
>>>>>> b44                    27751  0
>>>>>> ssb                    44714  1 b44
>>>>>> mmc_core               68400  1 ssb
>>>>>> mii                    12675  1 b44
>>>>>> pcmcia                 32734  1 ssb
>>>>>> pcmcia_core            18294  1 pcmcia
>>>>>> scsi_mod              162321  5 libata,usb_storage,sr_mod,sd_mod,sg
>>>>>> usbcore               128741  7 ehci_hcd,ohci_hcd,usb_storage,usbhid,snd_usbmidi_lib,snd_usb_audio
>>>>>> usb_common             12354  1 usbcore
>>>>>> -------------
>>>>>> FORCE_MODS:
>>>>>> -------------
>>>>>>
>>>>>> -------------
>>>>>> DENY_MODS:
>>>>>> -------------
>>>>>> kqemu vxfen
>>>>>> -------------
>>>>>> df result:
>>>>>> ----------
>>>>>> Sys. fich.                                             Type        1K-blocks     Util. Disponible Uti% Mont?? sur
>>>>>> rootfs                                                 rootfs       96124904  10822540   80419412  12% /
>>>>>> sysfs                                                  sysfs               0         0          0    - /sys
>>>>>> proc                                                   proc                0         0          0    - /proc
>>>>>> udev                                                   devtmpfs        10240         0      10240   0% /dev
>>>>>> devpts                                                 devpts              0         0          0    - /dev/pts
>>>>>> tmpfs                                                  tmpfs          406288       944     405344   1% /run
>>>>>> /dev/disk/by-uuid/4a5a9317-0b70-4796-a094-d61c01891c81 ext4         96124904  10822540   80419412  12% /
>>>>>> tmpfs                                                  tmpfs            5120         0       5120   0% /run/lock
>>>>>> tmpfs                                                  tmpfs         1008560       276    1008284   1% /run/shm
>>>>>> /dev/mapper/sysvg-optlv                                ext4         16803708  15010400     939704  95% /opt
>>>>>> /dev/mapper/data1vg-homelv                             ext4         51606140  41866076    7119008  86% /home
>>>>>> /dev/mapper/data1vg-wwwlv                              ext4          4809704   2794384    1770996  62% /www
>>>>>> /dev/mapper/data1vg-baseslv                            ext4          1923084    737276    1088120  41% /bases
>>>>>> /dev/mapper/data1vg-photoslv                           ext4         72248648  45036992   23541896  66% /photos
>>>>>> /dev/mapper/data1vg-videoslv                           ext4        154818540 108302512   38651708  74% /videos
>>>>>> /dev/mapper/data1vg-vboxlv                             ext4        134573320 104068176   23669128  82% /vbox
>>>>>> /dev/mapper/data1vg-graveurlv                          ext4         20642428   8094972   11498880  42% /graveur
>>>>>> rpc_pipefs                                             rpc_pipefs          0         0          0    - /var/lib/nfs/rpc_pipefs
>>>>>> binfmt_misc                                            binfmt_misc         0         0          0    - /proc/sys/fs/binfmt_misc
>>>>>> -------------
>>>>>> df -i result:
>>>>>> ----------
>>>>>> Sys. fich.                                              Inodes IUtil.  ILibre IUti% Mont?? sur
>>>>>> rootfs                                                 6111232 313566 5797666    6% /
>>>>>> udev                                                    497709    610  497099    1% /dev
>>>>>> tmpfs                                                   507860    667  507193    1% /run
>>>>>> /dev/disk/by-uuid/4a5a9317-0b70-4796-a094-d61c01891c81 6111232 313566 5797666    6% /
>>>>>> tmpfs                                                   507860      3  507857    1% /run/lock
>>>>>> tmpfs                                                   507860     15  507845    1% /run/shm
>>>>>> /dev/mapper/sysvg-optlv                                1068960  54781 1014179    6% /opt
>>>>>> /dev/mapper/data1vg-homelv                             3276800  83092 3193708    3% /home
>>>>>> /dev/mapper/data1vg-wwwlv                               305824  43214  262610   15% /www
>>>>>> /dev/mapper/data1vg-baseslv                             122160   1213  120947    1% /bases
>>>>>> /dev/mapper/data1vg-photoslv                           4587520  23609 4563911    1% /photos
>>>>>> /dev/mapper/data1vg-videoslv                           9830400    180 9830220    1% /videos
>>>>>> /dev/mapper/data1vg-vboxlv                             8552448     91 8552357    1% /vbox
>>>>>> /dev/mapper/data1vg-graveurlv                          1310720     80 1310640    1% /graveur
>>>>>> -------------
>>>>>> -------------
>>>>>> INFO: /boot/grub/grub.cfg content
>>>>>> -------------
>>>>>> #
>>>>>> # DO NOT EDIT THIS FILE
>>>>>> #
>>>>>> # It is automatically generated by grub-mkconfig using templates
>>>>>> # from /etc/grub.d and settings from /etc/default/grub
>>>>>> #
>>>>>>
>>>>>> ### BEGIN /etc/grub.d/00_header ###
>>>>>> if [ -s $prefix/grubenv ]; then
>>>>>>   load_env
>>>>>> fi
>>>>>> set default="0"
>>>>>> if [ "${prev_saved_entry}" ]; then
>>>>>>   set saved_entry="${prev_saved_entry}"
>>>>>>   save_env saved_entry
>>>>>>   set prev_saved_entry=
>>>>>>   save_env prev_saved_entry
>>>>>>   set boot_once=true
>>>>>> fi
>>>>>>
>>>>>> function savedefault {
>>>>>>   if [ -z "${boot_once}" ]; then
>>>>>>     saved_entry="${chosen}"
>>>>>>     save_env saved_entry
>>>>>>   fi
>>>>>> }
>>>>>>
>>>>>> function load_video {
>>>>>>   insmod vbe
>>>>>>   insmod vga
>>>>>>   insmod video_bochs
>>>>>>   insmod video_cirrus
>>>>>> }
>>>>>>
>>>>>> insmod part_msdos
>>>>>> insmod ext2
>>>>>> set root='(hd0,msdos5)'
>>>>>> search --no-floppy --fs-uuid --set=root 4a5a9317-0b70-4796-a094-d61c01891c81
>>>>>> if loadfont /usr/share/grub/unicode.pf2 ; then
>>>>>>   set gfxmode=640x480
>>>>>>   load_video
>>>>>>   insmod gfxterm
>>>>>>   insmod part_msdos
>>>>>>   insmod ext2
>>>>>>   set root='(hd0,msdos5)'
>>>>>>   search --no-floppy --fs-uuid --set=root 4a5a9317-0b70-4796-a094-d61c01891c81
>>>>>>   set locale_dir=($root)/boot/grub/locale
>>>>>>   set lang=fr_FR
>>>>>>   insmod gettext
>>>>>> fi
>>>>>> terminal_output gfxterm
>>>>>> set timeout=5
>>>>>> ### END /etc/grub.d/00_header ###
>>>>>>
>>>>>> ### BEGIN /etc/grub.d/05_debian_theme ###
>>>>>> insmod part_msdos
>>>>>> insmod ext2
>>>>>> set root='(hd0,msdos5)'
>>>>>> search --no-floppy --fs-uuid --set=root 4a5a9317-0b70-4796-a094-d61c01891c81
>>>>>> insmod png
>>>>>> if background_image /usr/share/images/desktop-base/joy-grub.png; then
>>>>>>   set color_normal=white/black
>>>>>>   set color_highlight=black/white
>>>>>> else
>>>>>>   set menu_color_normal=cyan/blue
>>>>>>   set menu_color_highlight=white/blue
>>>>>> fi
>>>>>> ### END /etc/grub.d/05_debian_theme ###
>>>>>>
>>>>>> ### BEGIN /etc/grub.d/10_linux ###
>>>>>> menuentry 'Debian GNU/Linux, avec Linux 3.2.0-4-amd64' --class debian --class gnu-linux --class gnu --class os {
>>>>>> load_video
>>>>>> insmod gzio
>>>>>> insmod part_msdos
>>>>>> insmod ext2
>>>>>> set root='(hd0,msdos5)'
>>>>>> search --no-floppy --fs-uuid --set=root 4a5a9317-0b70-4796-a094-d61c01891c81
>>>>>> echo 'Chargement de Linux 3.2.0-4-amd64 ...'
>>>>>> linux /boot/vmlinuz-3.2.0-4-amd64 root=UUID=4a5a9317-0b70-4796-a094-d61c01891c81 ro  quiet
>>>>>> echo 'Chargement du disque m??moire initial ...'
>>>>>> initrd /boot/initrd.img-3.2.0-4-amd64
>>>>>> }
>>>>>> menuentry 'Debian GNU/Linux, avec Linux 3.2.0-4-amd64 (mode de d??pannage)' --class debian --class gnu-linux --class gnu --class os {
>>>>>> load_video
>>>>>> insmod gzio
>>>>>> insmod part_msdos
>>>>>> insmod ext2
>>>>>> set root='(hd0,msdos5)'
>>>>>> search --no-floppy --fs-uuid --set=root 4a5a9317-0b70-4796-a094-d61c01891c81
>>>>>> echo 'Chargement de Linux 3.2.0-4-amd64 ...'
>>>>>> linux /boot/vmlinuz-3.2.0-4-amd64 root=UUID=4a5a9317-0b70-4796-a094-d61c01891c81 ro single
>>>>>> echo 'Chargement du disque m??moire initial ...'
>>>>>> initrd /boot/initrd.img-3.2.0-4-amd64
>>>>>> }
>>>>>> ### END /etc/grub.d/10_linux ###
>>>>>>
>>>>>> ### BEGIN /etc/grub.d/20_linux_xen ###
>>>>>> ### END /etc/grub.d/20_linux_xen ###
>>>>>>
>>>>>> ### BEGIN /etc/grub.d/20_memtest86+ ###
>>>>>> menuentry "Memory test (memtest86+)" {
>>>>>> insmod part_msdos
>>>>>> insmod ext2
>>>>>> set root='(hd0,msdos5)'
>>>>>> search --no-floppy --fs-uuid --set=root 4a5a9317-0b70-4796-a094-d61c01891c81
>>>>>> linux16 /boot/memtest86+.bin
>>>>>> }
>>>>>> menuentry "Memory test (memtest86+, serial console 115200)" {
>>>>>> insmod part_msdos
>>>>>> insmod ext2
>>>>>> set root='(hd0,msdos5)'
>>>>>> search --no-floppy --fs-uuid --set=root 4a5a9317-0b70-4796-a094-d61c01891c81
>>>>>> linux16 /boot/memtest86+.bin console=ttyS0,115200n8
>>>>>> }
>>>>>> menuentry "Memory test (memtest86+, experimental multiboot)" {
>>>>>> insmod part_msdos
>>>>>> insmod ext2
>>>>>> set root='(hd0,msdos5)'
>>>>>> search --no-floppy --fs-uuid --set=root 4a5a9317-0b70-4796-a094-d61c01891c81
>>>>>> multiboot /boot/memtest86+_multiboot.bin
>>>>>> }
>>>>>> menuentry "Memory test (memtest86+, serial console 115200, experimental multiboot)" {
>>>>>> insmod part_msdos
>>>>>> insmod ext2
>>>>>> set root='(hd0,msdos5)'
>>>>>> search --no-floppy --fs-uuid --set=root 4a5a9317-0b70-4796-a094-d61c01891c81
>>>>>> multiboot /boot/memtest86+_multiboot.bin console=ttyS0,115200n8
>>>>>> }
>>>>>> ### END /etc/grub.d/20_memtest86+ ###
>>>>>>
>>>>>> ### BEGIN /etc/grub.d/30_os-prober ###
>>>>>> menuentry "Windows Vista (loader) (on /dev/sda3)" --class windows --class os {
>>>>>> insmod part_msdos
>>>>>> insmod ntfs
>>>>>> set root='(hd0,msdos3)'
>>>>>> search --no-floppy --fs-uuid --set=root 0C6CE0BA6CE0A026
>>>>>> chainloader +1
>>>>>> }
>>>>>> ### END /etc/grub.d/30_os-prober ###
>>>>>>
>>>>>> ### BEGIN /etc/grub.d/40_custom ###
>>>>>> # This file provides an easy way to add custom menu entries.  Simply type the
>>>>>> # menu entries you want to add after this comment.  Be careful not to change
>>>>>> # the 'exec tail' line above.
>>>>>> ### END /etc/grub.d/40_custom ###
>>>>>>
>>>>>> ### BEGIN /etc/grub.d/41_custom ###
>>>>>> if [ -f  $prefix/custom.cfg ]; then
>>>>>>   source $prefix/custom.cfg;
>>>>>> fi
>>>>>> ### END /etc/grub.d/41_custom ###
>>>>>> -------------
>>>>>> -------------
>>>>>> INFO: /boot/grub/device.map content
>>>>>> -------------
>>>>>> (hd0) /dev/disk/by-id/ata-ST3320620AS_5QF2VWM8
>>>>>> -------------
>>>>>> Full fdisk info
>>>>>> ---------------
>>>>>>
>>>>>> Disque /dev/sda??: 320.1??Go, 320072933376??octets
>>>>>> 255??t??tes, 63??secteurs/piste, 38913??cylindres, total 625142448??secteurs
>>>>>> Unit??s = secteurs de 1 * 512 = 512??octets
>>>>>> Taille de secteur (logique / physique)??: 512??octets / 512??octets
>>>>>> taille d'E/S (minimale / optimale)??: 512??octets / 512??octets
>>>>>> Identifiant de disque??: 0x58000000
>>>>>>
>>>>>> P??riph??rique Amorce  D??but        Fin      Blocs     Id  Syst??me
>>>>>> /dev/sda1              63      112454       56196   de  Dell Utility
>>>>>> /dev/sda2          112640    21084159    10485760    7  HPFS/NTFS/exFAT
>>>>>> /dev/sda3   *    21093345   228379505   103643080+   7  HPFS/NTFS/exFAT
>>>>>> /dev/sda4       228380101   625141759   198380829+   5  ??tendue
>>>>>> /dev/sda5       228380103   423698309    97659103+  83  Linux
>>>>>> /dev/sda6       423698373   425658239      979933+  82  partition d'??change Linux / Solaris
>>>>>> /dev/sda7       425658368   625141759    99741696   8e  LVM Linux
>>>>>>
>>>>>> Disque /dev/sdb??: 1000.2??Go, 1000204886016??octets
>>>>>> 81??t??tes, 63??secteurs/piste, 382818??cylindres, total 1953525168??secteurs
>>>>>> Unit??s = secteurs de 1 * 512 = 512??octets
>>>>>> Taille de secteur (logique / physique)??: 512??octets / 512??octets
>>>>>> taille d'E/S (minimale / optimale)??: 512??octets / 512??octets
>>>>>> Identifiant de disque??: 0x0003513f
>>>>>>
>>>>>> P??riph??rique Amorce  D??but        Fin      Blocs     Id  Syst??me
>>>>>> /dev/sdb1            2048  1953525167   976761560   8e  LVM Linux
>>>>>>
>>>>>> Disque /dev/mapper/data1vg-photoslv??: 75.2??Go, 75161927680??octets
>>>>>> 255??t??tes, 63??secteurs/piste, 9137??cylindres, total 146800640??secteurs
>>>>>> Unit??s = secteurs de 1 * 512 = 512??octets
>>>>>> Taille de secteur (logique / physique)??: 512??octets / 512??octets
>>>>>> taille d'E/S (minimale / optimale)??: 512??octets / 512??octets
>>>>>> Identifiant de disque??: 0x00000000
>>>>>>
>>>>>>
>>>>>> Disque /dev/mapper/data1vg-videoslv??: 161.1??Go, 161061273600??octets
>>>>>> 255??t??tes, 63??secteurs/piste, 19581??cylindres, total 314572800??secteurs
>>>>>> Unit??s = secteurs de 1 * 512 = 512??octets
>>>>>> Taille de secteur (logique / physique)??: 512??octets / 512??octets
>>>>>> taille d'E/S (minimale / optimale)??: 512??octets / 512??octets
>>>>>> Identifiant de disque??: 0x00000000
>>>>>>
>>>>>>
>>>>>> Disque /dev/mapper/data1vg-homelv??: 53.7??Go, 53687091200??octets
>>>>>> 255??t??tes, 63??secteurs/piste, 6527??cylindres, total 104857600??secteurs
>>>>>> Unit??s = secteurs de 1 * 512 = 512??octets
>>>>>> Taille de secteur (logique / physique)??: 512??octets / 512??octets
>>>>>> taille d'E/S (minimale / optimale)??: 512??octets / 512??octets
>>>>>> Identifiant de disque??: 0x00000000
>>>>>>
>>>>>>
>>>>>> Disque /dev/mapper/data1vg-graveurlv??: 21.5??Go, 21474836480??octets
>>>>>> 255??t??tes, 63??secteurs/piste, 2610??cylindres, total 41943040??secteurs
>>>>>> Unit??s = secteurs de 1 * 512 = 512??octets
>>>>>> Taille de secteur (logique / physique)??: 512??octets / 512??octets
>>>>>> taille d'E/S (minimale / optimale)??: 512??octets / 512??octets
>>>>>> Identifiant de disque??: 0x00000000
>>>>>>
>>>>>>
>>>>>> Disque /dev/mapper/data1vg-wwwlv??: 5003??Mo, 5003804672??octets
>>>>>> 255??t??tes, 63??secteurs/piste, 608??cylindres, total 9773056??secteurs
>>>>>> Unit??s = secteurs de 1 * 512 = 512??octets
>>>>>> Taille de secteur (logique / physique)??: 512??octets / 512??octets
>>>>>> taille d'E/S (minimale / optimale)??: 512??octets / 512??octets
>>>>>> Identifiant de disque??: 0x00000000
>>>>>>
>>>>>>
>>>>>> Disque /dev/mapper/data1vg-baseslv??: 2000??Mo, 2000683008??octets
>>>>>> 255??t??tes, 63??secteurs/piste, 243??cylindres, total 3907584??secteurs
>>>>>> Unit??s = secteurs de 1 * 512 = 512??octets
>>>>>> Taille de secteur (logique / physique)??: 512??octets / 512??octets
>>>>>> taille d'E/S (minimale / optimale)??: 512??octets / 512??octets
>>>>>> Identifiant de disque??: 0x00000000
>>>>>>
>>>>>>
>>>>>> Disque /dev/mapper/data1vg-vboxlv??: 140.0??Go, 140001673216??octets
>>>>>> 255??t??tes, 63??secteurs/piste, 17020??cylindres, total 273440768??secteurs
>>>>>> Unit??s = secteurs de 1 * 512 = 512??octets
>>>>>> Taille de secteur (logique / physique)??: 512??octets / 512??octets
>>>>>> taille d'E/S (minimale / optimale)??: 512??octets / 512??octets
>>>>>> Identifiant de disque??: 0x00000000
>>>>>>
>>>>>>
>>>>>> Disque /dev/mapper/sysvg-optlv??: 17.5??Go, 17481859072??octets
>>>>>> 255??t??tes, 63??secteurs/piste, 2125??cylindres, total 34144256??secteurs
>>>>>> Unit??s = secteurs de 1 * 512 = 512??octets
>>>>>> Taille de secteur (logique / physique)??: 512??octets / 512??octets
>>>>>> taille d'E/S (minimale / optimale)??: 512??octets / 512??octets
>>>>>> Identifiant de disque??: 0x00000000
>>>>>>
>>>>>> ----------------
>>>>>> ------------------------------------
>>>>>> Your raw fstab file looks like this:
>>>>>> ------------------------------------
>>>>>> # /etc/fstab: static file system information.
>>>>>> #
>>>>>> # Use 'blkid' to print the universally unique identifier for a
>>>>>> # device; this may be used with UUID= as a more robust way to name devices
>>>>>> # that works even if disks are added and removed. See fstab(5).
>>>>>> #
>>>>>> # <file system>        <mount point>     <type>      <options>                   <dump> <pass>
>>>>>> # / was on /dev/sda5 during installation
>>>>>> UUID=4a5a9317-0b70-4796-a094-d61c01891c81 /    ext4  errors=remount-ro           0      1
>>>>>> # swap was on /dev/sda6 during installation
>>>>>> UUID=b4d7e5c0-207b-4a67-8b58-20523c509b87 none swap  sw                          0      0
>>>>>>
>>>>>> /dev/sr0               /media/cdrom0     udf,iso9660 user,noauto                 0      0
>>>>>>
>>>>>> #/dev/sysvg/homelv      /home             ext4        relatime,errors=remount-ro  0      1
>>>>>> /dev/sysvg/optlv       /opt              ext4        relatime,errors=remount-ro  0      1
>>>>>>
>>>>>> /dev/data1vg/homelv    /home             ext4        relatime,errors=remount-ro  0      2
>>>>>> /dev/data1vg/wwwlv     /www              ext4        relatime,errors=remount-ro  0      2
>>>>>> /dev/data1vg/baseslv   /bases            ext4        relatime,errors=remount-ro  0      2
>>>>>> /dev/data1vg/photoslv  /photos           ext4        relatime,errors=remount-ro  0      2
>>>>>> /dev/data1vg/videoslv  /videos           ext4        relatime,errors=remount-ro  0      2
>>>>>> /dev/data1vg/vboxlv    /vbox             ext4        relatime,errors=remount-ro  0      2
>>>>>> /dev/data1vg/graveurlv /graveur          ext4        relatime,errors=remount-ro  0      2
>>>>>>
>>>>>> # /dev/data0vg/homelv    /data0vg/home     ext4        relatime,errors=remount-ro  0      2
>>>>>> # /dev/data0vg/wwwlv     /data0vg/www      ext4        relatime,errors=remount-ro  0      2
>>>>>> # /dev/data0vg/baseslv   /data0vg/bases    ext4        relatime,errors=remount-ro  0      2
>>>>>> # /dev/data0vg/photoslv  /data0vg/photos   ext4        relatime,errors=remount-ro  0      2
>>>>>> # /dev/data0vg/videoslv  /data0vg/videos   ext4        relatime,errors=remount-ro  0      2
>>>>>> # /dev/data0vg/vboxlv    /data0vg/vbox     ext4        relatime,errors=remount-ro  0      2
>>>>>>
>>>>>> # /dev/data2vg/homelv    /data2vg/home     ext4        relatime,errors=remount-ro  0      2
>>>>>> # /dev/data2vg/wwwlv     /data2vg/www      ext4        relatime,errors=remount-ro  0      2
>>>>>> # /dev/data2vg/baseslv   /data2vg/bases    ext4        relatime,errors=remount-ro  0      2
>>>>>> # /dev/data2vg/photoslv  /data2vg/photos   ext4        relatime,errors=remount-ro  0      2
>>>>>> # /dev/data2vg/videoslv  /data2vg/videos   ext4        relatime,errors=remount-ro  0      2
>>>>>> # /dev/data2vg/vboxlv    /data2vg/vbox     ext4        relatime,errors=remount-ro  0      2
>>>>>> -----------------------------------
>>>>>> Your mountlist will look like this:
>>>>>> -----------------------------------
>>>>>> INFO: Analyzing LVM...
>>>>>> DEVICE          MOUNTPOINT      FORMAT          SIZE MB       LABEL/UUID    
>>>>>> ------          ----------      ------          -------       ----------    
>>>>>> INFO: Examining /dev/sdb1 (mount=lvm fmt=lvm psz=976761560)
>>>>>> /dev/sdb1       lvm             lvm              953868 c9qZKK-bpqn-sY7P-fWH2-SBlo-YsXS-udCgP7
>>>>>> INFO: Examining /dev/sda7 (mount=lvm fmt=lvm psz=99741696)
>>>>>> /dev/sda7       lvm             lvm               97404 yuL0j7-wJtb-ANiO-Omxi-AuEE-wCkJ-pfhEWi
>>>>>> INFO: Examining /dev/sda5 (mount=/ fmt=ext4 psz=97659103)
>>>>>> /dev/sda5       /               ext4              95370 4a5a9317-0b70-4796-a094-d61c01891c81
>>>>>> INFO: Examining /dev/sda6 (mount=swap fmt=swap psz=979928)
>>>>>> /dev/sda6       swap            swap                956 b4d7e5c0-207b-4a67-8b58-20523c509b87
>>>>>> INFO: Examining /dev/sysvg/optlv (mount=/opt fmt=ext4 psz=lvm)
>>>>>> /dev/sysvg/optlv /opt            ext4                lvm f1c4b976-0101-47ac-9ff8-c5a9e567553b
>>>>>> INFO: Examining /dev/data1vg/homelv (mount=/home fmt=ext4 psz=lvm)
>>>>>> /dev/data1vg/homelv /home           ext4                lvm e063df74-3fff-45ac-927d-bc6a60bd2970
>>>>>> INFO: Examining /dev/data1vg/wwwlv (mount=/www fmt=ext4 psz=lvm)
>>>>>> /dev/data1vg/wwwlv /www            ext4                lvm 7942603b-20c8-483a-ab36-98ee20ab7700
>>>>>> INFO: Examining /dev/data1vg/baseslv (mount=/bases fmt=ext4 psz=lvm)
>>>>>> /dev/data1vg/baseslv /bases          ext4                lvm 09f40cc9-fc3b-4205-a466-df38e5774a59
>>>>>> INFO: Examining /dev/data1vg/photoslv (mount=/photos fmt=ext4 psz=lvm)
>>>>>> /dev/data1vg/photoslv /photos         ext4                lvm 11ff707f-da12-46a3-9218-87fcf38ddc2f
>>>>>> INFO: Examining /dev/data1vg/videoslv (mount=/videos fmt=ext4 psz=lvm)
>>>>>> /dev/data1vg/videoslv /videos         ext4                lvm 11e0f5ef-75e4-4b7b-b34e-c9112b731f57
>>>>>> INFO: Examining /dev/data1vg/vboxlv (mount=/vbox fmt=ext4 psz=lvm)
>>>>>> /dev/data1vg/vboxlv /vbox           ext4                lvm 69e8fcf6-9518-4c3c-9052-53096c873cc4
>>>>>> INFO: Examining /dev/data1vg/graveurlv (mount=/graveur fmt=ext4 psz=lvm)
>>>>>> /dev/data1vg/graveurlv /graveur        ext4                lvm a5d30c9b-d333-46a3-8c28-ef2c4c1d9185
>>>>>> -----------------------------------
>>>>>> Mindi 3.0.0-r3332 is exiting
>>>>>> End date : lundi 19 janvier 2015, 22:16:59 (UTC+0100)
>>>>>
>>>>>> INFO: Time started: Mon Jan 19 22:16:43 2015
>>>>>>
>>>>>> DBG2: [TH=22705] libmondo-tools.c->setup_tmpdir#715: bkpinfo->tmpdir is being set to /tmp/mondo.tmp.4v41Vd
>>>>>> DBG2: [TH=22705] libmondo-tools.c->setup_scratchdir#736: Purging old scratchdir /mondo.scratch.*
>>>>>> DBG2: [TH=22705] libmondo-tools.c->setup_scratchdir#757: bkpinfo->scratchdir is being set to /tmp/mondo.scratch.3mNp4N
>>>>>> INFO: root is mounted at /dev/disk/by-uuid/aa9317-0b70-4796-a094-d61c01891c81
>>>>>>
>>>>>> INFO: That doesn't mean /dev/disk/by-uuid/aa9317-0b70-4796-a094-d61c01891c81 is the root partition. It's just a debugging message. Relax. It's part of am_I_in_disaster_recovery_mode().
>>>>>> DBG1: [TH=22705] libmondo-devices.c->am_I_in_disaster_recovery_mode#163: Is this a ramdisk? result = FALSE
>>>>>> INFO: running: dmesg -n1 > /tmp/mondo.tmp.4v41Vd/mondo-run-prog-thing.tmp 2> /tmp/mondo.tmp.4v41Vd/mondo-run-prog-thing.err
>>>>>> INFO: --------------------------------start of output-----------------------------
>>>>>> INFO: --------------------------------end of output------------------------------
>>>>>> INFO: ...ran just fine. :-)
>>>>>> INFO: Mondo Archive v3.2.0-r3332 --- http://www.mondorescue.org
>>>>>> INFO: running x86_64 binaries
>>>>>> INFO: running on x86_64 architecture
>>>>>> INFO: -----------------------------------------------------------
>>>>>> INFO: NB: Mondo logs almost everything, so don't panic if you see
>>>>>> INFO: some error messages.  Please read them carefully before you
>>>>>> INFO: decide to break out in a cold sweat.    Despite (or perhaps
>>>>>> INFO: because of) the wealth of messages. some users are inclined
>>>>>> INFO: to stop reading this log. If Mondo stopped for some reason,
>>>>>> INFO: chances are it's detailed here.  More than likely there's a
>>>>>> INFO: message at the very end of this log that will tell you what
>>>>>> INFO: is wrong. Please read it!                          -Devteam
>>>>>> INFO: -----------------------------------------------------------
>>>>>> INFO: Zero...
>>>>>> DBG1: [Main] mondoarchive.c->welcome_to_mondoarchive#96: One...
>>>>>> DBG2: [Main] mondoarchive.c->welcome_to_mondoarchive#97: Two...
>>>>>> DBG3: [Main] mondoarchive.c->welcome_to_mondoarchive#98: Three...
>>>>>> DBG4: [Main] mondoarchive.c->welcome_to_mondoarchive#99: Four...
>>>>>> DBG2: [Main] mondoarchive.c->distro_specific_kludges_at_start_of_mondoarchive#114: Unmounting old ramdisks if necessary
>>>>>> INFO: running: mount | grep cdrom | grep super > /tmp/mondo.tmp.4v41Vd/mondo-run-prog-thing.tmp 2> /tmp/mondo.tmp.4v41Vd/mondo-run-prog-thing.err
>>>>>> INFO: --------------------------------start of output-----------------------------
>>>>>> INFO: --------------------------------end of output------------------------------
>>>>>> INFO: ...ran with res=256
>>>>>> INFO: running: mount | grep floppy | grep super > /tmp/mondo.tmp.4v41Vd/mondo-run-prog-thing.tmp 2> /tmp/mondo.tmp.4v41Vd/mondo-run-prog-thing.err
>>>>>> INFO: --------------------------------start of output-----------------------------
>>>>>> INFO: --------------------------------end of output------------------------------
>>>>>> INFO: ...ran with res=256
>>>>>> DBG1: [Main] libmondo-tools.c->mount_boot_if_necessary#1155: Started sub
>>>>>> DBG4: [Main] libmondo-tools.c->mount_boot_if_necessary#1156: About to set g_boot_mountpt[0] to '\0'
>>>>>> DBG4: [Main] libmondo-tools.c->mount_boot_if_necessary#1158: Done. Great. Seeting command to something
>>>>>> DBG4: [Main] libmondo-tools.c->mount_boot_if_necessary#1160: Cool. Command = 'grep -v ":" /etc/fstab | grep -vE '^#.*$' | grep -E "[ ]/boot[ ]" | tr -s ' ' ' ' | cut -f1 | head -n1'
>>>>>> DBG4: [Main] libmondo-tools.c->mount_boot_if_necessary#1164: tmp = ''
>>>>>> DBG2: [Main] libmondo-tools.c->mount_boot_if_necessary#1165: /boot is at  according to /etc/fstab
>>>>>> DBG3: [Main] libmondo-tools.c->mount_boot_if_necessary#1182: command = mount | grep -E '^'
>>>>>> DBG1: [Main] libmondo-tools.c->mount_boot_if_necessary#1205: Ended sub
>>>>>> DBG1: [Main] libmondo-tools.c->get_kernel_version#245: g_kernel_version = 3.200000
>>>>>> INFO: running: rm -Rf /var/cache/mondo/changed.files* > /tmp/mondo.tmp.4v41Vd/mondo-run-prog-thing.tmp 2> /tmp/mondo.tmp.4v41Vd/mondo-run-prog-thing.err
>>>>>> INFO: --------------------------------start of output-----------------------------
>>>>>> INFO: --------------------------------end of output------------------------------
>>>>>> INFO: ...ran just fine. :-)
>>>>>> INFO: Checking sanity of your Linux distribution
>>>>>> INFO: running: grep ramdisk /proc/devices > /tmp/mondo.tmp.4v41Vd/mondo-run-prog-thing.tmp 2> /tmp/mondo.tmp.4v41Vd/mondo-run-prog-thing.err
>>>>>> INFO: --------------------------------start of output-----------------------------
>>>>>> INFO: 1 ramdisk
>>>>>> INFO: --------------------------------end of output------------------------------
>>>>>> INFO: ...ran just fine. :-)
>>>>>> INFO: running: mount | grep -Ew 'vfat|fat|dos' | grep -vE "/dev/fd|nexdisk" > /tmp/mondo.tmp.4v41Vd/mondo-run-prog-thing.tmp 2> /tmp/mondo.tmp.4v41Vd/mondo-run-prog-thing.err
>>>>>> INFO: --------------------------------start of output-----------------------------
>>>>>> INFO: --------------------------------end of output------------------------------
>>>>>> INFO: ...ran with res=256
>>>>>> DBG4: [Main] libmondo-files.c->find_home_of_exe#349: find_home_of_exe --- Found cmp at /usr/bin/cmp
>>>>>> INFO: running: mindi -V > /tmp/mondo.tmp.4v41Vd/mondo-run-prog-thing.tmp 2> /tmp/mondo.tmp.4v41Vd/mondo-run-prog-thing.err
>>>>>> INFO: --------------------------------start of output-----------------------------
>>>>>> INFO: Mindi v3.0.0-r3332
>>>>>> INFO: Le disque /dev/mapper/data1vg-photoslv ne contient pas une table de partitions valable
>>>>>> INFO: Le disque /dev/mapper/data1vg-videoslv ne contient pas une table de partitions valable
>>>>>> INFO: Le disque /dev/mapper/data1vg-homelv ne contient pas une table de partitions valable
>>>>>> INFO: Le disque /dev/mapper/data1vg-graveurlv ne contient pas une table de partitions valable
>>>>>> INFO: Le disque /dev/mapper/data1vg-wwwlv ne contient pas une table de partitions valable
>>>>>> INFO: Le disque /dev/mapper/data1vg-baseslv ne contient pas une table de partitions valable
>>>>>> INFO: Le disque /dev/mapper/data1vg-vboxlv ne contient pas une table de partitions valable
>>>>>> INFO: Le disque /dev/mapper/sysvg-optlv ne contient pas une table de partitions valable
>>>>>> INFO: --------------------------------end of output------------------------------
>>>>>> INFO: ...ran just fine. :-)
>>>>>> INFO: running: parted2fdisk -l 2>/dev/null | grep -i raid > /tmp/mondo.tmp.4v41Vd/mondo-run-prog-thing.tmp 2> /tmp/mondo.tmp.4v41Vd/mondo-run-prog-thing.err
>>>>>> INFO: --------------------------------start of output-----------------------------
>>>>>> INFO: --------------------------------end of output------------------------------
>>>>>> INFO: ...ran with res=256
>>>>>> INFO: Done.
>>>>>> DBG1: [Main] libmondo-cli.c->process_switches#181: Loglevel forced to 99
>>>>>> DBG20: [Main] libmondo-files.c->does_file_exist#188: /usr/bin/afio exists
>>>>>> DBG4: [Main] libmondo-files.c->find_home_of_exe#349: find_home_of_exe --- Found afio at /usr/bin/afio
>>>>>
>>>>>> ------------------------------------------------------------------------------
>>>>>> New Year. New Location. New Benefits. New Data Center in Ashburn, VA.
>>>>>> GigeNET is offering a free month of service with a new server in Ashburn.
>>>>>> Choose from 2 high performing configs, both with 100TB of bandwidth.
>>>>>> Higher redundancy.Lower latency.Increased capacity.Completely compliant.
>>>>>> http://p.sf.net/sfu/gigenet
>>>>>
>>>>>> _______________________________________________
>>>>>> Mondo-devel mailing list
>>>>>> [hidden email]
>>>>>> https://lists.sourceforge.net/lists/listinfo/mondo-devel
>>>>>
>>>>>
>>>>
>>>>
>>>
>>>
>>>
>>>
>>> ------------------------------------------------------------------------------
>>> Dive into the World of Parallel Programming. The Go Parallel Website,
>>> sponsored by Intel and developed in partnership with Slashdot Media, is your
>>> hub for all things parallel software development, from weekly thought
>>> leadership blogs to news, videos, case studies, tutorials and more. Take a
>>> look and join the conversation now. http://goparallel.sourceforge.net/
>>>
>>>
>>>
>>> _______________________________________________
>>> Mondo-devel mailing list
>>> [hidden email]
>>> https://lists.sourceforge.net/lists/listinfo/mondo-devel
>>>
>>
>>
>>
>> ------------------------------------------------------------------------------
>> Dive into the World of Parallel Programming. The Go Parallel Website,
>> sponsored by Intel and developed in partnership with Slashdot Media, is your
>> hub for all things parallel software development, from weekly thought
>> leadership blogs to news, videos, case studies, tutorials and more. Take a
>> look and join the conversation now. http://goparallel.sourceforge.net/
>> _______________________________________________
>> Mondo-devel mailing list
>> [hidden email]
>> https://lists.sourceforge.net/lists/listinfo/mondo-devel
>>
>>
>
>
>
> ------------------------------------------------------------------------------
> Dive into the World of Parallel Programming. The Go Parallel Website,
> sponsored by Intel and developed in partnership with Slashdot Media, is your
> hub for all things parallel software development, from weekly thought
> leadership blogs to news, videos, case studies, tutorials and more. Take a
> look and join the conversation now. http://goparallel.sourceforge.net/
> _______________________________________________
> Mondo-devel mailing list
> [hidden email]
> https://lists.sourceforge.net/lists/listinfo/mondo-devel
>
>


------------------------------------------------------------------------------
Dive into the World of Parallel Programming. The Go Parallel Website,
sponsored by Intel and developed in partnership with Slashdot Media, is your
hub for all things parallel software development, from weekly thought
leadership blogs to news, videos, case studies, tutorials and more. Take a
look and join the conversation now. http://goparallel.sourceforge.net/
_______________________________________________
Mondo-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/mondo-devel

mondoarchive.log (501K) Download Attachment
libmondo-cli.c (33K) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Re: [Mondo-devel] Segmentation error running mondoarchive v3.2.0-r3332

Philippe Lefevre
In reply to this post by Philippe Lefevre
Hello list,

I performed an entire backup test this morning with my fix.
That seems to be ok.
Please find attached the libmondo-cli.c fixed and a log trace from
mondoarchive test backup.

Kind regards,
Philippe


Le 06/02/2015 21:53, Philippe Lefevre a écrit :

> Hi list,
>
> I believe I found where the issue with -I is.
>
> In fact, the structure bkpinfo is well built with an include_paths entry
> initialized to NULL, but there is no malloc that would allow to store
> any string.
>
> I compared how is parsed the -E and -I options and supposed they should
> work in quite the same way.
>
> It seems to me that there is some code missing in libmondo-cli.c. So I
> made the following changes and that seems to work.
>
> ================================================
> libmondo-cli.c
> 231:if (flag_set['I']) {
>       if (bkpinfo->include_paths && bkpinfo->include_paths[0] == '-'){
>         retval++;
>         log_to_screen("Please supply a sensible value with '-I'\n");
>         }
>
> // Added
> mr_asprintf(tmp1, "%s", flag_val['I']);
> p = tmp1;
> q = tmp1;
> // End add
>
> // Modified
> if (!strcmp(tmp1, "/")) {
> // End modif
>                         log_msg(2, "'/' is pleonastic.");
>                         mr_free(bkpinfo->include_paths);  // Not sure
> this is needed
>                 }
> // Modified
> if (tmp1[0]) {
> // End modif
>                         mr_strcat(bkpinfo->include_paths, "|");
>                 }
>
> 249 :   /* Cut the flag_val['I'] in parts containing all paths to test
> them */
> ================================================
>
>
>
> I hope this help :)
>
> Kind regards,
> Philippe
>
>
>

------------------------------------------------------------------------------
Dive into the World of Parallel Programming. The Go Parallel Website,
sponsored by Intel and developed in partnership with Slashdot Media, is your
hub for all things parallel software development, from weekly thought
leadership blogs to news, videos, case studies, tutorials and more. Take a
look and join the conversation now. http://goparallel.sourceforge.net/
_______________________________________________
Mondo-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/mondo-devel

libmondo-cli.c.gz (11K) Download Attachment
mondoarchive.log.gz (64K) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Re: [Mondo-devel] Segmentation error running mondoarchive v3.2.0-r3332

Bruno Cornec-2
In reply to this post by Philippe Lefevre
Hello Philippe,

Thanks a lot for fnding the root cause. You are pointing to an issue
which is double as in addition to the core dump, the code doesn't do
what is expect in term of tests.

I'm proposing this patch based on yours:
http://trac.mondorescue.org/changeset?reponame=&new=3342%40branches&old=3341%40branches

Let me know if you want me to provide you with packages for this one so
you can test, or if you have what is needed to rebuild.

Greetings,
Bruno.

Philippe Lefevre said on Fri, Feb 06, 2015 at 09:53:32PM +0100:

> Hi list,
>
> I believe I found where the issue with -I is.
>
> In fact, the structure bkpinfo is well built with an include_paths entry
> initialized to NULL, but there is no malloc that would allow to store
> any string.
>
> I compared how is parsed the -E and -I options and supposed they should
> work in quite the same way.
>
> It seems to me that there is some code missing in libmondo-cli.c. So I
> made the following changes and that seems to work.
>
> ================================================
> libmondo-cli.c
> 231:if (flag_set['I']) {
>       if (bkpinfo->include_paths && bkpinfo->include_paths[0] == '-'){
>         retval++;
>         log_to_screen("Please supply a sensible value with '-I'\n");
>         }
>
> // Added
> mr_asprintf(tmp1, "%s", flag_val['I']);
> p = tmp1;
> q = tmp1;
> // End add
>
> // Modified
> if (!strcmp(tmp1, "/")) {
> // End modif
>                         log_msg(2, "'/' is pleonastic.");
>                         mr_free(bkpinfo->include_paths);  // Not sure
> this is needed
>                 }
> // Modified
> if (tmp1[0]) {
> // End modif
>                         mr_strcat(bkpinfo->include_paths, "|");
>                 }
>
> 249 :   /* Cut the flag_val['I'] in parts containing all paths to test
> them */
> ================================================
>
>
>
> I hope this help :)
>
> Kind regards,
> Philippe
>
>
>
> Le 02/02/2015 21:00, Philippe Lefevre a écrit :
> > OOPS !
> >
> > In my latest email:
> >> I reran it from compiled sources but this time I also had the same
> >> trouble with it and was not able to get the error.
> >
> > I meant "I was unable to get it work well again as I described in my
> > email dated of 17th of januray"
> >
> > Kind Rgds,
> > Philippe
> >
> > Le 01/02/2015 23:17, Philippe Lefevre a écrit :
> >> Hello list,
> >>
> >> I did again some tries with mondo 3.2.0
> >> Right: without -I option it works.
> >>
> >> I reran it from compiled sources but this time I also had the same
> >> trouble with it and was not able to get the error.
> >>
> >> I tried to understand what happen with this option and I believe it is
> >> linked to the pointer bkpinfo->include_paths which is empty in
> >> libmondo-cli.c:236
> >> We can see that flag_val['I'] is well setted to the arg value and
> >> flag_set['I'] is true in process_switches()
> >>
> >> Sorry, I must stop now and I'm afraid I will not have time those next
> >> days to grab into it again (may be next we ??) but I hope these traces
> >> may help.
> >>
> >> Please find attached some gdb steps.
> >>
> >> Kind regards,
> >> Philippe
> >>
> >>
> >> Le 26/01/2015 22:10, Philippe Lefevre a écrit :
> >>>
> >>> Great !
> >>>
> >>> Many thanks for your help and reply Bruno.
> >>>
> >>> Next week-end I'm going to reinstall 3.2.0 and supress -I option and see
> >>> what happen.
> >>>
> >>> One thing is strange anyway: in my tests after a mondoarchive
> >>> compilation, (pls, see my email dated on 17th january) I ran 3.2.0 with
> >>> -I option without any issue. The sigsegv was repructible when
> >>> mondoarchive was installed by the deb package ...
> >>>
> >>> I used :
> >>> [phlsys]root:/home/phl/mondo-3.2.0# gdb -args mondoarchive -D -OV -i -N
> >>> -G -s 780M -p sys-D7.7-diff_150105212200 -T /graveur -S /graveur -d
> >>> /graveur -I "/|/|/opt/Zuma" -E
> >>> "/bases/sybase|/graveur|/home|/opt|/photos|/quemu|/Sauvegardes|/var/crash|/var/backups|/var/log|/var/mail|/var/spool|/vbox|/videos|/www"
> >>>
> >>> and:
> >>>  ....
> >>>  Data archived OK.
> >>>  Mondoarchive ran OK.
> >>>  See /var/log/mondoarchive.log for details of backup run.
> >>>  Execution run ended; result=0
> >>>  Type 'less /var/log/mondoarchive.log' to see the output log [Inferior 1
> >>> (process 19382) exited normally]
> >>>  (gdb) quit
> >>>
> >>>
> >>> I'll let you know.
> >>> Kind regards,
> >>> Philippe
> >>>
> >>>
> >>>
> >>> Le 26/01/2015 01:09, Bruno Cornec a écrit :
> >>>> Hello Philippe,
> >>>>
> >>>> This is now fixed as described in BR:
> >>>> http://trac.mondorescue.org/ticket/764#comment:2
> >>>>
> >>>> Bruno.
> >>>>
> >>>> Philippe Lefevre said on Mon, Jan 19, 2015 at 10:34:24PM +0100:
> >>>>
> >>>>> Hello Gaetagno,
> >>>>>
> >>>>> Regarding the two slashes, as I said, I used the same syntax to get into
> >>>>> the same bug situation.
> >>>>>
> >>>>>
> >>>>> I did a try with only one / in the -I option and got the same
> >>>>> segmentation violation exception.
> >>>>>
> >>>>>
> >>>>> Mindi launched alone as your example and it ran fine and the iso file
> >>>>> successfully built.
> >>>>> Please find attached the mindi.log file.
> >>>>>
> >>>>> [phlsys]root:/home/phl/Devel/mondo# ls -al /var/cache/mindi/mindi.iso
> >>>>> -rw-r----- 1 root root 98721792 janv. 19 22:09 /var/cache/mindi/mindi.iso
> >>>>>
> >>>>>
> >>>>>
> >>>>> Ran mondoarchive with -K99 option crashed again with the sigsegv signal.
> >>>>> Please find attached the mondoarchive.log file.
> >>>>> Unfortunately, I'm afraid it is not so verbose than we would ...
> >>>>> This time, the log ends with :
> >>>>>
> >>>>> DBG1: [Main] libmondo-cli.c->process_switches#181: Loglevel forced to 99
> >>>>> DBG20: [Main] libmondo-files.c->does_file_exist#188: /usr/bin/afio exists
> >>>>> DBG4: [Main] libmondo-files.c->find_home_of_exe#349: find_home_of_exe
> >>>>> --- Found afio at /usr/bin/afio
> >>>>>
> >>>>>
> >>>>>
> >>>>> Running mondo without - E option crashed in the same way and with same
> >>>>> mondoarchive.log file.
> >>>>> [phlsys]root:/home/phl/Devel/mondo# /usr/sbin/mondoarchive -K99 -D -OV
> >>>>> -i -N -G -s 780M -p sys-D7.7-diff_150105212200 -T /graveur -S /graveur
> >>>>> -d /graveur -I "/opt/zuma"
> >>>>> See /var/log/mondoarchive.log for details of backup run.
> >>>>> Checking sanity of your Linux distribution
> >>>>> Done.
> >>>>> Erreur de segmentation
> >>>>>
> >>>>>
> >>>>> Thank you for your time Gaetagno.
> >>>>> Kind regards,
> >>>>> Philippe
> >>>>>
> >>>>>
> >>>>>
> >>>>> Le 19/01/2015 12:17, Gattegno, Victor (GSD CSC / GCC) a écrit :
> >>>>>> Hi Philippe,
> >>>>>>
> >>>>>> You used again two time "/"  in the include :
> >>>>>> -I "/|/|/opt/Zuma"
> >>>>>>
> >>>>>> Your mondorachive.log file ends with :
> >>>>>> DBG4: [Main] libmondo-files.c->find_home_of_exe#349: find_home_of_exe --- Found afio at /usr/bin/afio
> >>>>>>
> >>>>>> You can try a few things :
> >>>>>>
> >>>>>> Try mindi alone :
> >>>>>> # mindi
> >>>>>> Do you want to use your own kernel to build the boot disk ([y]/n) ? y
> >>>>>>
> >>>>>> Try your mondoarchive command without -E, with only -I, and choice only one directory, example :
> >>>>>> -I "/opt/Zuma"
> >>>>>>
> >>>>>> Try your mondoarchive command with more debug, example with -K 5, or with -K 99 (which is full debug mode, be aware that the log file could grow from 200 Kb to 50 Mb).
> >>>>>>
> >>>>>> Rgds,
> >>>>>> Victor
> >>>>>>
> >>>>>> -----Original Message-----
> >>>>>> From: Philippe Lefevre [mailto:[hidden email]]
> >>>>>> Sent: samedi 17 janvier 2015 20:14
> >>>>>> To: Mondo mailing list
> >>>>>> Subject: Re: [Mondo-devel] Segmentation error running mondoarchive v3.2.0-r3332
> >>>>>>
> >>>>>> Hello list,
> >>>>>>
> >>>>>> sorry Gaetagno for the delay, I was not able to find some time long enought to go back into my issue.
> >>>>>>
> >>>>>> I did it today (without removing the two slashes in order to be in the same situation) and .... what I compiled worked fine with what I have compiled. (I noticed the -v bug, thanks  ;)  )
> >>>>>>
> >>>>>> Run mondoarchive via dbg:
> >>>>>> [phlsys]root:/home/phl/mondo-3.2.0# gdb -args mondoarchive -D -OV -i -N -G -s 780M -p sys-D7.7-diff_150105212200 -T /graveur -S /graveur -d /graveur -I "/|/|/opt/Zuma" -E "/bases/sybase|/graveur|/home|/opt|/photos|/quemu|/Sauvegardes|/var/crash|/var/backups|/var/log|/var/mail|/var/spool|/vbox|/videos|/www"
> >>>>>>
> >>>>>> and:
> >>>>>> ....
> >>>>>> Data archived OK.
> >>>>>> Mondoarchive ran OK.
> >>>>>> See /var/log/mondoarchive.log for details of backup run.
> >>>>>> Execution run ended; result=0
> >>>>>> Type 'less /var/log/mondoarchive.log' to see the output log [Inferior 1 (process 19382) exited normally]
> >>>>>> (gdb) quit
> >>>>>>
> >>>>>>
> >>>>>> So I reinstalled the official debian package:
> >>>>>>
> >>>>>> Sélection du paquet libmondorescue-perl précédemment désélectionné.
> >>>>>> (Lecture de la base de données... 279208 fichiers et répertoires déjà
> >>>>>> installés.)
> >>>>>> Dépaquetage de libmondorescue-perl (à partir de
> >>>>>> .../libmondorescue-perl_3.2.0-1_all.deb) ...
> >>>>>> Préparation du remplacement de mindi-busybox 1.18.5-3 (en utilisant
> >>>>>> .../mindi-busybox_1.21.1-1_amd64.deb) ...
> >>>>>> Dépaquetage de la mise à jour de mindi-busybox ...
> >>>>>> Préparation du remplacement de mindi 2.1.7-1 (en utilisant
> >>>>>> .../mindi_3.0.0-1_amd64.deb) ...
> >>>>>> Dépaquetage de la mise à jour de mindi ...
> >>>>>> Préparation du remplacement de mondo 3.0.4-1 (en utilisant
> >>>>>> .../mondo_3.2.0-1_amd64.deb) ...
> >>>>>> Dépaquetage de la mise à jour de mondo ...
> >>>>>> Traitement des actions différées (« triggers ») pour « man-db »...
> >>>>>> Paramétrage de libmondorescue-perl (3.2.0-1) ...
> >>>>>> Paramétrage de mindi-busybox (1.21.1-1) ...
> >>>>>> Paramétrage de mindi (3.0.0-1) ...
> >>>>>> Installation de la nouvelle version du fichier de configuration /etc/mindi/deplist.d/minimal.conf ...
> >>>>>> Installation de la nouvelle version du fichier de configuration /etc/mindi/deplist.d/udev.conf ...
> >>>>>> Installation de la nouvelle version du fichier de configuration /etc/mindi/deplist.d/ProLiant.conf ...
> >>>>>> Installation de la nouvelle version du fichier de configuration /etc/mindi/deplist.d/base.conf ...
> >>>>>> Installation de la nouvelle version du fichier de configuration /etc/mindi/deplist.d/lvm.conf ...
> >>>>>> Installation de la nouvelle version du fichier de configuration /etc/mindi/perl-scripts ...
> >>>>>> Paramétrage de mondo (3.2.0-1) ...
> >>>>>>
> >>>>>>
> >>>>>> but launched in the same way, it crashed again with a segmentation error:
> >>>>>>
> >>>>>> [phlsys]root:/home/phl/telechargements/mondo-3.2.0# mondoarchive -D -OV -i -N -G -s 780M -p sys-D7.7-diff_150105212200 -T /graveur -S /graveur -d /graveur -I "/|/|/opt/Zuma" -E "/bases/sybase|/graveur|/home|/opt|/photos|/quemu|/Sauvegardes|/var/crash|/var/backups|/var/log|/var/mail|/var/spool|/vbox|/videos|/www"
> >>>>>> See /var/log/mondoarchive.log for details of backup run.
> >>>>>> Checking sanity of your Linux distribution Done.
> >>>>>> Erreur de segmentation
> >>>>>>
> >>>>>>
> >>>>>>
> >>>>>> Please find attached the relevant mondoarchive.log file.
> >>>>>> It seems to be stopped before logging something about the fault.
> >>>>>> I franckly don't know what I could do more.
> >>>>>> Do you have an idea about what I could do to explore deeper this issue ?
> >>>>>> Something might be going wrong into the deb pkg ???
> >>>>>> I got it with apt using:
> >>>>>>    deb ftp://ftp.mondorescue.org//debian 7 contrib
> >>>>>>
> >>>>>>
> >>>>>> Thanks for your help.
> >>>>>> Regards,
> >>>>>> Philippe
> >>>>>>
> >>>>>>
> >>>>>>
> >>>>>>
> >>>>>>
> >>>>>> Le 06/01/2015 17:28, Gattegno, Victor (GSD CSC / GCC) a écrit :
> >>>>>>> Hello Philippe,
> >>>>>>>
> >>>>>>> From mondoarchive man : " When using the -I option with the -E option, the -E content should be subdirectories of those mentioned in the -I only, as -I takes precedence."
> >>>>>>>
> >>>>>>> But if your -I and -E combination works it's ok (check if /opt/zuma and /opt/calibre are well backuped and restored).
> >>>>>>>
> >>>>>>> Regards,
> >>>>>>> Victor
> >>>>>>>
> >>>>>>> -----Original Message-----
> >>>>>>> From: Philippe Lefevre [mailto:[hidden email]]
> >>>>>>> Sent: lundi 5 janvier 2015 21:42
> >>>>>>> To: [hidden email]
> >>>>>>> Subject: Re: [Mondo-devel] Segmentation error running mondoarchive
> >>>>>>> v3.2.0-r3332
> >>>>>>>
> >>>>>>> Thanks for your help and reply Victor,
> >>>>>>>
> >>>>>>> I should be able to replay with all of that before the end of the week and let you know.
> >>>>>>> Regarding the double /, it is due to my shell script which build the final request. I will also do a try without it.
> >>>>>>>
> >>>>>>> I believe I couldn't remove -I flag as in the exclude part there is /opt and I want to include only 2 directories /opt/zuma and /opt/calibre. At least, I should use -I "/opt/calibre|/opt/Zuma" right?
> >>>>>>>
> >>>>>>> PS: my system backup is run by root and ulimit is setted unlimited:
> >>>>>>>
> >>>>>>> # ulimit -a
> >>>>>>> core file size          (blocks, -c) 0
> >>>>>>> data seg size           (kbytes, -d) unlimited
> >>>>>>> scheduling priority             (-e) 0
> >>>>>>> file size               (blocks, -f) unlimited
> >>>>>>> pending signals                 (-i) 31106
> >>>>>>> max locked memory       (kbytes, -l) 64
> >>>>>>> max memory size         (kbytes, -m) unlimited
> >>>>>>> open files                      (-n) 1024
> >>>>>>> pipe size            (512 bytes, -p) 8
> >>>>>>> POSIX message queues     (bytes, -q) 819200
> >>>>>>> real-time priority              (-r) 0
> >>>>>>> stack size              (kbytes, -s) 8192
> >>>>>>> cpu time               (seconds, -t) unlimited
> >>>>>>> max user processes              (-u) 31106
> >>>>>>> virtual memory          (kbytes, -v) unlimited
> >>>>>>> file locks                      (-x) unlimited
> >>>>>>>
> >>>>>>>
> >>>>>>> Rgds,
> >>>>>>> Philippe
> >>>>>>>
> >>>>>>>
> >>>>>>> Le 05/01/2015 16:32, Gattegno, Victor (GSD CSC / GCC) a écrit :
> >>>>>>>> Hello Philippe,
> >>>>>>>>
> >>>>>>>> Good gdb work, but don't focus on "mondoarchive -v" segmentation fault, it's a known failing bug. It's better to debug mondoarchive with the options that you use.
> >>>>>>>>
> >>>>>>>>  In your 27/12/2014 test and post:
> >>>>>>>>  - did you posted too the associated /var/log/mondoarchive.log (compressed) ?
> >>>>>>>>  - you used -I (with / included twice) and -E options, it's better to use only -E option.
> >>>>>>>>
> >>>>>>>> What's the result of "ulimit -a" on your Debian ?
> >>>>>>>>
> >>>>>>>> I wish to you - and to all this mailig-list users - a nice year 2015.
> >>>>>>>>
> >>>>>>>> Rgds,
> >>>>>>>> Victor
> >>>>>>>>
> >>>>>>>> -----Original Message-----
> >>>>>>>> From: Philippe Lefevre [mailto:[hidden email]]
> >>>>>>>> Sent: samedi 3 janvier 2015 14:32
> >>>>>>>> To: [hidden email]
> >>>>>>>> Subject: Re: [Mondo-devel] Segmentation error running mondoarchive
> >>>>>>>> v3.2.0-r3332
> >>>>>>>>
> >>>>>>>> Hi list,
> >>>>>>>>
> >>>>>>>> Some more information about my issue.
> >>>>>>>>
> >>>>>>>> I can confirm that in my case it is related to this new release as a I did a downgrade and successfully built a new full backup.
> >>>>>>>>
> >>>>>>>> I uninstalled and purged
> >>>>>>>>   libmondorescue-perl_3.2.0-1_all.deb
> >>>>>>>>   mindi-busybox_1.21.1-1_amd64.deb
> >>>>>>>>   mindi_3.0.0-1_amd64.deb
> >>>>>>>>   mondo_3.2.0-1_amd64.deb
> >>>>>>>>
> >>>>>>>> and reinstalled the previous version
> >>>>>>>>   mindi-busybox 1.18.5-3
> >>>>>>>>   mindi 2.1.7-1
> >>>>>>>>   mondo 3.0.4-1
> >>>>>>>>
> >>>>>>>> I also compiled mondo 3.2.0 from sources and ran gdb agai