On Thu, Feb 21, 2008 at 11:10:36PM -0500, Christoph Hellwig wrote:
> Looks good to me.
Any word on this critical patch? ;)
Josef 'Jeff' Sipek.
> On Mon, Feb 18, 2008 at 01:32:38AM -0500, Josef 'Jeff' Sipek wrote:
> > Signed-off-by: Josef 'Jeff' Sipek <jeffpc@xxxxxxxxxxxxxx>
> > ---
> > Documentation/filesystems/xfs.txt | 7 ++++---
> > 1 files changed, 4 insertions(+), 3 deletions(-)
> >
> > diff --git a/Documentation/filesystems/xfs.txt
> > b/Documentation/filesystems/xfs.txt
> > index 74aeb14..655bdfe 100644
> > --- a/Documentation/filesystems/xfs.txt
> > +++ b/Documentation/filesystems/xfs.txt
> > @@ -59,9 +59,10 @@ When mounting an XFS filesystem, the following options
> > are accepted.
> >
> > ikeep/noikeep
> > When inode clusters are emptied of inodes, keep them around
> > - on the disk (ikeep) - this is the traditional XFS behaviour
> > - and is still the default for now. Using the noikeep option,
> > - inode clusters are returned to the free space pool.
> > + on the disk (ikeep) - this is the traditional XFS behaviour.
> > + Using the noikeep option, inode clusters are returned to the
> > + free space pool. noikeep is the default for non-DMAPI mounts,
> > + while ikeep is the default when DMAPI is in use.
> >
> > inode64
> > Indicates that XFS is allowed to create inodes at any location
> > --
> > 1.5.4.rc2.85.g9de45-dirty
> >
> >
> ---end quoted text---
>
--
A CRAY is the only computer that runs an endless loop in just 4 hours...
|