From: Christoph Hellwig <hch@lst.de>
To: Anton Altaparmakov <aia21@cam.ac.uk>
Cc: Christoph Hellwig <hch@lst.de>, Andrew Morton <akpm@osdl.org>,
linux-fsdevel@vger.kernel.org
Subject: Re: [PATCH] block new writers on frozen filesystems
Date: Sun, 13 Feb 2005 16:24:21 +0100 [thread overview]
Message-ID: <20050213152421.GA2747@lst.de> (raw)
In-Reply-To: <Pine.LNX.4.60.0502131503001.27092@hermes-1.csi.cam.ac.uk>
On Sun, Feb 13, 2005 at 03:05:22PM +0000, Anton Altaparmakov wrote:
> > This should block new data writers. New metadata writes need to be
> > blocked in the individual filesystem, and only when the state is set
> > to SB_FREEZE_TRANS (a few steps later in freeze_bdev).
>
> Why this distinction? At least on NTFS metadata is stored in normal files
> (everything is a file in NTFS) and the same readpage/writepage address
> space operations are used to access both...
Because flushing the data after you block new writes usually involved
writing out metadata aswell, so you can't block them at the same time
without deadlocking.
prev parent reply other threads:[~2005-02-13 15:24 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-10 16:13 [PATCH] block new writers on frozen filesystems Christoph Hellwig
2005-02-10 23:14 ` Andrew Morton
2005-02-13 14:20 ` Christoph Hellwig
2005-02-13 15:05 ` Anton Altaparmakov
2005-02-13 15:24 ` Christoph Hellwig [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=20050213152421.GA2747@lst.de \
--to=hch@lst.de \
--cc=aia21@cam.ac.uk \
--cc=akpm@osdl.org \
--cc=linux-fsdevel@vger.kernel.org \
/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).