[Linux-cluster] unable to umount GFS

[Adam Manthei]

On Wed, Dec 22, 2004 at 03:21:33PM -0000, Raj  Kumar wrote:
> Typo in my posting's first line: I was unable to umount (not mount).
> 
> >what happens on umount?  Is it telling you that the file system is busy on
> >umount?  does it just hang?
> yes, it tells mountpoint is busy. So I used lsof and fuser to see who is using it. But no pid's were returned.

If it says it's busy, then the filesystem is in use.  You weren't by chance
trying to umount while in the directory?  while another filesystem was
mounted on GFS?
 
> >is lock_gulmd running on the client?
> yes, it was running.

> >is lock_gulmd quorate?
> I'm not running the cluster suite, just GFS. How do I check if lock_gulmd is quorate? On cluster I can use this command and check number of votes:
> cat /proc/cluster/status
>   

gulm_tool getstats <servername> | grep quorum

This will tell you what it has and needs for quorum.

> >did you ever restart lock_gulmd on the node mounting gfs?
> No. 
> 
> I was experimenting different test cases to check GFS stability for our purpose. I had exported a GFS file system as NFS to node2. node3 now accesses via samba the GFS file system on node2 (node2 uses NFS). So it is GFS(node1)-->NFS(node2)-->SAMBA(node3). I was unable to save files from node3 onto GFS filesystem. This has left many smbd daemons on node2 in 'D' state (Disk Sleep). The samba daemons might be holding some locks... but it is not clear. I restarted all the nodes and cluster is fine. How do I check if there are any file corruptions? using gfs_fsck?
> 
> Thanks,
> Raj
> 
> On Wed, 22 Dec 2004 Adam Manthei wrote :
> >On Wed, Dec 22, 2004 at 12:44:58AM -0000, Raj  Kumar wrote:
> > > Hello,
> > >
> > > I was unable to mount a GFS filesystem. fuser -m mountpoint shows no processes. lsof | grep mountpoint|pool also doesn't return any pid using it. gfs_tool lockdump mountpoint however shows some locks. How do I safely unmount the GFS file system now?
> > >
> > > Please help!!
> >
> >is lock_gulmd running on the client?
> >
> >is lock_gulmd quorate?
> >
> >what happens on umount?  Is it telling you that the file system is busy on
> >umount?  does it just hang?
> >
> >did you ever restart lock_gulmd on the node mounting gfs?
> >(see https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=129193)
> >
> >--
> >Adam Manthei  <amanthei at redhat.com>

-- 
Adam Manthei  <amanthei at redhat.com>