From: Jan Kara <jack@suse.cz>
To: Sage Weil <sage@newdream.net>
Cc: linux-fsdevel@vger.kernel.org
Subject: Re: syncing a single fs, and invalidate_bdev()
Date: Tue, 20 Jul 2010 16:27:21 +0200 [thread overview]
Message-ID: <20100720142720.GD3657@quack.suse.cz> (raw)
In-Reply-To: <Pine.LNX.4.64.1007091434320.25004@cobra.newdream.net>
Hi,
On Fri 16-07-10 14:09:24, Sage Weil wrote:
> I'd like to sync a single fs/superblock from userland. sync(2) is too
> heavyweight since it syncs all supers. The only thing I see is the
> BLKFLSBUF ioctl. That will fsync_bdev() (which does sync the super), and
> then does invalidate_bdev().
>
> Is that the right thing to do? Is there any issue with calling
> invalidate_bdev() under a running fs? Do any normal block file systems
> use the bdev's mapping for non-dirty data?
BLKFLSBUF is safe under all conditions. The bad thing is that it frees
the caches as well which you may not want. But looking at the code I don't
see a way how to sync a single filesystem in some other way from userspace...
Honza
--
Jan Kara <jack@suse.cz>
SUSE Labs, CR
prev parent reply other threads:[~2010-07-20 14:27 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-16 21:09 syncing a single fs, and invalidate_bdev() Sage Weil
2010-07-20 14:27 ` Jan Kara [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=20100720142720.GD3657@quack.suse.cz \
--to=jack@suse.cz \
--cc=linux-fsdevel@vger.kernel.org \
--cc=sage@newdream.net \
/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).