public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Ruben Porras <ruben.porras@linworks.de>
To: "xfs@oss.sgi.com" <xfs@oss.sgi.com>
Subject: Re: REVIEW: xfs_reno #2
Date: Wed, 17 Oct 2007 17:48:36 +0200	[thread overview]
Message-ID: <47162ED4.6000108@linworks.de> (raw)
In-Reply-To: <op.tznnweh23jf8g2@pc-bnaujok.melbourne.sgi.com>

Barry Naujok wrote:
> A couple changes from the first xfs_reno:
>
>  - Major one is that symlinks are now supported, but only
>    owner, group and extended attributes are copied for them
>    (not times or inode attributes).
>
>  - Man page!
>
>
> To make this better, ideally we need some form of
> "swap inodes" function in the kernel, where the entire
> contents of the inode themselves are swapped. This form
> can handle any inode and without any of the dir/file/attr/etc
> copy/swap mechanisms we have in xfs_reno.
>

If everything goes as planned I will have time next month to look at 
xfs_reno.

-- 
Rubén Porras
LinWorks GmbH

  reply	other threads:[~2007-10-17 16:15 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-04  4:25 REVIEW: xfs_reno #2 Barry Naujok
2007-10-17 15:48 ` Ruben Porras [this message]
2007-11-16  6:04 ` Vlad Apostolov
2007-11-16  6:20   ` Timothy Shimmin
2007-11-18 23:13     ` Vlad Apostolov
2007-11-18 23:19       ` Vlad Apostolov
2007-11-19 12:39     ` Christoph Hellwig
2007-11-19 15:52       ` Eric Sandeen
2007-11-19 22:08         ` Vlad Apostolov
2007-11-19  3:48 ` Lachlan McIlroy
2007-11-20  1:36 ` David Chinner
2007-11-23 14:30   ` Ruben Porras
2008-03-06 16:11   ` Ruben Porras
2008-03-06 16:10 ` Ruben Porras
2008-06-03 20:34   ` Christoph Hellwig

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=47162ED4.6000108@linworks.de \
    --to=ruben.porras@linworks.de \
    --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