[LU-6982] Not mounted drives in recording mode Created: 11/Aug/15 Updated: 21/Jan/22 Resolved: 21/Jan/22 |
|
| Status: | Resolved |
| Project: | Lustre |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major |
| Reporter: | Alex | Assignee: | WC Triage |
| Resolution: | Not a Bug | Votes: | 1 |
| Labels: | None | ||
| Environment: |
https://build.hpdd.intel.com/job/lustre-master/3133/ |
||
| Severity: | 3 |
| Rank (Obsolete): | 9223372036854775807 |
| Description |
|
Do not set the option to record (rw) discs when mounting. All discs |
| Comments |
| Comment by Andreas Dilger [ 11/Aug/15 ] |
|
I'm not quite sure I understand the original bug report, but are you asking for read-only mount support like |
| Comment by Alex [ 12/Aug/15 ] |
|
It is necessary that the file system has been mounted in the mode (rw) by default, but unfortunately mounted mode only (ro). I need to work mode (rw) |
| Comment by Joseph Gmitter (Inactive) [ 13/Aug/15 ] |
|
Hi Bob, |
| Comment by Andreas Dilger [ 13/Aug/15 ] |
|
Bob, you had mentioned that the RHEL7 server mount was reporting read-only (ro) to the mount command, even though the mountpoint was actually mounted read-write and showed up correctly in /proc/mounts. Alex, are you actually seeing errors in your Lustre usage, or is this only related to how "mount" or "/proc/mounts" show the state? If you are actually seeing usage errors, can you please provide your actual mount commands, the output from "cat /proc/mounts", and any error messages on the console (client, MDS, OSS). |
| Comment by Bob Glossman (Inactive) [ 13/Aug/15 ] |
|
As far as I can tell this is a non issue. strictly cosmetic. output from "cat /proc/mounts" always did show mounted mds/ost volumes as 'ro'. mount command began reporting the same thing starting in el7 because the mtab file became a symlink into /proc in el7. prior to that mtab was a real file. |
| Comment by Andreas Dilger [ 14/Aug/15 ] |
|
Bob, you are correct, and I've never noticed this before, but the server mounts on my 2.5 system are indeed all showing "ro" in /proc/mounts. I'm guessing that the problem is that we are not implementing the super_block operations method on the pseudo mount point to print the mount options, so "ro" is just the default option. It would probably be trivial to save the passed in mount options and print them out again. |
| Comment by Alex [ 14/Aug/15 ] |
|
cat /proc/mounts Mounted with parameters on the server Mounted with parameters on the client v2.6.94 On the server build #3139 mounted without problems |
| Comment by Andreas Dilger [ 21/Jan/22 ] |
|
The server mountpoints report "ro" because those mountpoints are not directly writable. They are only used for "df" and "ioctl()" commands passed to the underlying filesystem. |