linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Andrew Lutomirski <luto@mit.edu>
To: Marek Otahal <markotahal@gmail.com>
Cc: Josef Bacik <josef@redhat.com>,
	Daniel J Blueman <daniel.blueman@gmail.com>,
	Chris Mason <chris.mason@oracle.com>,
	Linux Btrfs <linux-btrfs@vger.kernel.org>
Subject: Re: kernel BUG at fs/btrfs/inode.c:4676!
Date: Fri, 10 Jun 2011 14:55:51 -0400	[thread overview]
Message-ID: <BANLkTinUDt4vCBF=z=2+3cdY7FS6evBPCQ@mail.gmail.com> (raw)
In-Reply-To: <201106102043.19025.markotahal@gmail.com>

On Fri, Jun 10, 2011 at 2:43 PM, Marek Otahal <markotahal@gmail.com> wrote:
>
> The test-case is quite easy,
> 1. mount the FS, just with compress-force=lzo option // I didn't try without, but on my other btrfs partition that doesn't use compression the err never happened ...so, can the others who experience the bug confirm compress=lzo used?

Yes, I use compress=lzo.

--Andy

  parent reply	other threads:[~2011-06-10 18:55 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-06 10:19 kernel BUG at fs/btrfs/inode.c:4676! Marek Otahal
2011-06-08 18:43 ` Marek Otahal
2011-06-09 15:39 ` Jan Steffens
2011-06-10  1:57 ` Andy Lutomirski
2011-06-10  2:06   ` Daniel J Blueman
2011-06-10 13:33     ` Josef Bacik
     [not found]       ` <201106102043.19025.markotahal@gmail.com>
2011-06-10 18:55         ` Andrew Lutomirski [this message]
2011-06-10 20:52         ` Josef Bacik
2011-06-10 21:52           ` Marek Otahal
2011-06-22 16:09             ` Josef Bacik
2011-07-20  6:05               ` David Woodhouse
2011-07-20  8:44                 ` Chris Mason
2011-07-20 14:37                   ` David Woodhouse
2011-09-17 19:13 ` Stephane Chazelas

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='BANLkTinUDt4vCBF=z=2+3cdY7FS6evBPCQ@mail.gmail.com' \
    --to=luto@mit.edu \
    --cc=chris.mason@oracle.com \
    --cc=daniel.blueman@gmail.com \
    --cc=josef@redhat.com \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=markotahal@gmail.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).