Date: Sun, 6 Oct 2019 15:11:18 +1030 From: "O'Connor, Daniel" <darius@dons.net.au> To: ticso@cicely.de Cc: Tomoaki AOKI <junchoon@dec.sakura.ne.jp>, freebsd-current@freebsd.org Subject: Re: nvdXpY dissapears while ZFS pool on it is imported Message-ID: <F38CB886-C753-4A02-9B4A-7674DB461326@dons.net.au> In-Reply-To: <20191005153617.GA77063@cicely7.cicely.de> References: <20191005145021.b38284e6f31f57607b4e5792@dec.sakura.ne.jp> <20191005153617.GA77063@cicely7.cicely.de>
next in thread | previous in thread | raw e-mail | index | archive | help
> On 6 Oct 2019, at 01:06, Bernd Walter <ticso@cicely7.cicely.de> wrote: >=20 > On Sat, Oct 05, 2019 at 02:50:21PM +0900, Tomoaki AOKI wrote: >> Hi. >>=20 >> By sets of commits starting from r351355 though r351747, nvd driver >> creates partitioned GEOM provider like /dev/nvd0p1. >>=20 >> Unfortunately, these partitioned GEOM providers dissapears when >> importing ZFS pool on it leaving /dev/nvd0, and re-appears when >> exporting the pool. >>=20 >> Mounting filesystems other than ZFS (at least msdosfs) doesn't >> affect. >=20 > 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?F38CB886-C753-4A02-9B4A-7674DB461326>