Received-SPF: pass (google.com: domain of linux-nfs+bounces-200-linux.lists.archive=gmail.com@vger.kernel.org designates 2604:1380:40f1:3f00::1 as permitted sender) client-ip=2604:1380:40f1:3f00::1;
From: Benjamin Coddington <bcodding@redhat.com>
To: Cedric Blancher <cedric.blancher@gmail.com>
Cc: Linux NFS Mailing List <linux-nfs@vger.kernel.org>
Subject: Re: NFSv4.2: How to deallocate a range of bytes in a file, aka
 "punch a hole"?
Date: Thu, 30 Nov 2023 07:45:19 -0500
Message-ID: <2F13FCCD-8450-43DA-8C2D-0554BAA32037@redhat.com>
In-Reply-To: <CALXu0Uc9Q-i4TPVP4LQGfHcbpp-vwSL4a1xEzVuFxqDQwfbUCw@mail.gmail.com>
References: <CALXu0Uc9Q-i4TPVP4LQGfHcbpp-vwSL4a1xEzVuFxqDQwfbUCw@mail.gmail.com>
Precedence: bulk
MIME-Version: 1.0
Content-Type: text/plain

On 30 Nov 2023, at 5:18, Cedric Blancher wrote:

> Good morning!
>
> Linux has fallocate(fd, FALLOC_FL_PUNCH_HOLE|FALLOC_FL_KEEP_SIZE, ...)
> to punch a hole into a file, i.e. deallocate the blocks given and make
> the file a "sparse file".
>
> But how is this implemented on NFSv4.2 COMPOUND level? How does a
> NFSv4 compound look like to punch a hole say from position 30000 to
> position 35721?

Are you interested in the current linux client's implementation?  You could
look at a wire capture of the operation to find out.

Its going to be something like PUTFH, DEALLOCATE, GETATTR..

Ben