Opened 6 years ago

Closed 6 years ago

#683 closed defect (fixed)

SIGSEGV on mondoarchive

Reported by: petr.balas Owned by: bruno
Priority: normal Milestone: 3.0.4
Component: mondo Version: 3.0.3
Severity: normal Keywords:
Cc:

Description

kerio:/usr/local/sbin# mondoarchive -Oi -9 -N -l LILO -E "/tmp|/proc|/sys|/_archive|/mnt/mnt|/var/cache/apt/archives|/home/_kerio/store|/opt/kerio|/home/_encryped" -s 4200m -d /_archive/kerio.bor-sro.cz-2013-05-15/

Initializing...

Execution run ended; result=-1

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

Neoprávněný přístup do paměti (SIGSEGV)

Debian 6.0.7 - packages from "deb ftp://ftp.mondorescue.org/debian 6.0 contrib"

kerio:/usr/local/sbin# cat /var/log/mondoarchive.log

[TH=10088] libmondo-tools.c->reset_bkpinfo#785: Hi root is mounted at /dev/md0

No, Schlomo, that doesn't mean /dev/md0 is the root partition. It's just a debugging message. Relax. It's part of am_I_in_disaster_recovery_mode(). [TH=10088] libmondo-devices.c->am_I_in_disaster_recovery_mode#166: Is this a ramdisk? result = 0

[TH=10088] libmondo-tools.c->setup_tmpdir#769: Failed to create global tmp directory for Mondo.

running: umount -d /mnt/cdrom > /mondo-run-prog-thing.tmp 2> /mondo-run-prog-thing.err


umount: /mnt/cdrom: not mounted


...ran with res=256

Change History (2)

comment:1 Changed 6 years ago by bruno

  • Status changed from new to assigned

What happens if you use the -T option to force the temp dir ?

Could you also please test the beta of mondo 3.0.4 later this week-end as it should fix this issue.

comment:2 Changed 6 years ago by bruno

  • Milestone changed from 3.0.5 to 3.0.4
  • Resolution set to fixed
  • Status changed from assigned to closed

Should be fixed with latest 3.0.4 as all the tmp management was reviewed and improved. Please reopen if not the case.

Note: See TracTickets for help on using tickets.