You are not logged in.
Pages: 1
I am in the process of upgrading my LAN and I have installed the boron release on my server and client.
On the client, when I enter:
mount -t nfs snider:/mnt/jjaLibrary /mnt/jjaLibrary
I get the error message:
mount.nfs: Connection refused
On the server host 'snider', if I run:
exportfs -va
The output includes:
exporting 192.168.1.0/24:/mnt/jjaLibrary
It seems that what I am doing should work. Is there something extra that
I should be doing to all the client to access the server?
Jim A.
Last edited by jjanderson5 (2025-08-09 17:30:16)
Offline
And further information --- On the server host, 'snider'. if I run:
systemctl status nfs-server.service
I receive the following response
snider# systemctl status nfs-server.service
○ nfs-server.service - NFS server and services
Loaded: loaded (/lib/systemd/system/nfs-server.service; enabled; preset: enabled)
Drop-In: /run/systemd/generator/nfs-server.service.d
└─order-with-mounts.conf
Active: inactive (dead)Aug 06 00:01:07 snider systemd[1]: mnt-jjaAlt.mount: Found ordering cycle on nfs-server.service/start
Aug 06 00:01:07 snider systemd[1]: mnt-jjaAlt.mount: Found dependency on mnt-jjaAlt.mount/start
Aug 06 00:01:07 snider systemd[1]: mnt-jjaAlt.mount: Unable to break cycle starting with mnt-jjaAlt.mount/start
The line
Active: inactive (dead)
indicates I have a problem with the nfs server, but it is not clear to me what the problem is. It looks like the nfs-server is going into an endless cycle, but I am not sure why.
Last edited by jjanderson5 (2025-08-06 05:50:09)
Offline
Some additional information.
When I run:
service nfs-kernel-server stop
service nfs-kernel-server start
The response is:
Failed to start nfs-kernel-server.service: Transaction order is cyclic. See system logs for details.
See system logs and 'systemctl status nfs-kernel-server.service' for details.
Again, it looks like the nfs server is going into a loop and failing. But I have no idea why this would happen.
Offline
I am closing this issue and plan to report it as a bug report.
My work around was to divide my 4 TB hard disk on the computer into 4 partitions, suspecting that the size of the hard drive was the problem. I check the online literature for Debian and 4 TB hard disk should work - but it did not in my case. Once setting up smaller partitions, all went well.
Offline
I will move this to the Bug Reports. I mistakenly deleted the bug report thread thinking it was a double up.
"All we are is dust in the wind, dude"
- Theodore "Ted" Logan
"Led Zeppelin didn't write tunes that everybody liked, they left that to the Bee Gees."
- Wayne Campbell
Offline
It's a long running issue, not specific to boron (Debian in general).
No definitive solution for it. Query your error:
Failed to start nfs-kernel-server.service: Transaction order is cyclic.
and the results are variable. Mounting the share in fstab, VM limits (2TB share size limit in VM??), etc ...
As example, this was an interesting exchange:
You must unlearn what you have learned.
-- yoda
Offline
It's a long running issue, not specific to boron (Debian in general).
So it's not a BunsenLabs bug.
Does it belong in this section? Maybe General Linux Discussion?
...elevator in the Brain Hotel, broken down but just as well...
( a boring Japan blog (currently paused), now on Bluesky, there's also some GitStuff )
Offline
Move it back to the General Help section where the post originated.
The OP should file a bug report with Debian. Or check their bug reports to see if there is a Debian fix/work around for this.
You must unlearn what you have learned.
-- yoda
Offline
Moved to Basic Help and Support.
...elevator in the Brain Hotel, broken down but just as well...
( a boring Japan blog (currently paused), now on Bluesky, there's also some GitStuff )
Offline
Pages: 1