From: Matthias Andree <matthias.andree@stud.uni-dortmund.de>
To: lkml <linux-kernel@vger.kernel.org>
Subject: Re: synchronous mounts
Date: Fri, 16 Nov 2001 11:47:28 +0100 [thread overview]
Message-ID: <20011116114728.J5520@emma1.emma.line.org> (raw)
In-Reply-To: <3BF376EC.EA9B03C8@zip.com.au> <20011115214525.C14221@redhat.com> <3BF45B9F.DEE1076B@mandrakesoft.com> <3BF4CF5C.18CBE4BC@zip.com.au>
In-Reply-To: <3BF4CF5C.18CBE4BC@zip.com.au>
On Fri, 16 Nov 2001, Andrew Morton wrote:
> A `dirsync' option does make sense though, for the reasons which
> Stephen outlined.
So we could then have:
- (no option) == async, which only syncs file + data on fsync() or
O_SYNC (BSD calls this async, it may corrupt file systems because
writes are out-of-order)
- dirsync, which syncs directories and metadata and causes ordered
writes thereof (BSD calls this noasync), no chance of corrupting
on-disk structure unrecoverably.
- sync, which syncs all filesystem operations (BSD calls this sync
also), will have at most 1 dirty block at a time on non-journaled file
systems(?)
I expect sync to be faster on journalled file systems in that case,
because "in-order execution" to journal will probably cause linear
writes, while on ext2, it will involve seeking.
--
Matthias Andree
"They that can give up essential liberty to obtain a little temporary
safety deserve neither liberty nor safety." Benjamin Franklin
next prev parent reply other threads:[~2001-11-16 10:48 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-15 8:03 Andrew Morton
2001-11-15 21:45 ` Stephen C. Tweedie
2001-11-15 22:02 ` Andrew Morton
2001-11-15 23:05 ` Stephen C. Tweedie
2001-11-16 0:19 ` Jeff Garzik
2001-11-16 8:33 ` Andrew Morton
2001-11-16 10:47 ` Matthias Andree [this message]
2001-11-16 12:28 ` Stephen C. Tweedie
2001-11-16 13:28 ` Jeff Garzik
2001-11-16 13:37 ` Jeff Garzik
2001-11-16 22:40 ` Matthias Andree
2001-11-16 3:07 ` Neil Brown
2001-11-17 7:13 ` Andrew Morton
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=20011116114728.J5520@emma1.emma.line.org \
--to=matthias.andree@stud.uni-dortmund.de \
--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®