All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tomasz Chmielewski <mangoo@wpkg.org>
To: Miguel Garrido <miguel@mjgar.com>
Cc: linux-btrfs <linux-btrfs@vger.kernel.org>
Subject: Re: No space left, with 80 GB space free
Date: Wed, 10 Aug 2011 12:38:31 +0200	[thread overview]
Message-ID: <4E425FA7.7030201@wpkg.org> (raw)
In-Reply-To: <BANLkTimA_dJDNUqPUssV5ZbLTr=T7k+doA@mail.gmail.com>

On 21.05.2011 01:05, Miguel Garrido wrote:
> On Fri, May 20, 2011 at 12:35 PM, Tomasz Chmielewski<mangoo@wpkg.org>  wrote:
>>
>> Nobody has a clue what makes btrfs run out of space when used with PostgreSQL, even when there is plenty of free space left?
>>
>>
>> # df -h
>> Filesystem            Size  Used Avail Use% Mounted on
>> /dev/sdb4             336G  257G   78G  77% /mnt/btrfs
>>
>>
>> coredb=# DELETE FROM core_trevent where "date"<  E'2011-05-07 00:00';
>> ERROR:  could not write block 1014999 of relation base/16384/16521: No space left on device
>> CONTEXT:  writing block 1014999 of relation base/16384/16521

Just a follow up - I'm able to reproduce the issue with 3.0.1 kernel, with plain rsync.
I'm trying to write a ~ 4 GB file to btrfs.

"Fast" writes will make btrfs output "No space left on device".
On the other hand, if I write slowly, btrfs will be happy and write the whole file.


cp ("full speed copy") fails after a few seconds, so let's try to write with ~5 MB/s - still fails:

# rsync -a -v --progress --bwlimit=5000 . /mnt/btrfs/temp
sending incremental file list
./
randomfile
   645136384  13%    4.87MB/s    0:13:32  
rsync: writefd_unbuffered failed to write 4 bytes to socket [sender]: Broken pipe (32)
rsync: write failed on "/mnt/btrfs/temp/randomfile": No space left on device (28)
rsync error: error in file IO (code 11) at receiver.c(302) [receiver=3.0.7]
rsync: connection unexpectedly closed (31 bytes received so far) [sender]
rsync error: error in rsync protocol data stream (code 12) at io.c(601) [sender=3.0.7]


Let's write with ~1 MB/s then - succeeds:

# rsync -a -v --progress --bwlimit=1000 . /mnt/btrfs/temp
sending incremental file list
./
randomfile
  4693411469 100%  988.30kB/s    1:17:17 (xfer#1, to-check=6/8)
(...)
sent 4758749321 bytes  received 112 bytes  1012176.84 bytes/sec
total size is 4758167972  speedup is 1.00


I don't think it's expected?


I see these in dmesg while copying the files:

[ 1703.978600] btrfs: free space inode generation (0) did not match free space cache generation (22496)
[ 1703.978605] btrfs: failed to load free space cache for block group 92371156992
[ 1704.026476] btrfs: free space inode generation (0) did not match free space cache generation (22502)
[ 1704.026481] btrfs: failed to load free space cache for block group 114919735296
[ 1704.035239] btrfs: free space inode generation (0) did not match free space cache generation (22503)
[ 1704.035243] btrfs: failed to load free space cache for block group 118140960768
[ 1704.035252] btrfs: free space inode generation (0) did not match free space cache generation (22481)
[ 1704.035255] btrfs: failed to load free space cache for block group 119214702592
[ 1704.294757] btrfs: free space inode generation (0) did not match free space cache generation (22503)
[ 1704.294761] btrfs: failed to load free space cache for block group 243231883264


-- 
Tomasz Chmielewski
http://wpkg.org

      parent reply	other threads:[~2011-08-10 10:38 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-16 18:08 No space left, with 80 GB space free Tomasz Chmielewski
2011-05-20 16:35 ` Tomasz Chmielewski
2011-05-20 23:05   ` Miguel Garrido
2011-05-20 23:49     ` Tomasz Chmielewski
2011-06-18 18:52     ` Tomasz Chmielewski
2011-08-10 10:38     ` Tomasz Chmielewski [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4E425FA7.7030201@wpkg.org \
    --to=mangoo@wpkg.org \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=miguel@mjgar.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.