On Mon, 17 Jan 2005, Theodore Ts'o wrote: > On Mon, Jan 17, 2005 at 04:25:46PM +0100, Walter Hofmann wrote: > > Package: e2fsprogs > > Version: 1.36rc2-1 > > Severity: normal > > > > I'm not sure how severe this is, but I e2fsck'ed a filesystem just after > > resizing it and got some bitmap errors. Below is a screendump of the > > whole session. > > The filesystem is on /dev/loop0 (cryptoloop). > > Can you replicate the problem? And would you be willing to send me > the output of "e2image -r | bzip2", preferably from before the > resize2fs, if you have backups? This will not send me the contents of > any data blocks, but I will see the directory names.
I have a backup, so I could theoretically do as you say. However: I would have to rename the directories. Will renaming all files to random names (of the same length, say) disturb the filesystem structure enough to make the image useless? The filesystem size is 60GB. Even if bzip2 does wonders this will take a while & lots of space. Maybe there are easier ways to find the problem. Would strace'ing or ltrace'ing resize2fs be of any help? Walter -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
