[Dump-users] dump data from a corrupted ext3 volume

[Dragan K. <dk...@ly...>]

I am trying to salvage data from an unlucky volume.
<br>The dump utility starts with following messages:
<br>
<br>  DUMP: Date of this level 0 dump: Wed Jan 10 18:07:37 2007
<br>  DUMP: Dumping /dev/sdl (/disc) to standard output
<br>  DUMP: Excluding inode 7 (resize inode) from dump
<br>  DUMP: Label: none
<br>  DUMP: Writing 64 Kilobyte records
<br>  DUMP: mapping (Pass I) [regular files]
<br>
<br>and then after about two and a half minutes it says
<br>
<br>/dev/sdl: Can't read next inode while scanning inode #2342912
<br>
<br>The volume was quite big, 3.5 TB, but it was only about 1.2 TB
<br>full. The dump utility apparently finds more than 2 million
<br>inodes but unfortunately it breaks with the above message
<br>before actually dumping any data.
<br>
<br>Is there some version of dump which would ignore such errors
<br>and just try to make sense out of the remaining sound data,
<br>even if there are corrupted chunks in between?
<br>
<br>Do you have some other suggestion, how to salvage as much 
<br>data as possible (e2fsck has even less patience with it)?
<br>
<br>Regards
<br>Dragan