From: Folkert van Heusden <folkert@vanheusden.com>
To: Pavel Machek <pavel@suse.cz>
Cc: Theodore Tso <tytso@mit.edu>, Chris Friesen <cfriesen@nortel.com>,
mikulas@artax.karlin.mff.cuni.cz, clock@atrey.karlin.mff.cuni.cz,
kernel list <linux-kernel@vger.kernel.org>,
aviro@redhat.com
Subject: Re: writing file to disk: not as easy as it looks
Date: Mon, 15 Dec 2008 21:08:05 +0100 [thread overview]
Message-ID: <20081215200805.GI7083@vanheusden.com> (raw)
In-Reply-To: <20081215110310.GA10274@elf.ucw.cz>
> > There are certainly things you can do. Put your fileservers's on
> > UPS's. Use RAID. Make backups. Do all three. :-)
>
> Okay, so we pretty much know that ext3 journalling helps in "user hit
> the reset button" case. (And we are pretty sure ext2/ext3 works in
> "clean unmount" case). Otherwise
>
> *) kernel bug -> journalling does not help.
>
> *) sudden powerfail -> journalling helps works on SGI high-end
> hardware. It may or may not help on PC-class hardware.
>
> We already do periodic checks, even on ext3. Maybe we should do fsck
> more often if we see evidence of unclean shutdowns (because we know
> PC hardware is crap...).
What we might need is on-line fsck. E.g. fsck while the fs is still
mounted.
Might be tricky to implement.
Folkert van Heusden
--
MultiTail is a versatile tool for watching logfiles and output of
commands. Filtering, coloring, merging, diff-view, etc.
http://www.vanheusden.com/multitail/
----------------------------------------------------------------------
Phone: +31-6-41278122, PGP-key: 1F28D8AE, www.vanheusden.com
next prev parent reply other threads:[~2008-12-15 20:09 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-02 9:40 writing file to disk: not as easy as it looks Pavel Machek
2008-12-02 14:04 ` Theodore Tso
2008-12-02 15:26 ` Pavel Machek
2008-12-02 16:37 ` Theodore Tso
2008-12-02 17:22 ` Chris Friesen
2008-12-02 20:55 ` Theodore Tso
2008-12-02 22:44 ` Pavel Machek
2008-12-02 22:50 ` Pavel Machek
2008-12-03 5:07 ` Theodore Tso
2008-12-03 8:46 ` Pavel Machek
2008-12-03 15:50 ` Mikulas Patocka
2008-12-03 15:54 ` Alan Cox
2008-12-03 17:37 ` Mikulas Patocka
2008-12-03 17:52 ` Alan Cox
2008-12-03 18:16 ` Pavel Machek
2008-12-03 18:33 ` Mikulas Patocka
2008-12-03 16:42 ` Theodore Tso
2008-12-03 17:43 ` Mikulas Patocka
2008-12-03 18:26 ` Pavel Machek
2008-12-03 15:34 ` Mikulas Patocka
2008-12-15 10:24 ` [patch] " Pavel Machek
2008-12-15 11:03 ` Pavel Machek
2008-12-15 20:08 ` Folkert van Heusden [this message]
2008-12-02 19:10 ` Folkert van Heusden
2008-12-02 23:01 ` Mikulas Patocka
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=20081215200805.GI7083@vanheusden.com \
--to=folkert@vanheusden.com \
--cc=aviro@redhat.com \
--cc=cfriesen@nortel.com \
--cc=clock@atrey.karlin.mff.cuni.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=mikulas@artax.karlin.mff.cuni.cz \
--cc=pavel@suse.cz \
--cc=tytso@mit.edu \
/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.