From: Chris Mason <chris.mason@oracle.com>
To: Thomas Lindroth <thomas.lindroth@gmail.com>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: kernel BUG at volumes.c:1705
Date: Mon, 23 Jun 2008 10:38:41 -0400 [thread overview]
Message-ID: <1214231921.10187.553.camel@think.oraclecorp.com> (raw)
In-Reply-To: <485CCB69.8050500@gmail.com>
On Sat, 2008-06-21 at 11:35 +0200, Thomas Lindroth wrote:
> Chris Mason wrote:
> > So, is the bittorrent program run every time you see the memory
> > corruption?
> >
> > Could you please send along a few of the most common errors you see?
>
>
> It's possible to recreate it with mv, cp and other tools without having
> the torrent program running.
>
> I've found a way to trigger the problem every time. If I copy a folder
> with music videos to a freshly created FS it will always fail on the
> same file when about 5.6G of data has been copied. The FS is 30G and
> there is nothing special with that file. If I only copy that file to a
> fresh FS everything works. I've also tried to run
> dd if=/dev/zero of=test to a fresh FS and I was able to write 15G, but I
> was not able to remove that file.
>
Something in your config is much less stable than my test boxes here.
Focusing on the dd test, it looks like random corruption in the FS
metadata. I see you've got gentoo i386 and a 2.6.24 kernel, are there
any other patches in that kernel?
-chris
next prev parent reply other threads:[~2008-06-23 14:38 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-12 16:07 kernel BUG at volumes.c:1705 Thomas Lindroth
2008-06-13 1:33 ` Chris Mason
2008-06-14 9:22 ` Thomas Lindroth
[not found] ` <1213618813.10187.387.camel@think.oraclecorp.com>
[not found] ` <3d08dbff0806180158o6718d3acy34ae5c48a23ad9f8@mail.gmail.com>
[not found] ` <1213792851.10187.420.camel@think.oraclecorp.com>
2008-06-21 9:35 ` Thomas Lindroth
2008-06-23 14:38 ` Chris Mason [this message]
2008-06-23 14:49 ` Joe Peterson
2008-06-24 20:20 ` Thomas Lindroth
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=1214231921.10187.553.camel@think.oraclecorp.com \
--to=chris.mason@oracle.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=thomas.lindroth@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