From nobody Sun Dec 24 23:00:17 2023 X-Original-To: fs@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4SyxMd27tyz54lK0 for ; Sun, 24 Dec 2023 23:00:29 +0000 (UTC) (envelope-from rick.macklem@gmail.com) Received: from mail-oa1-x2c.google.com (mail-oa1-x2c.google.com [IPv6:2001:4860:4864:20::2c]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1D4" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4SyxMd0S4kz3Zlx; Sun, 24 Dec 2023 23:00:29 +0000 (UTC) (envelope-from rick.macklem@gmail.com) Authentication-Results: mx1.freebsd.org; none Received: by mail-oa1-x2c.google.com with SMTP id 586e51a60fabf-2044d093b3fso1471638fac.3; Sun, 24 Dec 2023 15:00:29 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1703458828; x=1704063628; darn=freebsd.org; h=content-transfer-encoding:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:from:to:cc:subject:date :message-id:reply-to; bh=1SgrR8ZDFy9ABmSf9Ro25yoUpEUIc8vxFqR12WgAzg8=; b=gn0yLAbP9YhZ5m8EY93sgnA19MozGvr9w3OmrGrinuAoSfQEh4KqHVVw6tZnFzqyAS vkaqC39Y/Q+dg06x/zh7W5eHmRZmQjgj3jPCtkazmJwekY8J1gwnGkAwihOrluIAic6y BiaM1Q0P+eSXd5ZDqpbJsHYl7shcpflSX2KdktJKTzy2ZCEMFcsMstuyfrPGOps6Imx3 okWz4SzZoQPI2gTwNYDYw/bapj/zYVhQNeG8Wt90RqvwdoP8L6Gphfba2bmcmKOwvQlq 0DrcTqW6MIFL6mBA1vMIua+imi/XvKOgfYatYM+1KAeZT8bhrFAuAH7+5Jt8HDo8mvHH PKOw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1703458828; x=1704063628; h=content-transfer-encoding:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:x-gm-message-state:from:to:cc :subject:date:message-id:reply-to; bh=1SgrR8ZDFy9ABmSf9Ro25yoUpEUIc8vxFqR12WgAzg8=; b=g2MYhwctbEhtmxsuEGDH+3q9BO40kc8vo5dgxiLrA33fhi4UzZb4JKC489O5A7fHkW rvtAJLF+8VuBI4j2BKjHTnEbsA0S8vtlPJvnpKD1gUZ4uv3E15LOFN3KKcZaHeQTpT9c Ou2NkYaD4gTi0JkQ6SpzwhhUoY2FoHqC4I/aYbcNk8Ax9j5zptmETDjFUui1kGZAaNZ9 +8baJa6FXjvvtNKmtXA9kFlNoc79U5q8FYEAkJSc+hgaT2aIfCTar0WWeRe7L2aD/72l oH5uJQnQoTqpU19QbsTdu+URPd9x57KbUq27j4eTOzPybH4pfqBZAWnQFN+SkN14OEbY ozhA== X-Gm-Message-State: AOJu0YxvUzjU1+8/nXmiLuQgCE20ptUlx0jkevkzMpJmLYv4c26RSjKv RgAbTbvNhFhIEl8JmpqbJUA//bH8jNp7OGpJNP4mQM6LGQ== X-Google-Smtp-Source: AGHT+IFwNEXVOWOuC61JdBcNStQKS7Ab+pndhGy8TXleg19zKMt+GBqdm8aU+yLYy2q0mrTFKQ1LglUgWavimRatrPk= X-Received: by 2002:a05:6870:797:b0:204:7f1c:1ec8 with SMTP id en23-20020a056870079700b002047f1c1ec8mr1854986oab.2.1703458827845; Sun, 24 Dec 2023 15:00:27 -0800 (PST) List-Id: Filesystems List-Archive: https://lists.freebsd.org/archives/freebsd-fs List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-fs@freebsd.org MIME-Version: 1.0 References: In-Reply-To: From: Rick Macklem Date: Sun, 24 Dec 2023 15:00:17 -0800 Message-ID: Subject: Re: [Bug 275905] nfs client: mount becomes unresponsive To: bugzilla-noreply@freebsd.org Cc: fs@freebsd.org Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:15169, ipnet:2001:4860:4864::/48, country:US]; TAGGED_FROM(0.00)[] X-Spamd-Bar: ---- X-Rspamd-Queue-Id: 4SyxMd0S4kz3Zlx On Sun, Dec 24, 2023 at 8:01=E2=80=AFAM wrot= e: > > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D275905 > > --- Comment #5 from Lexi --- > the client keytab should be fine, since i only created it about 2 days ag= o when > i installed this host and there was no previous principal for this fqdn. > > 'kinit -k host/fqdn' on the client seems to work: > > # kinit -k host/ilythia.eden.le-fay.org > # klist > Credentials cache: FILE:/tmp/krb5cc_0 > Principal: host/ilythia.eden.le-fay.org@EDEN.LE-FAY.ORG > > Issued Expires Principal > Dec 24 15:54:16 2023 Dec 25 01:54:16 2023 > krbtgt/EDEN.LE-FAY.ORG@EDEN.LE-FAY.ORG > > > Does this hang occur frequently or was this a "one time" hang on a moun= t that usually behaves ok? > > as i mentioned, i only installed this host 2 days ago, so i can't say for= sure, > but so far it has reliably occurred twice about 10 hours after booting so= it > seems to be 100% reproducible. (iow, it never *hasn't* occurred at that = time.) > > in the mean time, i've temporarily switched the mount from sec=3Dkrb5p to > sec=3Dkrb5 to see if this fixes the issue; aiui, this means no GSS should= be > involved after the initial mount, so i expect it will, but i'm happy to d= o any > other testing you need. Not exactly. sec=3Dkrb5 says that a RPCSEC_GSS (think Kerberos) session is used to identify the user for all RPCs. The difference w.r.t. krb5p is t= hat it does not encrypt the NFS payload. I doubt it will make any difference, but it sounds like you'll know soon en= ough. I now have a hunch w.r.t. what might be broken, but I need to look at the c= ode (and if my hunch seems correct) and maybe come up with a patch. You could try the "syskrb5" mount option, which avoids use of the keytab an= d allows "system operations that maintain the state" to use AUTH_SYS, while t= he rest (all involving file data) use Kerberos. (If my hunch is correct, this will not fix the problem, but might cause it to behave better.) rick > > -- > You are receiving this mail because: > You are the assignee for the bug.