| To: | xfs@xxxxxxxxxxx |
|---|---|
| Subject: | Re: 64-bit inodes and back again |
| From: | Michael Cronenworth <mike@xxxxxxxxxx> |
| Date: | Wed, 28 Sep 2011 01:55:56 -0500 |
| In-reply-to: | <201109280748.33889@xxxxxx> |
| References: | <4E825C25.6050804@xxxxxxxxxx> <4E8278D8.9060309@xxxxxxxxxx> <4E828BE1.8030003@xxxxxxxxxx> <201109280748.33889@xxxxxx> |
| User-agent: | Mozilla/5.0 (X11; Linux x86_64; rv:6.0.2) Gecko/20110906 Thunderbird/6.0.2 |
On 09/28/2011 12:48 AM, Michael Monnerie wrote: I guess you'd need to mount with inode64 enabled so you can access the files, and after the tool finished to back to 32bit inodes. No. The xfs_reno manpage specifically says to *not* mount with 64-bit inodes enabled. It uses the kernel to generate a new inode. |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: [patch 3/4] mm: filemap: pass __GFP_WRITE from grab_cache_page_write_begin(), Minchan Kim |
|---|---|
| Next by Date: | Re: 64-bit inodes and back again, Michael Cronenworth |
| Previous by Thread: | Re: 64-bit inodes and back again, Michael Monnerie |
| Next by Thread: | [PATCH 0/5] xfsprogs: some libxcmd cleanups, Alex Elder |
| Indexes: | [Date] [Thread] [Top] [All Lists] |