Stopping NFS after VMs?

Apps and Virtualization
,
1

Is there a way to adjust the service shutdown order so that NFS is stopped after the VMs. I have a couple of VMs that use NFS to consume storage off the host and currently they loose access to the shares which causes delays in the power off of their VMs.

[FAILED] Failed unmounting /Share/Stuff
[75852.335298] nfs: server 192.168.17.3 not responding, timed out
[75855.343304] nfs: server 192.168.17.3 not responding, still trying
[75858.351359] nfs: server 192.168.17.3 not responding, timed out
1 Like
2

Not that I know of.

I think this affects me too. Even leads to the VM shutdown exceeding the max 300s timeout.

Bug report?

3

I see this problem too. Did you ever file a bug report?

4

There are two existing bug reports

This one was closed without any updates or guidance

There is an updated version under

I’ve added a note to the second ticket

5

@Steven_Ellis this is a valid feature request IMO. This should be raised here Feature Requests - TrueNAS Community Forums rather than in Jira.

It does look like that second ticket is in triage, but I suspect the feature request forum section is the best path for this request.

In my opinion: It’s not a bug, because middlewared has always (since CORE days and beyond) managed service startup routines. This is a particularly important part of Enterprise HA systems. But requesting the ability to make those changes in CE would be fair.

6

I have to disagree - this is bad logic and would impact any locally VM using TrueNAS as NFS / CIFS / ISCSI storage.

I’ll add some more comments to the ticket

7

No disagreement on the technical front here, I understand why this is a problem for your use case. I’m just trying to help direct you to get the quickest action.

Just so that I am clear…Asking to fix this specific issue so VMs consuming NFS aren’t impacted (the ticket) is not the same thing as allowing users to modify system startup routines (the feature request).

1 Like