From: Andreas Dilger <adilger@clusterfs.com>
To: Mark Fasheh <mark.fasheh@oracle.com>
Cc: "Amit K. Arora" <aarora@linux.vnet.ibm.com>,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-ext4@vger.kernel.org, xfs@oss.sgi.com, tytso@mit.edu,
cmm@us.ibm.com, suparna@in.ibm.com, dgc@sgi.com,
michael.kerrisk@gmx.net
Subject: Re: [PATCH 1/5][TAKE8] manpage for fallocate
Date: Thu, 19 Jul 2007 17:58:25 -0600 [thread overview]
Message-ID: <20070719235825.GY5992@schatzie.adilger.int> (raw)
In-Reply-To: <20070719034155.GE32734@ca-server1.us.oracle.com>
On Jul 18, 2007 20:41 -0700, Mark Fasheh wrote:
> On Sat, Jul 14, 2007 at 12:16:25AM +0530, Amit K. Arora wrote:
> > After a successful call, subsequent writes are guaranteed not to fail
> > because of lack of disk space.
>
> If a write to an unwritten region requires a node split, that could result
> in the allocation of new meta data which obviously could fail if the disk is
> truly full.
>
> Granted that's unlikely to happen but maybe we should be conservative and
> say something like:
>
> "After a successful call, subsequent writes are guaranteed to never require
> allocation of file data." ?
> --Mark
In the worst case, the unwritten extent could be zero-filled before the write
is done, so no exent split is needed. We discussed this recently for the
ext4 fallocate, but didn't consider it important enough to hold the code.
Cheers, Andreas
--
Andreas Dilger
Principal Software Engineer
Cluster File Systems, Inc.
next prev parent reply other threads:[~2007-07-19 23:58 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-13 18:41 [PATCH 0/5][TAKE8] fallocate system call Amit K. Arora
2007-07-13 18:46 ` [PATCH 1/5][TAKE8] manpage for fallocate Amit K. Arora
2007-07-19 3:41 ` Mark Fasheh
2007-07-19 5:10 ` David Chinner
2007-07-19 5:31 ` Mark Fasheh
2007-07-19 23:58 ` Andreas Dilger [this message]
2007-07-13 18:49 ` [PATCH 2/5][TAKE8] fallocate() implementation in i386, x86_64 and powerpc Amit K. Arora
2007-07-13 18:50 ` [PATCH 3/5][TAKE8] ext4: fallocate support in ext4 Amit K. Arora
2007-07-13 18:51 ` [PATCH 4/5][TAKE8] ext4: write support for preallocated blocks Amit K. Arora
2007-07-13 18:52 ` [PATCH 5/5][TAKE8] ext4: change for better extent-to-group alignment Amit K. Arora
2007-07-16 5:33 ` [PATCH] ia64 fallocate system call David Chinner
2007-07-16 5:37 ` [PATCH] xfs: implement fallocate V2 David Chinner
2007-07-16 5:55 ` [PATCH] introduce fallocate support into xfs_io David Chinner
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=20070719235825.GY5992@schatzie.adilger.int \
--to=adilger@clusterfs.com \
--cc=aarora@linux.vnet.ibm.com \
--cc=cmm@us.ibm.com \
--cc=dgc@sgi.com \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.fasheh@oracle.com \
--cc=michael.kerrisk@gmx.net \
--cc=suparna@in.ibm.com \
--cc=tytso@mit.edu \
--cc=xfs@oss.sgi.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 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).