Re: Recovery from full metadata with all device space consumed?

2018-04-20 Thread Duncan
Timofey Titovets posted on Fri, 20 Apr 2018 01:32:42 +0300 as excerpted: > 2018-04-20 1:08 GMT+03:00 Drew Bloechl : >> I've got a btrfs filesystem that I can't seem to get back to a useful >> state. The symptom I started with is that rename() operations started >> dying with

Re: Recovery from full metadata with all device space consumed?

2018-04-19 Thread Hugo Mills
On Thu, Apr 19, 2018 at 04:12:39PM -0700, Drew Bloechl wrote: > On Thu, Apr 19, 2018 at 10:43:57PM +, Hugo Mills wrote: > >Given that both data and metadata levels here require paired > > chunks, try adding _two_ temporary devices so that it can allocate a > > new block group. > > Thank

Re: Recovery from full metadata with all device space consumed?

2018-04-19 Thread Drew Bloechl
On Thu, Apr 19, 2018 at 10:43:57PM +, Hugo Mills wrote: >Given that both data and metadata levels here require paired > chunks, try adding _two_ temporary devices so that it can allocate a > new block group. Thank you very much, that seems to have done the trick: # fallocate -l 4GiB

Re: Recovery from full metadata with all device space consumed?

2018-04-19 Thread Hugo Mills
On Thu, Apr 19, 2018 at 03:08:48PM -0700, Drew Bloechl wrote: > I've got a btrfs filesystem that I can't seem to get back to a useful > state. The symptom I started with is that rename() operations started > dying with ENOSPC, and it looks like the metadata allocation on the > filesystem is full:

Re: Recovery from full metadata with all device space consumed?

2018-04-19 Thread Timofey Titovets
2018-04-20 1:08 GMT+03:00 Drew Bloechl : > I've got a btrfs filesystem that I can't seem to get back to a useful > state. The symptom I started with is that rename() operations started > dying with ENOSPC, and it looks like the metadata allocation on the > filesystem is full: >

Recovery from full metadata with all device space consumed?

2018-04-19 Thread Drew Bloechl
I've got a btrfs filesystem that I can't seem to get back to a useful state. The symptom I started with is that rename() operations started dying with ENOSPC, and it looks like the metadata allocation on the filesystem is full: # btrfs fi df /broken Data, RAID0: total=3.63TiB, used=67.00GiB