Carlos E. R. wrote:
On Wednesday, 2009-10-28 at 11:33 +0100, Ludwig Nussel wrote:
Stefan Seyfried wrote:
Sometimes you _want_ to check the fs, but even back when we still did autocheck ext3 every 180 days or so, we never did on cryptohome.
It should work if fs_passno != 0 in fstab.
It has a side effect, though: if, for instance, you enter the wrong password (a mistake easy to make with the long passwords used for this), the system will abort booting and enter filesystem repair mode.
Yes, that fsck behavior isn't optimal. Matthias König tried to improve it¹ and the outcome was that /etc/init.d/boot.localfs skips devices with mount option 'nofail' entirely. boot.crypto will take care of fsck then. That doesn't work with devices that need to by unlocked by boot.crypto-early already though :-( So for those you better set timeout=0,tries=0 in crypttab. I guess I should document that in the manpage. cu Ludwig [1] http://markmail.org/message/dso3oggybuygy2xe -- (o_ Ludwig Nussel //\ V_/_ http://www.suse.de/ SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nuernberg) -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org