Please don't reply to lustre-devel. Instead, comment in Bugzilla by using the following link: https://bugzilla.lustre.org/show_bug.cgi?id=11665
Depending on how you create the files, there may be a way. You can specify stripe size for a file that does not yet exist, and Lustre will create that file. Depending on your application this may be a workaround. There is some odd behavior with wildcarded names, due to shell interactions. If an expansion of the wild-carded file name already exists, the shell will expand it into a list, which causes lfs setstripe to exit with an error. This is really somewhat of a bug, as lfs setstripe should really allow a list of files as a param. If an expansion of the wild-carded file name does not exist, lfs will create a file and name it with the wild card. Thus, if we have a directory with the files dummy.1 and dummy.2 # lfs setstripe dummy.* 0 -1 1 will exit with an error, but # lfs setstripe bob.* 0 -1 1 will create a new file named 'bob.*' - not especially useful behavior, but 'bob.*' is a legal filename, so we're somewhat stuck with it. So the answer is you cannot give lfs setstripe a pattern as a file name. _______________________________________________ Lustre-devel mailing list [email protected] https://mail.clusterfs.com/mailman/listinfo/lustre-devel
