Date: Sat, 2 Mar 2013 08:18:56 +0200 From: Daniel Kalchev <daniel@digsys.bg> To: Freddie Cash <fjwcash@gmail.com> Cc: FreeBSD Filesystems <freebsd-fs@freebsd.org> Subject: Re: benefit of GEOM labels for ZFS, was Hard drive device names... serial numbers Message-ID: <F89F2896-B2CB-46B2-AACE-E04D53AB3B0C@digsys.bg> In-Reply-To: <CAOjFWZ5DH2wb8m2eTX-d1bxdfGLOCpDB06%2BRKqA7kL5Lyvawkg@mail.gmail.com> References: <512FE773.3060903@physics.umn.edu> <CAOjFWZ5DH2wb8m2eTX-d1bxdfGLOCpDB06%2BRKqA7kL5Lyvawkg@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 01.03.2013, at 05:30, Freddie Cash <fjwcash@gmail.com> wrote: > For example, we use the following pattern: encX-A-# >=20 > Where X tells you which enclosure it's in, A tells you which column it's i= n > (letters start at A increasing to the right), and # tells you the disk in > the column, numbered top-down. We use similar labeling, but usually rely on the vendor's drive cage labels a= nd do not use column numbers. But if your enclosures have column labels it m= akes sense. Anything that makes it obvious for the technician to locate the d= rive without consulting too much documentation makes sense. Just stick to on= e coordinate system for all enclosures in one location :) Using labels greatly simplifies ZFS management in cases of disaster - you ma= y have to boot another recovery system and no scripts or hard wired drive in= formation may be available to assist you. Daniel=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?F89F2896-B2CB-46B2-AACE-E04D53AB3B0C>