Mail Archive Search: <+subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*64\-bit\s+inodes\s+and\s+back\s+again\s*$/>

Results:

References: [ +subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*64\-bit\s+inodes\s+and\s+back\s+again\s*$/: 14 ]

Total 14 documents matching your query.

1. 64-bit inodes and back again (score: 1): Author: Michael Cronenworth <mike@xxxxxxxxxx>; Date: Tue, 27 Sep 2011 18:28:37 -0500; Hello, I enabled 64-bit inodes on a 2.6.35.14 kernel system. I ran into some software that did not handle this well, so I wanted to go back to 32-bit inodes. When I booted into the system again, any; /archives/xfs/2011-09/msg00463.html (7,775 bytes)
2. Re: 64-bit inodes and back again (score: 1): Author: Dave Chinner <david@xxxxxxxxxxxxx>; Date: Wed, 28 Sep 2011 11:10:20 +1000; I'm pretty sure this was fixed in 2.6.37. There's nothing wrong with the filesystem, just the kernel code had an arbitrary restriction on where inodes code be read from in 32-bit inode mode. That was; /archives/xfs/2011-09/msg00464.html (8,773 bytes)
3. Re: 64-bit inodes and back again (score: 1): Author: Michael Cronenworth <mike@xxxxxxxxxx>; Date: Tue, 27 Sep 2011 20:31:04 -0500; On 09/27/2011 08:10 PM, Dave Chinner wrote: I'm pretty sure this was fixed in 2.6.37. There's nothing wrong with the filesystem, just the kernel code had an arbitrary restriction on where inodes code; /archives/xfs/2011-09/msg00465.html (8,429 bytes)
4. Re: 64-bit inodes and back again (score: 1): Author: Michael Cronenworth <mike@xxxxxxxxxx>; Date: Tue, 27 Sep 2011 21:52:17 -0500; I upgraded to kernel 2.6.38. The files are now visible. http://xfs.org/index.php/Unfinished_work#The_xfs_reno_tool I'll give this a shot first. I did try this tool first, but it didn't seem to work f; /archives/xfs/2011-09/msg00466.html (9,301 bytes)
5. Re: 64-bit inodes and back again (score: 1): Author: Dave Chinner <david@xxxxxxxxxxxxx>; Date: Wed, 28 Sep 2011 15:35:39 +1000; It has to be able to access the files with inode numbers > 32 bit, so you need to run it on the 2.6.38 kernel. Once you've done that, you should be able to read all the files back on the .35 kernel,; /archives/xfs/2011-09/msg00468.html (10,671 bytes)
6. Re: 64-bit inodes and back again (score: 1): Author: Michael Monnerie <michael.monnerie@xxxxxxxxxxxxxxxxxxx>; Date: Wed, 28 Sep 2011 07:48:32 +0200; 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. -- mit freundlichen Grüssen, Michael Monnerie, Ing. BSc it-managemen; /archives/xfs/2011-09/msg00469.html (9,382 bytes)
7. Re: 64-bit inodes and back again (score: 1): Author: Michael Cronenworth <mike@xxxxxxxxxx>; Date: Wed, 28 Sep 2011 01:55:56 -0500; No. The xfs_reno manpage specifically says to *not* mount with 64-bit inodes enabled. It uses the kernel to generate a new inode.; /archives/xfs/2011-09/msg00473.html (8,588 bytes)
8. Re: 64-bit inodes and back again (score: 1): Author: Michael Cronenworth <mike@xxxxxxxxxx>; Date: Wed, 28 Sep 2011 01:58:55 -0500; On 09/28/2011 12:35 AM, Dave Chinner wrote: It has to be able to access the files with inode numbers> 32 bit, so you need to run it on the 2.6.38 kernel. Once you've done that, you should be able to; /archives/xfs/2011-09/msg00474.html (9,736 bytes)
9. Re: 64-bit inodes and back again (score: 1): Author: Dave Chinner <david@xxxxxxxxxxxxx>; Date: Wed, 28 Sep 2011 21:07:27 +1000; It's failing trying to copy the attributes on a directory. What are the attributes on the specific directory? Cheers, dave. -- Dave Chinner david@xxxxxxxxxxxxx; /archives/xfs/2011-09/msg00485.html (10,325 bytes)
10. Re: 64-bit inodes and back again (score: 1): Author: Michael Cronenworth <mike@xxxxxxxxxx>; Date: Wed, 28 Sep 2011 08:13:37 -0500; That particular directory was drwxrwsr-x root:mock However, I tried it on a number of other directories that had plain attributes like: drwxr-xr-x root:root It failed the same way on those directorie; /archives/xfs/2011-09/msg00490.html (10,172 bytes)
11. Re: 64-bit inodes and back again (score: 1): Author: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>; Date: Wed, 28 Sep 2011 12:37:51 -0500; On 9/28/2011 8:13 AM, Michael Cronenworth wrote: Dave Chinner on 09/28/2011 06:07 AM wrote: It's failing trying to copy the attributes on a directory. What are the attributes on the specific director; /archives/xfs/2011-09/msg00492.html (10,666 bytes)
12. Re: 64-bit inodes and back again (score: 1): Author: Michael Cronenworth <mike@xxxxxxxxxx>; Date: Wed, 28 Sep 2011 13:05:44 -0500; No. I do have quotas enabled, but they have been enabled all during this time from switching 64-bit inodes on and off.; /archives/xfs/2011-09/msg00493.html (9,678 bytes)
13. Re: 64-bit inodes and back again (score: 1): Author: Dave Chinner <david@xxxxxxxxxxxxx>; Date: Thu, 29 Sep 2011 10:25:11 +1000; I was asking about stuff like selinux attributes, not modes and owners. i.e: $ lsattr /usr/sbin/xfs_db --e- /usr/sbin/xfs_db $ attr -l /usr/sbin/xfs_db Attribute "selinux" has a 27 byte value for /us; /archives/xfs/2011-09/msg00496.html (10,063 bytes)
14. Re: 64-bit inodes and back again (score: 1): Author: Michael Cronenworth <mike@xxxxxxxxxx>; Date: Wed, 28 Sep 2011 19:37:16 -0500; SELinux is enabled and in Enforcing mode. It's the default Fedora policy. $ lsattr /var/lib/mock.save/dist-5E-build-377-1401 -- /var/lib/mock.save/dist-5E-build-377-1401/root $ attr -l /var/lib/mock.; /archives/xfs/2011-09/msg00497.html (10,313 bytes)

Current List: 1 - 14
Page: [1]