On Thu, 2025-03-20 at 05:06 +1030, Tim via users wrote: > On Wed, 2025-03-19 at 07:57 +0100, Marco Moock wrote: > > > The message is a bit arbitrary, but checking a network file system from > > > the remote is not intended IIRC, so disable the file system check > > > option in fstab. Do the checks on the remote system. > > Patrick O'Callaghan: > > Although the message is not as clear as it might be, it's still a big > > no-no to try to run fsck on *any* mounted filesystem, local or remote. > > Given that remote implies mounted, that's enough reason for the error. > > > > Even if you were just doing a validity check, and no attempts at > repairs, would remote access through NFS even be feasible to something > like that filesystem check? > > I would thought the NFS handler would act more as a barrier, than > acting as a bridge to make it appear seamlessly like local device > access. IMHO it makes no sense. NFS provides filesystem-level access, but fsck needs actual physical device access to check that the filesystem structure is valid. NFS will just believe what the superblock on the remote system says, but has no way to check that it's correct. A Google search shows that fsck.nfs (referenced by the fsck man page) did apparently exist about 20 years ago, but was essentially a dummy and is not in Fedora. The man page should maybe be updated. poc -- _______________________________________________ users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@xxxxxxxxxxxxxxxxxxxxxxx Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
