On Sat, Jul 2, 2016 at 11:34 AM, Hans van Kranenburg <hans.van.kranenburg@xxxxxxxxxx> wrote: > On 07/02/2016 07:14 PM, Hans van Kranenburg wrote: >> >> I just rebooted a VM into a 4.7 kernel. The joy didn't last long. After >> 177 seconds the btrfs data partition (root is on ext4) locked up. Worse, >> it keeps locking up on any action performed even when rebooting it with >> older kernels again. D: The filesystem initially mounts fine, but then >> locks up again immediately. >> >> Linux stacheldraht 4.7.0-rc4-amd64 #1 SMP Debian 4.7~rc4-1~exp1 >> (2016-06-20) x86_64 GNU/Linux >> >> ps output shows [btrfs-transaction] in D state: >> >> root 1108 0.0 0.0 0 0 ? D 17:42 0:00 \_ >> [btrfs-transacti] >> >> From dmesg: >> >> [blah blah blah] >> >> So, something happened inside the fs that makes it lock up every time I >> try to do anything with it... > > > I force-rebooted the poor thing again, and mounted the filesystem ro. It > mounts without any complaint. I can see all files now, I can do sub list > etc... > > So I think I'm going to copy some data to a new filesystem on a new block > device just in case. The thing has to move to new storage anyway it's about > 100 subvolumes with about 150GB of data, so that's a nice excercise with > send/receive. Two things might be interesting: 1. btrfs check (without repair) to add to the above and see whether it finds any problems. 2. For send, to try -e option, if you have related subvolume snapshots. See if this bug is really a bug or user error or maybe it's fixed. https://bugzilla.kernel.org/show_bug.cgi?id=111221 -- 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
