Hi Jason, Thanks for posting the results and configuration to this one. I just noticed the reply :-) Glad you were able to verify nfsv4 does the job.
/Dave On Mon, Mar 23, 2009 at 2:42 PM, JasonCzerak <czer...@jostens.com> wrote: > > I have found a solution!!! > > NFSv4. In it's default configuration on NetApp (DataOnTop 7.3.1, I > suspect > 7.2.x will be the same) and a simple client side mount option: > > mount -t nfs4 server:/vol/vol_mqdata_tst01 mqdata_tst01 > > With in 30 seconds the passive node can pick up the lock! > > NFS V3 will not work in the event of a power fail, panic or other critical > error > > > > JasonCzerak wrote: > > > > > > > > JasonCzerak wrote: > >> > >> I'm using the latest ActiveMQ 5.2.0 Release. I have a clustered > >> configuration for the NetApp filters. So my file system store is very > HA. > >> > >> I'm using the idea documented here: > >> http://activemq.apache.org/shared-file-system-master-slave.html > >> > >> This process works so long as the master sever never crashes hard. > >> (Kernel Panic, or power cable unplug). If I pull the plug, or issue a > >> "echo "c" > /proc/sysrq-trigger" the file system lock is never released > >> "until" the master server comes on line and mounts it's network files > >> sytem, or I kill the lock via NetApp's sm_mon command. > >> > >> Any ideas here to correct this? I'm going to convert the file system to > >> mixed (enable cifs) and see if that helps a little using samba client. > >> > >> > >> > >> > >> > > > > > > bump... anyone? someone had to have tested this configuration by now?!?! > > > > > > > > -- > View this message in context: > http://www.nabble.com/NFS-locking-issue-for-Master-Slave-tp22311102p22666517.html > Sent from the ActiveMQ - User mailing list archive at Nabble.com. > >
