From: Pavel Machek <pavel@suse.cz>
To: Olivier Galibert <galibert@pobox.com>,
Andrew Robinson <andrew.rw.robinson@gmail.com>,
linux-kernel@vger.kernel.org
Subject: Re: ReiserFS corruption with 2.6.19 (Was 2.6.19 is not stable with SATA and should not be used by any meansis not stable with SATA and should not be used by any means)
Date: Fri, 15 Dec 2006 16:15:45 +0000 [thread overview]
Message-ID: <20061215161544.GC4551@ucw.cz> (raw)
In-Reply-To: <20061212224527.GA4045@dspnet.fr.eu.org>
On Tue 12-12-06 23:45:27, Olivier Galibert wrote:
> On Tue, Dec 12, 2006 at 11:44:18AM -0700, Andrew Robinson wrote:
> > When I said hibernate, I did mention it was to disk, not to ram.
>
> Suspend to disk is not trustable on Linux, and does not look like it
> will be any time soon. Suspend to ram has a better chance of becoming
Stop spreading fud. Take powersave + suspend from suse10.2, and see
if you can break it.
sata_nv seems to have problem, that's it. and it triggered problem in
reiserfs. Use ext3 if you care about your data, and yes your drivers
need to support suspend/resume.
Pavel
--
Thanks for all the (sleeping) penguins.
next prev parent reply other threads:[~2006-12-16 7:50 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-12 18:44 Andrew Robinson
2006-12-12 19:28 ` Phillip Susi
2006-12-12 20:22 ` Jeff V. Merkey
2006-12-12 22:27 ` Phillip Susi
2006-12-12 22:16 ` Jeff V. Merkey
2006-12-12 22:45 ` Olivier Galibert
2006-12-15 16:15 ` Pavel Machek [this message]
2006-12-16 9:07 ` Jeffrey V. Merkey
2006-12-22 20:34 ` suspend to disk (was Re: ReiserFS corruption with 2.6.19 (Was 2.6.19 is not stable with SATA and should not be used by any meansis not stable with SATA and should not be used by any means)) Pavel Machek
2006-12-13 8:37 ` ReiserFS corruption with 2.6.19 (Was 2.6.19 is not stable with SATA and should not be used by any meansis not stable with SATA and should not be used by any means) Tejun Heo
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=20061215161544.GC4551@ucw.cz \
--to=pavel@suse.cz \
--cc=andrew.rw.robinson@gmail.com \
--cc=galibert@pobox.com \
--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
Powered by JetHome