On Tue, Sep 27, 2011 at 09:52:17PM -0500, Michael Cronenworth wrote: > Dave Chinner on 09/27/2011 08:10 PM wrote: > > I'm pretty sure this was fixed in 2.6.37. > > I upgraded to kernel 2.6.38. The files are now visible. > > Michael Cronenworth wrote: > >>xfs_reno is a tool designed to move all 64 bit inodes back into the > >>32 bit inode space again. > >> > >>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 for me: > > # xfs_reno -vv /tmp/q.save/7074d797d8cd5965224f21a778924aa44a0871f4-qt-x11-4.7.4-2.fc14-x86_64 > > xfs_reno: Cannot stat /tmp/q.save/7074d797d8cd5965224f21a778924aa44a0871f4-qt-x11-4.7.4-2.fc14-x86_64: > Invalid argument > # xfs_reno -fvv /tmp/q.save > Scanning directory tree... > Processing 1 directory... > xfs_reno: directory: 97367 1 /tmp/q.save > xfs_reno: unable to duplicate directory attributes: /tmp/q.save > 0 seconds elapsed > Done. > # ls -l /tmp/q.save/ > ls: cannot access /tmp/q.save/b0afb399c40e9a45061b5cee73770def741d270e-qt-4.7.4-2.fc14-x86_64: > Invalid argument > ls: cannot access /tmp/q.save/7074d797d8cd5965224f21a778924aa44a0871f4-qt-x11-4.7.4-2.fc14-x86_64: > Invalid argument > total 8 > drwxr-xr-x. 2 root root 4096 Sep 27 22:33 310514e5d8aff198342a469b59311b7fa3af0d28-qt-webkit-4.7.4-2.fc14-x86_64 > ??????????? ? ? ? ? ? > 7074d797d8cd5965224f21a778924aa44a0871f4-qt-x11-4.7.4-2.fc14-x86_64 > ??????????? ? ? ? ? ? > b0afb399c40e9a45061b5cee73770def741d270e-qt-4.7.4-2.fc14-x86_64 > -rw-------. 1 root root 83 Sep 27 22:38 xfs_reno.recover 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, too. Cheers, Dave. -- Dave Chinner david@xxxxxxxxxxxxx _______________________________________________ xfs mailing list xfs@xxxxxxxxxxx http://oss.sgi.com/mailman/listinfo/xfs
