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

conf-sanity 58: `/mnt/mds/OBJECTS': No such file or directory

Details

    • Bug
    • Resolution: Duplicate
    • Minor
    • None
    • Lustre 2.4.0
    • None
    • 3
    • 7296

    Description

      conf-sanity 58 is not working at all, in the sense that it can't find or destroy the OSP logs:

      CMD: client-26vm7 find /mnt/mds/OBJECTS -type f -delete
      client-26vm7: find: `/mnt/mds/OBJECTS': No such file or directory
      

      For instance, see https://maloo.whamcloud.com/sub_tests/e7389a98-914b-11e2-8a5c-52540035b04c

      Attachments

        Issue Links

          Activity

            [LU-2992] conf-sanity 58: `/mnt/mds/OBJECTS': No such file or directory

            Fixed via patch http://review.whamcloud.com/9675 "LU-2524 tests: enable conf-sanity/58 on ZFS"

            adilger Andreas Dilger added a comment - Fixed via patch http://review.whamcloud.com/9675 " LU-2524 tests: enable conf-sanity/58 on ZFS "

            Normally, tests use "/mnt/mds1" as the mount point and feed "mds1" to facet_mntpt(); it is not impossible that "/mnt/mds" does not exist.

            Anyway, the test output I posted is a bad example. What I wanted to point out is actually "OBJECTS" no longer exists, even if the test can mount the device successfully.

            liwei Li Wei (Inactive) added a comment - Normally, tests use "/mnt/mds1" as the mount point and feed "mds1" to facet_mntpt(); it is not impossible that "/mnt/mds" does not exist. Anyway, the test output I posted is a bad example. What I wanted to point out is actually "OBJECTS" no longer exists, even if the test can mount the device successfully.

            The mountpoint should be the same one that the MDS is originally mounted on:

                    local MNTDIR=$(facet_mntpt mds)
                    # remove all files from the OBJECTS dir
                    do_facet mds "mount -t ldiskfs $MDSDEV $MNTDIR"
            

            I'm not sure how that could be missing. However, in 2.x there are no logs under OBJECTS. It makes more sense to change the test to create the mountpoint, and also delete logs under O/1/d*:

                    local MNTDIR=$(facet_mntpt mds)
                    # remove all files from the OBJECTS dir
                    do_facet mds "mkdir -p $MNTDIR; mount -t ldiskfs $MDSDEV $MNTDIR"
                    do_facet mds "find $MNTDIR/OBJECTS $MNTDIR/O/1/d* -type f -delete"
            
            adilger Andreas Dilger added a comment - The mountpoint should be the same one that the MDS is originally mounted on: local MNTDIR=$(facet_mntpt mds) # remove all files from the OBJECTS dir do_facet mds "mount -t ldiskfs $MDSDEV $MNTDIR" I'm not sure how that could be missing. However, in 2.x there are no logs under OBJECTS . It makes more sense to change the test to create the mountpoint, and also delete logs under O/1/d* : local MNTDIR=$(facet_mntpt mds) # remove all files from the OBJECTS dir do_facet mds "mkdir -p $MNTDIR; mount -t ldiskfs $MDSDEV $MNTDIR" do_facet mds "find $MNTDIR/OBJECTS $MNTDIR/O/1/d* -type f -delete"
            green Oleg Drokin added a comment -

            kind of strange that MNTDIR does not exist, I guess we can try to create it before first access?
            this is even before knowing if we should fixthe rest of this test or not

            green Oleg Drokin added a comment - kind of strange that MNTDIR does not exist, I guess we can try to create it before first access? this is even before knowing if we should fixthe rest of this test or not

            It didn't mount the device. It does not matter what file you are looking for it won't be there.

            CMD: client-26vm7 mount -t ldiskfs /dev/lvm-MDS/P1 /mnt/mds
            client-26vm7: mount: mount point /mnt/mds does not exist
            CMD: client-26vm7 find /mnt/mds/OBJECTS -type f -delete
            client-26vm7: find: `/mnt/mds/OBJECTS': No such file or directory
            CMD: client-26vm7 umount /mnt/mds
            client-26vm7: umount: /mnt/mds: not found
            

            Are you sure you configuration / setup is correct?

            keith Keith Mannthey (Inactive) added a comment - It didn't mount the device. It does not matter what file you are looking for it won't be there. CMD: client-26vm7 mount -t ldiskfs /dev/lvm-MDS/P1 /mnt/mds client-26vm7: mount: mount point /mnt/mds does not exist CMD: client-26vm7 find /mnt/mds/OBJECTS -type f -delete client-26vm7: find: `/mnt/mds/OBJECTS': No such file or directory CMD: client-26vm7 umount /mnt/mds client-26vm7: umount: /mnt/mds: not found Are you sure you configuration / setup is correct?
            liwei Li Wei (Inactive) added a comment - - edited

            The logs no longer exist in "OBJECTS". They should be found under "O/1/d[0-9]+". There is no guarantee that all logs there are OSP logs, however. Hence, the test might need to read and parse "CATALOGS".

            liwei Li Wei (Inactive) added a comment - - edited The logs no longer exist in "OBJECTS". They should be found under "O/1/d [0-9] +". There is no guarantee that all logs there are OSP logs, however. Hence, the test might need to read and parse "CATALOGS".

            People

              wc-triage WC Triage
              liwei Li Wei (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: