Re: ZFS attaching direct access drives as Scsibus#target#drive#
- From: Javier Martín Rueda <jmrueda@xxxxxxxxxxxxx>
- Date: Fri, 31 Oct 2008 18:26:10 +0100
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...
_______________________________________________
freebsd-current@xxxxxxxxxxx mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscribe@xxxxxxxxxxx"
- Follow-Ups:
- Re: ZFS attaching direct access drives as Scsibus#target#drive#
- From: Dan Nelson
- Re: ZFS attaching direct access drives as Scsibus#target#drive#
- References:
- ZFS attaching direct access drives as Scsibus#target#drive#
- From: Daniel Jameson
- ZFS attaching direct access drives as Scsibus#target#drive#
- Prev by Date: Re: strange behaviour with /sbin/init and serial console
- Next by Date: Re: Atheros AR928x
- Previous by thread: Re: ZFS attaching direct access drives as Scsibus#target#drive#
- Next by thread: Re: ZFS attaching direct access drives as Scsibus#target#drive#
- Index(es):
Relevant Pages
|