[nfsv4] changing fileid of a file during a mount

Olga Kornievskaia <aglo@umich.edu> Thu, 08 March 2018 22:17 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 3476F12708C for <nfsv4@ietfa.amsl.com>; Thu, 8 Mar 2018 14:17:06 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.5
X-Spam-Level:
X-Spam-Status: No, score=-1.5 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_NONE=-0.0001, SPF_PASS=-0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com header.b=Nj0aO1fR; dkim=pass (2048-bit key) header.d=umich.edu header.b=WtGSaNTx
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 XTtKeNph_VaP for <nfsv4@ietfa.amsl.com>; Thu, 8 Mar 2018 14:17:05 -0800 (PST)
Received: from mail-ua0-x236.google.com (mail-ua0-x236.google.com [IPv6:2607:f8b0:400c:c08::236]) (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 4895D124234 for <nfsv4@ietf.org>; Thu, 8 Mar 2018 14:17:05 -0800 (PST)
Received: by mail-ua0-x236.google.com with SMTP id n24so952330ual.12 for <nfsv4@ietf.org>; Thu, 08 Mar 2018 14:17:05 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:sender:from:date:message-id:subject:to; bh=t1h6jcdSYXDZ/TXkbSVNdL9zawBP1vsdoWHcdtk2bMU=; b=Nj0aO1fRVeouvCd8R+l9kzu2hvMqIgv+RnPUd4u4nwBoKDwLfd1eUzbpfGyPvoyyA2 PMiWG18EZS7xDKbzi+OMKoajbrsICZDAN7Jpfr8elbuZgLW8PfyWRbQlsgLd2Sv55lbD XSft17gmxcIaniFY/O1PgJE8uPx+drAdW1HmFdmSJtrYmNT8nW03+Wf0V7bck7ZiiQRU k8uokdEj8BP7S5yzW0pE4aZxNXkPt/nkUL4DO8e/a5taa7LoGdoMx0RkR8BkmAQcaZEw L2g2m49GQRQI1cSXkw05ithya+MXB9tDmAHyticYSgrtIJuoLNC61RS5FEwQY2wz/mxF +bjQ==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=umich.edu; s=google-2016-06-03; h=mime-version:sender:from:date:message-id:subject:to; bh=t1h6jcdSYXDZ/TXkbSVNdL9zawBP1vsdoWHcdtk2bMU=; b=WtGSaNTxOb/Gbqdn6X2TifoOl17tpQwj/rK5mxY2whrzU6J30UiuWjYAG+RWDGD0US uRsS1HQlBdlG+/Ur8VSuWP9KA6G+VLFJcbxpzaliqYDas1JhkzcF8h89JZao6H3D9JGU IfORTcrm0YzpAJMakHmqOkzqS1kh8eoTx6D8pQ6SjO5HO6dj33qcGWfZsdNScntqtQQn 04m1mas+oktgoql7/ZvwW/zSSfZkRFnQuH8t9j418hQBLjqd5wodH3ZTfl/Ks/fNxnX1 XnAXY7vxUcOSQ8yVLEiFDn8YIIfOI1/vpea0gwnxrzKsPNW/BYf3J4PWUfOs4j9rkZAZ wIwA==
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:from:date:message-id:subject :to; bh=t1h6jcdSYXDZ/TXkbSVNdL9zawBP1vsdoWHcdtk2bMU=; b=EaD1ibe0jGq6bETwGC6NvnHUk+02/qduYaS9KoVjP1PTVxOcE0joaNsOpo/UtPW3Qf uLnumoc7EBg58cfHg/lZMtFUmxRIwa/vD2HJmJV250aE3n3jB7//Z8rm7zs6EvsRP46i XaqD6aHkWs+n0LdcjHitu7vTaa2hsxi5u1lYGjD84fjJNQwxggF/7xbzk3TdSuQL0NEI MM8NKiDa5+JttJGfyEB69i6ZVFuELfu5wYzMTi58sKwFS70Iz9MRNbubWgSgwEqKFgdk QC9VmEfGeKhsddE6igpqAX7fcfp/5ndlRCFREi0ux1J/vZt3kgXGTu+BknHRichjaKwG ZMXw==
X-Gm-Message-State: APf1xPDYsu+OkQVL4ZFPFQoTVkTgzJK946NjMp+2MlJwizsQ0HyIJwHD 09+V7yCBJynQWa+yQB2Tx0GffgPUwdS0nLDODrE5bQ==
X-Google-Smtp-Source: AG47ELvxqdZW4Xr/5dYG1styC9A9fL0N3PHMdUEsvS8Ec1XVJrd9wdSjvjXX/yP4iLH9FmcT+PyQ7xwYRlxMCrNO7g8=
X-Received: by 10.176.19.11 with SMTP id g11mr19929302uae.76.1520547424000; Thu, 08 Mar 2018 14:17:04 -0800 (PST)
MIME-Version: 1.0
Sender: olga.kornievskaia@gmail.com
Received: by 10.103.91.65 with HTTP; Thu, 8 Mar 2018 14:17:03 -0800 (PST)
From: Olga Kornievskaia <aglo@umich.edu>
Date: Thu, 08 Mar 2018 17:17:03 -0500
X-Google-Sender-Auth: x9p1Ycjdn4KNYQSqT1Sn38jgNSo
Message-ID: <CAN-5tyEce2x+e6AuYi7vBC-=5nOPvtEbTD1VvLYA_Q9VBcW0fA@mail.gmail.com>
To: nfsv4@ietf.org
Content-Type: text/plain; charset="UTF-8"
Archived-At: <https://mailarchive.ietf.org/arch/msg/nfsv4/DbnIIj0fROBEvNYolxe-Lsr2IFg>
Subject: [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:17:06 -0000

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? 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.

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.

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.