From: Christoph Hellwig <hch@infradead.org>
To: Dave Chinner <david@fromorbit.com>
Cc: KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>,
Christoph Hellwig <hch@infradead.org>,
Daniel Pittman <daniel@rimspace.net>,
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: Sun, 8 Nov 2009 11:49:13 -0500 [thread overview]
Message-ID: <20091108164913.GA12053@infradead.org> (raw)
In-Reply-To: <20091108082905.GA25494@discord.disaster>
On Sun, Nov 08, 2009 at 07:29:05PM +1100, Dave Chinner wrote:
> We already have an ioctl that does what you want: FIFREEZE.
Doesn't really help as there is not guarentee important metadata is
modified again before the bootloader accesses it, but that's a fate
share with any other kind of super sync. The only way to really fix
the problem is to implement proper (in-memory) log recovery in the
bootloader, especially as it doesn't only have to deal with the
relatively easy case of clean shutdowns but also needs to deal with the
case of an unclean shutdown with major amounts of updates to the lookup
and allocation data structures in the log.
IMHO the best option is to have a separate partition for /boot with a
very simple filesystem that we can expect boot loader developers to
implement fully and correctly.
next prev parent reply other threads:[~2009-11-08 16:49 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
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 [this message]
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=20091108164913.GA12053@infradead.org \
--to=hch@infradead.org \
--cc=daniel@rimspace.net \
--cc=david@fromorbit.com \
--cc=hmh@hmh.eng.br \
--cc=kosaki.motohiro@jp.fujitsu.com \
--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