This is https://jira.whamcloud.com/browse/LU-8417 "setstripe -o does not work on directories", which has not been implemented yet.
That said, setting the default striping to specific OSTs on a directory is usually not the right thing to do. That will result in OST imbalance. Equivalent mechanisms include OST pools (which also allow a subset of OSTs to be used, unlike -o currently does), and has the benefit of labeling files with the pool to find them easier in the future (eg. for migrating out of the pool). What is the end goal that you are trying to achieve? Cheers, Andreas On Nov 9, 2018, at 09:28, Mohr Jr, Richard Frank (Rick Mohr) <[email protected]<mailto:[email protected]>> wrote: On Nov 8, 2018, at 11:44 AM, Ms. Megan Larko <[email protected]<mailto:[email protected]>> wrote: I have been attempting this command on a directory on a Lustre-2.10.4 storage from a Lustre 2.10.1 client and I fail with the following message: lfs setstripe -c 4 -S 1m -o 1,2-4 custTest/ error on ioctl 0x4008669a for 'custTest' (3): Invalid argument error: setstripe: create striped file 'custTest' filed: Invalid argument Do you get the same error if you try to run this on a file instead of a directory? Also, don’t you typically need to add the “-d” option when setting stripe parameters for a directory? -- Rick Mohr Senior HPC System Administrator National Institute for Computational Sciences http://www.nics.tennessee.edu _______________________________________________ lustre-discuss mailing list [email protected]<mailto:[email protected]> http://lists.lustre.org/listinfo.cgi/lustre-discuss-lustre.org
_______________________________________________ lustre-discuss mailing list [email protected] http://lists.lustre.org/listinfo.cgi/lustre-discuss-lustre.org
