From: David Greaves <david@dgreaves.com>
To: xfs@oss.sgi.com,
"'linux-kernel@vger.kernel.org'" <linux-kernel@vger.kernel.org>,
David Chinner <dgc@sgi.com>
Subject: xfs freeze/umount problem
Date: Tue, 19 Jun 2007 09:10:08 +0100 [thread overview]
Message-ID: <46778F60.5090107@dgreaves.com> (raw)
David Chinner wrote:
> 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
> safe thing to do is freeze the filesystem before suspend and thaw it after
> resume.
Whilst testing a potential bug in another thread I accidentally found that
unmounting a filesystem that I'd just frozen would hang.
As the saying goes: "Well, duh!!"
I could eventually run an unfreeze but the mount was still hung. This lead to an
unclean shutdown.
OK, it may not be bright but it seems like this shouldn't happen; umount should
either unfreeze and work or fail ("Attempt to umount a frozen filesystem.") if
the fs is frozen.
Is this a kernel bug/misfeature or a (u)mount one?
Suggestions as to the best place to report it if not in the cc's?
David
next reply other threads:[~2007-06-19 8:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-19 8:10 David Greaves [this message]
2007-06-20 0:01 ` xfs freeze/umount problem 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=46778F60.5090107@dgreaves.com \
--to=david@dgreaves.com \
--cc=dgc@sgi.com \
--cc=linux-kernel@vger.kernel.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).