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 12:48:20 +0200	[thread overview]
Message-ID: <1410173300.2383.10.camel@daevel.fr> (raw)
In-Reply-To: <pan.2014.09.08.09.59.46@googlemail.com>


Le lundi 08 septembre 2014 à 09:59 +0000, Holger Hoffstätte a écrit :
> By default btrfsck doesn't do anything. What happens when you run it
> without --repair, just to see what it finds?

In fact I haven't enough memory to run it (8GB of RAM only, with a 2*3TB
FS in mirroring, btrfs mirroring).


  reply	other threads:[~2014-09-08 10:48 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
2014-09-08 10:48       ` Olivier Bonvalet [this message]
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=1410173300.2383.10.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