IETF Logo Mail Archive

Re: [nfsv4] question: remove of a file in multi-protocol case

David Noveck <davenoveck@gmail.com> Fri, 30 September 2022 18:55 UTC

Return-Path: <davenoveck@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 DB94CC14CF13 for <nfsv4@ietfa.amsl.com>; Fri, 30 Sep 2022 11:55:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.105
X-Spam-Level:
X-Spam-Status: No, score=-7.105 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id M7dzeLeYO5XY for <nfsv4@ietfa.amsl.com>; Fri, 30 Sep 2022 11:55:16 -0700 (PDT)
Received: from mail-oo1-xc2e.google.com (mail-oo1-xc2e.google.com [IPv6:2607:f8b0:4864:20::c2e]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 22B81C14CF14 for <nfsv4@ietf.org>; Fri, 30 Sep 2022 11:55:16 -0700 (PDT)
Received: by mail-oo1-xc2e.google.com with SMTP id r136-20020a4a378e000000b004755953bc6cso2818818oor.13 for <nfsv4@ietf.org>; Fri, 30 Sep 2022 11:55:16 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date; bh=UqDFGJW92+dJI2FDwhhJ7srnIsY56W895Oio0vPfeOw=; b=C4FnavhwNbnuX49kCvSnY814DHh+H175m+KQhUfHT6npsUVh9uEOLng8xs9VelxJyO DY94sSkoLs7ru7E1eJXeDtX93DXUsO/OGJSes3AS2xvT8PSMN+pUOXM4Ed6dmaA4Lnsk Bquc8du+Tbkz5e87OkLhWTpmZmg+zpqnsMQRo7E1RmMHeUxnWFbi66cCBeqV5v5186Xd JJKQcj9VPHpqyVXvlxHH2+TpKXH0lVunFVG3Fb28nsdWaGq8sHFzmVTbbEPF0xjGebJf 02Z255La95GQ++605PKOB7gIZ1GTdxsH3VAYE0QSeqbBgSiWbKd8ie6kEDNTOk5gWCB6 DQVw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date; bh=UqDFGJW92+dJI2FDwhhJ7srnIsY56W895Oio0vPfeOw=; b=tq0HTxHc9+tKB3g5z/vdsNcwTIlJAAgZg1oEWNfPSMwdyu3hq/7ckbJy8OrD+IM7FJ x8R3WrLk8aBo2/7yb74Vw3b0zICf6VdPThzFAcY1ENtUnrkAMXGpim8ubrKoG0+fAwYG S7NHdUKtuwenVwz4sro8nBm9jiJ/TdSNvCJ0O9PMn5IaNv0pNs0d7ULIAetcqyNUPdnx t1zbxDOk171yPUTkbosCZ+wJlJhcw9vr586PJr8dXpIm2cUOHIxg65ugfnPGpqiR4PP1 0s8IabZdj6KOU7m8/9tU0h9k6WnOIjZ+tqX6SdvA+bS1D5HvL96t1arwUgSSpLLCgkgH Wtjg==
X-Gm-Message-State: ACrzQf3HHyWZPbTkGkcuYWw6zDXU27z95jv2Bp30n0/sLIsnA4v8m+8q kX9U87mDTRVI4VC20Ys0+NK8ZIGnFcCukUXNwb8=
X-Google-Smtp-Source: AMsMyM6EJ2AOvi34CjDfaXNNrnxz3Ojlhp6xBVXYNgtK9QyebsX4wXK0Xb5i7zqF6JbbX+wdGQYXZtEE1kykEoD08aQ=
X-Received: by 2002:a05:6820:1505:b0:476:994:186e with SMTP id ay5-20020a056820150500b004760994186emr3860022oob.28.1664564114837; Fri, 30 Sep 2022 11:55:14 -0700 (PDT)
MIME-Version: 1.0
References: <CAN-5tyGiM8VZLhXdQ8tJn7jpydWiK8u+b8+xJgh-LXq_owgapw@mail.gmail.com>
In-Reply-To: <CAN-5tyGiM8VZLhXdQ8tJn7jpydWiK8u+b8+xJgh-LXq_owgapw@mail.gmail.com>
From: David Noveck <davenoveck@gmail.com>
Date: Fri, 30 Sep 2022 14:55:05 -0400
Message-ID: <CADaq8jfTRGhVykV=TAueDDrOhPy1O8-3PzzRu1J8CGbYJ1ebDw@mail.gmail.com>
To: Olga Kornievskaia <aglo@umich.edu>
Cc: NFSv4 <nfsv4@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000c555d705e9e9888d"
Archived-At: <https://mailarchive.ietf.org/arch/msg/nfsv4/iw9nhA03zRxDXfp1MB8CEIOLQbo>
Subject: Re: [nfsv4] question: remove of a file in multi-protocol case
X-BeenThere: nfsv4@ietf.org
X-Mailman-Version: 2.1.39
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: Fri, 30 Sep 2022 18:55:19 -0000

On Fri, Sep 30, 2022, 2:10 PM Olga Kornievskaia <aglo@umich.edu> wrote:

> Hi folks,
>
> What are the expectations of the server and client behaviours in the
> following situation?
>

There are multiple situations below.

>
> Say we have 2 clients (using different protocols (version), one of
> which is NFS), say v4.0 client and v4.1 clients


That's one situation which the spec should address but I'm not clear it
does.  5661bis will have to.

or it could be NFS and
> CIFS) have opened a file.


That cannot be dealt with by the spec, but I'll try to address the issue
here.

Both are accessing the file. Then an NFS
> client closes the file and issues a REMOVE of the file command.
>

The answer is different for v4.0 and v4.1.


> Can a client assume it can successfully perform a remove regardless of
> another party having the file opened?


Only if it is a 4.1client and got preserve-unlinked on the OPEN.

Or should the client be prepared
> to receive NFS4ERR_FILE_OPEN error (even though this client has closed
> its file descriptors)?
>

Yes.  He has to unless preserve-unlinked is involved.


> Should the server be expected to not error the client's REMOVE
> operation and. internally handle the removal while still allowing
> access to the file by another client?
>

If he supports preserve-unlinked, he has taken on that burden.  The other
open can be the result of any remote access protocol that has an OPEN
operation or can be the result of a local OPEN.

This all assumes the file cannot be accessed using the removed  name.


> Thank you for the feedback.
>
> _______________________________________________
> nfsv4 mailing list
> nfsv4@ietf.org
> https://www.ietf.org/mailman/listinfo/nfsv4
>

v2.23.0 | Report a Bug | By Email