Date: Wed, 23 Dec 2009 00:15:44 +0100 From: Miroslav Lachman <000.fbsd@quip.cz> To: Steven Schlansker <stevenschlansker@gmail.com> Cc: freebsd-fs@freebsd.org Subject: Re: ZFS: Can't repair raidz2 (Cannot replace a replacing device) Message-ID: <4B315320.5050504@quip.cz> In-Reply-To: <048AF210-8B9A-40EF-B970-E8794EC66B2F@gmail.com> References: <048AF210-8B9A-40EF-B970-E8794EC66B2F@gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Steven Schlansker wrote: > As a corollary, you may notice some funky concat business going on. > This is because I have drives which are very slightly different in size (< 1MB) > and whenever one of them goes down and I bring the pool up, it helpfully (?) > expands the pool by a whole megabyte then won't let the drive back in. > This is extremely frustrating... is there any way to fix that? I'm > eventually going to keep expanding each of my drives one megabyte at a time > using gconcat and space on another drive! Very frustrating... You can avoid it by partitioning the drives to the well known 'minimal' size (size of smallest disk) and use the partition instead of raw disk. For example ad12s1 instead of ad12 (if you creat slices by fdisk) of ad12p1 (if you creat partitions by gpart) You can also use labels instead of device name. Miroslav Lachman
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4B315320.5050504>