linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: cwillu <cwillu@cwillu.com>
To: Hendrik Friedel <hendrik@friedels.name>
Cc: linux-btrfs <linux-btrfs@vger.kernel.org>
Subject: Re: btrfsck errors is it save to fix?
Date: Sat, 2 Nov 2013 02:12:09 -0600	[thread overview]
Message-ID: <CAE5mzvijfSOi9dP0MWCMd6=R5MW3bhabote4QYmFnqNEerDifw@mail.gmail.com> (raw)
In-Reply-To: <52742B59.3060405@friedels.name>

> Now that I am searching, I see this in dmesg:
> [95764.899359]  [<ffffffffa00d9a59>] free_fs_root+0x99/0xa0 [btrfs]
> [95764.899384]  [<ffffffffa00dd653>] btrfs_drop_and_free_fs_root+0x93/0xc0
> [btrfs]
> [95764.899408]  [<ffffffffa00dd74f>] del_fs_roots+0xcf/0x130 [btrfs]
> [95764.899433]  [<ffffffffa00ddac6>] close_ctree+0x146/0x270 [btrfs]
> [95764.899461]  [<ffffffffa00b4eb9>] btrfs_put_super+0x19/0x20 [btrfs]
> [95764.899493]  [<ffffffffa00b754a>] btrfs_kill_super+0x1a/0x90 [btrfs]

Need to see the rest of the trace this came from.

  reply	other threads:[~2013-11-02  8:12 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-01 22:29 btrfsck errors is it save to fix? Hendrik Friedel
2013-11-02  8:12 ` cwillu [this message]
2013-11-02  8:58   ` Hendrik Friedel
2013-11-04 21:14     ` Hendrik Friedel
2013-11-05  2:03       ` cwillu
2013-11-06  6:45         ` Hendrik Friedel
2013-11-07 19:16           ` Hendrik Friedel
2013-11-08 10:09             ` Duncan
2013-11-09  8:33               ` Hendrik Friedel
2013-11-11 19:06                 ` Hendrik Friedel
2013-11-11 23:58                   ` Kai Krakow
2013-11-12  7:32                     ` Duncan
2013-11-12 19:37                       ` Kai Krakow
2013-11-13 12:20                         ` Duncan
2013-11-13 12:24                         ` Duncan
2013-11-16 12:32                           ` Hendrik Friedel

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='CAE5mzvijfSOi9dP0MWCMd6=R5MW3bhabote4QYmFnqNEerDifw@mail.gmail.com' \
    --to=cwillu@cwillu.com \
    --cc=hendrik@friedels.name \
    --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).