> And why would we want a pool imported on another host, or not marked > as belonging to this host, to show up as faulted? That seems an odd > use of the word. Unavailable, perhaps, but not faulted.
It certainly changes some semantics... In a UFS/VxVM world, I still have filesystems referenced in /etc/vfstab. I might expect (although have seen counterexamples), that if my VxVM group doesn't autoimport, then obviously my filesystems don't mount, and that will halt startup until I deal with the problem. This is often a good thing. With ZFS and non-legacy mounts, I don't really have a statement that the ZFS filesystem /path/to/critical/resource must be mounted at boot time other than the configuration of the pool. I guess I need to make some more explicit dependencies for services if I want some of them to notice. (Unfortunately creating/removing dependences takes a bit more work than maintaining a vfstab today). -- Darren Dunham [EMAIL PROTECTED] Senior Technical Consultant TAOS http://www.taos.com/ Got some Dr Pepper? San Francisco, CA bay area < This line left intentionally blank to confuse you. > _______________________________________________ zfs-discuss mailing list zfs-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
