All of lore.kernel.org
 help / color / mirror / Atom feed
From: Martin Steigerwald <Martin@lichtvoll.de>
To: linux-btrfs@vger.kernel.org
Subject: Re: 3.5-rc4: BTRFS unmountable after hard lockup
Date: Mon, 25 Jun 2012 20:48:51 +0200	[thread overview]
Message-ID: <201206252048.52022.Martin@lichtvoll.de> (raw)
In-Reply-To: <201206252029.34545.Martin@lichtvoll.de>

Am Montag, 25. Juni 2012 schrieb Martin Steigerwald:
> Hi!
> 
> I got a X server / drm related crash or hard lockup. After I rebooted I
> tried to mount the BTRFS on my esata disk. It has big metadata
> (mkfs.btrfs -l 32768 -n 32768).
> 
> 
> I got:
> 
[… backtrace …]

> BTRFS was not mounted. After trying to mount again, I got:
> 
> merkaba:~> ps aux | grep " D" | grep -v grep
> root      3446  0.0  0.0      0     0 ?        D    20:22   0:00
> [btrfs-transacti] root      4666  0.0  0.0  18640  1184 tty1     D+  
> 20:24   0:00 mount /mnt/amazon-daten
> 
> Any hints how to get my disk mounted?
> 
> I have a fairly recent backup, but I would prefer when I do not have to
> replay it. Its one of my expectations for a file system: be safe on
> sudden write interruptions like power loss or crash.

Well, I wanted to have back my disk ASAP. So I just tried that btrfs-zero-
log mantra again.

It worked. Hopefully the backtrace still gives you a clue on what has 
happened. I thought these kind of errors where gone now.

(Yeah, I know its still experimental… no indoctrination requested;-)

Thanks,
-- 
Martin 'Helios' Steigerwald - http://www.Lichtvoll.de
GPG: 03B0 0D6C 0040 0710 4AFA  B82F 991B EAAC A599 84C7

  reply	other threads:[~2012-06-25 18:48 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-25 18:29 3.5-rc4: BTRFS unmountable after hard lockup Martin Steigerwald
2012-06-25 18:48 ` Martin Steigerwald [this message]
2012-06-25 22:18 ` David Sterba
2012-06-26  3:47   ` Liu Bo
2012-06-26 12:28     ` Martin Steigerwald
2012-06-26 12:49     ` 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=201206252048.52022.Martin@lichtvoll.de \
    --to=martin@lichtvoll.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 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.