On Thu, Sep 24, 2015 at 8:34 AM, Jogi Hofmüller <jogi@xxxxxx> wrote: > All this runs on a virtual machine that uses kernel 4.1.3 (Debian build) > and btrfs-progs v4.0. Unrelated to the problem but I'd upgrade progs, in case it's ever needed. 4.1 and 4.2 have tons of bug fixes over 4.0 already. > > So finally I would ask what we can do to solve this problem? I also > appreciate comments to the situation and of course hints to what is > going on. This is over my head. The problem description is incomplete without a dmesg. If this is a systemd system, then I suggest journalctl -b -l -o short-monotonic > journal.txt Otherwise you can put in a trimmed /var/log/messages for the current boot. I think it's best to have kernel messages for the entire boot because the cause could be buried well before the Btrfs error messages. Attach that to the mailing list. If it's too big, the best option is file a bug, attach the file to the bug, and then post the URL for the bug in this thread. The fallback is put it up somewhere else, the problem there is it ends up being temporarily available so if someone runs into this thread in a year your attachment is MIA. -- 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
