Frank Cusack wrote:
On September 13, 2006 7:07:40 PM -0700 Richard Elling
<[EMAIL PROTECTED]> wrote:
Dale Ghent wrote:
James C. McPherson wrote:
As I understand things, SunCluster 3.2 is expected to have support
for HA-ZFS
and until that version is released you will not be running in a
supported
configuration.... and so any errors you encounter are *your fault
alone*.
Still, after reading Mathias's description, it seems that the former
node is doing an implicit forced import when it boots back up. This
seems wrong to me.
Repeat the experiment with UFS, or most other file systems, on a raw
device and you would get the same behaviour as ZFS: corruption.
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.
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.
--
Darren J Moffat
_______________________________________________
zfs-discuss mailing list
zfs-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
