nvdXpY dissapears while ZFS pool on it is imported

[O'Connor, Daniel]

> On 6 Oct 2019, at 01:06, Bernd Walter <ticso at cicely7.cicely.de> wrote:
> 
> On Sat, Oct 05, 2019 at 02:50:21PM +0900, Tomoaki AOKI wrote:
>> Hi.
>> 
>> By sets of commits starting from r351355 though r351747, nvd driver
>> creates partitioned GEOM provider like /dev/nvd0p1.
>> 
>> Unfortunately, these partitioned GEOM providers dissapears when
>> importing ZFS pool on it leaving /dev/nvd0, and re-appears when
>> exporting the pool.
>> 
>> Mounting filesystems other than ZFS (at least msdosfs) doesn't
>> affect.
> 
> It is not ZFS itself, it is the use of /dev/diskid/*, which ZFS prefers
> to open.
> Either explicitly import the volume with /dev/nvd* or use the other
> partitions with /dev/diskid/*
> What really sucks is that volume labels also disappear - e.g. /dev/msdosfs.

It Would Be Nice (tm) if all of the aliases were symlinks pointing to the canonical device which didn't disappear when it was opened.

No idea how feasible that is though :)

--
Daniel O'Connor
"The nice thing about standards is that there
are so many of them to choose from."
 -- Andrew Tanenbaum