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

mount.lustre with nochecksum optional flag has a side effect of changing the "user_xattr" to "nouser_xattr"

    XMLWordPrintable

Details

    • Bug
    • Resolution: Unresolved
    • Minor
    • None
    • None
    • None
    • 3
    • 9223372036854775807

    Description

      With the original mount looking like below

      # mount | grep lustre
      192.168.50.95@tcp:/lustre on /mnt/lustre type lustre (rw,checksum,flock,user_xattr,lruresize,lazystatfs,nouser_fid2path,verbose,noencrypt)

      Umount and re-mount with no-checksum flag

       

      # umount /mnt/lustre
      # mount.lustre 192.168.50.95@tcp:/lustre /mnt/lustre/ -o nochecksum
      

      The result is the changed "user_xattr" -> "nouser_xattr"

      # mount | grep lustre
      192.168.50.95@tcp:/lustre on /mnt/lustre type lustre (rw,nochecksum,flock,nouser_xattr,lruresize,lazystatfs,nouser_fid2path,verbose,noencrypt)

       

       

       

      Attachments

        Activity

          People

            wc-triage WC Triage
            arshad512 Arshad Hussain
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

              Created:
              Updated: