On Tue, 2011-06-28 at 11:36 +0200, Jan Kara wrote: > On Mon 27-06-11 23:21:17, Moffett, Kyle D wrote: [...] > > Please correct me if this is horribly horribly wrong: > > > > no journal: > > Nothing is journalled > > + Very fast. > > + Works well for filesystems that are "mkfs"ed on every boot > > - Have to fsck after every reboot > Fsck is needed only after a crash / hard powerdown. Otherwise completely > correct. Plus you always have a possibility of exposing uninitialized > (potentially sensitive) data after a fsck. > > Actually, normal desktop might be quite happy with non-journaled filesystem > when fsck is fask enough. [...] With no journal, there is a fair risk that fsck cannot recover the filesystem automatically (let alone the actual data). And normal users should never have to suffer questions from fsck. Ben. -- Ben Hutchings In a hierarchy, every employee tends to rise to his level of incompetence.
Attachment:
signature.asc
Description: This is a digitally signed message part
