From: Christoph Hellwig <hch@infradead.org>
To: Daniel Pittman <daniel@rimspace.net>
Cc: Henrique de Moraes Holschuh <hmh@hmh.eng.br>,
"Rafael J. Wysocki" <rjw@sisk.pl>,
linux-pm@lists.linux-foundation.org,
Maxim Levitsky <maximlevitsky@gmail.com>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [linux-pm] Massive ext4 filesystem corruption after a failed s2disk/ram cycle
Date: Wed, 7 Oct 2009 12:16:04 -0400 [thread overview]
Message-ID: <20091007161604.GA28849@infradead.org> (raw)
In-Reply-To: <87vdisq7bh.fsf@rimspace.net>
On Wed, Oct 07, 2009 at 01:14:10PM +1100, Daniel Pittman wrote:
> For what it is worth, I would also be quite interested to know /why/ XFS is
> bad in this regard. Is it just the previously stated "XFS writes to disk
> despite freezing kernel threads" issue, or something deeper?
sync pushes out all data to disk, but in a journaling filesystem that
might just but the log not the "normal" place on disk. For a boot
loader to deal with it properly it actually needs to do an replay of
the log. Grub does so for reiserfs but not for XFS for some reason.
I don't know why problems don't trigger more often with ext3, though.
next prev parent reply other threads:[~2009-10-07 16:16 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-06 21:06 Massive ext4 filesystem corruption after a failed s2disk/ram cycle Maxim Levitsky
2009-10-06 21:42 ` Theodore Tso
2009-10-06 23:02 ` Maxim Levitsky
2009-10-07 14:25 ` Jindrich Makovicka
2009-10-06 21:58 ` [linux-pm] " Rafael J. Wysocki
2009-10-06 22:53 ` Henrique de Moraes Holschuh
2009-10-06 23:02 ` Rafael J. Wysocki
2009-10-07 1:29 ` Henrique de Moraes Holschuh
2009-10-07 2:14 ` Daniel Pittman
2009-10-07 16:16 ` Christoph Hellwig [this message]
2009-11-04 2:18 ` KOSAKI Motohiro
2009-11-05 9:56 ` Henrique de Moraes Holschuh
2009-11-07 22:22 ` Thomas Fjellstrom
2009-11-08 8:29 ` Dave Chinner
2009-11-08 16:49 ` Christoph Hellwig
2009-11-09 9:42 ` Henrique de Moraes Holschuh
2009-10-10 3:26 ` ext4 filesystem corruption Maxim Levitsky
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=20091007161604.GA28849@infradead.org \
--to=hch@infradead.org \
--cc=daniel@rimspace.net \
--cc=hmh@hmh.eng.br \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@lists.linux-foundation.org \
--cc=maximlevitsky@gmail.com \
--cc=rjw@sisk.pl \
/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