Date: Sat, 2 Oct 2010 16:19:56 +0100 From: Bruce Cran <bruce@cran.org.uk> To: Matthew Seaman <m.seaman@infracaninophile.co.uk> Cc: "Marat N.Afanasyev" <amarat@ksu.ru>, stable@freebsd.org, Peter =?ISO-8859-1?Q?Ankerst=E5l?= <peter@pean.org> Subject: Re: device names changes for adX. Message-ID: <20101002161956.00007257@unknown> In-Reply-To: <4CA74C18.2020405@infracaninophile.co.uk> References: <1C68D21A-9539-473D-AEDB-9A8CCE4956F1@pean.org> <4CA73215.9030908@ksu.ru> <D05E5388-C330-47D8-A9F1-2A1C65D11B3E@pean.org> <4CA74C18.2020405@infracaninophile.co.uk>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sat, 02 Oct 2010 16:13:28 +0100 Matthew Seaman <m.seaman@infracaninophile.co.uk> wrote: > In fact, if you glabel the disks while ZFS is still active, it should > instantly recognise all the new names and update the 'zpool status' > output on the fly. Actually, that last is probably the right way to > do things -- you'll update the zpool.cache that way, which means that > ZFS will come up without any remedial action after reboot. Since glabel writes metadata to disk, won't doing this on a disk with a filesystem corrupt something? -- Bruce Cran
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20101002161956.00007257>