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-96 Lustre <p>llite_loop.ko will not currently build on systems with &gt;= 64k pages. 64k is apparently now the default in RHEL6 on ppc64 systems, so this may be an issue. For LLNL, we really only need client support, so we will be fine in the short term if <a href="https://jira.whamcloud.com/browse/LU-94" title="llite_lloop should not be part of the client build" class="issue-link" data-issue-key="LU-94"><del>LU-94</del></a> is integrated.</p> <p>By longer term, this problem in lustre/llite/lloop.c: needs to be addressed:</p> <p> CLASSERT(CFS_PAGE_SIZE &lt; (1 &lt;&lt; (sizeof(unsigned short) * 8)));<br/> blk_queue_logical_block_size(lo-&gt;lo_queue,<br/> (unsigned short)CFS_PAGE_SIZE);</p> <p>Lustre is setting the blk_queue_logical_block_size to the page size, but because it is an unsigned short (of 2 bytes) any number over 65535 will be truncated.</p> RHEL6, ppc64 LU-96

llite_loop.ko does not support >= 64k pages

Bug Minor Resolved Fixed Niu Yawei Christopher Morrone Wed, 23 Feb 2011 18:15:29 +0000 Mon, 21 Mar 2011 06:55:28 +0000 Mon, 21 Mar 2011 06:55:27 +0000 0 4 <p>This problem was imported at:</p> <p>commit 5bae6efc7d2f8c117d96483cc11d1d428bd6abd4<br/> Author: yangsheng &lt;sheng.yang@oracle.com&gt;<br/> Date: Thu Oct 21 16:23:42 2010 +0800</p> <p> b=22514 Update RHEL5.5 &amp; OEL5.5 to latest kernel.</p> <p> --RHEL5 2.6.18-194.17.1.el5.<br/> --OEL5 2.6.18-194.17.1.0.1.el5.<br/> --Switch using 'inkernel' OFED stack.<br/> --Build fixes for ppc64 &amp; ia64.</p> <p>Investigating it</p> <p>Hi, Xiong<br/> I don't see how this patch can fix the problem, since the 'hardsect_size'/'logical_block_size' is unsigned short in kernel.</p> <p>Hi, Andreas<br/> Do you have any thoughts/ideas about long term solution for this issue? I'll take it as a lower priority job. Thank you.</p> <p>I have a silly question, why we have to set the hardsect_size to PAGE_SIZE, is there anything wrong to set it 4k on a 64k page system?</p> <p>I don't recall if there was a requirement to keep the hatdsect size equal to the PAGE_SIZE or not, but I suspect yes - possibly to avoid sub-page IO tracking. Please look at the commit logs and/or bugzilla to see if there are any such requirements.</p> <p>It would be trivial to patch the client kernel to make hardsect size an int instead of a short, but for general use we do not patch the client kernel anymore, so that would either need to be maintained at LLNL and/or submitted upstream to RedHat. </p> <p>Hi, Andreas, Xiong</p> <p>I checked the bugzilla (b5498), and didn't find such requirement, and I didn't find any sub-page IO tracking problem in the code, I asked Xiong (he is the original producer of lloop) about this, he can't recall the exact reason neihter, so I speculate that there isn't any special purpose for this. Since the lloop is introduced for swap, we didn't get any throuble on this. However, if we want to use lloop device as back store for some local filesystem, we might meet trouble when formatting a fs with block size smaller than PAGE_SIZE.</p> <p>Xiong mentioned that clio can only support page size aligned direct io, which makes the lloop in 2.0 can only handle page size aligned IO. The detail is: clio direct io issues io by cl_page, but cl_page doesn't have offset/length (I guess it because cl_page was invented for buffered io), so it's hard to send partial page to OSS. I think that should be an implementation defect in clio direct io (and it has nothing to do whith the hardsect_size), but not sure if we plan to fix it. (Xiong, please correct me if I'm wrong)</p> <p>Given the assumption of no heavy change to the lloop, I think:</p> <ul class="alternate" type="square"> <li>if we only use lloop as swap device, then it's safe to always set the hardsect_size as 4k (no matter on 64k or 4k page system);</li> <li>if we want to use lloop as back store for some other local fs, it's better to set hardsect_size as a smaller value, and for 2.0, the problem of clio direct io limitation needs be fixed.</li> </ul> <p>I think the first solution doesn't require maintaining kernel patches, it should be easier for customer? Any comments?</p> <p>Jay\Andreas - are you able to comment? thanks</p> <p>I am ok with simply disabling the loop device for the PPC client for now, or 64k PAGE_SIZE (whichever is easier). This code is only marginally tested, if at all, and I'd rather it just be disabled on that arch until we have a need to use it there. </p> <p>Let's fix this after kernel has solved the `unsigned short' issue. There is someone else who have met similar problem and has a patch, hopefully we will see it in the mainline kernels.</p> <p>Thanks, Andreas and Jay. Let's just disable it for now (I think Chris and Brian is working on this in <a href="https://jira.whamcloud.com/browse/LU-94" title="llite_lloop should not be part of the client build" class="issue-link" data-issue-key="LU-94"><del>LU-94</del></a>).</p> <p>ok, so if the approach is to avoid this issue and wait for an upstream fix, can this ticket be marked as resolved?</p> Development Rank 1|hzvylb: Rank (Obsolete) 9789 Severity