[LU-13177] add e2fsprog support for SLES15SP1 Created: 28/Jan/20  Updated: 27/May/20  Resolved: 27/May/20

Status: Resolved
Project: Lustre
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Improvement Priority: Minor
Reporter: Minh Diep Assignee: Minh Diep
Resolution: Done Votes: 0
Labels: None

Issue Links:
Related
is related to LU-10335 Ubuntu1604 client sanity-130a: FAIL: ... Resolved
is related to LU-13204 sanity test 100: netstat: command not... Resolved
is related to LU-11310 support for SLES 15 Resolved
is related to LU-13604 rebase Lustre e2fsprogs onto 1.45.6 Resolved
Rank (Obsolete): 9223372036854775807

 Description   

We need SLES15SP1 spec file to build e2fsprogs for lustre



 Comments   
Comment by Gerrit Updater [ 28/Jan/20 ]

Minh Diep (mdiep@whamcloud.com) uploaded a new patch: https://review.whamcloud.com/37357
Subject: LU-13177 build: add support for SLES15SP1
Project: tools/e2fsprogs
Branch: master-lustre
Current Patch Set: 1
Commit: 0943aaa94d1ff46237cee18a52d3ce131a3b632e

Comment by Gerrit Updater [ 06/Feb/20 ]

Andreas Dilger (adilger@whamcloud.com) merged in patch https://review.whamcloud.com/37357/
Subject: LU-13177 build: add support for SLES15SP1
Project: tools/e2fsprogs
Branch: master-lustre
Current Patch Set:
Commit: a50869f6195d54ae856e3754fecf7ddec0c510f7

Comment by Jian Yu [ 11/Feb/20 ]

Hi Minh, could you please make e2fsprogs installed on the SLES15 SP1 node provisioned by loadjenkinsbuild? Thank you.

Comment by Jian Yu [ 17/Feb/20 ]

sanity test 130* are failing on SLES15 SP1 client with RHEL 7.7 server:
https://testing.whamcloud.com/test_sets/9d251eda-50bc-11ea-a90e-52540065bddc

Comment by Andreas Dilger [ 27/May/20 ]

Jian,
the sanity test_130* failures on SLES15 look to be the same as LU-10335, which is a bug in upstream e2fsprogs until 1.45 and 1.44.2, according to comments in that ticket.

Looking at the output of your test log, it shows that the SLES15 SP1 client is using e2fsprogs-1.43.8:

== sanity test 54c: block device works in lustre ====== 17:58:05 (1581731885)
mke2fs 1.43.8 (1-Jan-2018)

This problem is hit if users on SLES15 clients run "filefrag -v" on a Lustre file (or any other file with unknown FIEMAP flags) with the distro e2fsprogs. This is fairly unlikely, but not impossible. If they run with the Lustre-patched e2fsprogs on the client (based on 1.45.2) this problem is already fixed.

Neil,
I'm not sure whether an issue like this should be fixed in the SLES15 e2fsprogs-1.43.8 or not? The original patch is at https://marc.info/?l=linux-ext4&m=151993561511549 or upstream e2fsprogs commit v1.44.1-1-g17a1f2c1 for reference. Of course, updating to e2fsprogs-1.45.6 would be even better than applying just this one fix, but I'm not sure of your policy for mid-series updates.

In any case, this ticket can be closed because the Lustre e2fsprogs are building and passing their internal tests on SLES15, and have shown proper functionality for everything besides this one issue.

Generated at Sat Feb 10 02:59:03 UTC 2024 using Jira 9.4.14#940014-sha1:734e6822bbf0d45eff9af51f82432957f73aa32c.