public inbox for linux-kernel@vger.kernel.org
 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, 22 Dec 2003 13:30:26 +0900	[thread overview]
Message-ID: <3FE67362.2070704@labs.fujitsu.com> (raw)
In-Reply-To: <3FE62999.90309@labs.fujitsu.com>

Tsuchiya Yoshihiro wrote:

>>It could possibly be a core VFS bug, but the VFS is in general pretty
>>reliable under load.  We've had problems under specific edge conditions
>>such as races between sync and unmount, but the basic VFS behaviour
>>under load generally gets _lots_ of testing, so I'd definitely start by
>>looking elsewhere.  
>>
>>I'd also like to see how your 2.4.23 and 2.6.0-test11 testing is going. 
>>That might give some clues, too.  There's a race between clear_inode()
>>and read_inode() fixed in those kernels, but that doesn't look relevant
>>here; there may be something else changed that's significant, though.
>>
>> 
>>
>>    
>>
>EXT3 on 2.4.23 and 2.6.0-test11 both failed. I feel when I make the
>filesystem
>smaller - make the filesystem usage 70% to 80% during the test- ,
>the problem happens easyer.
>
>  
>

I tried it with IDE disk and it failed also. It was run on
ext2 on 2.4.23. So it's not a SCSI problem.


Thanks,
Yoshi

--
Yoshihiro Tsuchiya




  parent reply	other threads:[~2003-12-22  4:30 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
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 [this message]
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
  -- strict thread matches above, loose matches on Subject: below --
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=3FE67362.2070704@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