[Bug 1125] New: xfs hang on centos 7

[bugzilla-daemon@xxxxxxxxxxx]

Bug ID	1125
Summary	xfs hang on centos 7
Product	XFS
Version	unspecified
Hardware	All
OS	Linux
Status	RESOLVED
Severity	critical
Priority	P5
Component	XFS kernel code
Assignee	xfs-masters@oss.sgi.com
Reporter	danny.webb@thehutgroup.com
Classification	Unclassified
Status	RESOLVED
Resolution	DUPLICATE

Comment # 1 on bug 1125 from D Webb

sorry for the duplicate, the bugzilla was throwing an error when I raised this:

  Bugzilla has suffered an internal error. Please save this page and
send
    it to esa-is@sgi.com with details of what you were doing at
    the time this message appeared.

  URL: http://oss.sgi.com/bugzilla/post_bug.cgi





    There was an error sending mail from 'bugzilla-daemon'
    to '':
    error when closing pipe to /usr/lib/sendmail: 
Traceback:
 at Bugzilla/Mailer.pm line 196
        Bugzilla::Mailer::MessageToMTA(...) called at
Bugzilla/BugMail.pm line 370
        Bugzilla::BugMail::sendMail(...) called at Bugzilla/BugMail.pm
line 272
        Bugzilla::BugMail::Send(...) called at /oss/www/bugzilla
-4.2.5/post_bug.cgi line 226

*** This bug has been marked as a duplicate of bug 1124 ***

0 â gb1-li-lumberjack-004  ~ # rpm -qa|grep xfs
xfsprogs-3.2.0-0.10.alpha2.el7.x86_64
xfsdump-3.1.3-5.el7.x86_64
0 â gb1-li-lumberjack-004  ~ # uname -a
Linux gb1-li-lumberjack-004 3.10.0-123.el7.x86_64 #1 SMP Mon Jun 30 12:09:22
UTC 2014 x86_64 x86_64 x86_64 GNU/Linux

I have a box running CentOS 7.0.1406 on which the /opt partition has hung and
become unresponsive.  Backing disk is a VMDK sitting on a HP 3Par 7200.  

mount reports as rw:

0 â ~/xfs_issue # mount|grep opt
/dev/mapper/vg_root-opt on /opt type xfs
(rw,relatime,seclabel,attr2,inode64,noquota)

if you try and do any actions on the mount (even a lowly ls) the process hangs
in a blocking state.  Nothing has been reported to dmesg, /var/log/messages or
the journalctl logs.

I got some of the trace-cmd logs, but not sure how helpful they'll be as the
mount is already in the hung state.  I can't recreate the issue as I don't know
what causes it.  It has happened a few times on some other of our machines, all
running higher IO applications (postgres, elasticsearch).  

host was writing at ~12MB/s, reading at ~9MB/s at the time (based on our vmware
disk graphs).

---

      You are receiving this mail because:

• You are the assignee for the bug.