On Mon, 12 Jan 2015 12:27:12 +0000, Hugo Mills wrote: > On Mon, Jan 12, 2015 at 11:21:58AM +0000, Hugo Mills wrote: >> I've just added a new disk to my main storage filesystem. Running >> the obligatory balance to spread the data out, it's managed about 14% >> of the job, and then has gone into some kind of tight loop. No chunks >> have been found or balanced in the last 2 hours, and one kworker thread >> is pegged at 100%. There were no unusual or unexpected messages in the >> logs. Balance cancel has been waiting for the last 10 minutes without >> effect (as would be expected with the other symptoms). > > OK, an hour after I executed the cancel, and three hours after it > apparently jammed up, the cancel completed. I have restarted the balance > from the point it left off, and I'll see if it does something similar > again. I've looked through the patches I use since 3.18.0 and nothing too obvious stood out (to me), except for several patches from Filipe for fixes that revolve around the chunk reaper, which sound like they might result in confused threads. Also moving to 3.18.2 probably won't hurt, it's not like there are no bugs in the kernel itself - I recently managed to find a really wrong corner case in NFS that has gone unnoticed since 3.16. Finally: instead of balancing everything at once maybe try a piecemeal approach with the limit filter? Wrap it in a script, spread out the work of balancing 3-5 chunks a time.. -h -- 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
