https://jira.whamcloud.com This file is an XML representation of an issue en-us 9.4.14 940014 05-12-2023 https://jira.whamcloud.com/browse/LUDOC-264 Lustre Documentation <p>There is a "-o" option to the setstripe command that is not documented in the man page and also does not show up in the command usage.It is also not documented in section 18 of the Lustre Manual along with the other setstripe information. The first reference I believe is in 19.2.1.1 but there is no explanation there either.</p> IEEL 2.0.1.1 LUDOC-264

New "-o" option for setstripe missing from manpage and usage

Bug Minor Resolved Duplicate Lustre Manual Triage Gary Hagensen easy Mon, 5 Jan 2015 18:38:14 +0000 Thu, 12 Apr 2018 00:49:22 +0000 Thu, 12 Apr 2018 00:49:22 +0000 0 3 <p>The "-o" option is deprecated and intentionally omitted from the man page and usage message. It should also be removed from the manual. It is replaced by the "-i" option. Using "lfs setstripe -o" should print a message about it being deprecated in favour of "-i", and continue on. </p> <p>I'll move this bug over to LUDOC to update the manual. </p> <p>Hmm, to clarify my previous comment - the old "-o" option is deprecated since 2.3.0, but a new "-o" option (with forward compatible semantics, don't worry) has been added to Lustre 2.7.0 via <a href="https://jira.whamcloud.com/browse/LU-4665" title="utils: lfs setstripe to specify OSTs" class="issue-link" data-issue-key="LU-4665"><del>LU-4665</del></a>. I don't think that the new "-o" functionality is available in the release you are running, but we should document this option clearly in any case. </p> <p>In the context of the example in section 19.2.1.1, it should use "--index|-i" instead. There are also a couple of places where "lfs setstripe" is used with the deprecated positional parameters instead of named arguments that should also be fixed. </p> <p>The new <tt>-o</tt> option is documented in the <tt>lfs-setstripe.1</tt> man page via patch <a href="https://review.whamcloud.com/25741" class="external-link" target="_blank" rel="nofollow noopener">https://review.whamcloud.com/25741</a> since 2.10.</p> <p>IMHO, we should make some kind of automated process to import man pages from the Lustre source into the manual, or just remove them from the manual and reference some website that will do man page rendering for us. Keeping the manual up-to-date by hand is bound to be a losing battle, it is hard enough to keep the actual man pages in sync.</p> <p>Andreas, are you envisioning a man page appendix to the manual perhaps?</p> <p>I am going to open a new LUDOC ticket for the above.  I think this is a very worthwhile investigation.</p> <p><a href="https://jira.whamcloud.com/browse/LUDOC-398" title="Methodology to keep manual in sync with man pages" class="issue-link" data-issue-key="LUDOC-398">LUDOC-398</a> created.</p> <p>Fix the manual sync in <a href="https://jira.whamcloud.com/browse/LUDOC-398" title="Methodology to keep manual in sync with man pages" class="issue-link" data-issue-key="LUDOC-398">LUDOC-398</a>. </p> Related LUDOC-398 Development Rank 1|hzx37b: Rank (Obsolete) 16920 Severity