| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Date: Wed, 26 Aug 2009 15:10:28 +0200 From: Pavel Machek <pavel@....cz> To: david@...g.hm Cc: Rik van Riel <riel@...hat.com>, Ric Wheeler <rwheeler@...hat.com>, Theodore Tso <tytso@....edu>, Florian Weimer <fweimer@....de>, Goswin von Brederlow <goswin-v-b@....de>, Rob Landley <rob@...dley.net>, kernel list <linux-kernel@...r.kernel.org>, Andrew Morton <akpm@...l.org>, mtk.manpages@...il.com, rdunlap@...otime.net, linux-doc@...r.kernel.org, linux-ext4@...r.kernel.org, corbet@....net, jack@...e.cz Subject: Re: [patch] ext2/3: document conditions when reliable operation is possible >>> The metadata is just a way to get to my data, while the data >>> is actually important. >> >> Personally, I care about metadata consistency, and ext3 documentation >> suggests that journal protects its integrity. Except that it does not >> on broken storage devices, and you still need to run fsck there. > > as the ext3 authors have stated many times over the years, you still need > to run fsck periodicly anyway. Where is that documented? I very much agree with that, but when suse10 switched periodic fsck off, I could not find any docs to show that it is bad idea. Pavel -- (english) http://www.livejournal.com/~pavelmachek (cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists