From: Karl-Philipp Richter <krichter@posteo.de>
To: Anna Schumaker <schumaker.anna@gmail.com>
Cc: "linux-nfs@vger.kernel.org" <linux-nfs@vger.kernel.org>
Subject: Re: (Follow) sparse file support (development)
Date: Mon, 30 Jun 2014 13:40:52 +0200 [thread overview]
Message-ID: <53B14CC4.4000803@posteo.de> (raw)
In-Reply-To: <CAFX2Jfne-eDPBChRmBqp2N08-+i6tYBpSosnudg_J6Yd2dNNcg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1077 bytes --]
Hi Anna,
Yes you did, thank you! I'd like to recommend you to put this
information in the wiki, if you don't want to rely on $SEARCH_ENGINE
finding this thread in the mailing list archives only :)
Best regards,
Kalle
Am 30.06.2014 01:39, schrieb Anna Schumaker:
> Hi Kalle,
>
> Currently you can use SEEK_SET to create sparse files through seeking. NFS
> v4.2 (currently in development) will add support for an fallocate
> interface, but that won't be merged into Linux until after the draft is
> finished.
>
> I hope I answered your question!
>
> Anna
>
> On Sunday, June 29, 2014, Karl-Philipp Richter <krichter@posteo.de> wrote:
>
>> Hi together,
>> I had trouble finding a statement in the NFS wiki
>>
>> http://wiki.linux-nfs.org/wiki/index.php/Main_Page
>>
>> about sparse file support or development plans for it outside of (very
>> very) technical documents which I honestly didn't take the time to
>> understand. Maybe I can get you to give me short statement on this :).
>>
>> Best regards,
>> Kalle Richter
>>
>>
>
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 538 bytes --]
prev parent reply other threads:[~2014-06-30 11:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-29 16:29 (Follow) sparse file support (development) Karl-Philipp Richter
[not found] ` <CAFX2Jfne-eDPBChRmBqp2N08-+i6tYBpSosnudg_J6Yd2dNNcg@mail.gmail.com>
2014-06-30 11:40 ` Karl-Philipp Richter [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=53B14CC4.4000803@posteo.de \
--to=krichter@posteo.de \
--cc=linux-nfs@vger.kernel.org \
--cc=schumaker.anna@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.