Hi, I just noticed that fsck, when given a single device name, silently exits when it cannot find an appropriate fsck.%s program. Example: (/dev/sda1 is an EFI System Partition, so type=vfat) # fsck -V /dev/sda1 fsck from util-linux 2.36.1 # echo $? 0 Note that it also does not warn about fsck.vfat not being found or anything really. This appears because fsck.c has a "really_wanted" list of fstypes; anything not in there gets the mentioned behaviour. I find this to be very surprising. What are the reasons for this? I could try changing this code path, but I'm not sure if this is expected in the first place? Thanks, Chris
