linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Duncan <1i5t5.duncan@cox.net>
To: linux-btrfs@vger.kernel.org
Subject: Re: WARNING: at fs/btrfs/free-space-cache.c:1887 after hard shutdown.
Date: Wed, 27 Jun 2012 07:56:45 +0000 (UTC)	[thread overview]
Message-ID: <pan.2012.06.27.07.56.46@cox.net> (raw)
In-Reply-To: CACCfv7qEa-hVmNEB6DMy9khGfjcyPuLk27M1ue4VMDwgv9++FQ@mail.gmail.com

Jordan Windsor posted on Wed, 27 Jun 2012 13:16:44 +0930 as excerpted:

> My computer locked up and I had to press the reset button.
> Ever since then I can't mount the btrfs filesystem, here's the output:

Are you aware of the btrfs wiki and have you read up on btrfs there, yet?

https://btrfs.wiki.kernel.org/index.php/Main_Page

In particular, check the mount options listed there.  I had a similar 
problem when I was testing here (during the 3.4 kernel dev cycle, I 
decided btrfs was still too experimental for my current needs so am back 
on more reliable reiserfs for now), which turned out to be a corrupted 
space-cache.  Mounting with the listed nospace_cache option allowed the 
filesystem to mount and self-repair, after which I could mount it 
normally again.

https://btrfs.wiki.kernel.org/index.php/Mount_options

-- 
Duncan - List replies preferred.   No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master."  Richard Stallman


  reply	other threads:[~2012-06-27  7:56 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-27  3:46 WARNING: at fs/btrfs/free-space-cache.c:1887 after hard shutdown Jordan Windsor
2012-06-27  7:56 ` Duncan [this message]
2012-06-27 13:48 ` Josef Bacik
2012-06-29  5:36   ` Jordan Windsor
2012-06-29  5:39     ` Chris Samuel
2012-06-29  6:35       ` Jordan Windsor
2012-06-29 13:04         ` Josef Bacik
2012-06-29 16:15           ` Jordan Windsor

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=pan.2012.06.27.07.56.46@cox.net \
    --to=1i5t5.duncan@cox.net \
    --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;
as well as URLs for NNTP newsgroup(s).