Hi Matthew, As Tim said please provide the complete steps which helps us to guide you easily.
It is correct that you shouldn't keep ZFS file systems under FileSystemMountPoints property. You have use Zpools extension property and have to provide the ZFS pool names to be managed. Thanks & Regards Venku Matthew C Aycock wrote: > We are currently running sun cluster 3.2 on solaris 10u3. We are using > ufs/vxvm 4.1 as our shared file systems. However, I would like to migrate to > HA-NFS on ZFS. Since there is no conversion process from UFS to ZFS other > than copy, I would like to migrate on my own time. To do this I am planning > to add a new zpool HAStoragePlus resource to my existing HA-NFS resource > group. This way I can migrate data from my existing UFS to ZFS on my own time > and the clients will not know the difference. > > I made sure that the zpool was available on both nodes of the cluster. I then > created a new HAStoragePlus resource for the zpool. I updated my NFS resource > to depend on both HAStoragePlus resources. I added the two test file systems > to the current dfstab.nfs-rs file. > I manually ran the shares and I was able to mount the new zfs file system. > However, once the monitor ran it re-shared I guess and now the ZFS based > filesystems are not available. > > I read that you are not to add the ZFS based file systems to the > FileSystemMountPoints property. Any ideas? > -- > > This message posted from opensolaris.org > > _______________________________________________ > ha-clusters-discuss mailing list > ha-clusters-discuss at opensolaris.org > http://mail.opensolaris.org/mailman/listinfo/ha-clusters-discuss
