Re: [PATCH 1/5][TAKE8] manpage for fallocate

2007-07-19 Thread Andreas Dilger
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

Re: [PATCH 1/5][TAKE8] manpage for fallocate

2007-07-19 Thread Mark Fasheh
On Thu, Jul 19, 2007 at 03:10:52PM +1000, David Chinner wrote: > % git-log 84e1e99f112dead8f9ba036c02d24a9f5ce7f544 |head -10 > commit 84e1e99f112dead8f9ba036c02d24a9f5ce7f544 > Author: David Chinner <[EMAIL PROTECTED]> > Date: Mon Jun 18 16:50:27 2007 +1000 > > [XFS] Prevent ENOSPC from

Re: [PATCH 1/5][TAKE8] manpage for fallocate

2007-07-19 Thread Mark Fasheh
On Thu, Jul 19, 2007 at 03:10:52PM +1000, David Chinner wrote: % git-log 84e1e99f112dead8f9ba036c02d24a9f5ce7f544 |head -10 commit 84e1e99f112dead8f9ba036c02d24a9f5ce7f544 Author: David Chinner [EMAIL PROTECTED] Date: Mon Jun 18 16:50:27 2007 +1000 [XFS] Prevent ENOSPC from aborting

Re: [PATCH 1/5][TAKE8] manpage for fallocate

2007-07-19 Thread Andreas Dilger
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

Re: [PATCH 1/5][TAKE8] manpage for fallocate

2007-07-18 Thread David Chinner
On Wed, Jul 18, 2007 at 08:41:55PM -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

Re: [PATCH 1/5][TAKE8] manpage for fallocate

2007-07-18 Thread Mark Fasheh
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

Re: [PATCH 1/5][TAKE8] manpage for fallocate

2007-07-18 Thread Mark Fasheh
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

Re: [PATCH 1/5][TAKE8] manpage for fallocate

2007-07-18 Thread David Chinner
On Wed, Jul 18, 2007 at 08:41:55PM -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,

[PATCH 1/5][TAKE8] manpage for fallocate

2007-07-13 Thread Amit K. Arora
Following is the modified version of the manpage originally submitted by David Chinner. Please use `nroff -man fallocate.2 | less` to view. Following changed from TAKE7: * Removed FALLOC_ALLOCATE and FALLOCATE_RESV_SPACE modes. * Described only single flag for mode, i.e. FALLOC_FL_KEEP_SIZE. *

[PATCH 1/5][TAKE8] manpage for fallocate

2007-07-13 Thread Amit K. Arora
Following is the modified version of the manpage originally submitted by David Chinner. Please use `nroff -man fallocate.2 | less` to view. Following changed from TAKE7: * Removed FALLOC_ALLOCATE and FALLOCATE_RESV_SPACE modes. * Described only single flag for mode, i.e. FALLOC_FL_KEEP_SIZE. *