On 03/14/2011 01:34 PM, Terry Haley wrote:
Just to clarify.
I have a shell open that's currently hung doing an umount. So start another
shell and do the lazy umount?
If that hangs as well, then reboot?
Yes. First do an
killall -9 umount
before the other one. Might not work, but do try it. See if your dmesg
output has a call stack at the end indicating a kernel subsystem oops
(worse than a file system shutdown).
If you have to reboot do this:
mount -o remount,sync /
which will put the root into synchronous mode (fewer dirty buffers).
Then if you have to bounce the unit due to the hang (possible), you can
do so with somewhat more safety.
Thanks
-----Original Message-----
From: Joe Landman [mailto:[email protected]]
Sent: Monday, March 14, 2011 1:28 PM
To: Terry Haley
Cc: [email protected]
Subject: Re: [Gluster-users] Quick question regarding xfs_repair
On 03/14/2011 01:22 PM, Terry Haley wrote:
At this point, all I can see in my future is trying to reboot without
remounting and do the repair, which seems like a long shot?
Suggestions?
Yeah, looks like it couldn't write to the log, so it marked the file
system as down. Believe it or not, this may have saved you ...
Do a
umount -l /xfs/mount/point
and wait a bit. It will do the umount in the background. Put a
"noauto" option on this in the /etc/fstab just in case you need to reboot.
BTW: Which kernel is this? The stock Centos kernels xfs support comes
from centosplus. Support for xfs isn't bad, but in general, the
RHEL/Centos kernels aren't (in our experience) stable against very heavy
loads, nor are they terribly good with xfs. 5.5 is better.
Regards
Joe
--
Joseph Landman, Ph.D
Founder and CEO
Scalable Informatics Inc.
email: [email protected]
web : http://scalableinformatics.com
http://scalableinformatics.com/sicluster
phone: +1 734 786 8423 x121
fax : +1 866 888 3112
cell : +1 734 612 4615
_______________________________________________
Gluster-users mailing list
[email protected]
http://gluster.org/cgi-bin/mailman/listinfo/gluster-users
