Paul Jones posted on Sun, 09 Jul 2017 09:16:36 +0000 as excerpted: >> Marc MERLIN - 08.07.17, 21:34: >> > >> > This is now the 3rd filesystem I have (on 3 different machines) that >> > is getting corruption of some kind (on 4.11.6). >> >> Anyone else getting corruptions with 4.11? >> >> I happily switch back to 4.10.17 or even 4.9 if that is the case. I may >> even do so just from your reports. Well, yes, I will do exactly that. I >> just switch back for 4.10 for now. Better be safe, than sorry. > > No corruption for me - I've been on 4.11 since about .2 and everything > seems fine. Currently on 4.11.8 No corruptions here either. 4.12.0 now, previously 4.12-rc5(ish, git), before that 4.11.0. I have however just upgraded to new ssds then wiped and setup the old ones as another backup set, so everything is on brand new filesystems on fast ssds, no possibility of old undetected corruption suddenly triggering problems. Also, all my btrfs are raid1 or dup for checksummed redundancy, and relatively small, the largest now 80 GiB per device, after the upgrade. And my use-case doesn't involve snapshots or subvolumes. So any bug that is most likely on older filesystems, say those without the no-holes feature, for instance, or that doesn't tend to hit raid1 or dup mode, or that is less likely on small filesystems on fast ssds, or that triggers most often with reflinks and thus on filesystems with snapshots, is unlikely to hit me. -- Duncan - List replies preferred. No HTML msgs. "Every nonfree program has a lord, a master -- and if you use the program, he is your master." Richard Stallman -- 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
