From: Thomas Weber <thomas.weber.linux@googlemail.com>
To: Mitch Harder <mitch.harder@sabayonlinux.org>
Cc: Thomas Weber <thomas.weber.linux@googlemail.com>,
linux-btrfs@vger.kernel.org
Subject: Re: btrfs bug
Date: Tue, 31 Jan 2012 22:51:31 +0100 [thread overview]
Message-ID: <4F286263.7010502@gmail.com> (raw)
In-Reply-To: <CAKcLGm-z3pJZgr30WYs8D8_VnVFMcjErKtvG5_ys-FOo=dRPEw@mail.gmail.com>
Hello Mitch,
On 01/31/2012 10:37 PM, Mitch Harder wrote:
> On Tue, Jan 31, 2012 at 12:04 PM, Thomas Weber
> <thomas.weber.linux@googlemail.com> wrote:
>> Hello,
>>
>> this morning my laptop with btrfs crashed. It is an ssd drive.
>>
>> It is a Linux aramis 3.2.2-1-ARCH #1 SMP PREEMPT Thu Jan 26 08:40:20 CET
>> 2012 x86_64 Intel(R) Core(TM)2 Duo CPU T7250 @ 2.00GHz GenuineIntel
>> GNU/Linux
>>
>> Regards,
>> Thomas
>>
>>
>> This two lines are from a photo, that i made.
>>> kernel BUG at fs/btrfs/extent_io.c:4357!
>>> invalid opcode: 0000 [#1] PREEMPT SMP
>> The rest is from dmesg.
>>
> In your dmesg output, immediately prior to what you posted, there
> should have been a message like: "btrfs memmove bogus src_offset %lu
> move len %lu len %lu".
>
> If you still have this output, could you post that line with its values?
no, sorry i don't have more output.
Thomas
next prev parent reply other threads:[~2012-01-31 21:51 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-31 18:04 btrfs bug Thomas Weber
2012-01-31 21:37 ` Mitch Harder
2012-01-31 21:51 ` Thomas Weber [this message]
2012-02-01 5:20 ` Thomas Weber
2012-02-01 18:07 ` Mitch Harder
[not found] <016b3ac0-1524-6bfe-4261-c6adff00eb80.ref@aol.com>
2022-08-08 23:54 ` Augusto
-- strict thread matches above, loose matches on Subject: below --
2012-11-12 14:37 BTRFS Bug Ross Moore
2012-11-12 15:08 ` Liu Bo
2012-11-12 23:15 ` Ross Moore
2012-11-13 10:16 ` Sem
[not found] ` <CAJDbZnTMmzMJYR6=qkX1CTQ365MSYeSX7L8LrE_GLsxWAbz58Q@mail.gmail.com>
2012-11-20 13:20 ` Liu Bo
[not found] ` <CAJDbZnT2h8eoSHPHLjMVLMjKW+J0PcaV=pzPJs6r7=nkgTBP4Q@mail.gmail.com>
2012-11-20 13:58 ` Liu Bo
2011-05-16 22:43 btrfs bug Maciej Sujkowski
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=4F286263.7010502@gmail.com \
--to=thomas.weber.linux@googlemail.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=mitch.harder@sabayonlinux.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).