On Mon, Nov 16, 2015 at 11:40:12AM -0800, Freddie Cash wrote: > On Mon, Nov 16, 2015 at 11:36 AM, Kevin Oberman <rkober...@gmail.com> wrote: > > > On Mon, Nov 16, 2015 at 1:00 AM, Borja Marcos <bor...@sarenet.es> wrote: > > > > > > > > On Nov 14, 2015, at 3:31 PM, Gary Palmer wrote: > > > > > > > You can do thinks in /boot/loader.conf to hard code bus and drive > > > > assignments. > > > > > > > > e.g. > > > > > > > > hint.da.0.at="scbus0" > > > > hint.da.0.target="19" > > > > hint.da.0.unit="0" > > > > hint.da.1.at="scbus0" > > > > hint.da.1.target="18" > > > > hint.da.1.unit="0" > > > > > > Beware, the target number assignment is not predictable. There's no > > > guarantee especially if you replace > > > a disk. > > > > > > > > > > > > > > > > > > Borja. > > > > > > > As already mentioned, unless you are using zfs, use gpart to label you file > > systems/disks. Then use the /dev/gpt/LABEL as the mount device in fstab. > > > > Even if you are using ZFS, labelling the drives with the location of the > disk in the system (enclosure, column, row, whatever) makes things so much > easier to work with when there are disk-related issues. > > Just create a single partition that covers the whole disk, label it, and > use the label to create the vdevs in the pool.
Bad idea. Re-placed disk in different bay don't relabel automaticly. Other issuse where disk placed in bay some remotely hands in data center -- I am relay don't know how disk distributed by bays. Best way for identify disk -- uses enclouse services. I have many sites with ZFS on whole disk and some sites with ZFS on GPT partition. ZFS on GPT more heavy for administration. _______________________________________________ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"