[lustre-discuss] [EXTERNAL] lfs getstripe --ost fails

[Mohr, Rick]

John,

The reason your command fails is that you didn't specify a UUID for an ost after the option.  However, if you are trying to retrieve the starting ost, then you don't know it ahead of time and can't supply it on the command line.  So that option is clearly not working as intended.  Plus, the man page does not indicate --ost requires an option, but the error output does (a clear discrepancy).  I would suggest filing a bug report.

--Rick


On 4/1/26, 5:40 PM, "lustre-discuss on behalf of John Bauer via lustre-discuss" <lustre-discuss-bounces at lists.lustre.org> wrote:

All,
While working with the lfs getstripe command I came across this. The getstripe --pool works as expected, but getstripe --ost fails. The usage info that gets printed after the fail indicates it should be a valid option. Am I misunderstanding the man page?
John
[e63414 at cor-login dd]$ lfs getstripe --pool /lustre/e63414/mkstempvl4mYj
flash


[e63414 at cor-login dd]$ lfs getstripe --ost /lustre/e63414/mkstempvl4mYj
error: getstripe: no filename|pathname
To list the layout pattern for a given file or files in a
directory or recursively for all files in a directory tree.
usage: getstripe [--ost|-O UUID] [--quiet|-q] [--verbose|-v]
[--stripe-count|-c] [--stripe-index|-i] [--fid|-F]
[--pool|-p] [--stripe-size|-S] [--directory|-d]
[--mdt-index|-m] [--recursive|-r] [--raw|-R]
[--layout|-L] [--generation|-g] [--yaml|-y]
[--help|-h] [--component-id|-I[=COMP_ID]]
[--component-flags[=COMP_FLAGS]]
[--component-count]
[--extension-size|--ext-size|-z]
[--component-start[=[+-]COMP_START]]
[--component-end[=[+-]COMP_END]|-E[[+-]comp_end]]
[[!] --mirror-index=[+-]INDEX |
[!] --mirror-id=[+-]MIRROR_ID] [--mirror-count|-N]
[--no-follow]
<directory|filename> ...