Re: 4.4.0 - no space left with >1.7 TB free space left

[Tomasz Chmielewski <tch@virtall.com>]

On 2016-04-08 20:53, Roman Mamedov wrote:

>> > Do you snapshot the parent subvolume which holds the databases? Can you
>> > correlate that perhaps ENOSPC occurs at the time of snapshotting? If
>> > yes, then
>> > you should try the patch https://patchwork.kernel.org/patch/7967161/
>> >
>> > (Too bad this was not included into 4.4.1.)
>> 
>> By the way - was it included in any later kernel? I'm running 4.4.5 on
>> that server, but still hitting the same issue.
> 
> It's not in 4.4.6 either. I don't know why it doesn't get included, or 
> what
> we need to do. Last time I asked, it was queued:
> http://www.spinics.net/lists/linux-btrfs/msg52478.html
> But maybe that meant 4.5 or 4.6 only? While the bug is affecting people 
> on
> 4.4.x today.

FYI, I'm still getting this with 4.5.3, which probably means the fix was 
not yet included ("No space left" at snapshot time):

/var/log/postgresql/postgresql-9.3-main.log:2016-05-11 06:06:10 UTC LOG: 
  could not close temporary statistics file "pg_stat_tmp/db_0.tmp": No 
space left on device
/var/log/postgresql/postgresql-9.3-main.log:2016-05-11 06:06:10 UTC LOG: 
  could not close temporary statistics file "pg_stat_tmp/global.tmp": No 
space left on device
/var/log/postgresql/postgresql-9.3-main.log:2016-05-11 06:06:10 UTC LOG: 
  could not close temporary statistics file "pg_stat_tmp/db_0.tmp": No 
space left on device
/var/log/postgresql/postgresql-9.3-main.log:2016-05-11 06:06:10 UTC LOG: 
  could not close temporary statistics file "pg_stat_tmp/global.tmp": No 
space left on device


I've tried mounting with space_cache=v2, but it didn't help.



Tomasz Chmielewski
http://wpkg.org