Opened 10 years ago

Closed 9 years ago

#368 closed defect (fixed)

FATALERROR result=254 lors de l'utilisation de l'option "-I" avec un nom de volum group

Reported by: BIGOURIEE Owned by: bruno
Priority: normal Milestone: 2.2.9.5
Component: mondo Version: 2.2.9
Severity: normal Keywords:
Cc:

Description

Action: Réalisation d'une sauvegarde des disques internes (disques paritionnés avec LVM, donc sauvegarde du VG00 uniquement) d'un serveur linux SLES10 64 bits SP1 via la version 2.2.9 de Mondoarchive

Commande:exécuté: /usr/sbin/mondoarchive -O -l GRUB -I "/dev/vg00" -N -d <repertoire_destination> -s 650M -p <prefixe_image> -n <partage_NFS>

Le but est de ne sauvegarder que le Volume group VG00 et ainsi exclure les autres VG contenant notamment les données du SGBD (VG01, VG02, etc... qui sont montés sur une baie de disques et non sur les disques internes)

A l'exécution de la commande, retour de l'erreur suivante:

Archiving only the following file systems on /dev/vg00:

Not archiving the following file systems:

* buffer overflow detected *: /usr/sbin/mondoarchive terminated

======= Backtrace: =========

/lib64/libc.so.6(chk_fail+0x2f)[0x2ab79cd6919f]

/lib64/libc.so.6[0x2ab79cd686d9]

/lib64/libc.so.6(_IO_default_xsputn+0x8e)[0x2ab79cd01d3e]

/lib64/libc.so.6(_IO_vfprintf+0x36ff)[0x2ab79ccdc3ef]

/lib64/libc.so.6(vsprintf_chk+0x9d)[0x2ab79cd6877d]

/usr/sbin/mondoarchive[0x42d9f0]

/usr/sbin/mondoarchive[0x410561]

/usr/sbin/mondoarchive[0x43052c]

/usr/sbin/mondoarchive[0x432a3b]

/usr/sbin/mondoarchive[0x403753]

/lib64/libc.so.6(libc_start_main+0xf4)[0x2ab79ccb5154]

/usr/sbin/mondoarchive[0x402fe9]

======= Memory map: ========

00400000-0044e000 r-xp 00000000 fd:07 213231 /usr/sbin/mondoarchive

0054e000-00550000 rw-p 0004e000 fd:07 213231 /usr/sbin/mondoarchive

00550000-00576000 rw-p 00550000 00:00 0 [heap]

2ab79c951000-2ab79c96c000 r-xp 00000000 fd:03 65540 /lib64/ld-2.4.so

2ab79c96c000-2ab79c96e000 rw-p 2ab79c96c000 00:00 0

2ab79c97d000-2ab79c97e000 rw-p 2ab79c97d000 00:00 0

2ab79ca6b000-2ab79ca6d000 rw-p 0001a000 fd:03 65540 /lib64/ld-2.4.so

2ab79ca6d000-2ab79ca80000 r-xp 00000000 fd:07 361664 /usr/lib64/libnewt.so.0.52.1

2ab79ca80000-2ab79cb7f000 ---p 00013000 fd:07 361664 /usr/lib64/libnewt.so.0.52.1

2ab79cb7f000-2ab79cb81000 rw-p 00012000 fd:07 361664 /usr/lib64/libnewt.so.0.52.1

2ab79cb81000-2ab79cb93000 r-xp 00000000 fd:03 65573 /lib64/libpthread-2.4.so

2ab79cb93000-2ab79cc92000 ---p 00012000 fd:03 65573 /lib64/libpthread-2.4.so

2ab79cc92000-2ab79cc94000 rw-p 00011000 fd:03 65573 /lib64/libpthread-2.4.so

2ab79cc94000-2ab79cc98000 rw-p 2ab79cc94000 00:00 0

2ab79cc98000-2ab79cdbf000 r-xp 00000000 fd:03 65547 /lib64/libc-2.4.so

2ab79cdbf000-2ab79cebf000 ---p 00127000 fd:03 65547 /lib64/libc-2.4.so

2ab79cebf000-2ab79cec2000 r--p 00127000 fd:03 65547 /lib64/libc-2.4.so

2ab79cec2000-2ab79cec4000 rw-p 0012a000 fd:03 65547 /lib64/libc-2.4.so

2ab79cec4000-2ab79ceca000 rw-p 2ab79cec4000 00:00 0

2ab79ceca000-2ab79cf86000 r-xp 00000000 fd:07 361182 /usr/lib64/libslang.so.2.0.5

2ab79cf86000-2ab79d086000 ---p 000bc000 fd:07 361182 /usr/lib64/libslang.so.2.0.5

2ab79d086000-2ab79d0a1000 rw-p 000bc000 fd:07 361182 /usr/lib64/libslang.so.2.0.5

2ab79d0a1000-2ab79d0d3000 rw-p 2ab79d0a1000 00:00 0

2ab79d0d3000-2ab79d127000 r-xp 00000000 fd:03 65555 /lib64/libm-2.4.so

2ab79d127000-2ab79d226000 ---p 00054000 fd:03 65555 /lib64/libm-2.4.so

2ab79d226000-2ab79d228000 rw-p 00053000 fd:03 65555 /lib64/libm-2.4.so

2ab79d228000-2ab79d22a000 r-xp 00000000 fd:03 65553 /lib64/libdl-2.4.so

