linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Greaves <david@dgreaves.com>
To: David Robinson <zxvdr.au@gmail.com>
Cc: LVM general discussion and development <linux-lvm@redhat.com>,
	"'linux-kernel@vger.kernel.org'" <linux-kernel@vger.kernel.org>,
	xfs@oss.sgi.com, linux-pm <linux-pm@lists.osdl.org>,
	LinuxRaid <linux-raid@vger.kernel.org>
Subject: Re: [linux-lvm] 2.6.22-rc4 XFS fails after hibernate/resume
Date: Mon, 18 Jun 2007 08:49:34 +0100	[thread overview]
Message-ID: <4676390E.6010202@dgreaves.com> (raw)
In-Reply-To: <46751D37.5020608@dgreaves.com>

David Greaves wrote:
> David Robinson wrote:
>> 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.

<snip>

> OK, that gave me an idea.
> 
> Freeze the filesystem
> md5sum the lvm
> hibernate
> resume
> md5sum the lvm
<snip>
> So the lvm and below looks OK...
> 
> I'll see how it behaves now the filesystem has been frozen/thawed over 
> the hibernate...


And it appears to behave well. (A few hours compile/clean cycling kernel builds 
on that filesystem were OK).


Historically I've done:
sync
echo platform > /sys/power/disk
echo disk > /sys/power/state
# resume

and had filesystem corruption (only on this machine, my other hibernating xfs 
machines don't have this problem)

So doing:
xfs_freeze -f /scratch
sync
echo platform > /sys/power/disk
echo disk > /sys/power/state
# resume
xfs_freeze -u /scratch

Works (for now - more usage testing tonight)

David

  reply	other threads:[~2007-06-18  7:49 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 [this message]
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
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=4676390E.6010202@dgreaves.com \
    --to=david@dgreaves.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).