From: Chris Worley <cworley@symbionsys.com>
To: Hendrik Visage <hvisage@envisage.co.za>
Cc: reiserfs-list@namesys.com
Subject: Re: SUSE 9.1 with ReiserFS: / won't fsck, but is otherwise fine
Date: Fri, 24 Sep 2004 08:58:41 -0600 [thread overview]
Message-ID: <1096037921.17001.20.camel@xserver.local.net> (raw)
In-Reply-To: <20040924143210.GG1617@hvs.envisage.co.za>
On Fri, 2004-09-24 at 08:32, Hendrik Visage wrote:
> On Fri, Sep 24, 2004 at 07:56:31AM -0600, Chris Worley wrote:
> > 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.
>
> Then ignore it for a reiserfs...
>
> > 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.
>
> First understand a logging/journaling fs :)
I do understand a journaling fs, and have used Reiser for many years.
My understanding of journaling fs's is not the problem. There was a
time when this fs properly fsck'd at boot, and then a time when it
didn't. This is a problem. Furthermore, SuSE would not have forced the
fsck (irrespective of the fstab settings) of the root fs if it didn't
apply to Reiser.
Please re-read my original email, as I don't think you understand the
situation.
Thanks,
Chris
next prev parent reply other threads:[~2004-09-24 14:58 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-24 3:20 SUSE 9.1 with ReiserFS: / won't fsck, but is otherwise fine Chris Worley
2004-09-24 7:17 ` Vitaly Fertman
2004-09-24 13:20 ` Chris Worley
2004-09-24 13:30 ` Hendrik Visage
2004-09-24 13:56 ` Chris Worley
2004-09-24 14:32 ` Hendrik Visage
2004-09-24 14:58 ` Chris Worley [this message]
2004-09-27 14:44 ` Vitaly Fertman
2004-09-27 16:06 ` Chris Worley
2004-09-27 22:16 ` evilninja
2004-09-27 22:40 ` Chris Worley
2004-09-29 0:38 ` evilninja
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1096037921.17001.20.camel@xserver.local.net \
--to=cworley@symbionsys.com \
--cc=hvisage@envisage.co.za \
--cc=reiserfs-list@namesys.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.