Messages in this thread | | | Date | Mon, 4 Aug 2003 13:22:19 -0700 | From | Andrew Morton <> | Subject | Re: ext3 badness in 2.6.0-test2 |
| |
Daniel Jacobowitz <dan@debian.org> wrote: > > I came back this morning and found: > EXT3-fs error (device md0) in start_transaction: Journal has aborted > EXT3-fs error (device md0) in start_transaction: Journal has aborted > EXT3-fs error (device md0) in start_transaction: Journal has aborted > > Unfortunately, from the very first one, all writes failed; including all > writes to syslog. So I don't know what happened at the beginning. Is this > more likely to be something internal to ext3, or a problem with the RAID > layer?
Could have been an IO error, or the block/MD/device layer returned incorrect data. ext3 used to go BUG a lot in the latter case, but nowadays we try to abort the journal and go read-only.
Without the initial message we do not know. - 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/
| |