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-5425 Lustre <p>This issue was created by maloo for wangdi &lt;di.wang@intel.com&gt;</p> <p>This issue relates to the following test suite run: <a href="https://testing.hpdd.intel.com/test_sets/18cec46e-1676-11e4-9ba5-5254006e85c2" class="external-link" target="_blank" rel="nofollow noopener">https://testing.hpdd.intel.com/test_sets/18cec46e-1676-11e4-9ba5-5254006e85c2</a>.</p> <p>The sub-test test_32a failed with the following error:</p> <blockquote> <p>Lustre: DEBUG MARKER: /usr/sbin/lctl get_param -n mdt.t32fs-MDT0000.uuid<br/> Lustre: DEBUG MARKER: tunefs.lustre --dryrun /tmp/t32/ost<br/> Lustre: DEBUG MARKER: mount -t lustre -o loop,mgsnode=10.1.5.230@tcp /tmp/t32/ost /tmp/t32/mnt/ost<br/> LDISKFS-fs (loop1): Unrecognized mount option "extents" or missing value<br/> LustreError: 25985:0:(osd_handler.c:5780:osd_mount()) t32fs-OST0000-osd: can't mount /dev/loop1: -22<br/> LustreError: 25985:0:(obd_config.c:568:class_setup()) setup t32fs-OST0000-osd failed (-22)<br/> LustreError: 25985:0:(obd_mount.c:204:lustre_start_simple()) t32fs-OST0000-osd setup error -22<br/> LustreError: 25985:0:(obd_mount_server.c:1737:server_fill_super()) Unable to start osd on /dev/loop1: -22<br/> LustreError: 25985:0:(obd_mount.c:1351:lustre_fill_super()) Unable to mount (-22)<br/> Lustre: DEBUG MARKER: /usr/sbin/lctl mark conf-sanity test_32a: @@@@@@ FAIL: Mounting the OST <br/> Lustre: DEBUG MARKER: conf-sanity test_32a: @@@@@@ FAIL: Mounting the OST</p> <p>test_32a failed with 2</p></blockquote> <p>Info required for matching: conf-sanity 32a</p> LU-5425

Test failure on test suite conf-sanity, subtest test_32a (mount OST failed)

Bug Blocker Closed Duplicate Yang Sheng Maloo Mon, 28 Jul 2014 22:23:30 +0000 Wed, 18 Feb 2015 23:01:25 +0000 Wed, 18 Feb 2015 23:01:25 +0000 0 6 <p>This is caused by patch <br/> <a href="https://jira.whamcloud.com/browse/LU-5276" title="ldiskfs patches for FC19" class="issue-link" data-issue-key="LU-5276"><del>LU-5276</del></a> ldiskfs: Remove extents-mount-option patch</p> <p> Remove ext4-extents-mount-option.patch for ldiskfs. It<br/> means '-o </p> {extents|noextents} <p>' option not support anymore.</p> <p> Signed-off-by: Yang Sheng &lt;yang.sheng@intel.com&gt;<br/> Change-Id: I7989fbf9a94c1556728531c7837a887df67e6b19<br/> Reviewed-on: <a href="http://review.whamcloud.com/11088" class="external-link" target="_blank" rel="nofollow noopener">http://review.whamcloud.com/11088</a><br/> Tested-by: Jenkins<br/> Reviewed-by: Bob Glossman &lt;bob.glossman@intel.com&gt;<br/> Tested-by: Maloo &lt;hpdd-maloo@intel.com&gt;<br/> Reviewed-by: James Simmons &lt;uja.ornl@gmail.com&gt;<br/> Reviewed-by: Oleg Drokin &lt;oleg.drokin@intel.com&gt;</p> <p>Since the patch remove "extents" option, which cause the failure during upgrading.</p> <p>I don't think reverting the patch is the answer. Can we try to see if we disable extents option in enable_default_ext4_features located in mount_utils_ldiskfs.c should fix things.</p> <p>Looks like we may still keep this patch for back compatibility. But can consider remove extent flag in config file first.</p> <p>The patch has been reverted. So the problem no exist any more. We just need to review whether need other patch for remove extents patch in future. We must keep it for compatibility in present.</p> <p>Duplicate of <a href="https://jira.whamcloud.com/browse/LU-5276" title="ldiskfs patches for FC19" class="issue-link" data-issue-key="LU-5276"><del>LU-5276</del></a></p> Related LU-5276 Development Rank 1|hzwsin: Rank (Obsolete) 15096 Severity