Ayaz Anjum wrote:
HI !
I have tested the following scenario
created a zfs filesystem as part of HAStoragePlus in SunCluster 3.2,
Solaris 11/06
Currently i am having only one fc hba per server.
1. There is no IO to the zfs mountpoint. I disconnected the FC cable.
Filesystem on zfs still shows as mounted (because of no IO to
filesystem). I touch a file. Still ok. i did a "sync" and only then the
node panicked and zfs filesystem failed over to other cluster node.
however my file which i touched is lost !!!!
This is to be expected, I'd say.
HAStoragePlus is primarily a wrapper over zfs that manages the
import/export and mount/unmount. It can not and does not provide for a
retry of pending IOs.
The 'touch' would have been part of a zfs transaction group that never
got committed. And it stays lost when the pool is imported on the other
node.
In other words, it does not provide the same kind of high availability
that, say, PxFS for instance provides.
2. with zfs mounted on one cluster node, i created a file and keeps it
updating every second, then i removed the fc cable, the writes are still
continuing to the file system, after 10 seconds i have put back the fc
cable and my writes continues, no failover of zfs happens.
seems that all IO are going to some cache. Any suggestions on whts going
wrong over here and whts the solution to this.
I don't know for sure. But my guess is, if you do a fsync after the
writes and wait for the fsync to complete, then you might get some
action. fsync should fail. zfs could panic the node. If it does, you
will see a failover.
Hope that helps.
-Manoj
_______________________________________________
zfs-discuss mailing list
zfs-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
