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).
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
Note it appears the b1_8 branch was closed last month and all open pull
requests were abandonded.
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).
Ah - that explains it. I added additional files to the series, but
simply re-applied the original round of patches. They would've not
been tagged as v4, while the patches pertaining to the newly-modified
files had v4 in the subject.
I'll be more thorough in future patch revisions. Thanks for the explanation.
On Sat, May 23, 2015 at 8:39 AM, Sudip Mukherjee
> On Sat, May 23, 2015 at 08:09:54AM -0400, Michael Shuey wrote:
>> BTW, you keep mentioning a v5 that I sent. Where is that, exactly?
>> The last round of patches I sent I've kept labeled as "PATCH v4", and
>> I only hit git send-email once. Could you forward me something from
>> this v5 series, so I could see if anything is amiss on my end?
> I think it was not a v5. But what happened is in your series some
> of the patches were marked as v4 and some were not having any version
> so it appeared like a fresh series again. Like 1/13,2/13,3/13 has v4
> but the others donot have a version.