As pointed out by mr Sobolev, the fsck wrappers will blindly try to execute
fsck_$FS regardless of whether its there or not, and fail if it isn't.
This is a gotcha for non-fsck'able fses right now, such as nfs and ntfs.

The solution, which I forgot to add in my email, is to set pass to 0. This
forces fsck to NOT consider the FS for fsck-on-boot, and should make things

Note that swap / procfs in /etc/fstab already use dump/pass = 0, but this is
just to make sure.

Just FYI,


Adrian Chadd                    "The main reason Santa is so jolly is
<[EMAIL PROTECTED]>               because he knows where all the bad girls
                                    live." -- Random IRC quote

To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Reply via email to