On Fri, 21 Jan 2005, Theodore Ts'o wrote: > I've investigated the file you sent me, and it was very helpful > indeed, thanks. What is going on is that when a filesystem is resized > enough so that we need to move the inode table, we reserve both the > old and new locations of the inode table. However, we aren't > releasing the blocks where the inode table used to be located after > the resize. So this isn't a fatal error, in that it doesn't cause any > data loss; the next e2fsck will release the blocks.
Great that you found this bug! It actually sounds quite harmless, so no more fear for the data :-) Greetings, Walter -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
