Re: [nfsv4] changing fileid of a file during a mount
Olga Kornievskaia <aglo@umich.edu> Thu, 08 March 2018 22:38 UTC
Return-Path: <olga.kornievskaia@gmail.com>
X-Original-To: nfsv4@ietfa.amsl.com
Delivered-To: nfsv4@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6561F12708C for <nfsv4@ietfa.amsl.com>; Thu, 8 Mar 2018 14:38:56 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.2
X-Spam-Level:
X-Spam-Status: No, score=-2.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FORGED_FROMDOMAIN=0.25, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.25, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com header.b=gTOPWn8k; dkim=pass (2048-bit key) header.d=umich.edu header.b=SPCSzvNF
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id tTh3bmC7r2gB for <nfsv4@ietfa.amsl.com>; Thu, 8 Mar 2018 14:38:54 -0800 (PST)
Received: from mail-vk0-x22b.google.com (mail-vk0-x22b.google.com [IPv6:2607:f8b0:400c:c05::22b]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9222B1205D3 for <nfsv4@ietf.org>; Thu, 8 Mar 2018 14:38:54 -0800 (PST)
Received: by mail-vk0-x22b.google.com with SMTP id s1so959118vke.5 for <nfsv4@ietf.org>; Thu, 08 Mar 2018 14:38:54 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc; bh=BG98b0bBzVZSvhgv+ipd3rEtHQPpCYo8HZJNfYxRZFc=; b=gTOPWn8kHUbpkZZ8KQDXGBcOZg/X1YAr/wze90Ifyu0DlZhP3lKALYj3bl7eglK2h+ TEaSQlgoURaee9bs75zlMk2pUQ8VNt8IjgjnVZXX09ceNLizI03k1WvuQqow8UdZSKpu ftIEays3sSIANhRXMvKoUPJFEQcJ69qAX9wRe/tMqNy0i9qyLEfTf2h7dSNvXtboXjFF bgsx+OQqdvDLUUg2yaBYvfIkl09HxQTyMVIKTBuwMkLvqu0RMgus5B1ZhrD41rFXaTOe TSbUdbzbOJEwYABeRFGm+nU6k6sknnhRL3GEIPrduWMX5K3wDj/dejN2AX3J3QnxBtZP RMuQ==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=umich.edu; s=google-2016-06-03; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc; bh=BG98b0bBzVZSvhgv+ipd3rEtHQPpCYo8HZJNfYxRZFc=; b=SPCSzvNFsT1lxJrtojSyMfQ3b4zLCISVEhADe1D+4/nUcdvRNoyWhf5/DZiMOFN1dO swF0DOuAgmlSXlp6rXNbfljazebHdLbXDV2113DkFcd4W9wC4UqFG/ajsJk72Aixe4+f WitSSj7NU9/99ZVoifbqkT3EnC3Xf7+GIWirRqdDJbhq+JHfnznEYr15Fai4WQfBszg2 ujr238kpjL39zmffRl+bpIr6v373eTUMkW2mlJWJvksIEGoMql/13BEbubQxKkIePU7Z Kf1tv3WBh0D0KuYbqjyf5oGbHkmys+KGtXMUK3UxfHK5TPI3jQi4Nd8xeLMLpsQxLDKu SKiA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to:cc; bh=BG98b0bBzVZSvhgv+ipd3rEtHQPpCYo8HZJNfYxRZFc=; b=HUOZDCf9fDc0JS/RqoHUnCfaoK9aZGug3b0NhDec1iq5QXZuiTJykqJLn06tU5Jvab BzspOt/G5jBeLLb4HjbuKqkvG9aek5iSkBzHC4er1In6EsDsB+320XjWNpzLwru84psd Qv4YAsAe6xdr7cwpqVwcAbizQ4aHmzzDQWKyjg52GJgD1QSool/U9vkJczo0YtVdTlMB kFxsMdu8DyBvly9LJmgtheXhsqresz7LbUKhcnvzYGOLQiXNxWSGus818AKyxQ00N7OQ OEXOC/E4qekwFVjMwz1OzaxMBb/RQ2q9sIAm/lzDwO4QJzofe3VrLsn25pL8L+t9upOL aHnA==
X-Gm-Message-State: APf1xPAavjzNdvGoSGLRfuNUIOs98+yVw6MCdtk4Krp7iTg16o1slawN X+rdSgqQPU0UWu2RbX+2CgFcFqkeL1sVCEC5IkU=
X-Google-Smtp-Source: AG47ELsQj5nb2P1G28dIr9zH5yJjsqU5ZpK3pQolJO4lMkCQ3ssn0tbZpRxpla3SMugYYMGHKvsLDT/ANc3yxiubT3I=
X-Received: by 10.31.56.208 with SMTP id f199mr19757552vka.45.1520548733411; Thu, 08 Mar 2018 14:38:53 -0800 (PST)
MIME-Version: 1.0
Sender: olga.kornievskaia@gmail.com
Received: by 10.103.91.65 with HTTP; Thu, 8 Mar 2018 14:38:52 -0800 (PST)
In-Reply-To: <28CEC610-346C-4F01-BAC9-2AAED94E6C99@primarydata.com>
References: <CAN-5tyEce2x+e6AuYi7vBC-=5nOPvtEbTD1VvLYA_Q9VBcW0fA@mail.gmail.com> <28CEC610-346C-4F01-BAC9-2AAED94E6C99@primarydata.com>
From: Olga Kornievskaia <aglo@umich.edu>
Date: Thu, 08 Mar 2018 17:38:52 -0500
X-Google-Sender-Auth: fzybM-QT2F6CBpCvMUoSRu65Czg
Message-ID: <CAN-5tyEhVL5QYsxZ2GhZr0Zac0vfKiwpiG8hXfVkzHx=K7nnDQ@mail.gmail.com>
To: Thomas Haynes <loghyr@primarydata.com>
Cc: "nfsv4@ietf.org" <nfsv4@ietf.org>
Content-Type: text/plain; charset="UTF-8"
Archived-At: <https://mailarchive.ietf.org/arch/msg/nfsv4/4vTj-F1IY6R4Pdvb6rNqmd5LPP0>
Subject: Re: [nfsv4] changing fileid of a file during a mount
X-BeenThere: nfsv4@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: NFSv4 Working Group <nfsv4.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/nfsv4>, <mailto:nfsv4-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/nfsv4/>
List-Post: <mailto:nfsv4@ietf.org>
List-Help: <mailto:nfsv4-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/nfsv4>, <mailto:nfsv4-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 08 Mar 2018 22:38:56 -0000
On Thu, Mar 8, 2018 at 5:27 PM, Thomas Haynes <loghyr@primarydata.com> wrote: > > >> On Mar 8, 2018, at 2:17 PM, Olga Kornievskaia <aglo@umich.edu> wrote: >> >> Hi folks, >> >> Is it allowed that the server changes a fileid of a file on a mounted >> file system? >> >> Client opens a file a gets a filehandle A as well as attributes of fileid=1000. >> Server changes's this file's fileid=2000. >> client request attributes for the filehandle A and gets a fileid=2000. >> >> What is suppose to happen? Should the client simply update its >> attributes? > > No - the fileid uniquely determines the file within the filesystem. > >> Linux client at some point used to fail in this case with >> ESTALE. Currently linux client silently ignores the changes in the >> fileid done by the server. > > Bisect the change and see what the rational was for it? Anna changed it to fix a circular directory warning for "junctioned" mount points. Perhaps the fix wasn't necessary to ignore the changes in fileid. I think it was an attempt to also check that mounted_on_fileid didn't change. But unintentionally, if the mounted_on_fileid() didn't change that's what "validates" fileid even if fileid did change. >> In RFC 7530 I see wording that uses "fileid+fsid" to determine if two >> file handles are referring to the same file or not. But it doesn't say >> anything about if the "fileid" is like a filehandle and suppose to >> remain unchanged for the lifetime of the file object. > > If it changes, then it is no longer the same object that the > file handle referred to. I read this that you think that according to the spec changing fileid isn't allowed. > >> >> In RFC 5661 I read about transitions and how in transparent >> transitions, the file handles are persistent and fileid/fsid(s) don't >> change across transitions. But also in section "11.7.4. Fileids and >> File System Transitions" that talks about transition and how fileids >> are (or could be) changing specially if transition is between >> different vendors and can't preserve fileid sameness. >> >> But all of this makes me think that on a "non-transition" case a >> server shouldn't be changing a fileid. But I can't find anything in >> the spec to support this. >> >> Any clarification on this would be highly appreciated. Thank you for the comments! >> >> Thank you. >> >> _______________________________________________ >> nfsv4 mailing list >> nfsv4@ietf.org >> https://www.ietf.org/mailman/listinfo/nfsv4 >> >
- Re: [nfsv4] changing fileid of a file during a mo… Thomas Haynes
- [nfsv4] changing fileid of a file during a mount Olga Kornievskaia
- Re: [nfsv4] changing fileid of a file during a mo… Olga Kornievskaia
- Re: [nfsv4] changing fileid of a file during a mo… J. Bruce Fields