From: Tejun Heo <htejun@gmail.com>
To: Andrew Robinson <andrew.rw.robinson@gmail.com>
Cc: 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: Wed, 13 Dec 2006 17:37:48 +0900 [thread overview]
Message-ID: <457FBBDC.9050608@gmail.com> (raw)
In-Reply-To: <bc36a6210612121044vf259b34u4ec3cac4df56e43c@mail.gmail.com>
Andrew Robinson wrote:
> When I said hibernate, I did mention it was to disk, not to ram. I
> woke my computer up from work remotely using wakeonlan. When the
> computer was responsive, I started getting I/O errors and when I saw
> my kernel log I saw file corruption problems with my "/dev/sda2"
> device (which is my root file system and is one of two, the other is
> the swap partition)
sata_nv is just now receiving suspend/resume support in devel tree.
2.6.19 sata_nv doesn't have it and STD might have worked but I wouldn't
be surprised if it doesn't work from time to time or gets broken due to
unrelated changes in kernel. So, IO errors after STD are bad but kind
of expected. I dunno what went wrong with your fs after such IO errors.
Destroyed fs after some IO errors is pretty extreme tho.
So, my 5 cents is... don't do hibernation till 2.6.20 is out.
--
tejun
prev parent reply other threads:[~2006-12-13 13:01 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-12 18:44 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) 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
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 ` Tejun Heo [this message]
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=457FBBDC.9050608@gmail.com \
--to=htejun@gmail.com \
--cc=andrew.rw.robinson@gmail.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