[lkml]   [2006]   [Dec]   [7]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectDetecting I/O error and Halting System : come back
Hi evrybody,

I come back with my problem of "I/O error" (refer to
the following link to reffresh your mind :

I come back with a last question and I swear that I'll
stop annoying you with this problem.
Can you explain me why it seems that some part of the
hard drive are read only and others seems totaly
Some commands are available and works fine, others
generate an error like this :

-bash: /bin/some_command: Input/output error

Can you explain that?
Can I consider that the commands that are available
are in fact in the memory/cache and not read from the
hard drive?

Executing "e2fsck" turns sometimes in short : I got
"Bus error".
When I execute again "e2fsck" I optain this errors :
Error reading block XXXX ( Attempt to read block from
filesystem resulted in short read). Ignore error?
Inode XYZW (...) has bad mode (00).

When I try to write to a file (that I can read and
that is not empty), I loose it ?(size = 0, and the
content seems to be gone away...)

Why, when I execute the shutdown commande, I got a bus

Some Linux users pointed a journal commit problem;
what do you think about?
( see the link :

I googled and found that there are lot off similar
cases :

Nouveau : téléphonez moins cher avec Yahoo! Messenger ! Découvez les tarifs exceptionnels pour appeler la France et l'international.
Téléchargez sur
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

 \ /
  Last update: 2006-12-07 12:05    [W:0.023 / U:12.388 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site