From: David Robinson <zxvdr.au@gmail.com>
To: LVM general discussion and development <linux-lvm@redhat.com>
Cc: linux-pm <linux-pm@lists.osdl.org>,
"'linux-kernel@vger.kernel.org'" <linux-kernel@vger.kernel.org>,
xfs@oss.sgi.com
Subject: Re: [linux-lvm] 2.6.22-rc4 XFS fails after hibernate/resume
Date: Sun, 17 Jun 2007 08:29:51 +1000 [thread overview]
Message-ID: <4674645F.5000906@gmail.com> (raw)
In-Reply-To: <46744065.6060605@dgreaves.com>
David Greaves wrote:
> This isn't a regression.
>
> I was seeing these problems on 2.6.21 (but 22 was in -rc so I waited to
> try it).
> I tried 2.6.22-rc4 (with Tejun's patches) to see if it had improved - no.
>
> Note this is a different (desktop) machine to that involved my recent bugs.
>
> The machine will work for days (continually powered up) without a
> problem and then exhibits a filesystem failure within minutes of a resume.
>
> I know xfs/raid are OK with hibernate. Is lvm?
I have LVM working with hibernate w/o any problems (w/ ext3). If there
were a problem it wouldn't be with LVM but with device-mapper, and I
doubt there's a problem with either. The stack trace shows that you're
within XFS code (but it's likely its hibernate).
You can easily check whether its LVM/device-mapper:
1) check "dmsetup table" - it should be the same before hibernating and
after resuming.
2) read directly from the LV - ie, "dd if=/dev/mapper/video_vg-video_lv
of=/dev/null bs=10M count=200".
If dmsetup shows the same info and you can read directly from the LV I
doubt it would be a LVM/device-mapper problem.
Cheers,
Dave
next prev parent reply other threads:[~2007-06-16 22:29 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-16 19:56 [linux-lvm] 2.6.22-rc4 XFS fails after hibernate/resume David Greaves
2007-06-16 22:29 ` David Robinson [this message]
2007-06-17 11:38 ` David Greaves
2007-06-18 7:49 ` David Greaves
[not found] ` <20070618145007.GE85884050@sgi.com>
2007-06-18 19:14 ` David Greaves
[not found] ` <200706170047.20559.rjw@sisk.pl>
2007-06-17 11:37 ` [linux-lvm] " David Greaves
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=4674645F.5000906@gmail.com \
--to=zxvdr.au@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-lvm@redhat.com \
--cc=linux-pm@lists.osdl.org \
--cc=xfs@oss.sgi.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).