linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Chinner <dgc@sgi.com>
To: Pavel Machek <pavel@ucw.cz>
Cc: David Chinner <dgc@sgi.com>, David Greaves <david@dgreaves.com>,
	David Robinson <zxvdr.au@gmail.com>,
	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: Fri, 29 Jun 2007 14:55:53 +1000	[thread overview]
Message-ID: <20070629045553.GN31489@sgi.com> (raw)
In-Reply-To: <20070627204924.GA4777@ucw.cz>

On Wed, Jun 27, 2007 at 08:49:24PM +0000, Pavel Machek wrote:
> Hi!
> 
> > FWIW, I'm on record stating that "sync" is not sufficient to quiesce an XFS
> > filesystem for a suspend/resume to work safely and have argued that the only
> 
> Hmm, so XFS writes to disk even when its threads are frozen?

They issue async I/O before they sleep and expects
processing to be done on I/O completion via workqueues.

> > safe thing to do is freeze the filesystem before suspend and thaw it after
> > resume. This is why I originally asked you to test that with the other problem
> 
> Could you add that to the XFS threads if it is really required? They
> do know that they are being frozen for suspend.

We don't suspend the threads on a filesystem freeze - they continue
run. A filesystem freeze guarantees the filesystem clean and that
the in memory state matches what is on disk. It is not possible for
the filesytem to issue I/O or have outstanding I/O when it is in the
frozen state, so the state of the threads and/or workqueues does not
matter because they will be idle.

Cheers,

Dave.
-- 
Dave Chinner
Principal Engineer
SGI Australian Software Group

      parent reply	other threads:[~2007-06-29  4:55 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
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 [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=20070629045553.GN31489@sgi.com \
    --to=dgc@sgi.com \
    --cc=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=pavel@ucw.cz \
    --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).