Re: [Linux-cluster] GFS umount hang after heavy read/write from NFS client

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Sun, Feb 27, 2005 at 10:54:01PM +0800, ?????? wrote:
> Hello,all
> 
> I got messages as follows:
> 	
> GFS: fsid=MyTest:vgtest.2: Unmount seems to be stalled. Dumping lock state...

> What's the meaning ? GFS lock out,or NFS lock out?

GFS can't unlock those two locks for some reason; it's probably a dlm bug.
We saw this in the past, but not recently.  Maybe we're not running enough
GFS/NFS tests.

https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=142993

> And the "umount" process occupied 99.9% of CPU.
> The status of the "umount" process was 
> "29121 ?        R     74:08 umount /mnt/gfs/10".
> 
> I use the kernel 2.6.9.

It would be helpful to know if you see this with the current code in cvs
(which needs 2.6.10) and if it happens often.

-- 
Dave Teigland  <teigland@xxxxxxxxxx>


[Index of Archives]     [Corosync Cluster Engine]     [GFS]     [Linux Virtualization]     [Centos Virtualization]     [Centos]     [Linux RAID]     [Fedora Users]     [Fedora SELinux]     [Big List of Linux Books]     [Yosemite Camping]

  Powered by Linux