From: Daniel Pittman <daniel@rimspace.net>
To: linux-kernel@vger.kernel.org
Subject: Re: EXT intent logging
Date: Fri, 06 Aug 2004 19:57:54 +1000 [thread overview]
Message-ID: <87zn58lhb1.fsf@enki.rimspace.net> (raw)
In-Reply-To: S268081AbUHFEzL/20040806045511Z+197@vger.kernel.org
On 6 Aug 2004, Buddy Lumpkin wrote:
> I recently moved from a Sun/Solaris environment to a mostly linux environment
>
> A large NFS server went down recently and as it rebooted, fsck ran for
> a while before the data volumes could be mounted. I noticed the
> filesystem was ext3 and asked, is journaling disabled? Why on earth is
> fsck running at all? The admin assured me this is quite normal for
> ext3 and after a few minutes, the system was brought back online.
What is normal is that ext3 will perform an *occasional* fsck - by
default, once a month or every thirty-odd mounts - to catch any
corruption that has been missed by the journaling.
Also, the fsck will replay the journal outside the kernel if possible,
so you may have witnessed the journal replay.
This is done because it allows multiple filesystems to replay the
journal in parallel rather than sequentially as doing it in-kernel would
require.
Regards,
Daniel
--
If you ever reach total enlightenment while you're drinking a beer,
I bet it makes beer shoot out your nose.
-- Jack Handy
next prev parent reply other threads:[~2004-08-06 10:10 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-06 4:55 EXT intent logging Buddy Lumpkin
2004-08-06 9:57 ` Daniel Pittman [this message]
2004-08-06 13:22 ` Doug McNaught
2004-08-06 16:36 ` Buddy Lumpkin
2004-08-06 18:46 ` Bernd Eckenfels
2004-08-06 19:56 ` Theodore Ts'o
2004-08-07 4:50 ` Buddy Lumpkin
2004-08-08 1:54 ` Thomas Zimmerman
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=87zn58lhb1.fsf@enki.rimspace.net \
--to=daniel@rimspace.net \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox