Hi Michael, Looks like our replies crossed in the ether.
Michael Biebl <[email protected]> writes: > I considered whether I should forward this issue to upstream but then I > found [1]. So I guess it's pointless to raise that again with fsarchiver. I meant the lkml for btrfs. If fsarchiver upstream is unwilling to challenge their assumptions in light of new evidence then I'll agree it's pointless. > I will add a manual wipefs call for the btrfs autopkgtest in fsarchiver > even though I think this is only a work-around and not a proper fix. Oh, this is for an autopkgtest...I'm not sure how much what I wrote about safer UUID-handling approaches applies to actual fsarchive functioning. If it seems relevant, would you please forward what I sent you (and this bug) to fsarchiver's upstream? File systems and backup software are two things that should always follow best practises and err on the side of caution. > Anyway, thanks for your fast response on this matter. You're welcome! I hope as members of Debian that we can continue to be effective in encouraging the larger FLOSS community to do the right thing. Cheers, Nicholas
signature.asc
Description: PGP signature
