All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bernd Schubert <bernd-schubert@web.de>
To: Oleg Drokin <green@namesys.com>
Cc: reiserfs-list@namesys.com
Subject: Re: filesystem corruption ?
Date: Fri, 21 Mar 2003 14:01:38 +0100	[thread overview]
Message-ID: <200303211401.38329.bernd-schubert@web.de> (raw)
In-Reply-To: <20030321103230.C12315@namesys.com>

Hi,

> So, the beam of X-rays run through the memory module corrupting some bits?
> ;) This stuff should not have been written to disk, so probably
> plain reboot should fix everything? Can you test that?
>

indeed after rebooting everything is fine again. We will run another memtest86 
during the weekend, though I really don't believe we will find a problem.

Though this machine will be replaced by a real server in a few month, I'm 
still rather worried what happend. Even if its 'only' a hardware memory 
problem this means lots of trouble for us -- on the one hand it seems not to 
be memtest86 detectable and on the other hand our programs really do need 
working memory, but of course this is not of your concern.


Thanks for your help,
	Bernd

  parent reply	other threads:[~2003-03-21 13:01 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-03-20 16:25 filesystem corruption ? Bernd Schubert
2003-03-20 17:06 ` Oleg Drokin
2003-03-20 18:23   ` Bernd Schubert
2003-03-21  7:32     ` Oleg Drokin
2003-03-21 10:14       ` Bernd Schubert
2003-03-21 13:01       ` Bernd Schubert [this message]
2003-03-21 13:07         ` Oleg Drokin
2003-03-21 13:20           ` Bernd Schubert
2003-03-21 16:00           ` Russell Coker
2003-03-21 17:14             ` Valdis.Kletnieks
2003-03-22 18:18         ` Bernd Schubert
2003-03-22 18:37           ` Anders Widman
2018-10-22 20:02 Filesystem corruption? Gervais, Francois
2018-10-22 23:12 ` Qu Wenruo
2018-10-23  9:25 ` Juergen Sauer

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=200303211401.38329.bernd-schubert@web.de \
    --to=bernd-schubert@web.de \
    --cc=green@namesys.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.