From: Chris Mason <chris.mason@oracle.com>
To: Xavier Nicollet <nicollet@jeru.org>
Cc: linux-btrfs <linux-btrfs@vger.kernel.org>
Subject: Re: mini bug report
Date: Mon, 20 Dec 2010 11:12:09 -0500 [thread overview]
Message-ID: <1292861507-sup-724@think> (raw)
In-Reply-To: <20101220155801.GF24127@jeru.org>
Excerpts from Xavier Nicollet's message of 2010-12-20 10:58:01 -0500:
> Hi,
>
> I use btrfs on my laptop, 2.6.37-rc2 from kernel.org, under dm-crypt, as
> /. I use space_cache and compression (not forced).
>
> Today, my computer froze. At reboot, the kernel could not mount.
> The dmesg output, which I haven't saved was speaking of a null
> dereference.
>
> After that I rebooted on 2.6.34, which was not very happy: mount errors
> (space cache ?).
>
> Now I am on 2.6.37-rc2 again, which seems to work.
> So I guess it might come from space_cache.
>
> I would note on a paper if this comes back. However if anybody has any
> clue on what specific part of the dmesg should be reported, it would be
> very helpfull !
These sound like the free space caching bugs that josef fixed. If you
pull down the latest I think we've got it nailed.
-chris
prev parent reply other threads:[~2010-12-20 16:12 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-20 15:58 mini bug report Xavier Nicollet
2010-12-20 16:12 ` Chris Mason [this message]
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=1292861507-sup-724@think \
--to=chris.mason@oracle.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=nicollet@jeru.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;
as well as URLs for NNTP newsgroup(s).