[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: dump (for extX) broken in latest release? 0.4b44-1



On 17/07/11 21:00, Justin Piszcz wrote:
Hi,

Re-sending to correct list, per Mike:

I've been using dump for ~1-2+ years now and the syntax has not changed;
however, with the most recent update:

From: 0.4b43-1
To: 0.4b44-1

Dump no longer has the same behavior:

dump -0 -z9 -L 2011-07-16 -f file.ext4dump /
DUMP: Date of this level 0 dump: Sat Jul 16 05:57:02 2011
DUMP: Dumping /dev/sda2 (/) to file.ext4dump
DUMP: Label: 2011-07-16
DUMP: Writing 10 Kilobyte records
DUMP: Compressing output at compression level 9 (zlib)
DUMP: mapping (Pass I) [regular files]
DUMP: mapping (Pass II) [directories]
DUMP: estimated 92870566 blocks.
DUMP: Volume 1 started with block 1 at: Sat Jul 16 05:57:07 2011
DUMP: dumping (Pass III) [directories]
DUMP: dumping (Pass IV) [regular files]
DUMP: Rewriting attempted as response to unknown signal: 8.
DUMP: Closing file.ext4dump
DUMP: Volume 1 completed at: Sat Jul 16 05:57:10 2011
DUMP: Volume 1 took 0:00:03
DUMP: Volume 1 transfer rate: 2623 kB/s
DUMP: Volume 1 63945kB uncompressed, 7871kB compressed, 8.125:1
DUMP: Change Volumes: Mount volume #2
DUMP: Is the new volume mounted and ready to go?: ("yes" or "no")

In the past, I was never prompted for any input during a backup, and now,
it sems to be in an endless loop:

DUMP: Is the new volume mounted and ready to go?: ("yes" or "no") yes
DUMP: Volume 1 started with block 1 at: Sat Jul 16 05:57:07 2011
DUMP: dumping (Pass III) [directories]
DUMP: dumping (Pass IV) [regular files]
DUMP: Rewriting attempted as response to unknown signal: 8.
DUMP: Closing file.ext4dump
DUMP: Volume 1 completed at: Sat Jul 16 05:57:59 2011
DUMP: Volume 1 took 0:00:52
DUMP: Volume 1 transfer rate: 151 kB/s
DUMP: Volume 1 63945kB uncompressed, 7871kB compressed, 8.125:1
DUMP: Change Volumes: Mount volume #2
DUMP: Is the new volume mounted and ready to go?: ("yes" or "no") yes
DUMP: Volume 1 started with block 1 at: Sat Jul 16 05:57:07 2011
DUMP: dumping (Pass III) [directories]
DUMP: dumping (Pass IV) [regular files]
DUMP: Rewriting attempted as response to unknown signal: 8.
DUMP: Closing file.ext4dump
DUMP: Volume 1 completed at: Sat Jul 16 05:58:02 2011
DUMP: Volume 1 took 0:00:55
DUMP: Volume 1 transfer rate: 143 kB/s
DUMP: Volume 1 63945kB uncompressed, 7871kB compressed, 8.125:1
DUMP: Change Volumes: Mount volume #2
DUMP: Is the new volume mounted and ready to go?: ("yes" or "no")

Has anyone seen this? Is there a notification list for when critical
utilities (e.g. backups) break, I'd consider this pretty serious if someone
had ran a apt-get upgrade and then have his/her system fail afterwards, not
being able to recover would be a problem.

This occurs on any system with dump 0.4b44-1, on my older systems (not
upgraded yet), dump works fine: 0.4b43-1.

I have already submitted a bug report for this. It seems to have been caused by the latest update of e2fslibs. If you downgrade e2fslibs to 1.41.12-4stable1 dump will work again. You should also downgrade e2fsprogs, libcomerr2 and libss2.

Dom


Reply to: