[LU-15470] mount.lustre with nochecksum optional flag has a side effect of changing the "user_xattr" to "nouser_xattr" Created: 21/Jan/22 Updated: 21/Jan/22 |
|
| Status: | Open |
| Project: | Lustre |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Minor |
| Reporter: | Arshad Hussain | Assignee: | WC Triage |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | None | ||
| Severity: | 3 |
| Rank (Obsolete): | 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)
|
| Comments |
| Comment by Arshad Hussain [ 21/Jan/22 ] |
|
I thouht "orig_options" were old flags picked up. This seems to be paramter passed currently. (gdb) p mop.mo_orig_options $16 = 0x7fffffffe4cd "nochecksum" (gdb) |