I recently added the fsck hook to mkinitcpio.conf after seeing it being recommended in the forums. I don't have a separate /usr though.
Anyway, now after every boot i see:
performing fsck on <root-device>
It shows up clean, and happens in a flash of a second.
So my question is that is the hook supposed to perform fsck everytime? Earlier (without the hook), it used to happen only on unclean shutdowns.
On 03/26/2012 03:09 PM, gt wrote:
I recently added the fsck hook to mkinitcpio.conf after seeing it being recommended in the forums. I don't have a separate /usr though.
Anyway, now after every boot i see:
performing fsck on <root-device>
It shows up clean, and happens in a flash of a second.
So my question is that is the hook supposed to perform fsck everytime? Earlier (without the hook), it used to happen only on unclean shutdowns.
Yes, it's supposed to be like this. I think the main intention is to guarantee a clean root filesystem before trying to mount e.g. a seperate /home or /usr, which may depend on content of the rootfs (keyfiles, configuration files, ...).
This all adds up to be a precaution taken by the devs to guarantee a smooth experience IMO :)
Greetings, Christoph
On Mon, Mar 26, 2012 at 3:09 PM, gt static.vortex@gmx.com wrote:
I recently added the fsck hook to mkinitcpio.conf after seeing it being recommended in the forums. I don't have a separate /usr though.
Anyway, now after every boot i see:
performing fsck on <root-device>
It shows up clean, and happens in a flash of a second.
So my question is that is the hook supposed to perform fsck everytime? Earlier (without the hook), it used to happen only on unclean shutdowns.
We always perform fsck on all partitions on every boot. The difference with the fsck hook in initramf is that it fsck's the rootfs (and potentially /usr) before mounting them. The reason for wanting to do this is that otherwise you would be "out of luck" if your root could not be mounted, or your fsck binary i broken due to issues on the rootfs.
The reason fsck happens in a flash of a second is that it in most cases does nothing. The exemption is if you shutdown uncleanly, or you have booted a certain number of times without fscking.
-t
arch-general@lists.archlinux.org