linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Tsuchiya Yoshihiro <tsuchiya@labs.fujitsu.com>
To: "Stephen C. Tweedie" <sct@redhat.com>
Cc: linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: filesystem bug?
Date: Mon, 19 Jan 2004 16:52:52 +0900	[thread overview]
Message-ID: <400B8CD4.8000503@labs.fujitsu.com> (raw)
In-Reply-To: <1074256175.4006.24.camel@sisko.scot.redhat.com>

Hello,

Stephen C. Tweedie wrote:

>OK.  Under exactly what circumstances have you seen this in the past, as
>opposed to the other problem?  I have not been able to reproduce this
>one so far.
>  
>

The combinations of kernel versions and filesystem types are:
2.4.20-8 ext2
2.4.20-19.9 ext2, ext3
2.4.20-24.9 ext2
2.4.20-28.9 ext2

I do the test with mozilla-1.3.tar.gz and 6 processes in the script,
it happens with ext2 within a few hours.

I haven't seen the problem on 2.4.20,23 and 24.

So now I am testing followings:
2.4.24-pre2 ext2 (mozilla-1.3.tar.gz)
2.4.24 ext2 (nvi-1.79.tar.gz)
2.4.20 ext3 (mozilla-1.3.tar.gz)
2.4.23 ext3 (mozilla-1.3.tar.gz)
2.4.24 ext3 (mozilla-1.3.tar.gz)
2.4.20-28.9 ext3 (mozilla-1.3.tar.gz)

Other than 2.4.20-28.9, since they have been running for three days,
they seems nice at this point.

What exactly is the race condition between read_inode() and
clear_inode() you have
mentioned?

Thanks,
Yoshi
-- 
--
Yoshihiro Tsuchiya



  reply	other threads:[~2004-01-19  7:53 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-01-16  2:59 filesystem bug? Tsuchiya Yoshihiro
2004-01-16 12:29 ` Stephen C. Tweedie
2004-01-19  7:52   ` Tsuchiya Yoshihiro [this message]
2004-01-19 13:12     ` Stephen C. Tweedie
2004-01-20  8:36       ` Tsuchiya Yoshihiro
2004-01-20 16:27         ` Stephen C. Tweedie
  -- strict thread matches above, loose matches on Subject: below --
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
2003-12-26 13:22 土屋芳浩
2003-12-26 14:30 ` dlion
2003-12-28  8:26   ` dlion
2003-12-15  9:25 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
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

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=400B8CD4.8000503@labs.fujitsu.com \
    --to=tsuchiya@labs.fujitsu.com \
    --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).