> > Again, the difference is that with UFS your filesystems won't auto > > mount at boot. If you repeated with UFS, you wouldn't try to mount > > until you decided you should own the disk. > > Normally on Solaris UFS filesystems are mounted via /etc/vfstab so yes > the will probably automatically mount at boot time.
I think the idea is that in a cluster environment, you would not. The cluster would leave /etc/vfstab empty and mount only explicitly when it thought it safe. The explicit mounts make no changes to the boot-time behavior of the system. With ZFS, explicit mounts do change the boot-time behavior (via the zfs cache) in a way that appears to be difficult to override easily. > If you are either removing them from vfstab, not having them there, or > setting the 'mount at boot' flag in /etc/vfstab to off; then what ever > it is that is doing that *is* your cluster framework. You need to > rewrite/extend that to deal with the fact that ZFS doesn't use vfstab > and instead express it in terms of ZFS import/export. Exactly. What method could such a framework use to ask ZFS to import a pool *now*, but not also automatically at next boot? (How does the upcoming SC do it?) Does it just nuke the cache early in the boot and then force import any pools that aren't under the cluster solution, or have I just missed a simple option? -- 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
