Uploaded image for project: 'Lustre'
  1. Lustre
  2. LU-2768

2.1 <-> 2.4 interop can't create file after upgrade

Details

    • Bug
    • Resolution: Duplicate
    • Blocker
    • None
    • Lustre 2.4.0
    • 3
    • 2,775
    • 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
      

      Attachments

        Activity

          [LU-2768] 2.1 <-> 2.4 interop can't create file after upgrade
          di.wang Di Wang added a comment -

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

          di.wang Di Wang added a comment - this problem is actually related with 2775. I will make a patch to fix this. probably we can close this one.

          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.

          niu Niu Yawei (Inactive) added a comment - 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.

          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.

          adilger Andreas Dilger added a comment - 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.

          Alex, could you have a look at this blocker?

          jlevi Jodi Levi (Inactive) added a comment - Alex, could you have a look at this blocker?

          People

            bzzz Alex Zhuravlev
            niu Niu Yawei (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: