From: Ricardo Correia <rcorreia@wizy.org>
To: linux-kernel@vger.kernel.org
Subject: How to flush the disk write cache from userspace
Date: Sun, 14 Jan 2007 04:05:33 +0000 [thread overview]
Message-ID: <200701140405.33748.rcorreia@wizy.org> (raw)
Hi, (please CC: to my email address, I'm not subscribed)
Quick question: how can I flush the disk write cache from userspace?
Long question:
I'm porting the Solaris ZFS filesystem to the FUSE/Linux filesystem framework.
This is a copy-on-write, transactional filesystem and so it needs to ensure
correct ordering of writes when transactions are written to disk.
At the moment, when transactions end, I'm using a fsync() on the block device
followed by a ioctl(BLKFLSBUF).
This is because, according to the fsync manpage, even after fsync() returns,
data might still be in the disk write cache, so fsync by itself doesn't
guarantee data safety on power failure.
I was looking for something like the Solaris ioctl(DKIOCFLUSHWRITECACHE),
which does exactly what I need.
The most similar thing I could find was ioctl(BLKFLSBUF), however a search for
BLKFLSBUF on the Linux 2.6.15 source doesn't seem to return anything related
to IDE or SCSI disks.
Can I trust ioctl(BLKFLSBUF) to flush disks' write caches (for disks that
follow the specs)?
What about block devices of disk partitions, LVM logical volumes and the EMVS
volumes, do they propagate flush commands to the respective disks?
What about loop devices?
Thanks in advance.
next reply other threads:[~2007-01-14 4:12 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-14 4:05 Ricardo Correia [this message]
2007-01-16 0:38 ` Jens Axboe
2007-01-18 1:15 ` Ricardo Correia
[not found] <fa.y+HJNAxqDqX5AHUxcmThAo20Ivo@ifi.uio.no>
[not found] ` <fa.xbdrjhFpvWMJeTroG2DpPE4wd+M@ifi.uio.no>
[not found] ` <fa.lqQRZqIqMX2chyIAM888fc1jCuY@ifi.uio.no>
2007-01-19 0:35 ` Robert Hancock
2007-01-21 3:50 ` Jens Axboe
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=200701140405.33748.rcorreia@wizy.org \
--to=rcorreia@wizy.org \
--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
all inboxes | Powered by JetHome®