On 03/24/2015 09:40 PM, Chris Hunter wrote:
Yes, we still use Martin Hecht's backport of LU-1337 patch.
LU-5237 is used for builds with rhel 6.5 (it patches file
./kernel_patches/targets/targets/2.6-rhel6.target) and likely not
relevant for rhel 6.6.
ATM, we have o2iblnd issues for b1_8 clients with rhel kernels newer
than Oct 2014. IMO, its less work to move to a newer client version
than keep adding patches to b1_8 branch.
thanks for the clarification.
Let's see how b1_8 clients will behave for me.
yale hpc group
On 03/24/2015 03:46 PM, Marcin Dulak wrote:
> On 03/24/2015 06:45 PM, Chris Hunter wrote:
>> We apply patch for LU2800 & LU5237 (b2d09eb6,diff?) to git b1_8
>> branch. A couple optional patches for LU3067 & LU3596 are available.
>> It has become difficult to build 1.8 clients with recent redhat
>> kernels (they tend backport fixes from the 3.10 kernels).
> interesting. Does it mean the patch mentioned here
> is not necessary?
> What does it do?
> What's the purpose of LU5237
> I must say that with only LU2800
> git clone -b b1_8
> branch builds a lustre-client on 2.6.32-504.12.2.el6 for me.
> Best regards,
>> We have not moved to newer client version because of support for
>> legacy OS and (perceived) client performance issues with 2.1/2.4/2.5
>> versions. IMO the b2_5 client issues appear to be resolved so that's
>> likely our upgrade path.
>> Note it appears the b1_8 branch was closed last month and all open
>> pull requests were abandonded.
>> chris hunter
>> yale hpc group
>>> hmm... there are different versions of the patch and different git
>>> repositories around. This one:
>>> works for the github branch you mentioned:
>>> patch -p1 < ~/Downloads/2661328b.diff
>>> patching file lustre/llite/dir.c
>>> Hunk #1 succeeded at 1051 with fuzz 1 (offset -126 lines).
>>> Hunk #2 succeeded at 1197 (offset -112 lines).
>>> Hunk #3 succeeded at 1264 (offset -117 lines).
>> HPDD-discuss mailing list