All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@osdl.org>
To: Junfeng Yang <yjf@stanford.edu>
Cc: 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 01:11:41 -0800	[thread overview]
Message-ID: <20050304011141.5ff037dc.akpm@osdl.org> (raw)
In-Reply-To: <Pine.GSO.4.44.0503040025380.9443-100000@elaine24.Stanford.EDU>

Junfeng Yang <yjf@stanford.edu> wrote:
>
> On Thu, 3 Mar 2005, 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.)
> 
> I forget to mention, we are mainly looking for crash-recovery bugs.  The
> warnings can trigger this way:
> 1. do several file system operations
> 2. "crash" the test machine
> 3. get the crashed disk image, run fsck to recover
> 4. mount the recovered disk image
>
> I'm able to reproduce the same warnings on ext2 using the following
> program:
> 
> main()
> {
>         system("sudo umount /dev/hda9");
>         system("/sbin/mke2fs /dev/hda9");
>         system("sudo mount -t ext2 /dev/hda9 /mnt/sbd1 -o sync,dirsync");
>         creat("/mnt/sbd1/0002", 0777);
>         mkdir("/mnt/sbd1/0003", 0777);
> 	// unplug your power cord here :)  then use e2fsck to recover
> }

That would be a bug.  Please send the e2fsck output.

> uname -a shows
> Linux notus 2.6.8-1-686 #1 Thu Nov 25 04:34:30 UTC 2004 i686 GNU/Linux

It would be much better to test vaguely contemporary kernels.

  reply	other threads:[~2005-03-04  9:15 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
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 [this message]
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=20050304011141.5ff037dc.akpm@osdl.org \
    --to=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 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.