Date: Fri, 31 Oct 2008 18:26:10 +0100 From: =?ISO-8859-1?Q?Javier_Mart=EDn_Rueda?= <jmrueda@diatel.upm.es> To: Daniel Jameson <DJameson@emerytelcom.com> Cc: freebsd-current@freebsd.org Subject: Re: ZFS attaching direct access drives as Scsibus#target#drive# Message-ID: <490B3FB2.2040106@diatel.upm.es> In-Reply-To: <0A8710FF880BBB4687AEC66F9DCF7D0C26B462@SERVER1.emerytelcom.com> References: <0A8710FF880BBB4687AEC66F9DCF7D0C26B462@SERVER1.emerytelcom.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Daniel Jameson escribió: > Hello, > > > > I'm in the process of building several zfs pools for a backup-server, > the machine has 2 24 port sata 3 controllers and 48 1TB drives for > storage. I've done a little testing and found that building a pool by > using the da# device names can be inconsistent. For example if a device > is lost from the first controller and the box is re-booted all the da#s > shuffle up, which creates problems with adjacent pools, and the > potential for catastrophic failure. In the Sun documentation zpool > allows a pool to be built by using S#T#D# (Scsibus Target Drive) syntax, > when I attempt it in FBSD It returns:" cannot use '/dev/c0t0d0': must be > a GEOM provider" does anyone know a way to statically map a > scsibus/target/drive to a specific da# or a fix to allow specific drives > by target numbers to be added to a zpool? > You can edit /boot/device.hints to associate specific SCSI ids to specific da entries. Try something like this: hint.da.0.at="scbus0" hint.da.0.target="0" hint.da.0.unit="0" And so on...
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?490B3FB2.2040106>