From: Tsuchiya Yoshihiro <tsuchiya@labs.fujitsu.com>
To: tsuchiya@labs.fujitsu.com
Cc: Bryan Whitehead <driver@jpl.nasa.gov>,
"Stephen C. Tweedie" <sct@redhat.com>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: filesystem bug?
Date: Thu, 18 Dec 2003 08:24:54 +0900 [thread overview]
Message-ID: <3FE0E5C6.5040008@labs.fujitsu.com> (raw)
In-Reply-To: <3FDF95EB.2080903@labs.fujitsu.com>
Tsuchiya Yoshihiro wrote:
> Especially with Ext2 reproducing is easy, it happens in a few hours
> with my script.
> With Ext3, in a day if you are lucky.
>
> Now I am trying 2.4.23 from kernel.org with ext3, and 2.6.0-test11
> from kernel.org with ext3.
> So far, it's been a about a day, they are runing nicely. Let's see
> what happens.
>
> Following is the failed combination:
> Redhat9 with 2.4.20-8 ext2 and ext3
> Redhat9 with 2.4.20-19.9 ext2 and ext3
> Redhat9 with 2.4.20-24.9 ext2
I forgot to mention that I had been testing 2.4.20 from kernel.org
also.... And it failed now!
As you see below, /mnt/foo/ad/mozilla was gone. ad/mozilla had been used
to compare
with dir*/mozilla and it is basically read-only and will never be
removed by the script.
/mnt/foo/ae is ok and ae/mozilla is of cource there.
It had been almost 2days scince the test started, and the test was 58-th
turn.
It had run on ext2 filesystem, and the kernel was downloaded from
kernel.org.
I had seen the same problem--I mean read-only mozilla directory going
away--
on ext3 on redhat kernel 2.4.20-19.9.
[root@dell04 tsuchiya]# ls /mnt/foo/ad
dir0 dir14 dir2 dir25 dir30 dir36 dir41 dir47 dir52 dir58
dir1 dir15 dir20 dir26 dir31 dir37 dir42 dir48 dir53 dir6
dir10 dir16 dir21 dir27 dir32 dir38 dir43 dir49 dir54 dir7
dir11 dir17 dir22 dir28 dir33 dir39 dir44 dir5 dir55 dir8
dir12 dir18 dir23 dir29 dir34 dir4 dir45 dir50 dir56 dir9
dir13 dir19 dir24 dir3 dir35 dir40 dir46 dir51 dir57
[root@dell04 tsuchiya]# ls /mnt/foo/ae
dir0 dir14 dir2 dir25 dir30 dir36 dir41 dir47 dir52 dir58
dir1 dir15 dir20 dir26 dir31 dir37 dir42 dir48 dir53 dir6
dir10 dir16 dir21 dir27 dir32 dir38 dir43 dir49 dir54 dir7
dir11 dir17 dir22 dir28 dir33 dir39 dir44 dir5 dir55 dir8
dir12 dir18 dir23 dir29 dir34 dir4 dir45 dir50 dir56 dir9
dir13 dir19 dir24 dir3 dir35 dir40 dir46 dir51 dir57 mozilla
Yoshi
--
Yoshihiro Tsuchiya
next prev parent reply other threads:[~2003-12-17 23:25 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-15 9:25 filesystem bug? Tsuchiya Yoshihiro
2003-12-15 9:55 ` bert hubert
2003-12-16 13:44 ` Stephen C. Tweedie
2003-12-16 21:40 ` Bryan Whitehead
2003-12-16 21:50 ` Bryan Whitehead
2003-12-16 23:31 ` Tsuchiya Yoshihiro
2003-12-16 23:40 ` viro
2003-12-17 0:12 ` Tsuchiya Yoshihiro
2003-12-17 23:24 ` Tsuchiya Yoshihiro [this message]
2003-12-18 21:29 ` Stephen C. Tweedie
2003-12-21 23:15 ` Tsuchiya Yoshihiro
2003-12-22 1:54 ` Tsuchiya Yoshihiro
2003-12-22 4:30 ` Tsuchiya Yoshihiro
2003-12-22 12:03 ` Stephen C. Tweedie
2003-12-24 1:48 ` Tsuchiya Yoshihiro
2003-12-24 23:09 ` Tsuchiya Yoshihiro
2004-01-15 6:38 ` Tsuchiya Yoshihiro
2003-12-26 9:59 ` dlion
2003-12-26 12:27 ` dlion
2003-12-26 13:22 土屋芳浩
2003-12-26 14:30 ` dlion
2003-12-28 8:26 ` dlion
2003-12-27 14:35 Tsuchiya Yoshihiro
[not found] ` <Pine.LNX.4.58L.0312301556380.23875@logos.cnet>
[not found] ` <74964CA8-3B50-11D8-B879-00039341E01A@ybb.ne.jp>
[not found] ` <1074109164.4538.8.camel@sisko.scot.redhat.com>
[not found] ` <0586254E-46DA-11D8-B45E-00039341E01A@ybb.ne.jp>
2004-01-15 22:38 ` Stephen C. Tweedie
2004-01-16 2:59 Tsuchiya Yoshihiro
2004-01-16 12:29 ` Stephen C. Tweedie
2004-01-19 7:52 ` Tsuchiya Yoshihiro
2004-01-19 13:12 ` Stephen C. Tweedie
2004-01-20 8:36 ` Tsuchiya Yoshihiro
2004-01-20 16:27 ` Stephen C. Tweedie
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=3FE0E5C6.5040008@labs.fujitsu.com \
--to=tsuchiya@labs.fujitsu.com \
--cc=driver@jpl.nasa.gov \
--cc=linux-kernel@vger.kernel.org \
--cc=sct@redhat.com \
/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;
as well as URLs for NNTP newsgroup(s).