Re: filesystem bug?

[Bryan Whitehead <driver@jpl.nasa.gov>]

BTW, this happens on these filesystems we tried: ext2, ext3, and XFS.

Bryan Whitehead wrote:
> 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