[LU-2768] 2.1 <-> 2.4 interop can't create file after upgrade Created: 06/Feb/13  Updated: 08/Feb/13  Resolved: 08/Feb/13

Status: Resolved
Project: Lustre
Component/s: None
Affects Version/s: Lustre 2.4.0
Fix Version/s: None

Type: Bug Priority: Blocker
Reporter: Niu Yawei (Inactive) Assignee: Alex Zhuravlev
Resolution: Duplicate Votes: 0
Labels: HB

Severity: 3
Bugzilla ID: 2,775
Rank (Obsolete): 6709

 Description   

When I try to mount 2.1 devices with 2.4, I found the following error message:

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

And any following creation will fail with ENOSPC because osp_precreate_reserve() always return -PROTO:

[root@rhel6 tests]# dd if=/dev/zero of=/mnt/lustre/c bs=1M count=1 oflag=sync
dd: opening `/mnt/lustre/c': No space left on device


 Comments   
Comment by Jodi Levi (Inactive) [ 06/Feb/13 ]

Alex, could you have a look at this blocker?

Comment by Andreas Dilger [ 06/Feb/13 ]

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?

It looks like ost_validate_obdo() is complaining about an IDIF FID sent to this target.

Comment by Niu Yawei (Inactive) [ 06/Feb/13 ]

Yes, it's 2.1 formatted filesystem that has been upgraded to 2.4 for both client and servers.

Actually, adding a "dd to file" in the conf-sanity.sh test_32 can easily reproduce it.

Comment by Di Wang [ 08/Feb/13 ]

this problem is actually related with 2775. I will make a patch to fix this. probably we can close this one.

Generated at Sat Feb 10 01:28:02 UTC 2024 using Jira 9.4.14#940014-sha1:734e6822bbf0d45eff9af51f82432957f73aa32c.