From: Eric Sandeen <sandeen@sandeen.net>
To: Michael Monnerie <michael.monnerie@is.it-management.at>
Cc: xfs@oss.sgi.com
Subject: Re: [PATCH, RFC] xfsprogs: add xfs_reno(8)
Date: Fri, 29 May 2009 08:48:18 -0500 [thread overview]
Message-ID: <4A1FE7A2.9030302@sandeen.net> (raw)
In-Reply-To: <200905290837.11098@zmi.at>
Michael Monnerie wrote:
> 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?
Both. location == number == location == number ...
> 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.
that sounds like going in circles.... I wouldn't recommend it.
Either you want 64-bit inodes.... or not.
-Eric
> mfg zmi
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2009-05-29 13:48 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
2009-05-29 13:48 ` Eric Sandeen [this message]
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=4A1FE7A2.9030302@sandeen.net \
--to=sandeen@sandeen.net \
--cc=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