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-5032 Lustre <p>Running Sanity on 2.6 + <a href="https://jira.whamcloud.com/browse/LU-3321" title="2.x single thread/process throughput degraded from 1.8" class="issue-link" data-issue-key="LU-3321"><del>LU-3321</del></a> fails test 54c: </p> <p>mount: wrong fs type, bad option, bad superblock on /tmp/dal/loop54c,<br/> missing codepage or helper program, or other error<br/> In some cases useful info is found in syslog - try<br/> dmesg | tail or so</p> <p> sanity test_54c: @@@@@@ FAIL: error mounting /tmp/dal/loop54c on /tmp/dal/d54c</p> <p>dmesg log shows:<br/> Buffer I/O error on device loop3, logical block 0<br/> lost page write due to I/O error on loop3<br/> ...<br/> Buffer I/O error on device loop3, logical block 9<br/> lost page write due to I/O error on loop3<br/> EXT2-fs (loop3): error: can't find an ext2 filesystem on dev loop3.<br/> Lustre: DEBUG MARKER: sanity test_54c: @@@@@@ FAIL: error mounting /tmp/dal/loop54c on /tmp/dal/d54c</p> <p>error coming out of logfile:<br/> mount: wrong fs type, bad option, bad superblock on /tmp/dal/loop54c,<br/> missing codepage or helper program, or other error<br/> In some cases useful info is found in syslog - try<br/> dmesg | tail or so</p> <p> sanity test_54c: @@@@@@ FAIL: error mounting /tmp/dal/loop54c on /tmp/dal/d54c</p> <p>This test DOES have <a href="http://review.whamcloud.com/9658" class="external-link" target="_blank" rel="nofollow noopener">http://review.whamcloud.com/9658</a> in the build.</p> <p>Addtional patch was <a href="https://jira.whamcloud.com/browse/LU-3321" title="2.x single thread/process throughput degraded from 1.8" class="issue-link" data-issue-key="LU-3321"><del>LU-3321</del></a> that was under test.</p> Cray clients, 2.6 lustre + <a href="https://jira.whamcloud.com/browse/LU-3321" title="2.x single thread/process throughput degraded from 1.8" class="issue-link" data-issue-key="LU-3321"><strike>LU-3321</strike></a> LU-5032

Mount of loopdev in test 54c fails

Bug Blocker Resolved Duplicate Bob Glossman Mark Mansk Thu, 8 May 2014 13:40:25 +0000 Thu, 8 May 2014 14:48:38 +0000 Thu, 8 May 2014 14:00:58 +0000 Lustre 2.6.0 0 4 <p>A few quick clarifications:<br/> The environment for this is the Cray version of SLES11SP3, with master, or 2.5+the <a href="https://jira.whamcloud.com/browse/LU-3221" title="calling set_fs(KERNEL_DS) may break copy_from_user() on SPARC" class="issue-link" data-issue-key="LU-3221"><del>LU-3221</del></a> patch series, so it seems to have been introduced by that patch series. This issue does not occur on CentOS with the same code.</p> <p>From my investigation, an EINVAL is coming from the mount process in the kernel. Specifically, the superblock magic being read in doesn't match what's expected for ext2.<br/> This makes me suspect the problem may be in the format step rather than in the mount step.</p> <p>Unfortunately, as best I can tell, Lustre DK logs (with -1) for this entire test show no errors, so it's been hard to figure out what's going wrong. I'll see about attaching those logs later today.</p> <p>Known problem. kernel loop devices in SLES11 are incompatible with lustre due to implementation differences between SLES11 and everything else.</p> <p>Thanks, Bob. I'd looked, not sure how I missed <a href="https://jira.whamcloud.com/browse/LU-4351" title="sanity test_54c: can&#39;t find an ext2 filesystem on dev loop3" class="issue-link" data-issue-key="LU-4351"><del>LU-4351</del></a>.</p> Duplicate LU-4351 Development Rank 1|hzwm47: Rank (Obsolete) 13913 Severity