From: "Holger Hoffstätte" <holger.hoffstaette@googlemail.com>
To: linux-btrfs@vger.kernel.org
Subject: Re: Linux 3.14.18 : kernel BUG at fs/btrfs/file.c:890!
Date: Mon, 8 Sep 2014 09:59:46 +0000 (UTC) [thread overview]
Message-ID: <pan.2014.09.08.09.59.46@googlemail.com> (raw)
In-Reply-To: 1410169197.2383.3.camel@daevel.fr
On Mon, 08 Sep 2014 11:39:57 +0200, Olivier Bonvalet wrote:
> Ok, so the cause is probably solved, this is a very good news, thanks.
I don't *know* that this is your specific problem, it just looks like it
might be judging by the description in the patch.
> And yes, I can easily use 3.17-rc3 kernel.
Good.
> So the problem is with current data : I don't know an easy way to
> export/restore subvolumes & snapshots thought network, and I don't have
> physical access to this rent servers.
That's tricky, especially the snapshots. I don't remember seeing how
large the partition in question is, but is there really no place where
you can store a simple tar.gz dump, nuke & recreate the partition and
restore the tarball? If so I'm afraid you are what's known as
"up shit creek without a paddle"..
> Any hope that btrfsck be updated to fix that ?
By default btrfsck doesn't do anything. What happens when you run it
without --repair, just to see what it finds?
-h
next prev parent reply other threads:[~2014-09-08 10:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-07 16:39 Linux 3.14.18 : kernel BUG at fs/btrfs/file.c:890! Olivier Bonvalet
2014-09-07 17:48 ` Holger Hoffstätte
2014-09-08 9:39 ` Olivier Bonvalet
2014-09-08 9:59 ` Holger Hoffstätte [this message]
2014-09-08 10:48 ` Olivier Bonvalet
2014-09-08 12:29 ` Holger Hoffstätte
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=pan.2014.09.08.09.59.46@googlemail.com \
--to=holger.hoffstaette@googlemail.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.