On Fri, Jun 17, 2016 at 8:45 AM, Tyson Whitehead <twhitehead@xxxxxxxxx> wrote: > On May 27, 2016 12:12:54 PM Chris Murphy wrote: >> On Thu, May 26, 2016 at 11:55 AM, Tyson Whitehead <twhitehead@xxxxxxxxx> wrote: >> > Under the last several kernels versions (4.6 and I believe 4.4 and, 4.5) btrfs scrub aborts before completing. >> >> I can't reproduce this with btrfs-progs 4.5.2 and kernel 4.6.0. >> >> I think the bigger issue is the lack of information why a scrub is aborted. > > Thanks for checking into this Chris. > > Any advice on how to get some more information out of the scrub process? So I can't help you out with why scrub fails. That sounds like a bug, not least of which is there's no information why it's failing. So I suggest filing a bug with what you know to date and include in this thread for reference. The main point is that there *are* errors (a lot of them apparently) needing fixing up, but somehow certain kernel versions are aborting and there's no information why. Next you need to find out why this one device has so many errors. Put the output from smartctl -x /dev/sdb somewhere, maybe even attach it to the bug report since it's somewhat related. Either that device is simply unreliable, or you've got a bad cable connection. You need to include an entire dmesg, or even better would be dmesg and also 'journalctl -b -o short-monotonic' attached to the bug report also. While there may be no btrfs messages indicating what's going on, there might be usb or libata message indicating hardware problems that are instigating. -- Chris Murphy -- 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
