Whamcloud Community JIRA https://jira.whamcloud.com This file is an XML representation of an issue en-us 9.4.14 940014 05-12-2023 [LU-2768] 2.1 <-> 2.4 interop can't create file after upgrade https://jira.whamcloud.com/browse/LU-2768 Lustre <p>When I try to mount 2.1 devices with 2.4, I found the following error message:</p> <div class="code panel" style="border-width: 1px;"><div class="codeContent panelContent"> <pre class="code-java">LustreError: 11740:0:(ost_handler.c:122:ost_validate_obdo()) lustre-OST0001: client 0@lo sent invalid object 2:4295032832 LustreError: 11499:0:(osp_precreate.c:740:osp_precreate_cleanup_orphans()) lustre-OST0001-osc-MDT0000: cannot cleanup orphans: rc = -71 LustreError: 11740:0:(ost_handler.c:122:ost_validate_obdo()) lustre-OST0000: client 0@lo sent invalid object 2:4294967296 LustreError: 11-0: lustre-OST0000-osc-MDT0000: Communicating with 0@lo, operation ost_create failed with -71. LustreError: Skipped 1 previous similar message LustreError: 11497:0:(osp_precreate.c:740:osp_precreate_cleanup_orphans()) lustre-OST0000-osc-MDT0000: cannot cleanup orphans: rc = -71 </pre> </div></div> <p>And any following creation will fail with ENOSPC because osp_precreate_reserve() always return -PROTO:</p> <div class="code panel" style="border-width: 1px;"><div class="codeContent panelContent"> <pre class="code-java">[root@rhel6 tests]# dd <span class="code-keyword">if</span>=/dev/zero of=/mnt/lustre/c bs=1M count=1 oflag=sync dd: opening `/mnt/lustre/c': No space left on device </pre> </div></div> LU-2768 2.1 <-> 2.4 interop can't create file after upgrade Bug Blocker Resolved Duplicate Alex Zhuravlev Niu Yawei Wed, 6 Feb 2013 06:19:41 +0000 Fri, 8 Feb 2013 04:06:26 +0000 Fri, 8 Feb 2013 04:06:26 +0000 Lustre 2.4.0 0 4 <p>Alex, could you have a look at this blocker?</p> <p>Niu, could you please describe your test configuration better. Is it a 2.1-formatted filesystem that has been upgraded to 2.4 server code on both OSS and MDS?</p> <p>It looks like ost_validate_obdo() is complaining about an IDIF FID sent to this target.</p> <p>Yes, it's 2.1 formatted filesystem that has been upgraded to 2.4 for both client and servers.</p> <p>Actually, adding a "dd to file" in the conf-sanity.sh test_32 can easily reproduce it.</p> <p>this problem is actually related with 2775. I will make a patch to fix this. probably we can close this one.</p> Bugzilla ID 2775.0 Development Rank 1|hzvipr: Rank (Obsolete) 6709 Severity