[LU-5276] ldiskfs patches for FC19

• Status: Resolved
• Project: Lustre
• Fix Version/s: Lustre 2.7.0
• Type: Improvement
• Priority: Minor
• Reporter: Yang Sheng
• Assignee: Yang Sheng
• Resolution: Fixed

Description

This ticket intended to track ldiskfs patches work on FC19 3.7 kernel.

Issue Links

• is related to: LU-5992 ldiskfs patches for FC20
• is related to: LU-3373 ldiskfs patches for FC19
• is related to: LU-4993 support for 3.14 linux kernel
• is related to: LU-5425 Test failure on test suite conf-sanit...

Comments

[Jodi Levi (Inactive)]

This is to track the remaining patch http://review.whamcloud.com/#/c/8116

[James A Simmons]

Patch to enable FC20 ldiskfs support:

http://review.whamcloud.com/#/c/11000

Can someone link this ticket to LU-4993. Thank you.

[Andreas Dilger]

The patch http://review.whamcloud.com/11088 that was landed under this bug to remove the "extents" mount option was reverted via http://review.whamcloud.com/11267 because it was causing test failures in conf-sanity test_32a and test_32b. It seems these test images contain mount options with the "extents" string in their configurations, so it isn't just a matter of removing any current users of this option, we also need to handle upgrades from old filesystems (which is exactly what conf-sanity.sh test_32* is about).

I think what is needed is to check what version of Lustre stopped setting the "extents" mount option explicitly, and then we can make a decision based on when we deprecate support for that version and/or require a --writeconf before mounting. It would also be helpful to document this information in the header for these patches so this is easy to find in the future.

[Yang Sheng]

Looks like we still write 'extent' and '^extetns'(OST) in configuration. In fact, It just needed in mkfs stage and doesn't need in runtime environment. So can we remove 'extents' flag in mkfs first?

[Jodi Levi (Inactive)]

Patches for FC19 landed to Master.