From: "Theodore Ts'o" <tytso@mit.edu>
To: Andi Kleen <ak@muc.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: New concept of ext3 disk checks
Date: Thu, 12 Aug 2004 19:48:57 -0400 [thread overview]
Message-ID: <20040812234857.GA8098@thunk.org> (raw)
In-Reply-To: <m3acx0szwu.fsf@averell.firstfloor.org>
On Fri, Aug 13, 2004 at 01:24:33AM +0200, Andi Kleen wrote:
> Theodore Ts'o <tytso@mit.edu> writes:
>
> > 4) If there were no errors detecting by the fsck run, run the command
> > "tune2fs -C 0 -T now /dev/XXX" on the live filesystem. This sets the
> > mount count and last filesystem checked time to the appropriate values
> > in the superblock.
>
> Is it safe now to run tune2fs on a mounted busy fs? afaik it would
> need at least support to quiescence the fs temporarily. Otherwise you
> have a race window where changes to the superblock could get lost.
Modern versions of e2fsprogs do byte-level writes only to the fields
that are being changed by the userspace program; given that these are
fields that are not touched by the kernel once the filesystem is
mounted, this is safe.
- Ted
next prev parent reply other threads:[~2004-08-12 23:49 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <2ssbz-jB-1@gated-at.bofh.it>
[not found] ` <2swyz-3ny-13@gated-at.bofh.it>
2004-08-12 23:24 ` New concept of ext3 disk checks Andi Kleen
2004-08-12 23:48 ` Theodore Ts'o [this message]
2004-08-12 17:58 Otto Wyss
2004-08-12 18:58 ` Bernd Eckenfels
2004-08-12 21:07 ` Lee Revell
2004-08-12 19:46 ` Alan Cox
2004-08-14 7:26 ` Otto Wyss
2004-08-12 22:39 ` Theodore Ts'o
2004-08-12 23:55 ` Bernd Eckenfels
2004-08-13 0:34 ` Andreas Dilger
2004-08-14 7:15 ` Otto Wyss
2004-08-15 0:23 ` Andreas Dilger
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=20040812234857.GA8098@thunk.org \
--to=tytso@mit.edu \
--cc=ak@muc.de \
--cc=linux-kernel@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.