From: David Greaves <david@dgreaves.com>
To: "Burnes, James" <james.burnes@gwl.com>
Cc: bernd-schubert@web.de, reiserfs-list@namesys.com
Subject: Re: support for Reiserfs 3.6 failed on ~1Tb lvm2 lv on 2.6.6?
Date: Tue, 08 Jun 2004 21:55:19 +0100 [thread overview]
Message-ID: <40C627B7.9000803@dgreaves.com> (raw)
In-Reply-To: <3DF9165145FACB4C96977FF650C1E9040C46A03F@its-mail1.its.corp.gwl.com>
Thanks - I'll try both :)
I'm talking to namesys too.
I am wondering if the resync corrupted the data.
I'm pretty happy that I didn't do anything 'wrong' - something is either
broken in hw (mem) or buggy.
David
Burnes, James wrote:
>Rather than running memtest86 for two days you might find it easier to
>simply re-seat your memory modules and try again.
>
>If that doesn't fix it, then run memtest.
>
>
>
>jim burnes
>security engineer
>great-west, denver
>
>
>
>
>>-----Original Message-----
>>From: bernd-schubert@web.de [mailto:bernd-schubert@web.de]
>>Sent: Tuesday, June 08, 2004 1:18 PM
>>To: reiserfs-list@namesys.com
>>Cc: David Greaves
>>Subject: Re: support for Reiserfs 3.6 failed on ~1Tb lvm2 lv on 2.6.6?
>>
>>Did you already run memtest86 for at least a couple of ours, but
>>
>>
>better
>
>
>>several days (all tests have to be enabled)? I also had problems like
>>
>>
>this
>
>
>>several times and usually it simply had been memory problems. On my
>>notebook
>>even the shared memory graphics card could cause this...
>>
>>Cheers,
>> Bernd
>>
>
>
>
>
next prev parent reply other threads:[~2004-06-08 20:55 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-08 19:45 support for Reiserfs 3.6 failed on ~1Tb lvm2 lv on 2.6.6? Burnes, James
2004-06-08 20:55 ` David Greaves [this message]
2004-06-08 21:33 ` Bernd Schubert
2004-06-08 21:38 ` daniel.poelzleithner
-- strict thread matches above, loose matches on Subject: below --
2004-06-08 16:08 David Greaves
2004-06-08 19:18 ` Bernd Schubert
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=40C627B7.9000803@dgreaves.com \
--to=david@dgreaves.com \
--cc=bernd-schubert@web.de \
--cc=james.burnes@gwl.com \
--cc=reiserfs-list@namesys.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 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.