Re: Errors not found by btrfsck or scrub

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Jan 11, 2013, at 9:43 PM, Chris Carlin <chrisrcarlin@xxxxxxxxx> wrote:

>> Based on some experiences I've had, and also seen on the list recently, you might be able to back out of this situation by adding another device to the volume. It almost doesn't matter how big it is. It could be a small partition on another disk, or even a USB stick. I can't tell you how much space. It might only need a few MB, but I'd give it what you can. And then see if you can redo the balance. But it sounds to me like the file system is very close to full, at least it can't allocate more space for metadata it seems.
> 
> Aha! Worked fine.
> 
> I added a temporary 10GB device, and everything instantly started
> working. After I ran another balance command with -dusage=5, I deleted
> the new device and everything's fine with the original two devices.
> The temporary device was barely touched by the filesystem, if it was
> touched at all.
> 
> A weird thing is "btrfs fi show" showed tens of gigs of unallocated
> space the whole time.
> 
> Anyway, so for anyone who might have a similar problem in the future,
> giving btrfs a little temporary scratch space did the trick.

Well you never did show us your before btrfs fi show, but going back to your fi df from the original email:

Metadata, RAID1: total=512.00MB, used=511.60MB
Metadata, DUP: total=1.00GB, used=1022.39MB

It's out of space for metadata, is the problem I see above. There's not even 2 MB of space left.

Yes in this portion for data:

Data, RAID0: total=776.32GB, used=717.56GB
Data: total=81.00GB, used=29.44GB

This implies  you have lots of space, but actually it's the first value that matters in these cases because data and metadata allocations are separate. This space you think you have free is allocated for data. I don't know the details of whether, when, or how Btrfs can deallocate a data chunk and reallocate it for metadata but clearly it was unable or unwilling to do so in this case. So when you added the temporary space, it was immediately able to allocate some additional for metadata chunk and unwind itself.

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


[Index of Archives]     [Linux Filesystem Development]     [Linux NFS]     [Linux NILFS]     [Linux USB Devel]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]

  Powered by Linux