[LUDOC-171] Document "lfs setstripe" behavior when the second setstripe with a different attribute reset the first attribute value Created: 02/Aug/13  Updated: 02/Nov/18  Resolved: 11/Mar/17

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

Type: Improvement Priority: Minor
Reporter: Young Jong Pao Assignee: Lustre Manual Triage
Resolution: Won't Fix Votes: 0
Labels: None
Environment:

Lustre 2.0 Operations Manual
32.1 lfs


Issue Links:
Duplicate
duplicates LU-11603 lfs setstripe of directory one stripe... Open
Rank (Obsolete): 9527

 Description   

If one stripe attribute is changed on a default directory, then a 2nd setstripe command is issued to change a different stripe attribute, the first change is lost. e.g. if lfs setstripe is used to adjust the stripe size from default, and another lfs setstripe cmd is issued to adjust the stripe count, the stripe size reverts back to the default.

  1. lfs setstripe -s 65536 /mnt/lustre/dir
    crystal:/lus/scratch # lfs getstripe /mnt/lustre/dir
    /mnt/lustre/dir
    stripe_count: 1 stripe_size: 65536 stripe_offset: -1
  1. lfs setstripe -c 2 /mnt/lustre/dir
  2. lfs getstripe /mnt/lustre/dir
    /mnt/lustre/dir
    stripe_count: 2 stripe_size: 1048576 stripe_offset: -1

stripe_size is reset to its default value of 1048576.

Is it possible to document this in the Lustre 2.X Operations Manual and/or in the man page?



 Comments   
Comment by Cory Spitz [ 14/Aug/13 ]

Another way of characterizing this quirk is that setstripe is not 'additive'.

Comment by Andreas Dilger [ 11/Mar/17 ]

This was fixed in the Lustre code in 2.9+ - the setstripe will inherit the parameters that are not specified from the directory.

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