All of lore.kernel.org
 help / color / mirror / Atom feed
From: Anders Aagaard <aagaande@gmail.com>
To: Alexander Lyamin <flx@Msu.ru>
Cc: reiserfs-devel@vger.kernel.org
Subject: Re: Correct fsck behavior on boot
Date: Thu, 11 Sep 2008 14:21:11 +0200	[thread overview]
Message-ID: <48C90D37.1060201@gmail.com> (raw)
In-Reply-To: <80294dc60809110450i20d43214o144b754b33713f48@mail.gmail.com>

Alexander Lyamin wrote:
> Why one have to worry about cleanness   of a  _journaled_ fs ?
> Its seems like immediate return on -a is intended behavior.

I suspect it is, I'm just making sure I have something to fire back with 
when a gentoo developer complains about my patch here:

http://bugs.gentoo.org/show_bug.cgi?id=237393

> 
> On Thu, Sep 11, 2008 at 3:26 PM, Anders Aagaard <aagaande@gmail.com 
> <mailto:aagaande@gmail.com>> wrote:
> 
>     Hi
> 
>     What's the correct options to pass to reiser4.fsck on boot to get it
>     to check the filesystem when it's not marked as clean?
> 
>     reiser4 fsck does implement -a, but it seems to return right away,
>     including when the filesystem wasn't unmounted cleanly.  Is the
>     filesystem integrity still secured by hash'es, so skipping fsck is
>     intentional?
>     --check --fix seems a tad bit excessive on every boot.
> 
>     Anders Aagaard
> 
> 
> 
> -- 
> connecting the dots


  parent reply	other threads:[~2008-09-11 12:21 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-09-11 11:26 Correct fsck behavior on boot Anders Aagaard
     [not found] ` <80294dc60809110450i20d43214o144b754b33713f48@mail.gmail.com>
2008-09-11 12:21   ` Anders Aagaard [this message]
     [not found]     ` <80294dc60809110523t3009e87bx9f2c2cb5f88aaebc@mail.gmail.com>
2008-09-11 12:53       ` Anders Aagaard
2008-10-13 12:11     ` Edward Shishkin

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=48C90D37.1060201@gmail.com \
    --to=aagaande@gmail.com \
    --cc=flx@Msu.ru \
    --cc=reiserfs-devel@vger.kernel.org \
    /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.