journal commit i/o error on 12.3

Yesterday, while playing a game on my computer, I suddenly got a couple of popup messages about a journal commit i/o error.

You don’t need to tell me to backup my data; that’s the first thing I did. Then I ran S.M.A.R.T. extended tests on each of my hard drives. Both tests completed without error.

Other than the messages, my computer appears to be working fine.

Any idea what could have caused this? What else should I check?

Act of god, cosmic rays, power line hiccup,…

You have a cpu that is executing billions of operations per second and even though the reliability is extremely good nothing is perfect.

Turned out to be more than just a hiccup. About 3 days ago S.M.A.R.T. started showing errors on one of my drives, a Western Digital. I repaired it with WD’s utility, but there were more errors the next day, so yesterday I replaced it. Luckily it was still functional enough that I could just clone everything on it to the new drive. So I guess that journal commit i/o error message should be regarded as an early warning of drive failure, even before S.M.A.R.T. sees anything.

On 2013-11-02 12:56, dimesio wrote:
>
> Turned out to be more than just a hiccup. About 3 days ago S.M.A.R.T.
> started showing errors on one of my drives, a Western Digital. I
> repaired it with WD’s utility, but there were more errors the next day,
> so yesterday I replaced it. Luckily it was still functional enough that
> I could just clone everything on it to the new drive. So I guess that
> journal commit i/o error message should be regarded as an early warning
> of drive failure, even before S.M.A.R.T. sees anything.

Not really. It happened that the failed write operation hit be chance
the journal disk space. A failure to write the journal is perhaps
considered worse that a failure anywhere else in the partition.


Cheers / Saludos,

Carlos E. R.
(from 12.3 x86_64 “Dartmouth” at Telcontar)