public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Michael Monnerie <michael.monnerie@is.it-management.at>
To: xfs@oss.sgi.com
Subject: Re: [PATCH, RFC] xfsprogs: add xfs_reno(8)
Date: Fri, 29 May 2009 08:37:06 +0200	[thread overview]
Message-ID: <200905290837.11098@zmi.at> (raw)
In-Reply-To: <20090528151804.GA31976@infradead.org>


[-- Attachment #1.1: Type: text/plain, Size: 760 bytes --]

On Donnerstag 28 Mai 2009 Christoph Hellwig wrote:
> The Linux port of xfs_reno

When used, does it move inodes on disk, or just change the numbers?

Because there seems to be still danger on inode64, would it be worth to 
sometimes run xfs_reno to get most files back to inode32, but still 
mount with inode64? I know this would create big inodes again, but at 
least old data would be safe.

mfg zmi
-- 
// Michael Monnerie, Ing.BSc    -----      http://it-management.at
// Tel: 0660 / 415 65 31                      .network.your.ideas.
// PGP Key:         "curl -s http://zmi.at/zmi.asc | gpg --import"
// Fingerprint: AC19 F9D5 36ED CD8A EF38  500E CE14 91F7 1C12 09B4
// Keyserver: wwwkeys.eu.pgp.net                  Key-ID: 1C1209B4


[-- Attachment #1.2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 197 bytes --]

[-- Attachment #2: Type: text/plain, Size: 121 bytes --]

_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs

  reply	other threads:[~2009-05-29  6:37 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-28 15:18 [PATCH, RFC] xfsprogs: add xfs_reno(8) Christoph Hellwig
2009-05-29  6:37 ` Michael Monnerie [this message]
2009-05-29 13:48   ` Eric Sandeen
2009-07-16 18:08 ` Eric Sandeen

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=200905290837.11098@zmi.at \
    --to=michael.monnerie@is.it-management.at \
    --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