On Fri, May 1, 2009 at 2:54 AM, Tracy Reed wrote:
> Sorry, I was unclear: I meant manage in a public-relations sort of
> way. Not in a technical way. You are absolutely right that bad RAM or
> CPU means you are hosed.
Even so, it's a perfect opportunity to not make things worse by trying
to write
On Thu, Apr 30, 2009 at 10:08:04AM +0100, Paul Komkoff spake thusly:
> On Wed, Apr 29, 2009 at 8:32 PM, Tracy Reed wrote:
> > Note that this will be a problem that btrfs must properly manage. And
> > it must be done MUCH better than a certain previously semi-popular
> > filesystem did. The expecta
On Wed, Apr 29, 2009 at 8:32 PM, Tracy Reed wrote:
> Note that this will be a problem that btrfs must properly manage. And
> it must be done MUCH better than a certain previously semi-popular
> filesystem did. The expectation needs to be set that due to the much
I don't think it's workable or fea
On Thu, Apr 30, 2009 at 5:04 AM, Marc R. O'Connor
wrote:
>> If you can stomach it, you can get a second opinion from the bootable
>> windows memory testing iso:
>>
>> http://oca.microsoft.com/en/windiag.asp
>
>
> It will be hard but I might just try it. Two versions of memtest86+ die
> in the mi
On Wed, Apr 29, 2009 at 02:40:19PM -0400, Chris Mason spake thusly:
> Well, then I'm surprised btrfs doesn't crash more violently and more
> often ;)
Note that this will be a problem that btrfs must properly manage. And
it must be done MUCH better than a certain previously semi-popular
filesystem
> Do you think you're hitting a memtest bug or is the HW really bad?
If you can stomach it, you can get a second opinion from the bootable
windows memory testing iso:
http://oca.microsoft.com/en/windiag.asp
- z
--
To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
the b
Zach Brown wrote:
>> Do you think you're hitting a memtest bug or is the HW really bad?
>
> If you can stomach it, you can get a second opinion from the bootable
> windows memory testing iso:
>
> http://oca.microsoft.com/en/windiag.asp
>
> - z
It will be hard but I might just try it. Two v
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
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 Mason wrote:
> On Wed, 2009-04-29 at 14:21 -0400, Marc R. O'Connor wrote:
>> Chris Mason wrote:
>>> On Wed, 2009-04-29 at 12:04 -0400, Marc R. O'Connor wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
full file-item.c attached
Chris Mason wrote:
> On Tu
On Wed, 2009-04-29 at 14:21 -0400, Marc R. O'Connor wrote:
>
> Chris Mason wrote:
> > On Wed, 2009-04-29 at 12:04 -0400, Marc R. O'Connor wrote:
> >> -BEGIN PGP SIGNED MESSAGE-
> >> Hash: SHA1
> >>
> >> full file-item.c attached
> >>
> >> Chris Mason wrote:
> >>> On Tue, 2009-04-28 at 13:3
Chris Mason wrote:
> On Wed, 2009-04-29 at 12:04 -0400, Marc R. O'Connor wrote:
>> -BEGIN PGP SIGNED MESSAGE-
>> Hash: SHA1
>>
>> full file-item.c attached
>>
>> Chris Mason wrote:
>>> On Tue, 2009-04-28 at 13:39 -0400, Marc R. O'Connor wrote:
I have had two 'kernel bug' issues today
On Wed, 2009-04-29 at 12:04 -0400, Marc R. O'Connor wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> full file-item.c attached
>
> Chris Mason wrote:
> > On Tue, 2009-04-28 at 13:39 -0400, Marc R. O'Connor wrote:
> >> I have had two 'kernel bug' issues today both referencing file-item
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
full file-item.c attached
Chris Mason wrote:
> On Tue, 2009-04-28 at 13:39 -0400, Marc R. O'Connor wrote:
>> I have had two 'kernel bug' issues today both referencing file-item.c.
>> The first oops happened when i was cp'ing from and external HD(ext3)
Chris Mason wrote:
> On Tue, 2009-04-28 at 13:39 -0400, Marc R. O'Connor wrote:
>> I have had two 'kernel bug' issues today both referencing file-item.c.
>> The first oops happened when i was cp'ing from and external HD(ext3) to
>> and ext3 partition. The second happened during boot up. I have at
On Tue, 2009-04-28 at 13:39 -0400, Marc R. O'Connor wrote:
> I have had two 'kernel bug' issues today both referencing file-item.c.
> The first oops happened when i was cp'ing from and external HD(ext3) to
> and ext3 partition. The second happened during boot up. I have attached
> them both.
>
> I
16 matches
Mail list logo
