On Fri, Nov 03, 2017 at 08:07:37AM +0100, Stephane HUC "PengouinBSD" wrote:
>
> Le 11/03/17 à 07:27, Otto Moerbeek a écrit :
> (...)
> >
> > My guess is that if you use duids in fstab then you should call it by
> > that name withc fsck (which uses fstab). Alternatively, specify the
> > mount point.
> >
> > -Otto
> >
> >
>
> Interesting point of view, but:
>
> 1/ I've not change the writing of the fstab file. It is the fact of the
> installer OpenBSD.
>
> 2/ Normally, fsck uses fstab. But, as i wrote in my first message, it
> seems it not doing it.
>
> > # fsck sd0d
> > fsck: sd0d: unknown special file or file system.
It does use fstab, but it cannot find sd0d in fstab.
>
> 3/ By using duids, how i call fsck?
fsck ef1ea0f909e0b8d8.d
>
> # fsck /tmp
>
> ???
That line didn't show properly in my mal client.
>
> 4/ And, yes, calling fsck as:
>
> # fsck /dev/sd0d
>
> seems run correctly!
Yes, because if a full path is given, fsck uses that without
needing to consult fstab.
>
> => But then why is it written in the FAQ this below, since it doesn't
> seem to work? (at least with stable amd64 OpenBSD)
>
> "Before the partition can be mounted again, its integrity must be
> checked with fsck(8):
>
> # fsck sd0h
> "
That's an error in the FAQ. It has been fixed now,
-Otto
