In the last episode (Oct 31), Javier MartÃ*n Rueda said:
> Daniel Jameson escribió:
> > 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:

Another method is to use glabel to label your devices, then build your
zpools on the labeled devices:

(root@dan) /root># glabel status
Name Status Components
label/da0_zfs_local N/A da0s1d
label/da1_zfs_local N/A da1s1d
(root@dan) /root># zpool status
pool: local
state: ONLINE
scrub: none requested

local ONLINE 0 0 0
mirror ONLINE 0 0 0
label/da1_zfs_local ONLINE 0 0 0
label/da0_zfs_local ONLINE 0 0 0

errors: No known data errors

Dan Nelson
_______________________________________________ mailing list
To unsubscribe, send any mail to ""