Re: ext3 journal on software raid (was Re: PROBLEM: Kernel 2.6.10 crashing repeatedly and hard)

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Peter T. Breuer wrote:

ext3 journals are much safer on mirrored devices than on non-mirrored


That's irrelevant - you don't care what's in the journal, because if
your system crashes before committal you WANT the data in the journal
to be lost, rolled back, whatever, and you don't want your machine to
have acked the write until it actually has gone to disk.

Or at least that's what *I* want. But then everyone has different
wants and needs. What is obvious, however, are the issues involved.


err, no.

If the journal is safely written to the journal device and the machine crashes whilst updating the main filesystem you want the journal to be replayed, not erased. The journal entries are designed to be replayable to a partially updated filesystem.

That's the whole point of journalling filesystems, write the deltas to the journal, make the changes to the fs, delete the deltas from the journal.

If the machine crashes whilst the deltas are being written then you won't play them back - but your fs will be consistent.

Journaled filesystems simply ensure the integrity of the fs metadata - they don't protect against random acts of application/user level vandalism (ie power failure).

David
-
To unsubscribe from this list: send the line "unsubscribe linux-raid" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html

[Index of Archives]     [Linux RAID Wiki]     [ATA RAID]     [Linux SCSI Target Infrastructure]     [Linux Block]     [Linux IDE]     [Linux SCSI]     [Linux Hams]     [Device Mapper]     [Device Mapper Cryptographics]     [Kernel]     [Linux Admin]     [Linux Net]     [GFS]     [RPM]     [git]     [Yosemite Forum]


  Powered by Linux