From nobody Wed Mar 27 21:43:11 2024 X-Original-To: freebsd-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 4V4gCN223Nz5FXLF for ; Wed, 27 Mar 2024 21:43:28 +0000 (UTC) (envelope-from rick.macklem@gmail.com) Received: from mail-pj1-x102b.google.com (mail-pj1-x102b.google.com [IPv6:2607:f8b0:4864:20::102b]) (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 4V4gCM6c50z4rTT for ; Wed, 27 Mar 2024 21:43:27 +0000 (UTC) (envelope-from rick.macklem@gmail.com) Authentication-Results: mx1.freebsd.org; none Received: by mail-pj1-x102b.google.com with SMTP id 98e67ed59e1d1-29ddfada0d0so267456a91.3 for ; Wed, 27 Mar 2024 14:43:27 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1711575806; x=1712180606; 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=1ysJ4Jb/L4uUVTtmr54I09xF045SdCAD2jftnZVWIeE=; b=PVIkc5x5+PMGV8OQPC2BQ83WjO+VY08jegt/OEfZlOkV+zbjfkHDgf0B43nI1+TCsc yTVVsiYdVqyxocrN/8WKjXUkGxzx/SjAqfWUVHdtQJwcOvEQTtVf2OBYveb7QxlvwDFE 1XDT+V52St6QwDhgQyVKbmBQGfTu9+JeDPHmUkuwbbD7CtjyrqW7ODGF2zbuwVtCtqU6 L9uf6zsZAd8EDd7JwogwdT6Mv3H1XbuwKx1rmmXbiK7Ib/j6H8DXoavqj306Nt/loZJI tS/WBASn/E4V6Xu8GEjP4GUnh4t7IXA/HiAUKTKBnP7rFqS6HeEPMYP45w7n7XSjjvBD UjmQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1711575806; x=1712180606; 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=1ysJ4Jb/L4uUVTtmr54I09xF045SdCAD2jftnZVWIeE=; b=AScMETH4RryhwCVowiYcYvZWRbPn061Tn43+RK2RyL7NaGaM1QZpJp8p2+nAp7R/lF iRDuPeel2I9JduqeMyiWepYkio3Q3tBLLk3OLRXHJ/gNoMIfXIiS5X6S4/8l6IBF5NTq Qma9AjookJpJjJALMurC3opqUztdUYwAO9pzC+no6jyTVarsqtYHnJUuoImFcD9B6eh1 /sFbFFqlqB2NjfnmCLBxgT5HczF8gRoBZQ0i3JRCiuuYngLzhWhK38tKoo8aYem+aefT mm+FV4T+8n51FnI23109qSFdQKAYciy+vkRZPMpGoSdVLFuqQ3SBX/JOfwaTlfH1D6kN 50aQ== X-Gm-Message-State: AOJu0Yw7UAN10W8Q1lC6HNO/Mea6nueRvkwnJEmPReEtdXke9traaDvz BFz3avDykuc+eCxBe/5Tuepp3SAt7kJbI6muWbdtacmRwBj9i8teJsJHPmsRXDlh/7imfJ9OotH HaG+KXXpDAMPoP+soqVl36WdVDct/e3c= X-Google-Smtp-Source: AGHT+IFyS4Ou7n+lNPkqgepnA+VV4RGK8EfpVWep5N/moL3cn+QFcER+ys9LZUynRN6sqylouAbZAVkBacUEd7gOGPs= X-Received: by 2002:a17:90b:5211:b0:29b:9d82:9d55 with SMTP id sg17-20020a17090b521100b0029b9d829d55mr920405pjb.8.1711575806303; Wed, 27 Mar 2024 14:43:26 -0700 (PDT) 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: <9sr72194-0pp8-1q35-ps81-236sro7437n4@yvfgf.mnoonqbm.arg> In-Reply-To: <9sr72194-0pp8-1q35-ps81-236sro7437n4@yvfgf.mnoonqbm.arg> From: Rick Macklem Date: Wed, 27 Mar 2024 14:43:11 -0700 Message-ID: Subject: Re: newnfs fileid changed "(BROKEN NFS SERVER OR MIDDLEWARE)" To: "Bjoern A. Zeeb" Cc: freebsd-fs@freebsd.org Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Spamd-Bar: ---- 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)[]; TAGGED_FROM(0.00)[]; ASN(0.00)[asn:15169, ipnet:2607:f8b0::/32, country:US] X-Rspamd-Queue-Id: 4V4gCM6c50z4rTT On Wed, Mar 27, 2024 at 11:44=E2=80=AFAM Bjoern A. Zeeb wrote: > > Hi, > > I got this recently with both sides being FreeBSD when doing NFS root in > the lab... > > newnfs: server '192.0.2.2' error: fileid changed. fsid 0:0: expected file= id 0x7034be6, got 0x7034a79. (BROKEN NFS SERVER OR MIDDLEWARE) > > Should I be worried? It usually happens when you have more than one client with the same /etchostid doing NFSv4 mounts. Either make sure each client has a unique /etc/hostid or do not use NFSv4 mounts. The NFSv4 mounts will be broken, since the server thinks they= are the same client. Often happens when systems are cloned. If you are using a diskless root fs, I'm not sure what you can do other than having a separate /etc/hostid for each of t= hem. (Maybe a symlink to a separate mounted fs?) rick > > -- > Bjoern A. Zeeb r15:7 >