On 22 February 2016 at 17:22, Jameson <imntr...@gmail.com> wrote: > On Sun, Feb 21, 2016 at 6:36 AM Guus Snijders <gsnijd...@gmail.com> wrote: > >> Op 20 feb. 2016 16:06 schreef "Jameson Pugh" <imntr...@gmail.com>: >> > >> > >> > >> > On Sat, Feb 20, 2016 at 8:04 AM, Alistair Grant <akgrant0...@gmail.com> >> wrote: >> >> >> >> On 20 February 2016 at 02:38, Jameson Pugh <imntr...@gmail.com> wrote: >> >>> >> >>> I have a raid6 btrfs filesystem which I filled up, and added a disk >> to: >> [...] >> >> >> If you haven't already done so, I'd also suggest posting this to the >> >> linux-btrfs mailing list (see >> >> https://btrfs.wiki.kernel.org/index.php/Btrfs_mailing_list) >> > >> > >> > Yes. I've tried removing files after adding the device. Unfortunately, >> there are no snapshots. I could try removing subvolumes. I'll try the btrfs >> list. >> >> Out of pure curiosity I took a quick look at the archives of that list and >> it looked quite promising (though i'm not sure if it was the same OP). >> >> If it works, could you post here also? I have a feeling you won't be the >> last person to run into this situation. >> > > Removing subvolumes, and clobbering files didn't help, so I wound up > starting over. The first thing I did was create a base subvolume, and then > added a quota to it before creating subvolumes nested under it. Hopefully, > this will help. Unfortunately, with the way btrfs reports free space, it > will still be challenge to manage. > > Thanks, > Jameson
Hi! You should not use quotas on btrfs currently. It is known to cause significant performance issues on the long run (and potentially has many undiscovered bugs). If you wish I can dig up the relevant discussion on the btrfs mailing list for you. Regards, Garmine
