Details

    • Bug
    • Resolution: Fixed
    • Minor
    • Lustre 2.5.0, Lustre 2.6.0
    • Lustre 2.5.0
    • None
    • RHEL 6.4, Lustre from master at 02a976b LU-3974 libcfs: replace num_physpages with totalram_pages
    • 3
    • 10863

    Description

      Reexport works but in kernel messages logged the following:
      Lustre: ctl-lustre-MDT0000: super-sequence allocation rc = 0 [0x0000000200000400-0x0000000240000400):0:mdt
      LustreError: 3819:0:(llite_nfs.c:105:search_inode_for_lustre()) can't get object attrs, fid [0x200000400:0x1:0x0], rc -2
      LustreError: 3819:0:(llite_nfs.c:105:search_inode_for_lustre()) can't get object attrs, fid [0x200000400:0x1:0x0], rc -2
      LustreError: 3819:0:(llite_nfs.c:105:search_inode_for_lustre()) can't get object attrs, fid [0x200000400:0x1:0x0], rc -2
      LustreError: 3819:0:(llite_nfs.c:105:search_inode_for_lustre()) can't get object attrs, fid [0x200000400:0x1:0x0], rc -2
      LustreError: 3819:0:(llite_nfs.c:105:search_inode_for_lustre()) can't get object attrs, fid [0x200000400:0x1:0x0], rc -2
      LustreError: 3819:0:(llite_nfs.c:105:search_inode_for_lustre()) can't get object attrs, fid [0x200000400:0x1:0x0], rc -2
      LustreError: 3819:0:(llite_nfs.c:105:search_inode_for_lustre()) Skipped 1 previous similar message
      LustreError: 3819:0:(llite_nfs.c:105:search_inode_for_lustre()) can't get object attrs, fid [0x200000400:0x1:0x0], rc -2
      LustreError: 3819:0:(llite_nfs.c:105:search_inode_for_lustre()) Skipped 2 previous similar messages

      Attachments

        Issue Links

          Activity

            [LU-4050] NFS reexport issue
            jlevi Jodi Levi (Inactive) made changes -
            Fix Version/s New: Lustre 2.6.0 [ 10595 ]
            dmiter Dmitry Eremin (Inactive) made changes -
            Fix Version/s New: Lustre 2.5.0 [ 10295 ]
            Resolution New: Fixed [ 1 ]
            Status Original: Open [ 1 ] New: Resolved [ 5 ]

            Dmitry,
            Would you open a new ticket for the remaining work that needs to be completed for this? Then close this ticket with a FixVersion of 2.5.0?
            Thank you!

            jlevi Jodi Levi (Inactive) added a comment - Dmitry, Would you open a new ticket for the remaining work that needs to be completed for this? Then close this ticket with a FixVersion of 2.5.0? Thank you!
            pjones Peter Jones added a comment -

            THis may simply be a duplicate of LU-3240 (now marked as a 2.5.0 blocker) in which case it can be closed as a duplicate of that ticket. If there is still any residual work then it is a lower priority and can be handled in a later release

            pjones Peter Jones added a comment - THis may simply be a duplicate of LU-3240 (now marked as a 2.5.0 blocker) in which case it can be closed as a duplicate of that ticket. If there is still any residual work then it is a lower priority and can be handled in a later release
            pjones Peter Jones made changes -
            Priority Original: Blocker [ 1 ] New: Minor [ 4 ]
            pjones Peter Jones made changes -
            Fix Version/s Original: Lustre 2.5.0 [ 10295 ]
            jhammond John Hammond added a comment -

            Andreas, you're not wrong. The parent directory is not updated for creates. From looking at this and the NFS side, it seems like nanosecond timestamps are the rightest thing here.

            jhammond John Hammond added a comment - Andreas, you're not wrong. The parent directory is not updated for creates. From looking at this and the NFS side, it seems like nanosecond timestamps are the rightest thing here.

            With this patch make directory on NFS share in sync with Lustre if used readdir(). But stat() is not updated if mtime is not changed in terms of seconds. Probably it's fine but I'd like to investigate what can be done to proper updating stat().

            dmiter Dmitry Eremin (Inactive) added a comment - With this patch make directory on NFS share in sync with Lustre if used readdir(). But stat() is not updated if mtime is not changed in terms of seconds. Probably it's fine but I'd like to investigate what can be done to proper updating stat().

            Dmitry,

            Can you clarify what you mean by helps? Does it resolve the issue? Or if it doesn't resolve the issue, how exactly does it help?

            paf Patrick Farrell (Inactive) added a comment - Dmitry, Can you clarify what you mean by helps? Does it resolve the issue? Or if it doesn't resolve the issue, how exactly does it help?

            Also patch set #6 of http://review.whamcloud.com/#/c/6460/ helps with this issue.

            dmiter Dmitry Eremin (Inactive) added a comment - Also patch set #6 of http://review.whamcloud.com/#/c/6460/ helps with this issue.

            People

              dmiter Dmitry Eremin (Inactive)
              dmiter Dmitry Eremin (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              11 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: