From: Tejun Heo <htejun@gmail.com>
To: David Greaves <david@dgreaves.com>
Cc: David Chinner <dgc@sgi.com>, linux-pm <linux-pm@lists.osdl.org>,
"'linux-kernel@vger.kernel.org'" <linux-kernel@vger.kernel.org>,
xfs@oss.sgi.com, LinuxRaid <linux-raid@vger.kernel.org>,
LVM general discussion and development <linux-lvm@redhat.com>,
David Robinson <zxvdr.au@gmail.com>
Subject: Re: [linux-lvm] 2.6.22-rc5 XFS fails after hibernate/resume
Date: Tue, 19 Jun 2007 18:44:54 +0900 [thread overview]
Message-ID: <4677A596.7090404@gmail.com> (raw)
In-Reply-To: <4677A0C7.4000306@dgreaves.com>
Hello,
David Greaves wrote:
>> Good :)
> Now, not so good :)
Oh, crap. :-)
> So I hibernated last night and resumed this morning.
> Before hibernating I froze and sync'ed. After resume I thawed it. (Sorry
> Dave)
>
> Here are some photos of the screen during resume. This is not 100%
> reproducable - it seems to occur only if the system is shutdown for
> 30mins or so.
>
> Tejun, I wonder if error handling during resume is problematic? I got
> the same errors in 2.6.21. I have never seen these (or any other libata)
> errors other than during resume.
>
> http://www.dgreaves.com/pub/2.6.22-rc5-resume-failure.jpg
> (hard to read, here's one from 2.6.21
> http://www.dgreaves.com/pub/2.6.21-resume-failure.jpg
Your controller is repeatedly reporting PHY readiness changed exception.
Are you reading the system image from the device attached to the first
SATA port?
> I _think_ I've only seen the xfs problem when a resume shows these errors.
The error handling itself tries very hard to ensure that there is no
data corruption in case of errors. All commands which experience
exceptions are retried but if the drive itself is doing something
stupid, there's only so much the driver can do.
How reproducible is the problem? Does the problem go away or occur more
often if you change the drive you write the memory image to?
--
tejun
next prev parent reply other threads:[~2007-06-19 9:44 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <46744065.6060605@dgreaves.com>
[not found] ` <4674645F.5000906@gmail.com>
2007-06-17 11:38 ` [linux-lvm] 2.6.22-rc4 XFS fails after hibernate/resume David Greaves
2007-06-18 7:49 ` David Greaves
2007-06-18 14:50 ` David Chinner
2007-06-18 19:14 ` David Greaves
2007-06-19 9:24 ` [linux-lvm] 2.6.22-rc5 " David Greaves
2007-06-19 9:44 ` Tejun Heo [this message]
2007-06-19 14:13 ` David Greaves
2007-06-20 8:03 ` Tejun Heo
2007-06-21 18:06 ` David Greaves
2007-06-29 8:20 ` David Greaves
2007-07-02 10:56 ` Tejun Heo
2007-07-02 14:08 ` Rafael J. Wysocki
2007-07-02 14:32 ` David Greaves
2007-07-02 15:12 ` Rafael J. Wysocki
2007-07-02 16:36 ` David Greaves
2007-07-02 20:15 ` Rafael J. Wysocki
2007-06-19 11:21 ` Rafael J. Wysocki
2007-06-19 15:31 ` David Greaves
2007-06-20 0:18 ` David Chinner
2007-06-27 20:49 ` [linux-lvm] 2.6.22-rc4 " Pavel Machek
2007-06-28 15:27 ` Rafael J. Wysocki
2007-06-28 22:00 ` [linux-pm] " Pavel Machek
2007-06-28 22:16 ` Rafael J. Wysocki
2007-06-29 5:00 ` David Chinner
2007-06-29 7:40 ` David Greaves
2007-06-29 7:43 ` David Chinner
2007-06-29 7:54 ` David Greaves
2007-06-29 13:18 ` Rafael J. Wysocki
2007-06-29 13:30 ` David Greaves
2007-06-29 4:55 ` David Chinner
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=4677A596.7090404@gmail.com \
--to=htejun@gmail.com \
--cc=david@dgreaves.com \
--cc=dgc@sgi.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-lvm@redhat.com \
--cc=linux-pm@lists.osdl.org \
--cc=linux-raid@vger.kernel.org \
--cc=xfs@oss.sgi.com \
--cc=zxvdr.au@gmail.com \
/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;
as well as URLs for NNTP newsgroup(s).