On Mon, Mar 04, 2013 at 09:17:51AM -0600, Eric Sandeen wrote:
> On 3/4/13 6:47 AM, Ole Tange wrote:
> > On Fri, Mar 1, 2013 at 11:32 PM, Eric Sandeen <sandeen@xxxxxxxxxxx> wrote:
> >> Ole, you can xfs_mdrestore your metadump image and run test repairs on the
> >> result,
> >> if you want a more realistic "dry run" of what repair would do.
> > I have never run xfs_mdrestore before.
> > From the man page:
> > xfs_mdrestore should not be used to restore metadata onto an
> > existing filesystem unless you are completely certain the target can
> > be destroyed.
> > It is unclear to me if you are suggesting me to do:
> > xfs_mdrestore the-already-created-dump /dev/md5p1
> no. definitely not. :)
> > followed by xfs_repair. Or if you want me to restore the metadata on
> > another 100 TB partition (I do not have that available).
> Nope - to a sparse file, on a filesystem which can hold a file with
> 100T offsets - like xfs.
> > Maybe you have a trick so that it can be restored on some smaller
> > block device, so I do not need the 100 TB partition, but I will still
> > be able to see how many files are being removed? If you have such a
> > trick, consider including it in the manual.
> Probably worth doing, or putting in the xfs faq.
Examples of how to do these sorts of operations should go into the
xfs users guide here: