public inbox for linux-btrfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Josef Bacik <josef@redhat.com>
To: Jan Engelhardt <jengelh@medozas.de>
Cc: Josef Bacik <josef@redhat.com>, linux-btrfs@vger.kernel.org
Subject: Re: Bug at extent-tree.c:3190
Date: Tue, 3 Mar 2009 11:16:14 -0500	[thread overview]
Message-ID: <20090303161614.GA5446@unused.rdu.redhat.com> (raw)
In-Reply-To: <alpine.LSU.2.00.0903031708140.855@fbirervta.pbzchgretzou.qr>

On Tue, Mar 03, 2009 at 05:11:06PM +0100, Jan Engelhardt wrote:
> 
> On Tuesday 2009-03-03 16:40, Josef Bacik wrote:
> >> 
> >> The following oops was obtained by doing some copying; it's tainted-P by 
> >> nvidia but maybe it still gives some hints.
> >> The testcase is basically
> >> 
> >> $ rsync -HPSav a/ b/
> >> 
> >> where by a/ is a collection of kernel trees, and b/ is a fresh btrfs.
> >> 
> >> $ ls -l a/
> >> drwxr-xr-x 19 jengelh users 4096 Jan 10 07:32 linux17
> >> drwxr-xr-x 19 jengelh users 4096 Jan 10 07:34 linux18
> >> drwxr-xr-x 19 jengelh users 4096 Jan 10 07:34 linux19
> >> drwxr-xr-x 19 jengelh users 4096 Jan 10 07:34 linux20
> >> drwxr-xr-x 19 jengelh users 4096 Jan 10 07:35 linux21
> >> drwxr-xr-x 19 jengelh users 4096 Jan 10 07:35 linux22
> >> drwxr-xr-x 19 jengelh users 4096 Jan 10 07:35 linux23
> >> drwxr-xr-x 20 jengelh users 4096 Jan 10 07:35 linux24
> >> drwxr-xr-x 21 jengelh users 4096 Jan 10 07:36 linux25
> >> drwxr-xr-x 21 jengelh users 4096 Jan 10 07:36 linux26
> >> drwxr-xr-x 22 jengelh users 4096 Jan 10 07:37 linux27
> >> drwxr-xr-x 22 jengelh users 4096 Jan 10 07:37 linux28
> >
> >ENOSPC, sorry :)
> 
> Ah heh, could be a cause. Even so, there is still "plenty" of
> space (loop1 with btrfs is also 4184064K in size):
> 
> Filesystem    Type   1K-blocks      Used Available Use% Mounted on
> /dev/loop0     xfs     4184064   3676644    507420  88% /lo/kernel

Yeah you ran out of data area, the rest of the space is reserved for metadata
space.  If you use the current git tree with my enospc patch this problem
shouldnt happen (as easily anyway).  Thanks,

Josef

      reply	other threads:[~2009-03-03 16:16 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-03  3:09 Bug at extent-tree.c:3190 Jan Engelhardt
2009-03-03 15:40 ` Josef Bacik
2009-03-03 16:11   ` Jan Engelhardt
2009-03-03 16:16     ` Josef Bacik [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=20090303161614.GA5446@unused.rdu.redhat.com \
    --to=josef@redhat.com \
    --cc=jengelh@medozas.de \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox