Re: journal aborted, system read-only

[Stephen C. Tweedie]

Hi,

On Thu, 2004-09-16 at 06:03, Gene Heskett wrote:

> >Well, we really need to see _what_ error the journal had encountered
...
> It just did it to me again, this time with 2.6.9-rc1-mm5.

> And as usual in these cases, the logs are spotlessly clean 
> because /var is on /, which is on /dev/hda7, an syslog couldn't write 
> when its read-only.

Possibility the first is to create a separate partition for /var;
possibility the second is to set up a serial console.  Without access to
that log information, all we know is "there was an IO error," and that's
really not enough to narrow down the search. :-)

Thanks,
 Stephen

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/