On Thu, Sep 07, 2006 at 06:31:30PM -0700, Darren Dunham wrote: > > 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).
Currently, a faulted pool will not prevent you from coming up (that is, filesystem/* services will continue to come up). There are already some folks thinking about how failed /etc/vfstab mounts should affect boot (not everyone wants it to fail coming up). Similar thought should probably be given to what it means for a faulted pool and/or dataset. - Eric -- Eric Schrock, Solaris Kernel Development http://blogs.sun.com/eschrock _______________________________________________ zfs-discuss mailing list zfs-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
