All of lore.kernel.org
 help / color / mirror / Atom feed
From: Chris Mason <chris.mason@oracle.com>
To: Tomasz Chmielewski <mangoo@wpkg.org>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: how can I copy files bigger than ~32 GB when using compress-force?
Date: Mon, 4 Oct 2010 16:37:43 -0400	[thread overview]
Message-ID: <20101004203743.GH5090@think> (raw)
In-Reply-To: <4CAA3872.3080106@wpkg.org>

On Mon, Oct 04, 2010 at 10:26:26PM +0200, Tomasz Chmielewski wrote:
> I'm trying to copy a ~220 GB file from a ext4 to btrfs filesystem
> with 336 GB free space on it. System is running 2.6.36-rc6.
> 
> File size on a ext4 filesystem:
> 
> # ls -l srv1-backup.qcow2
> -rw-r--r-- 1 root root 219564146688 2010-09-26 21:56 srv1-backup.qcow2
> 
> 
> Unfortunately it fails when only about 32 GB is copied (with
> compress-force mount option enabled).

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.

Does it happen with any 32gb file that doesn't compress well?

-chris

  reply	other threads:[~2010-10-04 20:37 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-04 20:26 how can I copy files bigger than ~32 GB when using compress-force? Tomasz Chmielewski
2010-10-04 20:37 ` Chris Mason [this message]
  -- strict thread matches above, loose matches on Subject: below --
2010-10-04 21:42 Tomasz Chmielewski
2010-10-04 22:28 ` 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

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=20101004203743.GH5090@think \
    --to=chris.mason@oracle.com \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=mangoo@wpkg.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.