Date: Fri, 11 Aug 2017 09:24:59 +0300 From: Vitalij Satanivskij <satan@ukr.net> To: Chris Ross <cross+freebsd@distal.com> Cc: freebsd-fs@freebsd.org Subject: Re: ZFS: Device names in a raidz1 pool after changing controllers Message-ID: <20170811062459.GA30374@hell.ukr.net> In-Reply-To: <6976A8FF-994C-48D3-99B1-2181CD15C94C@distal.com> References: <6976A8FF-994C-48D3-99B1-2181CD15C94C@distal.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Hello for disabling diskid kern.geom.label.disk_ident.enable="0" same for gptid kern.geom.label.gptid.enable="0" same for gpt label kern.geom.label.gpt.enable="0" In /boot/loader.conf Just choose how you prefer And if tank isn't boot pool you can export and import with -d option to choose which naming of devices to use (eg /dev/gpt /dev/diskid etc) Chris Ross wrote: CR> CR> I’m moving one of my systems from the on-board SATA controller to a SATA/SAS controller. A side effect of the first experiement, of moving half of the SATA drives onto the new controller, is that they went from being named “ada2” and “ada3” to being “da0” and “da1”. CR> CR> ZFS, happily, just coped with this. But, the raidz1 pool that was spread across parts of disks on both sides, now looks like: CR> CR> NAME STATE READ WRITE CKSUM CR> tank ONLINE 0 0 0 CR> raidz1-0 ONLINE 0 0 0 CR> ada1p4 ONLINE 0 0 0 CR> diskid/DISK-WOL240261932p1 ONLINE 0 0 0 CR> diskid/DISK-WOL240261922p1 ONLINE 0 0 0 CR> CR> (where before, the second and third components were ada2p1 and ada3p1). CR> CR> 1) Is it possible to rename how zpool lists these disk identifiers? CR> 2) If so, is there consensus on whether device names or diskid are “better”, perhaps simply “more recommended"? In a way, I’d like an idea how to tell which disk in the enclosure is which device in the pool, which I think diskid would make harder… CR> CR> Thanks. CR> CR> - Chris CR>
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20170811062459.GA30374>