From: Matt Mackall <mpm@selenic.com>
To: Junfeng Yang <yjf@stanford.edu>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
ext2-devel@lists.sourceforge.net,
jfs-discussion@www-124.southbury.usf.ibm.com, reiser@namesys.com,
mc@cs.Stanford.EDU
Subject: Re: [CHECKER] Do ext2, jfs and reiserfs respect mount -o sync/dirsync option?
Date: Thu, 3 Mar 2005 23:16:13 -0800 [thread overview]
Message-ID: <20050304071613.GQ3163@waste.org> (raw)
In-Reply-To: <Pine.GSO.4.44.0503032211570.7754-100000@elaine24.Stanford.EDU>
On Thu, Mar 03, 2005 at 10:33:40PM -0800, Junfeng Yang wrote:
>
> Hi,
>
> FiSC (our file system checker) emits several warnings on ext2, jfs and
> reiserfs, complaining that diretories or files are lost while FiSC
> believes they should already be persistent on disk. (ext3 behaves
> correctly.)
>
> All warnings boil down to a single cause: when these file systems are
> mounted -o sync or dirsync, dirty blocks are still written out
> asynchronously. It appears to me that these mount options don't have any
> effect on these file systems. Is this the intended behavior?
I don't believe so. The sync option should definitionally make calls
to fsync for integrity redundant. This probably got broken ages ago
for ext2 in one of the many buffer/page cache refactorings.
--
Mathematics is the supreme nostalgia of our time.
next prev parent reply other threads:[~2005-03-04 7:17 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-04 6:33 [CHECKER] Do ext2, jfs and reiserfs respect mount -o sync/dirsync option? Junfeng Yang
2005-03-04 7:16 ` Matt Mackall [this message]
2005-03-04 7:34 ` Jan Engelhardt
2005-03-04 8:01 ` Junfeng Yang
2005-03-07 17:29 ` Alan Cox
2005-03-07 22:29 ` Junfeng Yang
2005-03-07 22:29 ` Junfeng Yang
2005-03-04 8:43 ` [MC] " Junfeng Yang
2005-03-04 9:11 ` Andrew Morton
2005-03-04 9:44 ` Junfeng Yang
2005-03-04 10:27 ` Lars Marowsky-Bree
2005-03-04 11:20 ` Andrew Morton
2005-03-04 23:03 ` Junfeng Yang
2005-03-04 23:29 ` Andrew Morton
2005-03-08 0:31 ` Bernd Eckenfels
2005-03-19 22:34 ` Florian Weimer
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=20050304071613.GQ3163@waste.org \
--to=mpm@selenic.com \
--cc=ext2-devel@lists.sourceforge.net \
--cc=jfs-discussion@www-124.southbury.usf.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mc@cs.Stanford.EDU \
--cc=reiser@namesys.com \
--cc=yjf@stanford.edu \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.