| To: | "Rafael J. Wysocki" <rjw@xxxxxxx> |
|---|---|
| Subject: | Re: [linux-pm] Re: [linux-lvm] 2.6.22-rc4 XFS fails after hibernate/resume |
| From: | David Chinner <dgc@xxxxxxx> |
| Date: | Fri, 29 Jun 2007 15:00:24 +1000 |
| Cc: | Pavel Machek <pavel@xxxxxx>, David Chinner <dgc@xxxxxxx>, linux-pm <linux-pm@xxxxxxxxxxxxxx>, "'linux-kernel@xxxxxxxxxxxxxxx'" <linux-kernel@xxxxxxxxxxxxxxx>, xfs@xxxxxxxxxxx, LinuxRaid <linux-raid@xxxxxxxxxxxxxxx>, LVM general discussion and development <linux-lvm@xxxxxxxxxx>, David Robinson <zxvdr.au@xxxxxxxxx>, David Greaves <david@xxxxxxxxxxxx>, Oleg Nesterov <oleg@xxxxxxxxxx> |
| In-reply-to: | <200706290016.45719.rjw@sisk.pl> |
| References: | <46744065.6060605@dgreaves.com> <200706281727.35430.rjw@sisk.pl> <20070628220045.GA4521@elf.ucw.cz> <200706290016.45719.rjw@sisk.pl> |
| Sender: | xfs-bounce@xxxxxxxxxxx |
| User-agent: | Mutt/1.4.2.1i |
On Fri, Jun 29, 2007 at 12:16:44AM +0200, Rafael J. Wysocki wrote: > There are two solutions possible, IMO. One would be to make these workqueues > freezable, which is possible, but hacky and Oleg didn't like that very much. > The second would be to freeze XFS from within the hibernation code path, > using freeze_bdev(). The second is much more likely to work reliably. If freezing the filesystem leaves something in an inconsistent state, then it's something I can reproduce and debug without needing to suspend/resume. FWIW, don't forget you need to thaw the filesystem on resume. Cheers, Dave. -- Dave Chinner Principal Engineer SGI Australian Software Group |
| Previous by Date: | Re: [linux-lvm] 2.6.22-rc4 XFS fails after hibernate/resume, David Chinner |
|---|---|
| Next by Date: | TAKE 967035 - lockdep inumorder annotations are busted, David Chinner |
| Previous by Thread: | Re: [linux-pm] Re: [linux-lvm] 2.6.22-rc4 XFS fails after hibernate/resume, Rafael J. Wysocki |
| Next by Thread: | Re: [linux-pm] Re: [linux-lvm] 2.6.22-rc4 XFS fails after hibernate/resume, David Greaves |
| Indexes: | [Date] [Thread] [Top] [All Lists] |