After some more balance passes with different values of -dusage and removal of some files (around 50GB) I finally managed to convert the volume back to raid1. So my problem is solved, but it still seems like bug to me. //Nisse 2016-06-15 18:29 GMT+02:00 Chris Murphy <lists@xxxxxxxxxxxxxxxxx>: > On Wed, Jun 15, 2016 at 10:00 AM, Nisse Karlsson <nisse@xxxxxxxx> wrote: >> Thanks, >> >> Will update the bug-report with more information. >> Not sure I trust the device info in dmesg though, when running device >> delete /dev/sdh /files it still refers to to sdb in dmesg. I think it >> just shows the device that was used for mounting the fs. > > Hmm that's not very helpful if it's not reporting the device that's > having the enospc problem... > > Anyway, the debugfs output should probably make this more clear, but > also the dmesg will still be useful in that it'll report what block > group was being worked on at the time. So it'll be possible to see > that in the debugfs output along with stripe info for that bg. > > > -- > 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
