Date: Wed, 23 Dec 2009 19:32:53 -0500 From: Rich <rincebrain@gmail.com> 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: <5da0588e0912231632v14b5dfcdrc913a9deeac9e38a@mail.gmail.com> In-Reply-To: <ED4451CA-E72F-4FA2-B346-77C44018AC3E@gmail.com> References: <048AF210-8B9A-40EF-B970-E8794EC66B2F@gmail.com> <4B315320.5050504@quip.cz> <ED4451CA-E72F-4FA2-B346-77C44018AC3E@gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
That's fascinating - I'd swear it used to be the case (in Solaris-land, at least) that resilvering with a smaller vdev resulted in it shrinking the available space on other vdevs as though they were all as large as the smallest vdev available. In particular, I'd swear I've done this with some disk arrays I have laying around with 7x removable SCA drives, which I have in 2, 4.5, 9, and 18 GB varieties... But maybe I'm just hallucinating, or this went away a long time ago. (This was circa b70 in Solaris.) I know you can't do this in FreeBSD; I've also run into the "insufficient space" problem when trying to replace with a smaller vdev. - Rich On Wed, Dec 23, 2009 at 7:29 PM, Steven Schlansker <stevenschlansker@gmail.com> wrote: > > On Dec 22, 2009, at 3:15 PM, Miroslav Lachman wrote: > >> 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= (< =A01MB) >>> and whenever one of them goes down and I bring the pool up, it helpfull= y (?) >>> 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? =A0I'm >>> eventually going to keep expanding each of my drives one megabyte at a = time >>> using gconcat and space on another drive! =A0Very 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) > > > Yes, this makes sense. =A0Unfortunately, I didn't do this when I first ma= de the array > as the documentation says you should use whole disks so that it can enabl= e the write > cache, which I took to mean you shouldn't use a partition table. =A0And n= ow there's no > way to fix it after the fact, as you can't shrink a zpool even by a singl= e > MB :( > > > _______________________________________________ > freebsd-fs@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-fs > To unsubscribe, send any mail to "freebsd-fs-unsubscribe@freebsd.org" > --=20 [We] use bad software and bad machines for the wrong things. -- R. W. Hammi= ng
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?5da0588e0912231632v14b5dfcdrc913a9deeac9e38a>