| To: | "Amit K. Arora" <aarora@xxxxxxxxxxxxxxxxxx> |
|---|---|
| Subject: | Re: [PATCH 1/5][TAKE8] manpage for fallocate |
| From: | Mark Fasheh <mark.fasheh@xxxxxxxxxx> |
| Date: | Wed, 18 Jul 2007 20:41:55 -0700 |
| Cc: | linux-fsdevel@xxxxxxxxxxxxxxx, linux-kernel@xxxxxxxxxxxxxxx, linux-ext4@xxxxxxxxxxxxxxx, xfs@xxxxxxxxxxx, tytso@xxxxxxx, cmm@xxxxxxxxxx, suparna@xxxxxxxxxx, adilger@xxxxxxxxxxxxx, dgc@xxxxxxx, michael.kerrisk@xxxxxxx |
| In-reply-to: | <20070713184625.GB12156@amitarora.in.ibm.com> |
| Organization: | Oracle Corporation |
| References: | <20070713184125.GA12156@amitarora.in.ibm.com> <20070713184625.GB12156@amitarora.in.ibm.com> |
| Reply-to: | Mark Fasheh <mark.fasheh@xxxxxxxxxx> |
| Sender: | xfs-bounce@xxxxxxxxxxx |
| User-agent: | Mutt/1.5.11 |
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
--
Mark Fasheh
Senior Software Developer, Oracle
mark.fasheh@xxxxxxxxxx
|
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: XFS repair on / in a hosted environment, David Chinner |
|---|---|
| Next by Date: | Re: [PATCH 1/5][TAKE8] manpage for fallocate, David Chinner |
| Previous by Thread: | [PATCH 1/5][TAKE8] manpage for fallocate, Amit K. Arora |
| Next by Thread: | Re: [PATCH 1/5][TAKE8] manpage for fallocate, David Chinner |
| Indexes: | [Date] [Thread] [Top] [All Lists] |