Linux Btrfs filesystem development
 help / color / mirror / Atom feed
From: Olivier Bonvalet <btrfs.list@daevel.fr>
To: "Holger Hoffstätte" <holger.hoffstaette@googlemail.com>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: Linux 3.14.18 : kernel BUG at fs/btrfs/file.c:890!
Date: Mon, 08 Sep 2014 11:39:57 +0200	[thread overview]
Message-ID: <1410169197.2383.3.camel@daevel.fr> (raw)
In-Reply-To: <pan.2014.09.07.17.48.53@googlemail.com>


Le dimanche 07 septembre 2014 à 17:48 +0000, Holger Hoffstätte a écrit :
> On Sun, 07 Sep 2014 18:39:40 +0200, Olivier Bonvalet wrote:
>
> I cannot really offer much assistance, but that particular area of code
> looks suspiciously like something fixed later and *not* yet backported
> to 3.14.8:
> 
> "Btrfs: fix leaf corruption caused by ENOSPC while hole punching"
> https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/fs/btrfs?id=fc19c5e73645f95d3eca12b4e91e7b56faf1e4a4
> 
> The symptoms described in the patch sound like they might be your OOPS.
> Unfortunately (I think) that would mean that just installing different
> kernels will not fix the problem, since the problem is on disk. :/
> 
> So to me it seems your best course of action is to backup/mkfs/restore
> the affected partition and stick with 3.17-rc3, since that has tons
> more fixes.
> 
> If you really need/want 3.14.x and are not afraid of building your
> own kernel, you can try applying my btrfs-* patches from:
> https://github.com/hhoffstaette/kernel-patches/tree/master/3.14
> which apply cleanly to the latest 3.14.18-stable.
> 
> However even that will not fix a bungled tree on disk.
> 
> -h
> 
> --

Ok, so the cause is probably solved, this is a very good news, thanks.
And yes, I can easily use 3.17-rc3 kernel.

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.

Any hope that btrfsck be updated to fix that ?

Olivier


  reply	other threads:[~2014-09-08  9:45 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 [this message]
2014-09-08  9:59     ` Holger Hoffstätte
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=1410169197.2383.3.camel@daevel.fr \
    --to=btrfs.list@daevel.fr \
    --cc=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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox