On Tue, Oct 14, 2008 at 01:56:01PM -0600, Daniel Jameson wrote: > 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? The Sun documentation is not at all relevent when you get to the disk attachment bit since we use geom. You can wire da# allocation down which should do what you want. There's some documentation in sys/conf/NOTES. -- Brooks
This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:39:36 UTC