All of lore.kernel.org
 help / color / mirror / Atom feed
From: Francesco Cepparo <francesco.cepparo@gmail.com>
To: linux-btrfs@vger.kernel.org
Subject: kernel BUG at fs/btrfs/extent_io.c:1890!
Date: Wed, 11 Apr 2012 14:44:26 +0000	[thread overview]
Message-ID: <CACfQV3hb92zrYUJ8to1mq8s1wzfdEoMBDi9b5VmfZ0AZ=UBkFA@mail.gmail.com> (raw)

Hi, I've been using btrfs for a while now, and some months ago one of
my filesystems stopped mounting. I tried to fix it by mounting it with
the recovery option, by using btrfs-zero-log and by restoring the
superblock but it didn't work, so I left the filesystem standing there
waiting for the fsck repairing tool to be released (running the
version of fsck I had at the time produced the following output:
http://dl.dropbox.com/u/2565562/btrfsck-old-output while running the
2012-03-28 version of btrfsck produces the following output:
http://dl.dropbox.com/u/2565562/btrfsck-20120328-output.gz ).
I'm still waiting for the repairing tool and I haven't tried the
dangerous don't ever use branch, but as I have updated the kernel to
version 3.4.0-rc2 I tried to mount the filesystem again with the new
kernel, and instead of failing with this error message:
http://dl.dropbox.com/u/2565562/btrfs-kernel-3.3 as it did with kernel
3.3.1 and the previous kernels, with 3.4.0-rc2 it now hits the
following kernel BUG:
http://dl.dropbox.com/u/2565562/btrfs-kernel-3.4-bug

I hope I can be of any help in improving the already great btrfs.
Also, is there any hope for me to recover my old filesystem? :)

             reply	other threads:[~2012-04-11 14:44 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-11 14:44 Francesco Cepparo [this message]
2012-04-11 15:01 ` kernel BUG at fs/btrfs/extent_io.c:1890! Josef Bacik
2012-04-11 23:59   ` Francesco Cepparo
2012-04-12 18:08     ` Josef Bacik
2012-04-12 18:15       ` Chris Mason
2012-04-12 18:20         ` Josef Bacik
2012-04-12 21:56           ` Francesco Cepparo
2012-04-13 14:45             ` Josef Bacik
2012-04-14  0:06               ` Francesco Cepparo
2012-04-16 13:34                 ` Josef Bacik

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='CACfQV3hb92zrYUJ8to1mq8s1wzfdEoMBDi9b5VmfZ0AZ=UBkFA@mail.gmail.com' \
    --to=francesco.cepparo@gmail.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 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.