public inbox for linux-btrfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Tore Anderson <tore.anderson@redpill-linpro.com>
To: Josef Bacik <josef@redhat.com>
Cc: linux-btrfs@vger.kernel.org, Hugo Mills <hugo-lkml@carfax.org.uk>
Subject: Re: Crash in __btrfs_reserve_extent
Date: Thu, 06 Aug 2009 19:41:49 +0200	[thread overview]
Message-ID: <4A7B15DD.2010101@redpill-linpro.com> (raw)
In-Reply-To: <20090806142750.GE3655@dhcp231-156.rdu.redhat.com>

* Josef Bacik

> Ooookay, now that I'm awake lets try this again :).  You are right, I
> thought it was 212GB used, not 16GB used.  Something has gone
> horribly wrong, btrfs seems to think thats all the space it can use.
> The command you need to use is btrfs-vol -b.  Please try that and see
> if it behaves better.  Before you run that please do a btrfs-show and
> post the output, I'd like to see how big the fs thinks its supposed
> to be.

It doesn't print much of anything, I'm afraid:

root@echo:~/misc/btrfs-progs-unstable# ./btrfs-show /dev/mapper/vg_echo-lv_root  
failed to read /dev/sr0
failed to read /dev/sdf
failed to read /dev/sde
failed to read /dev/sdd
failed to read /dev/sdc
failed to read /dev/sdb
Btrfs Btrfs v0.19

Same output with btrfs-progs-0.19.  The devices it's complaining about
is a USB memory card reader and my optical drive, if I disconnect
those from the SCSI layer the output is simply "Btrfs Btrfs v0.19".

I tried to run btrfsck earlier today, but it only gave me an error
message.  Perhaps that just made things worse?

I've got a btrfs-image dump that I took right after the problem showed
for the first time (before the fsck), by the way.  It's available at
<http://greed.fud.no/hosed_rootfs.btrfsimage.Z> in case you have any
use for it.

Best regards,
-- 
Tore Anderson
Redpill Linpro AS - http://www.redpill-linpro.com/
Tel: +47 21 54 41 27

  reply	other threads:[~2009-08-06 17:41 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-08-06  7:00 Crash in __btrfs_reserve_extent Tore Anderson
2009-08-06  8:53 ` Tore Anderson
2009-08-06 13:54   ` Josef Bacik
2009-08-06 14:15     ` Tore Anderson
2009-08-06 14:27       ` Josef Bacik
2009-08-06 17:41         ` Tore Anderson [this message]
2009-08-06 18:04           ` Josef Bacik
2009-08-06 18:14             ` Tore Anderson
2009-08-06 18:37               ` Josef Bacik
2009-08-06 18:49                 ` Tore Anderson
2009-08-06 18:57                   ` Chris Mason
2009-08-06 19:01                   ` Josef Bacik
2009-08-06 19:22                     ` Chris Mason
2009-08-06 22:01                       ` Tore Anderson
  -- strict thread matches above, loose matches on Subject: below --
2009-08-06 14:57 Robert Förster
2009-08-06 15:20 ` Josef Bacik
2009-08-06 15:36   ` Robert Förster
2009-08-07  5:10     ` Robert Förster
2009-08-06 17:15   ` Tore Anderson
2009-08-06 17:57     ` Robert Förster

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=4A7B15DD.2010101@redpill-linpro.com \
    --to=tore.anderson@redpill-linpro.com \
    --cc=hugo-lkml@carfax.org.uk \
    --cc=josef@redhat.com \
    --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