A quick search suggests the default value is 1024.
From: lustre-discuss [lustre-discuss-boun...@lists.lustre.org] on behalf of
E.S. Rosenberg [esr+lus...@mail.hebrew.edu]
Sent: Tuesday, September 08, 2015 4:09 PM
To: lustre-discuss@lists.lustre.org
Subject:
Hi all,
I'm trying to build lustre 2.7 with kernel 4.1.6 from source, I applied the
patches that appear in:
lustre/kernel_patches/series/3.x-fc18.series
The following patch:
blkdev_tunables-3.7.patch
Seems to be adding the use of a define that left the kernel a while ago:
BLK_DEF_MAX_SECTORS
As f
Thanks a lot for the response. Seems like we need to explore upgrading the
servers. Do you happen to know how smooth that process is likely to be? We have
lustre 1.8.8 on CentOS 5.4 there, I presume we need to upgrade the OS and then
follow the upgrade procedure in the lustre manual, maybe it is
Which would be easily merged with the mainline kernel git instead of the
current setup of manually patching
Thanks,
Eli
___
lustre-discuss mailing list
lustre-discuss@lists.lustre.org
http://lists.lustre.org/listinfo.cgi/lustre-discuss-lustre.org
I was thinking the same thing, except the staging client might work, and
might be in Ubuntu 14.
I can¹t recall the 1.8<->2x interop rules, though. IIRC, it was only 1.8
clients that played well, but I could be wrong.
-Ben Evans
On 9/8/15, 11:16 AM, "lustre-discuss on behalf of Patrick Farrell"
Lewis,
My own understanding is you are out of luck - the 1.8 client cannot
realistically be brought forward to newer kernels. Far too many changes over
too long a period.
As far as version compatibility, I believe no newer clients will talk to
servers running 1.8. If any will, they would be
Hello-
We have a working 1.8 lustre cluster with which we are very happy. The object
and metadata servers are running one of the recommended CentOS distributions
(5.4), but the clients are all Ubuntu 10.04 LTS, with kernel 2.6.32. It is not
feasible for us to change on the client side to a dif
