Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 10 Jan 2018 07:04:03 +0000
From:      Grzegorz Junka <list1@gjunka.com>
To:        Ben Woods <woodsb02@gmail.com>
Cc:        freebsd-questions@freebsd.org
Subject:   Re: NVMe ZFS mount
Message-ID:  <c5f34128-b91e-f26d-87c9-68869f265dcb@gjunka.com>
In-Reply-To: <CAOc73CDfe4L03=a6V38Ojr7gxJErXqS2A5Z7VViHySS1h0GgKA@mail.gmail.com>
References:  <3f89d154-d878-a267-66a5-e898cc2621f5@gjunka.com> <CAOc73CDfe4L03=a6V38Ojr7gxJErXqS2A5Z7VViHySS1h0GgKA@mail.gmail.com>

Next in thread | Previous in thread | Raw E-Mail | Index | Archive | Help

On 08/01/2018 22:58, Ben Woods wrote:
> On Tue, 9 Jan 2018 at 6:47 am, Grzegorz Junka <list1@gjunka.com 
> <mailto:list1@gjunka.com>> wrote:
>
>     Hi,
>
>     I've two zfs mirrors, one on two SATA drives and one on two NVMe
>     drives.
>     SATA are used to boot the system. I observed that after booting the
>     system zfs datasets on NVMe drives aren't mounted. The pool is
>     imported
>     and I can list the datasets but command mount doesn't show any mounts
>     apart from the system (SATA) drives.
>
>     Do ZFS datasets on NVMe need any special treatment to be mounted
>     by the
>     system automatically, e.g. an entry in /etc/fstab?
>
>     Thanks
>
>     GrzegorzJ
>
>
> I don’t believe NVMe needs any special treatment, but I haven’t used 
> it. What about the boot order... when you watch it boot, do the NVMe 
> devices show up before the /etc/rc.d/zfs script is run?
>
> Check the “canmount” parameter of each of your datasets.
> zfs get -r canmount,mountpoint,mounted nvmepool
>

NVMe devices are enumerated at about the same time as other devices, 
even slightly before SATA drivers. And much earlier than ZFS tries to 
mount the root directory. It may not be the same as /etc/rc.d/zfs 
script. Would this script leave any trace in dmesg?

I will check the zfs command you gave when I have access to the system 
and report back.

Thanks
GregJ



Want to link to this message? Use this URL: <http://docs.FreeBSD.org/cgi/mid.cgi?c5f34128-b91e-f26d-87c9-68869f265dcb>