mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: dlion <dlion2004@sina.com.cn>
To: lkml <linux-kernel@vger.kernel.org>
Subject: Re: filesystem bug?
Date: Fri, 26 Dec 2003 17:59:05 +0800	[thread overview]
Message-ID: <7624288781.20031226175905@sina.com.cn> (raw)
In-Reply-To: <3FDD7DFD.7020306@labs.fujitsu.com>

Hello Tsuchiya,

Monday, December 15, 2003, 5:25:17 PM, you wrote:

TY> Hi,

TY> Ext2 and Ext3 filesystem go to inconsistent status by
TY> simple test program on my system.

TY> My test program is a script that extract a tar+gzip archive
TY> twice and compare them, and remove one of the tree, and then
TY> another extracting, and compare them again. A very simple test.

I tried your script on ext2 and ext3 filesystem on a ramdisk. I got errors,
too. It seems that this problem is unrelated to device driver or
hardware.

The mozilla tarball is too big for a ramdisk. I use a
zhcon-0.2.1.tar.gz (4,991,350 bytes) instead.

I only got one kind of error on ext2 filesystem. That is, the script
 said the read-only directory zhcon-0.2.1 is missing, but it _is_ there.
I used e2fsck to check the ramdisk and found no error.

I got other errors on ext3 filesystem include:
1. missing file
2. corrupted file
but when I used fsck.ext3 to check the ramdisk, the result was clean.

My system is:
CPU:  AMD Athlon XP 1800+
RAM:  256M DDR333
Chipset: VIA KT400A
Linux Distribution: Fedora Core 1
Linux Kernel: kernel-2.4.22-1.2115.nptl.athlon.rpm

-- 
Best regards,
 dlion                            mailto:dlion2004_at_sina.com.cn



  parent reply	other threads:[~2003-12-26  9:59 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
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 [this message]
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=7624288781.20031226175905@sina.com.cn \
    --to=dlion2004@sina.com.cn \
    --cc=linux-kernel@vger.kernel.org \
    /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

all inboxes | Powered by JetHome®