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

need to remount after sanity 133g

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Critical Critical
    • Lustre 2.6.0
    • Lustre 2.6.0
    • 3
    • 13801

      Sanity 133g tries to write garbage to every file in /proc/fs/lustre,... As you can imagine, this may affect the other tests in subtle ways.

      [18:14:13] John Hammond: I'm a bit concerned that sanity 133g may be having/exposing some subtle effects on sanity.
      [18:14:53] John Hammond: I see weird messages that the current identity upcall is '^E'.
      [18:15:33] John Hammond: Just FYI. I'll probably create an issue here soon.
      [18:16:41] Oleg Drokin: ah… I very well can believe that. Luckily, we do not use identity-upcall in our testing I think
      [18:16:56] John Hammond: We do use it.
      [18:18:07] Oleg Drokin: do we? interesting
      [18:18:37] Oleg Drokin: sigh, need to make it the very last test then?
      [18:18:40] John Hammond: If the mdt.*.identity_upcall is set to something other than NONE then we use that.
      [18:19:43] John Hammond: I see mdt_identity_do_upcall() being executed several times in a sanity run.
      [18:20:13] Oleg Drokin: hopefully mostly before test 133
      [18:20:29] Oleg Drokin: but there were some other side effects like disabling changelog masks and such
      [18:20:37] Oleg Drokin: so it does make sense to move the test to be the very last one
      [18:22:13] John Hammond: Or unmount and remount after it.

            bobbielind Bobbie Lind (Inactive)
            jhammond John Hammond
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

              Created:
              Updated:
              Resolved: