| To: | Michael Monnerie <michael.monnerie@xxxxxxxxxxxxxxxxxxx> |
|---|---|
| Subject: | Re: [PATCH, RFC] xfsprogs: add xfs_reno(8) |
| From: | Eric Sandeen <sandeen@xxxxxxxxxxx> |
| Date: | Fri, 29 May 2009 08:48:18 -0500 |
| Cc: | xfs@xxxxxxxxxxx |
| In-reply-to: | <200905290837.11098@xxxxxx> |
| References: | <20090528151804.GA31976@xxxxxxxxxxxxx> <200905290837.11098@xxxxxx> |
| User-agent: | Thunderbird 2.0.0.21 (Macintosh/20090302) |
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 |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: [PATCH 9/7] xfs: remove SYNC_BDFLUSH, Sujit Karataparambil |
|---|---|
| Next by Date: | Re: xfsdump on mounted filesystem, Christoph Hellwig |
| Previous by Thread: | Re: [PATCH, RFC] xfsprogs: add xfs_reno(8), Michael Monnerie |
| Next by Thread: | [PATCH, RFC] xfsprogs: add xfs_loggen, Christoph Hellwig |
| Indexes: | [Date] [Thread] [Top] [All Lists] |