From: Tomasz Chmielewski <mangoo@wpkg.org>
To: linux-btrfs@vger.kernel.org
Subject: Re: how can I copy files bigger than ~32 GB when using compress-force?
Date: Mon, 04 Oct 2010 23:42:12 +0200 [thread overview]
Message-ID: <4CAA4A34.80701@wpkg.org> (raw)
> I'm assuming this works without compress-force? I can make a guess at
> what is happening, the compression forces a relatively small extent
> size, and this is making our worst case metadata reservations get upset.
Yes, it works without compress-force.
Interesting is that cp or rsync sometimes just exit quite fast with "no
space left".
Sometimes, they just "hang" (waited up to about an hour) - file size
does not grow anymore, last modified time is not updated, iostat does
not show any bytes read/written, there are no btrfs or any other
processes taking too much CPU, cp/rsync is not in "D" state (although it
gets to "D" state and uses 100% CPU as I try to kill it).
Could it be we're hitting two different bugs here?
> Does it happen with any 32gb file that doesn't compress well?
The 220 GB qcow2 file was basically uncompressible (backuppc archive
full of bzip2-compressed files).
--
Tomasz Chmielewski
http://wpkg.org
next reply other threads:[~2010-10-04 21:42 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-04 21:42 Tomasz Chmielewski [this message]
2010-10-04 22:28 ` how can I copy files bigger than ~32 GB when using compress-force? Chris Mason
2010-10-05 4:12 ` Chester
2010-10-05 6:16 ` Tomasz Chmielewski
2010-10-12 11:12 ` Tomasz Chmielewski
2010-10-12 15:01 ` Tomasz Chmielewski
-- strict thread matches above, loose matches on Subject: below --
2010-10-04 20:26 Tomasz Chmielewski
2010-10-04 20:37 ` Chris Mason
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=4CAA4A34.80701@wpkg.org \
--to=mangoo@wpkg.org \
--cc=linux-btrfs@vger.kernel.org \
/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.