From: Lars Marowsky-Bree <lmb@suse.de>
To: Junfeng Yang <yjf@stanford.edu>, Andrew Morton <akpm@osdl.org>
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: [MC] [CHECKER] Do ext2, jfs and reiserfs respect mount -o sync/dirsync option?
Date: Fri, 4 Mar 2005 11:27:27 +0100 [thread overview]
Message-ID: <20050304102726.GS14495@marowsky-bree.de> (raw)
In-Reply-To: <Pine.GSO.4.44.0503040136010.9975-100000@elaine24.Stanford.EDU>
On 2005-03-04T01:44:06, Junfeng Yang <yjf@stanford.edu> wrote:
> > That would be a bug. Please send the e2fsck output.
>
> Here is the trace
>
> 1. file system is made with sbin/mkfs.ext2 -F -b 1024 /dev/hda9 60
> and mounted with -o sync,dirsync
>
> 1. operations FiSC did:
>
> creat(/mnt/sbd0/0001)
> write(/mnt/sbd0/0001)
> rename(/mnt/sbd0/0001, /mnt/sbd0/0002)
> mkdir(/mnt/sbd0/0003)
>
> 2. FiSC "crashed" the test machine after mkdir returns. Crashed
> disk image can be downloaded at: http://fisc.stanford.edu/bug2/crash.img.bz2
I've run into similar issues. For example, a "touch foo" also isn't
synchronous with -o sync, but stays entirely in the cache. Andrea tells
me this is expected behaviour, so I've given up on this one...
Sincerely,
Lars Marowsky-Brée <lmb@suse.de>
--
High Availability & Clustering
SUSE Labs, Research and Development
SUSE LINUX Products GmbH - A Novell Business
next prev parent reply other threads:[~2005-03-04 10:27 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-04 6:33 Junfeng Yang
2005-03-04 7:16 ` Matt Mackall
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-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 [this message]
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=20050304102726.GS14495@marowsky-bree.de \
--to=lmb@suse.de \
--cc=akpm@osdl.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome