Re: [RESEND for ML] wic: imager/direct: passno is set to 0 for all entries in the fstab

["Richard Purdie" <richard.purdie@linuxfoundation.org>]

On Fri, 2020-11-06 at 10:07 +0100, Claudius Heine wrote:
> I looked into periodic file system checks for ext* partitions, in
> order to increase robustness for systems that use those file systems
> and was  surprised that the fstab that wic generates that `0` hard
> coded as the  passno parameter [1]. This prevents for instance
> systemd-fsck@(8) [2]  from running checks on those file systems.
> 
> It seems that wic/mic generated a fstab with passno=0 from the
> beginning 
> [3]. What is the reason for that? Was it a conscious decision to do 
> that, or just copy&paste for a different project?
> 
> How would a way forward look like? Should a patch that changes passno
> from 0 to 2 be enough, or do we rather have this parameter
> configurable somehow?

I suspect changing things so fsck was run at every boot would upset
existing use cases, particularly on ext2/3 systems without a journal.
The only option would therefore me to make it configurable.

Cheers,

Richard