Hello
I'm trying to control the amount of cache memory used by Lustre clients
with Lustre 2.0
There is a /proc tuning called max_cache_mb in llite which is
documented in Lustre manual.
Unfortunately, after testing it and checking the source code it seems
this variable is present but it not
We've been seeing occasional hangs on our MDS and I'd like to see if
anyone else is seeing this or can provide suggestions on where to look.
This might not even be a Lustre problem at all.
We're running Lustre 1.8.4 with OFED 1.5.2, and kernel version
2.6.18-194.3.1.el5_lustre.1.8.4.
The
Unfortunately, we've had lot's of reports of IB instability. It does appear
to happen
quite a bit, and generally is not a Lustre problem at all.
- Check all mechanical connections, cables, etc. - replace if need be - many
issues have been cable-related.
- Check firmware versions of all IB cards,
On 2011-03-17, at 6:37 AM, DEGREMONT Aurelien wrote:
I'm trying to control the amount of cache memory used by Lustre clients
with Lustre 2.0
There is a /proc tuning called max_cache_mb in llite which is
documented in Lustre manual.
Unfortunately, after testing it and checking the source
Hello!
On Mar 17, 2011, at 5:44 PM, Andreas Dilger wrote:
I did not find if this was removed or this was partially included in
Lustre 2.0.
What's the current status of this and how can I tell to my client to
avoid caching too many data?
The client VM usage was one of the areas that was
