On Mon, Jan 23, 2017 at 2:50 PM, Chris Murphy > I haven't found the commit for that patch, so maybe it's something > with the combination of that patch and the previous commit.
I think that's provably not the case based on the bisect log, because I hit the problem with kernel that has only the commit, as well as the commit plus the updated patch. So the patch neither causes nor fixes the problem I'm experiencing. If it's useful the btrfs-image is here; mentioned in a previous thread, this image mounts find, btrfs check --mode=original has no complaints, but btrfs check --mode=lowmem has complaints. There's no problem using the parent subvolume as rootfs. Only snapshots of that subvolume result in the problem. https://drive.google.com/open?id=0B_2Asp8DGjJ9ZmNxdEw1RDBPcTA -- Chris Murphy -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
