public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: David Chinner <dgc@sgi.com>
To: Christoph Hellwig <hch@infradead.org>
Cc: Barry Naujok <bnaujok@sgi.com>,
	"xfs@oss.sgi.com" <xfs@oss.sgi.com>, xfs-dev <xfs-dev@sgi.com>
Subject: Re: REVIEW: xfs_reno
Date: Tue, 2 Oct 2007 19:19:51 +1000	[thread overview]
Message-ID: <20071002091951.GE995458@sgi.com> (raw)
In-Reply-To: <20071002090216.GA22721@infradead.org>

On Tue, Oct 02, 2007 at 10:02:16AM +0100, Christoph Hellwig wrote:
> On Tue, Oct 02, 2007 at 05:08:59PM +1000, Barry Naujok wrote:
> > 
> > The attached tool allows an inode64 filesystem to be converted to inode32.
> > For this to work, the filesystem has to be mounted inode32 before it's run.
> > 
> > I'm not sure if there is any packaging changes required.
> 
> Together with the stop allocating from specific AGs patch this should be
> 90% towards an xfs_shrinkfs, right?

Well, this just moves the inodes - it's one piece of the puzzle.  We
still need to collide xfs_fsr with xfs_reno to move the data.

After that, we need to work out how to move the orphan metadata
blocks out of the AGs that are to be truncated off. That's not
simple....

After that, we need the transaction to shrink the fs.

At that point, we'll got a "working" shrink that will allow
shrinking to only 50% of the original size because the log will
get in the way. To fix that, we'll need to implement transactions
to move the log...

Cheers,

Dave.
-- 
Dave Chinner
Principal Engineer
SGI Australian Software Group

  reply	other threads:[~2007-10-02  9:20 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-02  7:08 REVIEW: xfs_reno Barry Naujok
2007-10-02  7:20 ` Nathan Scott
2007-10-02  9:02 ` Christoph Hellwig
2007-10-02  9:19   ` David Chinner [this message]
2007-10-02 16:41     ` Russell Cattelan
2007-10-02 23:41       ` David Chinner
2007-10-03  1:05     ` Barry Naujok
2007-10-03  4:58       ` David Chinner
2007-10-03  1:30     ` Timothy Shimmin
2007-10-03  5:50       ` 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=20071002091951.GE995458@sgi.com \
    --to=dgc@sgi.com \
    --cc=bnaujok@sgi.com \
    --cc=hch@infradead.org \
    --cc=xfs-dev@sgi.com \
    --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