Description of problem: I have been having trouble nfs mounting from a server. I have both the base of a filesystem (/local and /fastlocal mounted from a partition on an SSdisk and various subdirectories from that being mounted on a client. Eg, /fastlocal/usrlocal /fastlocal/unruhhome But the client has extreme problems either in mounting them or in mounting what is actually on them I am assuming this arose out of exportfs on the server not assigning unique fsids to the various exported filesystems. This is a severe bug. I have now put in an fsid= option into all of the filesystems I export, making sure that they are all distint. I am not getting the problems I had before. (This problem popped up orginally when the server was on mga5 but it continued when I updated to Mga7. ) There is nothing in any of the documentation I have seen which makes assigning fsid compulsory suddenly for nfs exports. But since I have done so, I do not seem to be having the previous problems. (I have no way of determining what fsid exportfs is assigning the various exports I have). Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3.
> I am assuming this arose out of exportfs on the server not assigning unique > fsids to the various exported filesystems. There might be a different reason, although your own solution points this way. But that would surely make the problem widespread. It would certainly help to be able to find out what fsid's are being assigned 'naturally' when the problem occurs, but I do not have NFS to explore this. Assigning to guillomovitch for 'nfs-utils'.
Assignee: bugsquad => guillomovitchSummary: nfs seems to assign same fsid to different exports, confsing the hell out of nfs mounting on clients => nfs seems to assign same fsid to different exports, confusing the nfs mounting on clientsSource RPM: ? nfs-util => nfs-utils-2.3.4-3.mga7.src.rpm
According to exportfs(5), fsid is only needed when the underlying filesystem doesn't have UUID or device: https://linux.die.net/man/5/exports Anyway, I'm far from an expert, and it's unlikely to be a mageia-specific issue, you'd better ask for support on more knowledgeable mailing list, such as linux-nfs for instance (https://www.linux-nfs.org/wiki/index.php/Main_Page).
Mageia 7 is EOL since July 1st 2021. There will not have any further bugfix for this release. You are encouraged to upgrade to Mageia 8 as soon as possible. @reporter, if this bug still apply with Mageia 8, please let us know it. @packager, if you work on the Mageia 7 version of your package, please check the Mageia 8 package if issue is also present. In this case, please fix the Mageia 8 version instead. This bug report will be closed OLD if there is no further notice within 1st September 2021.
Hi bug reporter and hi assignee and others involved, Please reopen this bug report if it is still valid for Mageia 8 or 9(cauldron), and change "Version:" in the upper left of this report accordingly. This report is being closed as OLD because it was filed against Mageia 7, for which support ended on June 30th 2021. Thanks, Marja
Resolution: (none) => OLDStatus: NEW => RESOLVED