2016-12-24 11:37 GMT+02:00 Duncan <1i5t5.duncan@xxxxxxx>: > Dāvis Mosāns posted on Sat, 24 Dec 2016 04:22:24 +0200 as excerpted: > >> On two disk RAID1 btrfs partition one disk went offline, other was still >> writing, then kernel paniced. > > [snip btrfs fi usage as not needed for this reply] > >> Now kernel panics every time after some time when accessing that >> partition. > > > Have you done a scrub on the filesystem since the event that offlined one > of the two component devices? If not, please do so ASAP. Expect some > repairs. > Running scrub also causes kernel panic, but it does fix some things. I'll send that kernel log in separate email. > As for the continued panics, I'm not a dev (just a list regular and btrfs > raid1 user affected by this myself) so can't read enough of that bug-dump > to know if this is the bug or not, but do you use btrfs compression, > either via the compress mount option or via later compression using > defrag with the appropriate commandline option? > It definitely is a bug, it's just unhandled case, it shouldn't cause kernel panic but fix if it can or if can't then log it and continue. And yeah, compression is enabled, mount option is rw,noatime,autodefrag,compress=lzo,subvol=root > The problem is that sometimes the affected filesystems are used by boot > services, so I have to boot to systemd emergency or rescue mode (I forgot > which, whichever one does the mounts but doesn't start normal services) > and do the scrub from there, because if I try to boot normally, the > starting services read enough affected files from the filesystem to > trigger the panic before I get a chance to do the scrub. > Yeah that was happening since it's my / root partition and it paniced before it even finished booting. Now when I mounted it from other system it caused kernel panic even there on 4.8.13 Thanks for detailed reply! -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
