Actions
Bug #8617
closednfs client writes invalid (working) fstab entry
Pull Request:
Severity:
Major - prevents use of part of Rudder | no simple workaround
UX impact:
User visibility:
Operational - other Techniques | Technique editor | Rudder settings
Effort required:
Priority:
0
Name check:
Fix check:
Regression:
Description
Hello!
I've tested the nfs client technique.
There was a few hickups I noticed.
Here's the active mount:
Filesystem 1K-blocks Used Available Use% Mounted on
none 4061980 0 4061980 0% /dev
tmpfs 813060 73368 739692 10% /run
/dev/nbd0 47929956 1564748 43907420 4% /
tmpfs 4065284 0 4065284 0% /dev/shm
tmpfs 5120 0 5120 0% /run/lock
tmpfs 4065284 0 4065284 0% /sys/fs/cgroup
10.1.84.169:/var/lib/one/datastores 249937920 1259520 248678400 1% /var/lib/one/datastores
tmpfs 813060 0 813060 0% /run/user/9869
tmpfs 813060 0 813060 0% /run/user/0
root@ref-one-host1:~# cat /etc/fstab
- UNCONFIGURED FSTAB FOR BASE SYSTEM
10.1.84.169:/var/lib/one/datastores /var/lib/one/datastores nfs defaults@
this is missing the mount order entries (0 0 or 0 0)
Please check the reasoning why there's none of that.
Further many OS might even need _netdev
We also noticed there's no way to set the mount options, meaning this will be a pure hardmount.
In summary:
I think the missing fields are definitely not ok.
For the rest, better ask someone who uses this more productively. I've only tested it since it was still on my list.
Updated by François ARMAND over 8 years ago
- Assignee set to Alexis Mousset
- Target version set to 3.1.14
Updated by Benoît PECCATTE about 8 years ago
- Severity set to Major - prevents use of part of Rudder | no simple workaround
- User visibility set to Operational - other Techniques | Technique editor | Rudder settings
- Priority set to 32
Updated by Vincent MEMBRÉ almost 8 years ago
- Target version changed from 3.1.21 to 3.1.22
- Priority changed from 31 to 30
Updated by Vincent MEMBRÉ over 6 years ago
- Target version changed from 4.1.17 to 4.1.18
- Priority changed from 43 to 0
Actions