From: Christoph Hellwig <hch@lst.de>
To: Benny Halevy <bhalevy@panasas.com>
Cc: Rees <rees@citi.umich.edu>, linux-nfs@vger.kernel.org
Subject: Re: [RFC] spnfs-block: restore i_op->fallocate
Date: Thu, 31 Mar 2011 15:53:38 +0200 [thread overview]
Message-ID: <20110331135338.GA20235@lst.de> (raw)
In-Reply-To: <4D942506.1020505@panasas.com>
Btw, how is the spnfs-block support supposed to work at all?
fallocate creates unwritten extents, and I can't actually
spot a place that would later convert them to regular extents.
And how does it work for filesystems without ->fallocate like
ext3?
And how do we prevent clients from reading uninitialized
blocks in areas allocated on the server but not written
to yet. Is there anything like unwritten extents in the
on the write protocol?
next prev parent reply other threads:[~2011-03-31 13:53 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1301500460-16467-1-git-send-email-bhalevy@panasas.com>
2011-03-30 15:58 ` [RFC] spnfs-block: restore i_op->fallocate Christoph Hellwig
2011-03-30 17:11 ` Benny Halevy
2011-03-30 17:33 ` Christoph Hellwig
2011-03-31 6:53 ` Benny Halevy
2011-03-31 13:53 ` Christoph Hellwig [this message]
2011-04-01 8:30 ` Benny Halevy
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=20110331135338.GA20235@lst.de \
--to=hch@lst.de \
--cc=bhalevy@panasas.com \
--cc=linux-nfs@vger.kernel.org \
--cc=rees@citi.umich.edu \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).