Veritas Cluster Filesystem on RedHat - du command time anomaly
Red HatThis forum is for the discussion of Red Hat Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Veritas Cluster Filesystem on RedHat - du command time anomaly
Hi,
I have a 2 node RH 5u4 64-bit. I have installed and configured the latest Veritas CFS (Cluster File System) which also uses Veritas Cluster Server. File system if VxFS. Storage is on EMC Symmetrix arrays with Veritas Mirroring between the arrays.
We have noticed that running 'du -hs' on the shared directory/filesystem where it takes about 3 minutes on one node and 30 - 45 minutes on the other node.
I've been running strace on 'du'. 'du' runs an 'lstat' on each file (66,000+ files). On the slower node, the ave time spent in 'du' is about .001 seconds longer, which accounts for the 30-45 minutes. Also, the standard deviation is much larger, which means to me that the lstat times are all over the place!
Another interesting thing is that iozone profiling shows that the i/o rates from both nodes are darn near identical, with no anomalies at various buffer & file sizes! And, iostat looks really good as does 'vxdmpadm iostat show'!!!
Any ideas on this one? Is lstat an issue on large clustered directories?
Great ideas for checking; I should have pointed out that both nodes are identical hardware, the rpm's installed post build and any configuration post build are the same and both are built from the same kickstart image.
Currently, WCM is running, but there's little to no activity going on this server as the app guys are waiting on me to hand it over to them (formally).
I'll recheck the kernel parms ... they have been adjusted per Oracle recommendations; Oracle now owns WCM and we also have an oracle client that connects to a back-end database which stores information about the files in the clustered file system. I'll check on Monday!
Packages on both servers are identical as is hardware; Veritas DMP is setup to have the ruleset min-q-length on all dmp devices and that appears to be working as expected.
Kernel Settings are identical on both nodes, too.
strace of du command shows a large 'delay' after getdents is called, but only from the *slow* node:
And, that is very consistent but happens on both nodes even if I swap the CFS Primary Server!
I have a feeling that some meta-data update occurs after calling getdents and that requires some communication/handshake that shows up under lstat as lstat is probably waiting on something to happen within the volume/filesystem.
Sound familiar to anyone?
Last edited by DantePasquale; 04-12-2010 at 01:13 PM.
Reason: more info
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.