On Monday 05 January 2009 13:16:58 Theodore Tso wrote: > On Sun, Jan 04, 2009 at 01:56:32PM -0600, Rob Landley wrote: > > On Saturday 03 January 2009 17:01:58 Martin MOKREJŠ wrote: > > > > Still handy for recovering badly broken filesystems, I'd say. > > > > > > Me as well. How about improving you doc patch with some summary of > > > this thread (although it is probably not over yet)? ;-) Definitely, > > > a note that one can mount it as ext2 while read-only would be helpful > > > when doing some forensics on the disk. > > > > Although make sure you _do_ mount it as read only because if you mount an > > ext3 filesystem read/write as ext2 I've had it zap the journal entirely > > and then you have to tune2fs -j the sucker to turn it back into ext3. > > > > Ext3 is... touchy. > > Um.... horse pucky: Well I managed to kill it more than once, but I could easily have the reproduction sequence wrong. (I wasn't _trying_ to do it again...) > # mke2fs -q -t ext3 /dev/thunk/footest > # debugfs -R features /dev/thunk/footest > debugfs 1.41.3 (12-Oct-2008) > Filesystem features: has_journal ext_attr resize_inode dir_index filetype > sparse_super large_file # mount -t ext2 /dev/thunk/footest /mnt > # touch /mnt/foo > # umount /mnt > # debugfs -R features /dev/thunk/footest > debugfs 1.41.3 (12-Oct-2008) > Filesystem features: has_journal ext_attr resize_inode dir_index filetype > sparse_super large_file If I can figure out what I did, I'll get back to you. > - Ted Rob -- To unsubscribe from this list: send the line "unsubscribe linux-doc" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html