LKML Archive on
help / color / mirror / Atom feed
From: zine el abidine Hamid <>
Subject: Detecting I/O error and Halting System  : come back
Date: Thu, 7 Dec 2006 12:01:04 +0100 (CET)	[thread overview]
Message-ID: <> (raw)

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

             reply	other threads:[~2006-12-07 11:01 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-12-07 11:01 zine el abidine Hamid [this message]
2006-12-07 12:27 ` linux-os (Dick Johnson)

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \ \ \ \
    --subject='Re: Detecting I/O error and Halting System  : come back' \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

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