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. //Nisse 2016-06-15 17:33 GMT+02:00 Chris Murphy <lists@xxxxxxxxxxxxxxxxx>: > > > On Wed, Jun 15, 2016 at 3:58 AM, Nisse Karlsson <nisse@xxxxxxxx> wrote: >> >> >> Unallocated: >> /dev/sdb 222.50GiB > > > The filed bug report needs a complete dmesg attached (at least from the time > the fs is mounted and including enospc), what mount options are used, and > what btrfs-progs version is used. > > But the fact sdb reports this much free space and yet the enospc kernel > message you report later refers to sdb is unexpected, so it's good to have > filed a bug. > > You can also include as an attachment the output from btrfs-debugfs which is > a python script not normally installed as a part of btrfs-progs but you can > get it from here: > https://github.com/kdave/btrfs-progs > > btrfs-debugfs -b <mountpoint> > > > > -- > 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
