Tristate moount option comatibility fixup
Status from this message: NAK, programs that require DAX semantics for files stored on XFS must
Get series with b4
b4 am [email protected]Versions newest first
Patches in v1
| # | Subject and files | Size | Replies | Applied |
|---|---|---|---|---|
| 1/2 | xfs: show the dax option in mount options.fs/ | +1 | 11 replies | |
| 2/2 | ext4: show the dax option in mount optionsfs/ | +1 | 0 replies |
Reviews trailers per patch
1 of 2 patches has a Reviewed-by or Acked-by.
| Patch | Eric Sandeen |
|---|---|
| 1/2 | R-b |
| 2/2 |
Trailers given in replies are filled; those carried in the patches from earlier versions are outlined with dashes.
Cover letter [PATCH 0/2] Tristate moount option comatibility fixup
Hello,
after the tristate dax option change some applications fail to detect pmem devices because the dax option no longer shows in mtab when device is mounted with -o dax.
At first it might seem stupid to detect pmem by looking at the mount options.
However, if the application actually wants a mount point properly configured for dax rather than just backed by pmem I do not see any other easy way.
Also this happens during early installtion steps when the mounted filesystem is typically empty and you want to perform non-destructive detection.
If there are better ways to detect dax enabled mount poins I want to hear all about it. In the meantime we have legacy applications to support.
It also makes sense that when you mount a device with -o dax it actually shows dax in the mount options. Not doind so is confusing for humans as well.
Thanks
Michal
Michal Suchanek (2):
xfs: show the dax option in mount options.
ext4: show the dax option in mount options
References: bsc#1178366
fs/ext4/super.c | 2 +- fs/xfs/xfs_super.c | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-)
Signature · 1 line
2.26.2