All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Maria Wikström" <maria@ponstudios.se>
To: cwillu <cwillu@cwillu.com>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: Kernel BUG at fs/btrfs/inode.c:2281 & 4665
Date: Tue, 12 Apr 2011 22:25:44 +0200	[thread overview]
Message-ID: <1302639944.7214.33.camel@localhost> (raw)
In-Reply-To: <BANLkTim8OsPEodhgq5+6bg3E8jKWTOoyeA@mail.gmail.com>

On tis, 2011-04-12 at 09:29 -0600, cwillu wrote:
> On Tue, Apr 12, 2011 at 9:11 AM,  <maria@ponstudios.se> wrote:
> >
> > The computer was idle when the first bug happened and after the reboot
> > btrfs can't be mounted. It can't delete orphans and replay the log.
> > It would be nice if I can get the data out, there is nothing important
> > there but it would be nice. I was actually fixing typos in the backup
> > scripts when the bug attacked :)
> 
> There's a "btrfs-zero-log" in the progs-unstable git repository that
> will probably get you up and running again.  You have to build it
> manually via "make btrfs-zero-log".

Thanks! It worked, I got the data out :)

I found the one who has been crashing the computer every now and then
and has probably been corrupting btrfs. scsi_lib.c:1147
So I don't think this is btrfs fault, more likely faulty hardware.

> > I have written this by hand so there may be typos. I skipped the parts
> > that I don't think is necessary, the rest is on paper if I missed
> > something important.
> 
> Digital cameras are wonderful things :p

When they have charged batteries ;)

// Maria



  reply	other threads:[~2011-04-12 20:25 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-12 15:11 Kernel BUG at fs/btrfs/inode.c:2281 & 4665 maria
2011-04-12 15:29 ` cwillu
2011-04-12 20:25   ` Maria Wikström [this message]
2011-04-12 18:20 ` Peter Stuge
2011-04-12 20:26   ` Maria Wikström

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=1302639944.7214.33.camel@localhost \
    --to=maria@ponstudios.se \
    --cc=cwillu@cwillu.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.