2ab79d22a000-2ab79d32a000 ---p 00002000 fd:03 65553 /lib64/libdl-2.4.so

2ab79d32a000-2ab79d32c000 rw-p 00002000 fd:03 65553 /lib64/libdl-2.4.so

2ab79d32c000-2ab79d32e000 rw-p 2ab79d32c000 00:00 0

2ab79d32e000-2ab79d33b000 r-xp 00000000 fd:03 65626 /lib64/libgcc_s.so.1

2ab79d33b000-2ab79d43a000 ---p 0000d000 fd:03 65626 /lib64/libgcc_s.so.1

2ab79d43a000-2ab79d43b000 rw-p 0000c000 fd:03 65626 /lib64/libgcc_s.so.1

7fff0e140000-7fff0e159000 rw-p 7fff0e140000 00:00 0 [stack]

ffffffffff600000-ffffffffffe00000 ---p 00000000 00:00 0 [vdso]

SIGABRT signal received from OS

Abort - probably failed assertion. I'm sleeping for a few seconds so you can rea

Fatal error... MondoRescue? is terminating in response to a signal from the OS

---FATALERROR--- MondoRescue? is terminating in response to a signal from the OS

If you require technical support, please contact the mailing list.

See http://www.mondorescue.org for details.

The list's members can help you, if you attach that file to your e-mail.

Log file: /var/log/mondoarchive.log

Mondo has aborted.

Execution run ended; result=254

Type 'less /var/log/mondoarchive.log' to see the output log

Attachments (2)

mindi.log (30.4 KB) - added by BIGOURIEE 10 years ago.
Log mindi
Ticket_368.zip (10.5 KB) - added by BIGOURIEE 10 years ago.

Download all attachments as: .zip

Change History (10)

Changed 10 years ago by BIGOURIEE

Log mindi

comment:1 Changed 10 years ago by bruno

  • Milestone changed from 2.2.9.1 to 2.2.10
  • Status changed from new to assigned

comment:2 Changed 10 years ago by bruno

  • Milestone changed from 2.2.10 to 2.2.9.3

Could you check again with 2.2.9.2 if that problem has been solved at least by *excluding* the PV you do not want (this one should work much better). Then hopefully your *vg* inclusion should now work as well, but I've not tested a lot that part myself.

TIA.

comment:3 Changed 10 years ago by bruno

  • Resolution set to worksforme
  • Status changed from assigned to closed

BTW, the inclusion as you describe it is not possible, as there is not such device as /dev/vg00. You should be able to include the mountpoints corresponding to that vg by using -I "/dev/vg00/lv01 /dev/vg00/lv02" e.g.

At least in 2.2.9.3 you shouldn't have any pb with device exclusion anymore. Reopen if not the case.

comment:4 Changed 10 years ago by BIGOURIEE

  • Resolution worksforme deleted
  • Status changed from closed to reopened

Following your response, we applied the solution by excluding filesystem mounted on volume groups different from vg00 using the command:

/usr/sbin/mondoarchive -O -l GRUB -E "$(df | grep /dev | grep -v vg00 | grep -v /boot | awk '{print $1}') /var/lib/ntp/proc" -N -d $hostbkp/$DESTINATION -s 650M -p $PREFIXE -n $NFS_SHARE -S ${MNT_POINT}/${hostbkp}/scratch -T ${MNT_POINT}/${hostbkp}/temp

Unfortunately, the output of df is stored in a variable and when the system stored contains a large number of filesystem (eg: 15 filesystem mounted on vg01 and vg02), the script fails with buffer overflow error.

The command works well when we edit manualy the list of filesystem in the "-E" argument but our goal is to automatically retrieve a list of file system mounted on a volume group different from vg00 with a script in order to exclude them from backup.

Is there no possibility to use the argument "-E" with a file in parameter. This file will contain a list of FS to exclude (idem as the argument "-J")?

comment:5 Changed 10 years ago by bruno

Could you attach your /var/log/mondoarchive.log corresponding to that error please (with option -K 99 added), and also try to run valgrind/gdb on it in order to check where precisely the issue is (as described in http://trac.mondorescue.org/wiki/TroubleShooting#Trouble-Shootingmondo)

Maybe linked to #421 as well.

Could you also try to test the beta of 2.2.9.4 at ftp://ftp.mondorescue.org/test/sles/10 I made to try to improve that issue ?

Changed 10 years ago by BIGOURIEE

comment:6 Changed 10 years ago by BIGOURIEE

You will find attached the results of mondoarchive.log with adding the "-k 99" in the command mondoarchive. Valgrind tool has been inserted in the execution of the command mondoarchive. The log (save_mondo.rtf) is also attached.

I'm doing a test with the beta version 2.2.9.4 and will keep you

Another error was encountered also on the backup of a cluster Oracle

Fatal error ... Your 'E' parameter is Too Long. Increase MAX_STR_LEN --- --- Your FatalError? 'E' parameter is Too Long. Increase MAX_STR_LEN If you require "technical support, please contact the mailing list. See http://www.mondorescue.org for details.

What is the limit for the number of exclusions in the parameter:-E?

comment:7 Changed 9 years ago by bruno

  • Milestone changed from 2.2.9.3 to 2.2.9.5

comment:8 Changed 9 years ago by bruno

  • Resolution set to fixed
  • Status changed from reopened to closed

Fixed as of rev [2709] in 2.2.9.5, backporting dynamic allocation for exclude list from 2.2.10

Note: See TracTickets for help on using tickets.