Re: xfsdump | xfsrestore resulting in files->orphanage
From: Gao Xiang <hidden>
Date: 2021-03-25 01:18:15
Hi, On Wed, Mar 24, 2021 at 05:43:39PM -0700, L A Walsh wrote:
oops, forgot to cc list. -------- Original Message -------- On 2021/03/24 16:58, Eric Sandeen wrote:quoted
This is a bug in root inode detection that Gao has fixed, and I really need to merge. In the short term, you might try an older xfsdump version, 3.1.6 or earlier.--- In the short term -- I was dumping from a dumpdir for a partition (just to make a copy of it on the new disk), but there was no real requirement to do so, so I just dumped from the "source" dir, which for whatever reason didn't have the problem. My final try would have been to use rsync or such.quoted
(Assuming you don't actually have a bind mount)--- Not on that partition... 3.1.6? Hasn't 318 been out for quite a while? I looked through my bins only have 312 and 314 (and 318)... tried 314, but it started out with the same inode confusion -- didn't wait until it started spitting out any other errors.
Not sure get all your point.
That is because commit ("xfsdump: handle bind mount targets") was included in
3.1.7. So it would be better to confirm if 3.1.6 works as expected.
In principle, 3.1.6 should work if applying to non-bindmount root dir. (I mean
if no new non-identify potential issue here)
Thanks,
Gao Xiang