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

sanity/test_413a and conf-sanity/test_32[b,c,e,h] permanent timeout/failures with ZFS back-end only

Details

    • Bug
    • Resolution: Fixed
    • Minor
    • Lustre 2.17.0
    • None
    • 3
    • 9223372036854775807

    Description

      sanity/test_413a failure/timeout example at https://testing.whamcloud.com/test_sets/2398dece-98fe-44d8-b89d-3c76dbef0216

      conf-sanity/test_32[b,c,e,h] failures example at https://testing.whamcloud.com/test_sets/431e1d95-39e3-43bb-b721-df2e51d0ea6f

      all look directly related to LU-18646 findings ("dd if=/dev/zero ..." commands do not consume expected space due to ZFS recently using data compression by default) and could be fixed the same way (https://review.whamcloud.com/c/fs/lustre-release/+/57871).

      there are more conf-sanity subtests failures following but they do not look directly caused by this same problem and may only be consequences of the first failures...

      Attachments

        Issue Links

          Activity

            [LU-18728] sanity/test_413a and conf-sanity/test_32[b,c,e,h] permanent timeout/failures with ZFS back-end only

            Patch landed that fixes just conf-sanity 32 test. Other test will be fixed under LU-18652

            simmonsja James A Simmons added a comment - Patch landed that fixes just conf-sanity 32 test. Other test will be fixed under LU-18652

            One patch landed and one more to go.

            simmonsja James A Simmons added a comment - One patch landed and one more to go.

            "Oleg Drokin <green@whamcloud.com>" merged in patch https://review.whamcloud.com/c/fs/lustre-release/+/58115/
            Subject: LU-18728 tests: use urandom to really consume ZFS space
            Project: fs/lustre-release
            Branch: master
            Current Patch Set:
            Commit: 6153eed3ee180e8695c9e2e3d9ad9db8a6b73ad8

            gerrit Gerrit Updater added a comment - "Oleg Drokin <green@whamcloud.com>" merged in patch https://review.whamcloud.com/c/fs/lustre-release/+/58115/ Subject: LU-18728 tests: use urandom to really consume ZFS space Project: fs/lustre-release Branch: master Current Patch Set: Commit: 6153eed3ee180e8695c9e2e3d9ad9db8a6b73ad8

            There are 2 patches for this ticket so once one patch lands please don't close.

            simmonsja James A Simmons added a comment - There are 2 patches for this ticket so once one patch lands please don't close.
            pjones Peter Jones added a comment -

            Bruno

            I think that you should be able to find what you need on the test parameters page of the Whamcloud wiki

            Peter

            pjones Peter Jones added a comment - Bruno I think that you should be able to find what you need on the test parameters page of the Whamcloud wiki Peter

            Gerrit #58115 is an attempt to fix these tests accordingly to Gerrit #57871 for LU-18646.

            I am missing (forgot...) the way/tag to only run with ZFS back-end , can I get some hint ? Thx in advance !

             

            bfaccini-nvda Bruno Faccini added a comment - Gerrit #58115 is an attempt to fix these tests accordingly to Gerrit #57871 for LU-18646 . I am missing (forgot...) the way/tag to only run with ZFS back-end , can I get some hint ? Thx in advance !  

            "Bruno Faccini <bfaccini@nvidia.com>" uploaded a new patch: https://review.whamcloud.com/c/fs/lustre-release/+/58115
            Subject: LU-18728 tests: use urandom to really consume ZFS space
            Project: fs/lustre-release
            Branch: master
            Current Patch Set: 1
            Commit: ac427f2272cb065b0025b069f44e9b409f4bc32d

            gerrit Gerrit Updater added a comment - "Bruno Faccini <bfaccini@nvidia.com>" uploaded a new patch: https://review.whamcloud.com/c/fs/lustre-release/+/58115 Subject: LU-18728 tests: use urandom to really consume ZFS space Project: fs/lustre-release Branch: master Current Patch Set: 1 Commit: ac427f2272cb065b0025b069f44e9b409f4bc32d

            The config-sanity test are know about under LU-18652. I disabled those test so they shouldn't be failing anymore. Are you running the latest master? There was another ticket for the 413a timeouts. I haven't seen them but if they still happen then we need to look at the failures. Peter we had a ticket for the 413a timeouts but I closed out the ticket since the failures seemed to go away. Should I reopen that ticket.

            simmonsja James A Simmons added a comment - The config-sanity test are know about under LU-18652 . I disabled those test so they shouldn't be failing anymore. Are you running the latest master? There was another ticket for the 413a timeouts. I haven't seen them but if they still happen then we need to look at the failures. Peter we had a ticket for the 413a timeouts but I closed out the ticket since the failures seemed to go away. Should I reopen that ticket.

            People

              bfaccini-nvda Bruno Faccini
              bfaccini-nvda Bruno Faccini
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: