chas williams - CONTRACTOR wrote: > In message <[EMAIL PROTECTED]>,Yuriy Umanets writes: > >> Will fix it tomorrow, but the fix will come to current 1.6 branch so >> only will be available in next release. >> > > hi Williams, > if you have a fix, i can apply it as a point patch to my local copy. > its not a huge deal. > It turned out to be a bit more complex issue which was already observed earlier in bug 13766. Some more info on this bug is also located in bug 14353. It is related to aggressive memory pressure event handling in server side ldlm pools code. I have the patch (quite big, 55K) for 1.6.4 version. It fixes this as well as other related things. But it is completely not tested on serious HW and I would not like to make you deal with stuff unless you ask for it.
If you really like to give it a try and will not use this on some alive storage with sensitive data, you need to update your local copy to 1.6.4 and I will send you the patch. But as soon as I think you only want to make lustre behave like 1.6.2 about IO performance, you probably do not need this and may disable this feature by configure key --disable-lru-resize Thanks. -- umka _______________________________________________ Lustre-discuss mailing list [email protected] https://mail.clusterfs.com/mailman/listinfo/lustre-discuss
