From owner-freebsd-questions@FreeBSD.ORG Sun Nov 15 01:19:32 2009 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 8DEE1106566B for ; Sun, 15 Nov 2009 01:19:32 +0000 (UTC) (envelope-from arab@tangerine-army.co.uk) Received: from smtp-out4.blueyonder.co.uk (smtp-out4.blueyonder.co.uk [195.188.213.7]) by mx1.freebsd.org (Postfix) with ESMTP id 247F08FC14 for ; Sun, 15 Nov 2009 01:19:31 +0000 (UTC) Received: from [172.23.170.145] (helo=anti-virus03-08) by smtp-out4.blueyonder.co.uk with smtp (Exim 4.52) id 1N9Tm6-0003fY-KV for freebsd-questions@freebsd.org; Sun, 15 Nov 2009 01:19:30 +0000 Received: from [94.168.156.45] (helo=Mercury.galaxy.lan.lcl) by asmtp-out5.blueyonder.co.uk with esmtp (Exim 4.52) id 1N9Tm6-0001FB-7E for freebsd-questions@freebsd.org; Sun, 15 Nov 2009 01:19:30 +0000 Date: Sun, 15 Nov 2009 01:19:29 -0000 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Message-ID: <01FB8F39BAD0BD49A6D0DA8F7897392904F747@Mercury.galaxy.lan.lcl> Content-class: urn:content-classes:message In-Reply-To: X-MimeOLE: Produced By Microsoft Exchange V6.5 X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: ZFS disk replacement questions Thread-Index: AcpdMA6AcizAviYGSJaJzvYhGz212gIX5WYg References: <4AF07493.7050208@comcast.net><4AF08A42.9000900@comcast.net> From: "Graeme Dargie" To: "FreeBSD Questions" Subject: RE: ZFS disk replacement questions X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 15 Nov 2009 01:19:32 -0000 -----Original Message----- From: krad [mailto:kraduk@googlemail.com]=20 Sent: 04 November 2009 09:19 To: Steve Polyack Cc: Derrick Ryalls; FreeBSD Questions Subject: Re: ZFS disk replacement questions 2009/11/3 Steve Polyack > Derrick Ryalls wrote: > >> On Tue, Nov 3, 2009 at 10:21 AM, Steve Polyack >> wrote: >> >> >>> Derrick Ryalls wrote: >>> >>> >>>> 1) In the event of a disk failure, how do I trace back the name such >>>> as adX to a physical drive in the enclosure? Is there a way to take >>>> the drive offline then use atacontrol to spin it down or something so >>>> it is easy to identify? >>>> >>>> >>>> >>> In my opinion you are best off using glabel(8) to give names to the >>> disks. >>> This way you can name them in a way that makes sense to you. >>> Additionally, >>> when you create the ZFS pool you will use the glabel'd names. This means >>> that the pool will still come up properly if something causes your >>> devices >>> to be numbered differently (i.e. a drive dies and you happen to reboot >>> the >>> system). >>> >>> >> >> I believe ZFS does this automatically. Supposedly, if you take a >> working set of RAIDZ drives from one machine and put it in another, >> ZFS will figure out the drives since they get labelled by ZFS >> internally. My question concerns how to identify the physical disk in >> question based on the adX or glabel name? Different name in software >> is fine, but if the drive fails I want to make sure I pull the correct >> drive. >> >> >> > This is possible, but I don't remember reading that ZFS handles this > anywhere, and I've seen glabel(8) recommended elsewhere for the same reason. > > Either way, you can add your drives one-by-one and label them on the > enclosure "arraydrive00" and then glabel the individual disks with the same > name. This way when ZFS tells you "arraydrive03" is dead/offline, you can > look at your enclosure and pull the drive with the arraydrive03 label. > > Depending on your controller it is also probably worth it to use one of >>> the >>> SATA-specific drivers in FreeBSD 8 - these are ones like ahci(4) and >>> siis(4). While the generic ata(4) driver will work for pretty much >>> everything, the updated AHCI drivers can take advantage of some more >>> features. Enable the modules at boot to use them. >>> >>> >> >> I will look into it, thanks. The machine in question is 2 year old >> hardware currently with a 3ware raid card. I will be going software >> raid only, but FreeBSD already recognizes the eSATA drive I have >> attached as a backup device so I know the O/S can at least talk to >> sata drives attached to the mobo. >> >> >> > > _______________________________________________ > freebsd-questions@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to " > freebsd-questions-unsubscribe@freebsd.org" > One thing to note about resilvering; unlike most raid systems zfs knows what is going on at the filesystem level as well as block level. Therefore when a drive has to be resilvered, only the data on the drive is rebuilt rather than every block as with most other raid subsystems. eg if you have a 1TB hd but only have 20 Gig of data, only 20 gig is copied/rebuilt rather than 1 TB of data if you were using gvinum/gmirror. This massively speeds up rebuild times and stress on the other drives. However the fuller the drive the less the benefits _______________________________________________ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscribe@freebsd.org" Hi All Sorry to jump in on someone else's question / answer but I have a related query. I notice the previous answer mentioned specific achi(4) driver and Freebsd 8.0 are these available in 7.2 ? Will the achi(4) driver work happily along side the ata driver. I just replaced every drive in my raidz array the dirty way as I could not see away to make the replacement drive show up without doing a reboot, would the achi(4) driver allow me to hot swap the disks in the future ? Regards Graeme