| |||||||||||||
|
| |||||||||||||
Filesystems (ext3, reiser, xfs, jfs) comparison on Debian Etch (DebianFilesystems (ext3, reiser, xfs, jfs) comparison on Debian Etch (DebianPosted Apr 27, 2006 13:08 UTC (Thu) by erich (subscriber, #7127)In reply to: Filesystems (ext3, reiser, xfs, jfs) comparison on Debian Etch (Debian by dmantione Parent article: Filesystems (ext3, reiser, xfs, jfs) comparison on Debian Etch (Debian Administration)
--rebuild-tree didn't work for me, and reiserfsck made things actually _worse_. It's crap. Or it was back then, when I stopped using reiserfs.
(Log in to post comments)
Filesystems (ext3, reiser, xfs, jfs) comparison on Debian Etch (Debian Posted Apr 27, 2006 13:54 UTC (Thu) by dmantione (guest, #4640) [Link] Yes, --rebuild-tree rebuilds the entire filesystem, so if it fails thefilesystem is not accessible because the old tree is no longer available. This situation remains until a successfull rebuild has been done, so investigate what the cause of the failure is and try again.
Filesystems (ext3, reiser, xfs, jfs) comparison on Debian Etch (Debian Posted Apr 29, 2006 10:56 UTC (Sat) by nix (subscriber, #2304) [Link] This is, of course, an extremely... peculiar design. The robust approach would be to build a new tree in parallel with the old (as long as space was available and the old tree was undamaged enough to determine which blocks were free), then switch over to the old atomically.
This is harder, but it does make the thing fail-safe.
|
|
||||||||||||