Date: Tue, 26 Jan 2010 17:25:03 +0100 From: Gerrit =?ISO-8859-1?Q?K=FChn?= <gerrit@pmp.uni-hannover.de> To: Chuck Swiger <cswiger@mac.com> Cc: freebsd-stable@freebsd.org Subject: Re: ZFS "zpool replace" problems Message-ID: <20100126172503.927e1bb5.gerrit@pmp.uni-hannover.de> In-Reply-To: <FA0BAC0D-35A7-4296-B52C-9D4D8A6CC609@mac.com> References: <20100126143021.GA47535@icarus.home.lan> <20100126160320.6ed67b92.gerrit@pmp.uni-hannover.de> <FA0BAC0D-35A7-4296-B52C-9D4D8A6CC609@mac.com>
index | next in thread | previous in thread | raw e-mail
On Tue, 26 Jan 2010 08:15:27 -0800 Chuck Swiger <cswiger@mac.com> wrote about Re: ZFS "zpool replace" problems: CS> > Meanwhile I took out the ad18 drive again and tried to use a CS> > different drive. But that was listed as "UNAVAIL" with corrupted CS> > data by zfs. CS> There's your problem-- the Silicon Image 3112/4 chips are remarkably CS> buggy and exhibit data corruption: Hm, sure? I would expect the same behaviour (detaching) as with the first drive if the controller was the reason in this case. CS> http://unix.derkeiler.com/Mailing-Lists/FreeBSD/stable/2005-08/0208.html I already thought about replacing the controller to get rid of the detach-problem. However, I cannot do this online and I really would prefer fixing the disk firmware problem first. I could remove the hotspare drive ad14 and use this slot for putting in a replacement disk. Is it possible to get ad18 out of zfs' replacing process? Maybe by detaching the disk from the pool? cu Gerrithome | help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20100126172503.927e1bb5.gerrit>