IETF Logo Mail Archive

Re: [nfsv4] LAYOUTERROR in draft-ietf-nfsv4-minorversion2-40

Trond Myklebust <trondmy@gmail.com> Sun, 24 January 2016 17:34 UTC

Return-Path: <trondmy@gmail.com>
X-Original-To: nfsv4@ietfa.amsl.com
Delivered-To: nfsv4@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4C1B41A8828 for <nfsv4@ietfa.amsl.com>; Sun, 24 Jan 2016 09:34:33 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level:
X-Spam-Status: No, score=-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_FROM=0.001, SPF_PASS=-0.001] autolearn=ham
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 y6QwA2qPPK3t for <nfsv4@ietfa.amsl.com>; Sun, 24 Jan 2016 09:34:31 -0800 (PST)
Received: from mail-yk0-x242.google.com (mail-yk0-x242.google.com [IPv6:2607:f8b0:4002:c07::242]) (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 AFA721A882B for <nfsv4@ietf.org>; Sun, 24 Jan 2016 09:34:31 -0800 (PST)
Received: by mail-yk0-x242.google.com with SMTP id v14so10122248ykd.1 for <nfsv4@ietf.org>; Sun, 24 Jan 2016 09:34:31 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=kZcFbthm8GIPce4IAjznLwyu/OLnz0mqbOkJpqEyRio=; b=f2pcmYxyf4IUo0M2PYltdGNVec3BEFpfj69dDBjh4C+nMCBfjC2hJfeXLaxhfyLC8v bdBaN6Ov2U/bhgtPQvsjC4pqZGG9BQXE+TKEqEBxkDbRTSHaV66iuzOrisz8laHZ0jdu kZ0xrZ3hddM/cnRPSn0FTp3nUp8IgcGE6Dbl5At3Ngf60OiW6NvOtIEEwmFmzGEUtp6M kSUekyYXvK18dq0n2DqGH8/YXhhCS6QCMZh0OlXU9BNDZ/JlrTfTz+K8B+9UbUSRIfHp mgW44s7kPI5VIHaPp8Thxf2tgi9dESn+4QZv2l2Z3jQQ5+Ghc5t75POFT1305KhOE3qj VqUg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=kZcFbthm8GIPce4IAjznLwyu/OLnz0mqbOkJpqEyRio=; b=herAIywsVUJAoQJPJ79gN1ZdJEwMxVOa8XHCxOz5itGIgZFgy4chQ/6qZW23US6aSL owUTcexE8cnzPkn6ixTIp2SZjzjDojkY7+Y65IB+DVpIXQmR5tgY7hSBGJbwt6QTthze fFGAvDAGdMlQg3WMVd5FKSOEXLSFhOgOfsfeBxoI/EqYtVxGu7CQEs6c9Uj0ti/bX+51 qb+xJXaFTaNDIyo9Fx61Swwn9aSSEJwNE9lGjHkSiUCEUr95kzAm/lP5zWYwYJ5N1Hpw kg6mlQlaIbEgokC6DAV8xPZbgkSuyWK+Ek2j74tzjemQl1OrE/HyGHq6GfShibEGMra6 rvrw==
X-Gm-Message-State: AG10YOR931k0ubYfiGAmTTbDU8yGm+aH6+L0pY2jMmxSRJrCZDxLBJx2cFw39PvtIu8OQbwzS5zeCJ9IHpuG9Q==
MIME-Version: 1.0
X-Received: by 10.129.106.2 with SMTP id f2mr6664419ywc.119.1453656870918; Sun, 24 Jan 2016 09:34:30 -0800 (PST)
Received: by 10.13.218.70 with HTTP; Sun, 24 Jan 2016 09:34:30 -0800 (PST)
In-Reply-To: <CADaq8jcE-0KqyMkbyxvFykQ3QwxgJG8X3WLNX9KaJwX9Uw+dTQ@mail.gmail.com>
References: <CAABAsM5Nv_m9UwKzCoJV5HsBb8Lm4L8VWaoVDYPD2cVGd1QWPw@mail.gmail.com> <CADaq8jcE-0KqyMkbyxvFykQ3QwxgJG8X3WLNX9KaJwX9Uw+dTQ@mail.gmail.com>
Date: Sun, 24 Jan 2016 12:34:30 -0500
Message-ID: <CAABAsM6MxEYHkX+RrRvt=nsNNHZUo8jgLovo2cgHbrhSQO1vXQ@mail.gmail.com>
From: Trond Myklebust <trondmy@gmail.com>
To: David Noveck <davenoveck@gmail.com>
Content-Type: text/plain; charset="UTF-8"
Archived-At: <http://mailarchive.ietf.org/arch/msg/nfsv4/TaWfOhuT1ZfZRq0mZZgHTtwE5oE>
Cc: "nfsv4@ietf.org" <nfsv4@ietf.org>
Subject: Re: [nfsv4] LAYOUTERROR in draft-ietf-nfsv4-minorversion2-40
X-BeenThere: nfsv4@ietf.org
X-Mailman-Version: 2.1.15
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: Sun, 24 Jan 2016 17:34:33 -0000

As I said in the reply to Benny's email, the question then becomes
"what values are servers setting for 'ca_maxoperations' during session
negotiation"?

Cheers
  Trond

On Sun, Jan 24, 2016 at 5:23 AM, David Noveck <davenoveck@gmail.com> wrote:
> You might consider reporting multiple ranges by using multiple
> LAYOUTERRORs in a COMPOUND, given that each
> LAYOUTERROR only allows a single range to be reported.
>
> On Sat, Jan 23, 2016 at 10:45 AM, Trond Myklebust <trondmy@gmail.com> wrote:
>>
>> Hi,
>>
>> When looking to implement LAYOUTERROR from
>> https://tools.ietf.org/html/draft-ietf-nfsv4-minorversion2-40, I
>> noticed there is a major difference between it and the way we're doing
>> error passing in LAYOUTRETURN. While the latter allows you to send an
>> array of several error reports for different byte ranges on the same
>> file, the LAYOUTERROR spec only allows you to specify a single byte
>> range.
>>
>> Being able to specify errors as an array of ranges is somewhat of a
>> requirement for the flexfiles environment. In the case where the data
>> is mirrored across several DSes, reporting the actual byte ranges
>> where errors occurred can significantly cut down on the amount of work
>> that the server has to perform to fix the mirroring when errors start
>> to occur; instead of rewriting the whole file, it can just rewrite
>> those chunks that had errors.
>>
>> A typical scenario where this might happen is if the file is fenced,
>> and so the WRITEs start receiving EACCES calls; unless you are
>> extraordinarily lucky, the fencing will leave one set of successful
>> writes on one mirror image, and a different set on the other (due to
>> timing, RPC reordering, etc).
>>
>> While I can continue to use LAYOUTRETURN for most cases, I was hoping
>> to use LAYOUTERROR for those cases where we have queued up lots of
>> errors (due to parallel WRITEs), and so want to split the error
>> reporting into multiple RPC calls.
>>
>> Cheers
>>   Trond
>>
>> _______________________________________________
>> nfsv4 mailing list
>> nfsv4@ietf.org
>> https://www.ietf.org/mailman/listinfo/nfsv4
>
>

v2.23.0 | Report a Bug | By Email