public inbox for linux-btrfs@vger.kernel.org
 help / color / mirror / Atom feed
From: "Marc R. O'Connor" <mroconnor@oel.state.nj.us>
To: Chris Mason <chris.mason@oracle.com>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: kernel bug in file-item.c
Date: Wed, 29 Apr 2009 14:46:48 -0400	[thread overview]
Message-ID: <49F8A098.4020106@oel.state.nj.us> (raw)
In-Reply-To: <1241030419.20099.55.camel@think.oraclecorp.com>

[-- Attachment #1: Type: text/plain, Size: 929 bytes --]

To be honest I have no idea. Let me see if I can find a different
version to test with and see. I think I'm still under warranty. ;)

Chris Mason wrote:
> On Wed, 2009-04-29 at 14:38 -0400, Marc R. O'Connor wrote:
>>>> I have done that on all btrfs partitions I have and btrfsck did not
>>>> return anything odd.
>>>>
>>> In that case, the bad ordering is being introduced at run time.  Could
>>> you please run memtest86 on the box?
>>>
>>> -chris
>>>
>>>
>>  memtest comes back with two errors very early on then reboots the
>> sysrescueCD. :(
> 
> Well, then I'm surprised btrfs doesn't crash more violently and more
> often ;)
> 
> Do you think you're hitting a memtest bug or is the HW really bad?
> 
> -chris
> 
> 
> 
> 

-- 

--
Marc R. O'Connor
Information Systems
Camden County Board of Social Services
600 Market St.
Camden, NJ 08102
mroconnor@oel.state.nj.us
856-225-8915 Ofc.
609-206-3458 Blackberry
319D8AF1 BB PIN


[-- Attachment #2: mroconnor.vcf --]
[-- Type: text/x-vcard, Size: 260 bytes --]

begin:vcard
fn:Marc O'Connor
n:O'Connor;Marc
org:Camden County Board of Social Services;Information Technology
adr:;;600 Market St.;Camden;NJ;08102;USA
email;internet:mroconnor@oel.state.nj.us
tel;work:856-225-8915
tel;cell:609-206-3458
version:2.1
end:vcard


[-- Attachment #3: disclaimer.txt --]
[-- Type: Text/Plain, Size: 662 bytes --]

This E-mail, including any attachments, may be intended solely for the personal 
and confidential use of the sender and recipient(s) named above. This message 
may include advisory, consultative and/or deliberative material and, as such, 
would be privileged and confidential and not a public document. Any Information 
in this e-mail identifying a client of the Department of Human Services is 
confidential. If you have received this e-mail in error, you must not review, 
transmit, convert to hard copy, copy, use or disseminate this e-mail or any 
attachments to it and you must delete this message. You are requested to notify 
the sender by return e-mail.

  reply	other threads:[~2009-04-29 18:46 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-28 17:39 kernel bug in file-item.c Marc R. O'Connor
2009-04-28 19:23 ` Chris Mason
2009-04-28 19:30   ` Marc R. O'Connor
2009-04-29 16:04   ` Marc R. O'Connor
2009-04-29 17:53     ` Chris Mason
2009-04-29 18:21       ` Marc R. O'Connor
2009-04-29 18:30         ` Chris Mason
2009-04-29 18:38           ` Marc R. O'Connor
2009-04-29 18:40             ` Chris Mason
2009-04-29 18:46               ` Marc R. O'Connor [this message]
2009-04-29 18:50               ` Zach Brown
2009-04-29 19:04                 ` Marc R. O'Connor
2009-04-30  7:23                   ` Dmitri Nikulin
2009-04-29 19:32               ` Tracy Reed
2009-04-30  9:08                 ` Paul Komkoff
2009-04-30 16:54                   ` Tracy Reed
2009-05-01  2:13                     ` Dmitri Nikulin

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=49F8A098.4020106@oel.state.nj.us \
    --to=mroconnor@oel.state.nj.us \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox