https://bugs.kde.org/show_bug.cgi?id=471289
Tomas Trnka <tomastr...@gmx.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |tomastr...@gmx.com
--- Comment #2 from Tomas Trnka <tomastr...@gmx.com> ---
(In reply to tagwerk19 from comment #1)
> That looks like the inode is OK but the device number is changing each
> reboot/remount. This is something that's been affecting BTRFS mounts,
> interesting to see that it's catching NFS as well.
Yes, of the most common filesystems on Linux, Btrfs, NFS, and CIFS (a.k.a. SMB)
all use dynamically allocated device numbers, so they are all affected the same
way.
> There is a merge request drafted, specifically for the BTRFS case, that
> might also deal with this:
> https://invent.kde.org/frameworks/baloo/-/merge_requests/131
It will probably help, depending on server configuration. The Linux NFS server
will by default use the FSID of the underlying filesystem when presenting an
export to clients, so the Linux NFS client should expose an unique FSID.
However, the server could be running something like XFS as the underlying
filesystem (which does not have a stable FSID), or the exported FSID can be
overridden in server configuration, possibly making it non-unique across
servers. If server A exports a custom fsid=123 and server B exports a different
filesystem with the same custom fsid, a client mounting both filesystems will
see two unrelated trees with the same FSID.
--
You are receiving this mail because:
You are watching all bug changes.
