From: Dan Nilsson <zyrax@home.se>
To: sander@humilis.net
Cc: reiserfs-list@namesys.com
Subject: Re: Reoccuring corruption problem
Date: Sat, 21 Aug 2004 07:43:41 +0200 [thread overview]
Message-ID: <200408210743.41317.zyrax@home.se> (raw)
In-Reply-To: <20040819194222.GC29745@favonius>
> Sounds like bad memory nevertheless. Can you try memtest86 for at least
> 24 hours?
Yes,
I put the computer running memtest86 after getting your email and it did in
fact pass all tests (after ~24hrs i aborted the test).
I have fairly recently upgraded the computer by adding a memory module which i
suspected would show up the errors (if any).
After running the test I fsck:ed to remove the corruptions, then proceeded by
removed my /usr/portage tree (where corruptions seem to easily occur) and
reinstalled all the files (with rsync). The same type of corruption occured
but now to a different directory than "usual".
I have absolutely no idea what causes it. Nothing shows up in syslog and there
doesn't seem to be any problems with the hard drive (which, by the way is a
2Gb drive with the corruptions occuring on a 1.6 Gb partition).
Thanks,
Dan Nilsson
next prev parent reply other threads:[~2004-08-21 5:43 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-19 18:46 Reoccuring corruption problem Dan Nilsson
2004-08-19 19:42 ` Sander
2004-08-21 5:43 ` Dan Nilsson [this message]
2004-08-21 7:59 ` mjt
2004-08-21 8:16 ` Sander
2004-08-24 8:21 ` Dan Nilsson
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=200408210743.41317.zyrax@home.se \
--to=zyrax@home.se \
--cc=reiserfs-list@namesys.com \
--cc=sander@humilis.net \
/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.