From: Andrew Morton <akpm@osdl.org>
To: Andrey Borzenkov <arvidjaar@mail.ru>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Syncing single filesystem (slow USB writing)
Date: Fri, 29 Jul 2005 10:52:20 -0700 [thread overview]
Message-ID: <20050729105220.4004e794.akpm@osdl.org> (raw)
In-Reply-To: <200507291544.23545.arvidjaar@mail.ru>
Andrey Borzenkov <arvidjaar@mail.ru> wrote:
>
> On Friday 29 July 2005 15:20, Andrew Morton wrote:
> > Andrey Borzenkov <arvidjaar@mail.ru> wrote:
> > > On Friday 29 July 2005 07:50, Andrew Morton wrote:
> > > > > One idea how to improve situation - continue to mount with dsync
> > > > > (having basically old case) and do frequent sync of filesystem (this
> > > > > culd be started as HAL callout or whatever). Unfortunately, I could
> > > > > not find a way to request a sync (flush) of single mount point or
> > > > > block device. Have I missed something?
> > > >
> > > > It's trivial to do in-kernel but no, I'm afraid there isn't a userspace
> > > > interface for this.
> > >
> > > apparently one should not ask such a question at 7 am. Any reason why
> > > BLKFLSBUF does not suite?
> >
> > That'll only write back data associated with /dev/hdXX (ie: filesystem
> > metadata) and not the data associated with all the files in the filesystem
> > which is mounted on /dev/hdXX.
>
> I am confused. BKLFLSBUF boils down to sync_inodes_sb for mounted device, and
> that appears to write out direty inode pages?
Oh, you're right. How cunning. Yes, `blockdev --flushbufs /dev/hda1'
would indeed appear to sync all data associated with that device.
next prev parent reply other threads:[~2005-07-29 17:53 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-29 3:31 Syncing single filesystem (slow USB writing) Andrey Borzenkov
2005-07-29 3:50 ` Andrew Morton
2005-07-29 4:12 ` Andrey Borzenkov
2005-07-29 10:28 ` Andrey Borzenkov
2005-07-29 11:20 ` Andrew Morton
2005-07-29 11:44 ` Andrey Borzenkov
2005-07-29 17:52 ` Andrew Morton [this message]
2005-07-29 7:53 ` Jan Engelhardt
2005-07-29 21:10 ` Chris Wedgwood
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=20050729105220.4004e794.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=arvidjaar@mail.ru \
--cc=linux-kernel@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