linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Bryan Whitehead <driver@jpl.nasa.gov>
To: "Stephen C. Tweedie" <sct@redhat.com>
Cc: tsuchiya@labs.fujitsu.com, linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: filesystem bug?
Date: Tue, 16 Dec 2003 13:40:48 -0800	[thread overview]
Message-ID: <3FDF7BE0.205@jpl.nasa.gov> (raw)
In-Reply-To: <1071582242.5462.1.camel@sisko.scot.redhat.com>

I get this problem all the time here at JPL. I can always get the files 
back by remounting the filesystem.

For example if /dev/sdb1 mounted on /export/project is getting wierd 
"Input/output" errors I can simply run this command:
mount -o remount /dev/sdb1 /export/project

It's been about a year of these problems... I'll try running the test 
Tsuchiya Yoshihiro made to reproduce. (I have not been able to create a 
test that can consistantly reproduce... but the problem has sure screwed 
up some data-gathering runs in the lab).

These are all on Mandrake kernels though.... (from the 9.0 series). so 
that's 2.4.19+tonOfPatches.

Stephen C. Tweedie wrote:
> Hi,
> 
> On Mon, 2003-12-15 at 09:25, Tsuchiya Yoshihiro wrote:
> 
> 
>>Following is an Ext2 result and the inode is filled by zero.
>>I think the inode becomes a badinode.
> 
> 
>>[root@dell04 tsuchiya]# ls -l /mnt/foo/ae/dir0/mozilla/layout/html/tests/table/bugs/bug2757.html
>>ls: /mnt/foo/ae/dir0/mozilla/layout/html/tests/table/bugs/bug2757.html: Input/output error
> 
> 
> "Input/output error" can sometimes mean that the kernel has found a
> filesystem problem, but it also often indicates a device-layer problem. 
> Is there anything helpful in the kernel logs?
> 
> Cheers,
>  Stephen
> 
> 
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/


-- 
Bryan Whitehead
SysAdmin - JPL - Interferometry and Large Optical Systems
Phone: 818 354 2903
driver@jpl.nasa.gov


  reply	other threads:[~2003-12-16 21:40 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 [this message]
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
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=3FDF7BE0.205@jpl.nasa.gov \
    --to=driver@jpl.nasa.gov \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sct@redhat.com \
    --cc=tsuchiya@labs.fujitsu.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).