In regard to: [Networker] RHEL6/XFS/NW 7.6.2, Francis Swasey said (at...:

Before I ask EMC and RedHat to point fingers at each other,

:-)

I thought
I'd ping you illustrious folk to see if any of you know of anything that
would indicate I have either royally screwed up by choosing XFS or if
perhaps you have more experience with XFS and can suggest something in
the way of tuning to "make it stop" (right now, I'm using mostly default
options, with the single exception of adding the inode64 option to allow
inodes to be placed beyond the first 4TB of the 17TB disk).

XFS obviously isn't as widely tested on Linux as something like ext3, but
sometimes it's the only viable choice.

It's been a while since I've used it on Linux and the usage pattern was
different, so I don't think I can offer any useful configuration
suggestions for XFS.

If you haven't already done so, though, I highly suggest you enable the
Linux "Magic SysRq" key on the troublesome storage node, as well as enable
netdump(8).  Have the SysRq key guide printed out and available to your
operators, so they can get a task list, lock list, memory state, etc.
Might help Red Hat track down what's going on.

Tim
--
Tim Mooney                                             Tim.Mooney AT ndsu DOT 
edu
Enterprise Computing & Infrastructure                  701-231-1076 (Voice)
Room 242-J6, IACC Building                             701-231-8541 (Fax)
North Dakota State University, Fargo, ND 58105-5164

To sign off this list, send email to listserv AT listserv.temple DOT edu and type 
"signoff networker" in the body of the email. Please write to networker-request 
AT listserv.temple DOT edu if you have any problems with this list. You can access the 
archives at http://listserv.temple.edu/archives/networker.html or
via RSS at http://listserv.temple.edu/cgi-bin/wa?RSS&L=NETWORKER