linux-kernel.vger.kernel.org archive mirror
 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 22:30:21 +0800	[thread overview]
Message-ID: <17140565218.20031226223021@sina.com.cn> (raw)
In-Reply-To: <8BD3ED34-37A6-11D8-A9B5-00039341E01A@ybb.ne.jp>

Hello ,

Friday, December 26, 2003, 9:22:25 PM, you wrote:

Bxynj> Hi,

 >>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.

Bxynj> Dlion,  how did the corrupted file look like?
Bxynj> (its file size, number of blocks etc.)

1. some corrupted files is truncated to 0 bytes. Blockcount is 0.

2. some corrupted files is truncated . the result is a shorter file.
the new size is multiple of block size.

3. maybe all corrupted files' mtime is exactly the same
wrong value. Should be around 2003.12.26 21:30:00, but
is 2002.05.12 12:00:48(hex value is 0x3cdde8f0) . ctime
and atime is correct. The system's clock time is unchanged.

4. it seems that the corrupted files tends to exist in the same
directory.

Use a 128000k bytes ramdisk you can get these results in less than
30 minutes. BTW, your test script is very good. Thank you.




  reply	other threads:[~2003-12-26 14:31 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-12-26 13:22 filesystem bug? 土屋芳浩
2003-12-26 14:30 ` dlion [this message]
2003-12-28  8:26   ` dlion
  -- strict thread matches above, loose matches on Subject: below --
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
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-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=17140565218.20031226223021@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;
as well as URLs for NNTP newsgroup(s).