Bug 269297 - zfs: Unable to shutdown zfs machine after 52bcdd58f42dd37ca13e3671cb0d4ca87ce9a2a1(kgssapi: Increase timeout for kernel to gssd(8) upcalls)
Summary: zfs: Unable to shutdown zfs machine after 52bcdd58f42dd37ca13e3671cb0d4ca87ce...
Status: Closed Not A Bug
Alias: None
Product: Base System
Classification: Unclassified
Component: kern (show other bugs)
Version: CURRENT
Hardware: Any Any
: --- Affects Only Me
Assignee: freebsd-fs (Nobody)
URL: https://cgit.freebsd.org/src/commit/?...
Keywords: regression
Depends on:
Blocks:
 
Reported: 2023-02-03 05:14 UTC by Masachika ISHIZUKA
Modified: 2023-02-06 13:37 UTC (History)
3 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Masachika ISHIZUKA 2023-02-03 05:14:24 UTC
Unable to shutdown zfs machine.
I've waited over 10 minutes and the shutdown process seems to hang.
Reverting this patch allowed me to shutdown gracefully.
Comment 1 Mark Linimon freebsd_committer freebsd_triage 2023-02-06 02:31:47 UTC
Assign to mailing list but Cc: committer in question.
Comment 2 Rick Macklem freebsd_committer freebsd_triage 2023-02-06 03:46:49 UTC
Ok, sounds weird. I have no idea why ZFS
would have anything to do with the KGSSAPI
and upcalls to the gssd, which is the only
case the timeout change affects.

A few questions about your setup:
- Are you running the gssd(8) daemon and
  using Kerberized NFS?
  - If not, there is no reason to run the
    gssd or even load the kgssapi.ko module.
- Do you have "options KGSSAPI" in your kernel
  config?
- What are you doing to "shutdown" the system?

You can try changing the timeout from "5 * 60"
to "60", since the timeout only needs to be
increased slightly to fix the problem this commit
addresses.
The only case I know of that causes the approximately
27sec delay in an upcall is a misconfigured DNS.
Make sure your /etc/resolv.conf refers to a valid DNS
service or delete the file.
Comment 3 Masachika ISHIZUKA 2023-02-06 06:14:34 UTC
(In reply to Rick Macklem from comment #2)
Thank you for reply.
It happend again without this patch, today.
So, I think this hang has occured another reason.
I'm sorry to disturb you.

- Are you running the gssd(8) daemon and
  using Kerberized NFS?

No. I don't use gssd nor Kerberized NFS.

- If not, there is no reason to run the
   gssd or even load the kgssapi.ko module.

I don't run gssd and don't load kgssapi.ko

- Do you have "options KGSSAPI" in your kernel
  config?

No.

- What are you doing to "shutdown" the system?

% su
# shutdown -p now

- Make sure your /etc/resolv.conf refers to a valid DNS service or delete the file.

% cat /etc/resolv.conf
search foo.bar
nameserver 127.0.0.1
options edns0

And local_unbound is working fine.
Comment 4 Masachika ISHIZUKA 2023-02-06 06:22:46 UTC
(In reply to Masachika ISHIZUKA from comment #3)
The situation where shutdown is still not possible continues, but it seems to be another cause, so I will close this thread for now.
Comment 5 Rick Macklem freebsd_committer freebsd_triage 2023-02-06 13:37:51 UTC
Ok, thanks for letting me know.
Since you do not run gssd or load
kgssapi.ko, this change cannot affect
your system.

Good luck finding why it wouldn't shut down.