linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Tomasz Chmielewski <tch@virtall.com>
To: Shilong Wang <wangshilong1991@gmail.com>
Cc: Wang Shilong <wangsl.fnst@cn.fujitsu.com>,
	"linux-btrfs@vger.kernel.org" <linux-btrfs@vger.kernel.org>
Subject: Re: kernel BUG at fs/btrfs/relocation.c:1062
Date: Sat, 21 Dec 2013 12:08:56 +0900	[thread overview]
Message-ID: <20131221120856.417ab384@virtall.com> (raw)
In-Reply-To: <CAP9B-Q=rmMssHkNsypKmqcFdVgnT=hPsZSgdvq57v+P_XaCH9A@mail.gmail.com>

On Sat, 21 Dec 2013 01:11:00 +0800
Shilong Wang <wangshilong1991@gmail.com> wrote:

> ok, It seems that your filesystem is not in consistency anymore.
> To confirm your filesystem status, you can try to run btrfsck to
> check if there is something wrong.
> 
> To get a stable fs now, you can try to mount btrfs with option
> skip_balance and recovery, recovery options try to get a previous
> good tree root which might help you
> get a stable fs.

Unfortunately even after using these mount options it breaks as before,
as soon as I remove snapshots, or even copy some data in with rsync.

Oh well, at least I have read only access...


-- 
Tomasz Chmielewski
http://wpkg.org

      reply	other threads:[~2013-12-21  3:09 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-12-19 12:09 kernel BUG at fs/btrfs/relocation.c:1062 Tomasz Chmielewski
2013-12-19 12:14 ` Wang Shilong
2013-12-19 12:30   ` Tomasz Chmielewski
2013-12-19 12:49     ` Wang Shilong
2013-12-19 13:07       ` Tomasz Chmielewski
2013-12-20 15:06         ` Tomasz Chmielewski
2013-12-20 15:52           ` Shilong Wang
2013-12-20 15:59             ` Tomasz Chmielewski
2013-12-20 16:07               ` Shilong Wang
2013-12-20 16:41                 ` Tomasz Chmielewski
2013-12-20 17:11                   ` Shilong Wang
2013-12-21  3:08                     ` Tomasz Chmielewski [this message]

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=20131221120856.417ab384@virtall.com \
    --to=tch@virtall.com \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=wangshilong1991@gmail.com \
    --cc=wangsl.fnst@cn.fujitsu.com \
    /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).