From: Sean Reifschneider <jafo@tummy.com>
To: Chris Mason <chris.mason@oracle.com>, linux-btrfs@vger.kernel.org
Subject: Re: btrstress caused kernel oops after 8-ish days.
Date: Tue, 27 Apr 2010 19:30:51 -0600 [thread overview]
Message-ID: <4BD78FCB.3050707@tummy.com> (raw)
In-Reply-To: <20100427114628.GC6513@think>
[-- Attachment #1: Type: text/plain, Size: 603 bytes --]
On 04/27/2010 05:46 AM, Chris Mason wrote:
> This oops is fixed in later kernels, and it's why things stopped.
Thanks for the reply. I'm not sure I have the time to give this with
respect to following the trunk kernel right now. If the btrfs project
doesn't have test machines that could be set up for longer-term testing of
something like btrstress, let me know and I'll look at it when I have some
more time in the future.
Thanks,
Sean
--
Sean Reifschneider, Member of Technical Staff <jafo@tummy.com>
tummy.com, ltd. - Linux Consulting since 1995: Ask me about High Availability
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 253 bytes --]
prev parent reply other threads:[~2010-04-28 1:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-27 11:14 btrstress caused kernel oops after 8-ish days Sean Reifschneider
2010-04-27 11:46 ` Chris Mason
2010-04-28 1:30 ` Sean Reifschneider [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=4BD78FCB.3050707@tummy.com \
--to=jafo@tummy.com \
--cc=chris.mason@oracle.com \
--cc=linux-btrfs@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.