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/LU-11012 Lustre <p>on following conf : 3 OST 2 POOLS (POOL1=OST0 POOL2=OST1 OST3)</p> <p>lfs setstripe -E 4M -p POOL1 -E 8M -p POOL2 -E EOF -c 3 pfl1</p> <ol> <li>lfs getstripe pfl1<br/> pfl1<br/> lcm_layout_gen: 3<br/> lcm_mirror_count: 1<br/> lcm_entry_count: 3<br/> lcme_id: 1<br/> lcme_mirror_id: 0<br/> lcme_flags: init<br/> lcme_extent.e_start: 0<br/> lcme_extent.e_end: 4194304<br/> lmm_stripe_count: 1<br/> lmm_stripe_size: 1048576<br/> lmm_pattern: raid0<br/> lmm_layout_gen: 0<br/> lmm_stripe_offset: 0<br/> lmm_pool: POOL1<br/> lmm_objects:</li> </ol> <ul class="alternate" type="square"> <li>0: { l_ost_idx: 0, l_fid: <span class="error">&#91;0x100000000:0x1e:0x0&#93;</span> }</li> </ul> <p>lcme_id: 2<br/> lcme_mirror_id: 0<br/> lcme_flags: 0<br/> lcme_extent.e_start: 4194304<br/> lcme_extent.e_end: 8388608<br/> lmm_stripe_count: 1<br/> lmm_stripe_size: 1048576<br/> lmm_pattern: raid0<br/> lmm_layout_gen: 0<br/> lmm_stripe_offset: -1<br/> lmm_pool: POOL2</p> <p>lcme_id: 3<br/> lcme_mirror_id: 0<br/> lcme_flags: 0<br/> lcme_extent.e_start: 8388608<br/> lcme_extent.e_end: EOF<br/> lmm_stripe_count: 2      -&gt; wrong should be 3 (but logic because of pool choice)<br/> lmm_stripe_size: 1048576<br/> lmm_pattern: raid0<br/> lmm_layout_gen: 0<br/> lmm_stripe_offset: -1<br/> lmm_pool: POOL2               &lt;- wrong, no POOL was specified in layout component</p> <p> </p> LU-11012

lfs settripe does not clear pool in PFL

Bug Minor Resolved Fixed Peter Jones CEA Thu, 10 May 2018 07:50:43 +0000 Wed, 5 Aug 2020 13:32:57 +0000 Mon, 10 Sep 2018 17:46:44 +0000 Lustre 2.12.0 0 4 <p>Hi JC,<br/> This is working as expected. The PFL file components will inherit parameters (stripe_count, stripe_size, pool) from the previous component (or the filesystem-wide defaults for the first component) if they are not specified. This avoids the need to specify the same parameter for each component repeatedly.</p> <p>To specify that no pool should be used in your example, you can use <tt>-<del>pool=""</tt> for the last component. In Lustre 2.11, it is also possible to use "<tt></del>-pool=none</tt>" to specify no pool. </p> <p>Hi Andreas,</p> <p>This is a good news. May be I have read the manual too quickly (pdf and man) but I did not find this inherit concept.</p> <p>If absence in manuals is confirmed, we should add it clearly in the manuals</p> <p>Andreas Dilger (andreas.dilger@intel.com) uploaded a new patch: <a href="https://review.whamcloud.com/32463" class="external-link" target="_blank" rel="nofollow noopener">https://review.whamcloud.com/32463</a><br/> Subject: <a href="https://jira.whamcloud.com/browse/LU-11012" title="lfs settripe does not clear pool in PFL" class="issue-link" data-issue-key="LU-11012"><del>LU-11012</del></a> doc: describe layout inheritance in lfs-setstripe.1<br/> Project: fs/lustre-release<br/> Branch: master<br/> Current Patch Set: 1<br/> Commit: db543efd37eaa462c6445a22402b085234323351</p> <p>Oleg Drokin (green@whamcloud.com) merged in patch <a href="https://review.whamcloud.com/32463/" class="external-link" target="_blank" rel="nofollow noopener">https://review.whamcloud.com/32463/</a><br/> Subject: <a href="https://jira.whamcloud.com/browse/LU-11012" title="lfs settripe does not clear pool in PFL" class="issue-link" data-issue-key="LU-11012"><del>LU-11012</del></a> doc: improve the lfs-setstripe.1 man page<br/> Project: fs/lustre-release<br/> Branch: master<br/> Current Patch Set: <br/> Commit: cd4489a34cfd640a99d6a1ceb65303fddd34a7ae</p> <p>Landed for 2.12</p> Development Rank 1|hzzx13: Rank (Obsolete) 9223372036854775807 Severity