linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Josef Bacik <josef@redhat.com>
To: Elric Milon <whirm@gmx.com>
Cc: linux-btrfs <linux-btrfs@vger.kernel.org>
Subject: Re: kernel BUG at fs/btrfs/inode.c:149!
Date: Tue, 31 May 2011 09:56:09 -0400	[thread overview]
Message-ID: <4DE4F379.707@redhat.com> (raw)
In-Reply-To: <201105301312.43460.whirm@gmx.com>

On 05/30/2011 07:12 AM, Elric Milon wrote:
> On Monday 23 May 2011 21:51:57 Josef Bacik wrote:
>> On 05/23/2011 07:57 AM, Elric Milon wrote:
>>> On Monday 16 May 2011 18:28:49 you wrote:
>>>> On 05/16/2011 11:01 AM, Whirm wrote:
>>>>> On Monday 16 May 2011 16:11:19 Josef Bacik wrote:
>>>>>
>>>>>
>>>>> Sorry yes, I meant this is how I managed to get the corrupted
>>>>> filesystem.
>>>>>
>>>>> Ill try to break it again.
>>>>
>>>> Oh ok perfect, yeah I will try and do the same sort of things and see if
>>>> I can get it to happen as well.  Thanks,
>>>
>>> Great, btw, I tried to see if I can mount the corrupted filesystem with
>>> the patch you told me about applied, and it fails, here's the log:
>>>
>>> http://pastebin.com/raw.php?i=4Kfv927B
>>>
>>> That happens using 2.6.39-rc7+ from git with the following patch applied
>>> (its
>>
>>> the debug patch and the possible fix you told me about):
>> Ok so this is a different kind of corruption, wooo!  Can you apply this
>> debug patch and get me the output so we can try and fix this bit?  Thanks,
>>
>> Josef
>>
> 
> Sorry for the delay, here's the log:
> 
> http://pastebin.com/raw.php?i=zNqJVpA1
> 

Ok so you have a corrupt extent entry in your tree.  I will come up with
something so we deal with this case better than panicing.  Thanks for
running these debug patches,

Josef

  reply	other threads:[~2011-05-31 13:56 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <201105051954.48405.whirm@gmx.com>
2011-05-05 18:57 ` kernel BUG at fs/btrfs/inode.c:149! Josef Bacik
2011-05-13 17:19   ` whirm
2011-05-13 18:52     ` Josef Bacik
2011-05-16  9:17       ` whirm
2011-05-16 14:11         ` Josef Bacik
2011-05-16 15:01           ` Whirm
2011-05-16 16:28             ` Josef Bacik
2011-05-23 11:57               ` Elric Milon
2011-05-23 19:51                 ` Josef Bacik
2011-05-30 11:12                   ` Elric Milon
2011-05-31 13:56                     ` Josef Bacik [this message]
     [not found] <201105051412.03175.whirm@gmx.com>
2011-05-05 17:53 ` Josef Bacik
2011-05-04 14:26 whirm
2011-05-04 14:46 ` Josef Bacik
2011-05-04 17:43   ` whirm
2011-05-04 18:21     ` Josef Bacik

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=4DE4F379.707@redhat.com \
    --to=josef@redhat.com \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=whirm@gmx.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).