On 11/18/2017 10:40 AM, Roman Mamedov wrote: > On Sat, 18 Nov 2017 02:08:46 +0100 > Hans van Kranenburg <hans.van.kranenb...@mendix.com> wrote: > >> It's using send + balance at the same time. There's something that makes >> btrfs explode when you do that. >> >> It's not new in 4.14, I have seen it in 4.7 and 4.9 also, various >> different explosions in kernel log. Since that happened, I made sure I >> never did those two things at the same time. > > Shouldn't it prevent send during balance, or balance during send then, if > that's the case? > > You talk about it "exploding" like it's a normal thing,
No, no, it's absolutely not normal of course. It's pretty scary. > to have Invalid opcode > BUGs in kernel log, and the user has to take care to not use two of the > regular FS features at the same time. > > Seems to be a bug which should be fixed, rather than warning everyone "not to > send during balance". Yes, sure. In the meantime, watch out with that combination. And that's what I quickly typed yesterday, because it was too late already. My experience with reporting bugs like this is that to get time spent on it, either a developer himself has to experience the issue, or you have to be able to provide a reliable reproducer. And yes, I also never got to doing that myself yet. So, who wants to help? 1. Find a test system that you can crash. 2. Create a test filesystem with some data. 3. Run with 4.14? (makes the most sense I think) 4. Continuously feed the data to balance and send everything to /dev/null 5. Collect stack traces and borken filesystem images. -- Hans van Kranenburg -- 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
