[LU-64] lfs getstripe output inconsistent for directory default value

• Type: Bug
• Resolution: Fixed
• Priority: Minor
• Fix Version/s: Lustre 2.1.0, Lustre 1.8.7
• Affects Version/s: Lustre 1.8.6
• Environment: Linux x86_64
• Severity: 3
• Bugzilla ID: 23,802
• Assignee: Lai Siyao
• Reporter: Prakash Surya (Inactive)

Description

lfs getstripe is printing inconsistent values for default striping values for directories.

Our filesystem default values for striping are: count=2, size=1048576, offset=-1.

If I create a new directory and look at its stripe values I see:

$ mkdir testdir
$ lfs getstripe testdir
testdir
stripe_count: 2 stripe_size: 1048576 stripe_offset: -1

That is perfectly reasonable. But when I set any one of those values, it changes the way that the
other default values are printed:

$ lfs setstripe --count 4 testdir
$ lfs getstripe testdir
testdir
stripe_count: 4 stripe_size: 0 stripe_offset: -1

A user looks at that and says "oh no, it changed the size to zero!". Sure, essentially they are
the same, since 0 in the size field means "use the default".

If I recollect correctly from my experience with bug 19102 (and we are carrying the patch from that
bug), the problem is that when the EA is not set ("lfs setstripe -c 0 -s 0 -o -1" clears the EA),
it looks up the fs defaults and prints them. But when the EA IS set, the command is not looking up
the global defaults for the fields that mean "use the default".

This really needs to be consistent.

See Also: Bugzilla #23802 https://bugzilla.lustre.org/show_bug.cgi?id=23802

Issue Links

• is related to: LU-17655 lfs setstripe --stripe-count 0 --stripe-size 0 cannot change the pfl file/dir to use default attribute
• is related to: LU-995 1.8 <-> 2.1.54 ost-pools 24
• Trackbacks: Lustre 1.8.x known issues tracker While testing against Lustre b18 branch, we would hit known bugs which were already reported in Lustre Bugzilla https://bugzilla.lustre.org/. In order to move away from relying on Bugzilla, we would create a JIRA