Re: SUSE 9.1 with ReiserFS: / won't fsck, but is otherwise fine

[Chris Worley <cworley@symbionsys.com>]

On Fri, 2004-09-24 at 07:30, Hendrik Visage wrote:
> 1) Why do you *want* to fsck a reiserfs? Unless you have troubles, then a
> fsck on a reiserfs is not needed by design of a logging/journaling fs

You don't have a choice on the root file system... fsck will be run.

Once booted, I am just running a ro fsck of / (on a rw mounted file
system).

If there's really nothing wrong with the FS, then I'm okay just making a
no-op fsck.reiserfs and leaving it at that... I'm just worried that
something is really wrong with the file system, and I need to fix that. 
As it sits atop an LVM, I want to add a few more partitions to the LVM
and extend the Reiser fs... but I'm paranoid, with this error, to
proceed.

> 2) any fsck needs to be done on a read-only mounted fs, 

Which is the state when fsck is run during boot.  I get the same error
when booting and dropping into fsck mode as I do after the system is
booted.

> and then if
> anything have been fixed, that fs preferably needs to be umounted (see the
> trouble with / already mounted) and mounted again to makesure the caches etc.
> is cleared.

If the Reiser tools would just recognize this as a fs, I'd be satisfied.

Thanks,

Chris