All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andreas Dilger <adilger@turbolabs.com>
To: Ryan Mack <rmack@mackman.net>
Cc: linux-kernel@vger.kernel.org, ext2-devel@lists.sourceforge.net
Subject: Re: [Ext2-devel] [BUG?] ext3 0.9.10-2410 - root partition never marked dirty
Date: Mon, 24 Sep 2001 15:32:16 -0600	[thread overview]
Message-ID: <20010924153216.H14526@turbolinux.com> (raw)
In-Reply-To: <Pine.LNX.4.33.0109241409490.990-100000@mackman.net>
In-Reply-To: <Pine.LNX.4.33.0109241409490.990-100000@mackman.net>

On Sep 24, 2001  14:15 -0700, Ryan Mack wrote:
> It seems that the aforementioned changes in 2.4.10 has prevented the root
> filesystem from having its superblock updated as dirty.  It may be my
> imagination, but since the root fs is already mounted ro when it's
> remounted rw, the superblock isn't being updated with the needs_recovery
> flag.

OK, it's not exactly clear what you are referring to, but:
1) On ext3 the superblock is NEVER marked dirty, because of the journal.
   As long as the journal is running normally, the filesystem will always
   be "clean".
2) There should _not_ be a problem with the needs_recovery flag being set
   from within the kernel.  HOWEVER, attempts to read it from user-space
   may fail because of a disconnect between the buffer cache and the page
   cache.

Now that these issues are in the open (and already being discussed) they
will likely be fixed in a relatively short timeframe.

Cheers, Andreas
--
Andreas Dilger  \ "If a man ate a pound of pasta and a pound of antipasto,
                 \  would they cancel out, leaving him still hungry?"
http://www-mddsp.enel.ucalgary.ca/People/adilger/               -- Dogbert


  reply	other threads:[~2001-09-24 21:32 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-09-24 21:15 [BUG?] ext3 0.9.10-2410 - root partition never marked dirty Ryan Mack
2001-09-24 21:32 ` Andreas Dilger [this message]
2001-09-24 21:40 ` [BUG?] ext3 0.9.10-2410 - assertion failed Ryan Mack
2001-09-26 16:14   ` Stephen C. Tweedie

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=20010924153216.H14526@turbolinux.com \
    --to=adilger@turbolabs.com \
    --cc=ext2-devel@lists.sourceforge.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rmack@mackman.net \
    /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.