On Mon, Mar 28, 2016 at 12:51 PM, Nazar Mokrynskyi <[email protected]> wrote:
>>> # btrfs check --repair /dev/mapper/fanbtr >>> bad metadata [4425377054720, 4425377071104) crossing stripe boundary >>> bad metadata [4425380134912, 4425380151296) crossing stripe boundary >>> bad metadata [4427532795904, 4427532812288) crossing stripe boundary >>> bad metadata [4568321753088, 4568321769472) crossing stripe boundary >>> bad metadata [4568489656320, 4568489672704) crossing stripe boundary >>> bad metadata [4571474493440, 4571474509824) crossing stripe boundary >>> bad metadata [4571946811392, 4571946827776) crossing stripe boundary >>> bad metadata [4572782919680, 4572782936064) crossing stripe boundary >>> bad metadata [4573086351360, 4573086367744) crossing stripe boundary >>> bad metadata [4574221041664, 4574221058048) crossing stripe boundary >>> bad metadata [4574373412864, 4574373429248) crossing stripe boundary >>> bad metadata [4574958649344, 4574958665728) crossing stripe boundary >>> bad metadata [4575996018688, 4575996035072) crossing stripe boundary >>> bad metadata [4580376772608, 4580376788992) crossing stripe boundary http://git.kernel.org/cgit/linux/kernel/git/kdave/btrfs-progs.git/tree/cmds-check.c line 7722 discusses this error message and it looks like there's no repair function for it yet; uncertain what problems can result from this. line 4576 has a possible clue, but I don't know what "can't handle" means, if real problems just silently are permitted or what. -- Chris Murphy -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
