[LU-8151] OST/MDT /proc/mounts always shows "ro" for server mountpoints Created: 16/May/16  Updated: 14/Dec/23  Resolved: 08/Nov/22

Status: Resolved
Project: Lustre
Component/s: None
Affects Version/s: None
Fix Version/s: Lustre 2.16.0

Type: Bug Priority: Minor
Reporter: Andreas Dilger Assignee: Arshad Hussain
Resolution: Fixed Votes: 0
Labels: medium

Issue Links:
Gantt End to Start
has to be done after LU-16280 Make conf-sanity/117 call setup() onl... Resolved
Related
is related to LU-137 ioctl passthrough mechanism for Lustr... Resolved
Severity: 3
Rank (Obsolete): 9223372036854775807

 Description   

The /proc/mounts output for all MDT and OST devices shows "ro" (read-only) all the time, even when the devices are working properly. This caused confusion when trying to debug an OST that had actually gone read-only. This is because the "shadow" mountpoints on the server have MS_RDONLY set to prevent users/admins trying to write into these devices, which are only for "statfs" (df) and possibly ioctl() calls (LU-137).

It would be better to define our own .show_options method in obdclass/obd_mount_server.c::super_operations. It can do an internal dt_statfs() to get the current filesystem state and print "rw" or "ro" as appropriate. It would also be good to print out the rest of the mount options that were used.



 Comments   
Comment by Gerrit Updater [ 25/Apr/22 ]

"Arshad Hussain <arshad.hussain@aeoncomputing.com>" uploaded a new patch: https://review.whamcloud.com/47131
Subject: LU-8151 tests: Handle shadow mountpounts for server
Project: fs/lustre-release
Branch: master
Current Patch Set: 1
Commit: 7a45c6accebb2bed5e21a9fb8ab853fb53763bd8

Comment by Gerrit Updater [ 08/Nov/22 ]

"Oleg Drokin <green@whamcloud.com>" merged in patch https://review.whamcloud.com/c/fs/lustre-release/+/47131/
Subject: LU-8151 obd: Show correct shadow mountpoints for server
Project: fs/lustre-release
Branch: master
Current Patch Set:
Commit: 0171801df517988b0eb1023378c2c8c07a0a36f1

Comment by Peter Jones [ 08/Nov/22 ]

Landed for 2.16

Generated at Sat Feb 10 02:15:05 UTC 2024 using Jira 9.4.14#940014-sha1:734e6822bbf0d45eff9af51f82432957f73aa32c.