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 <reiserfs-list@namesys.com>
Subject: Re: fs errors on thinkpad R31
Date: Sun, 10 Nov 2002 15:55:51 +0100	[thread overview]
Message-ID: <200211101555.52164.bernd-schubert@web.de> (raw)
In-Reply-To: <20030110173246.A10156@namesys.com>

On Friday 10 January 2003 15:32, Oleg Drokin wrote:
> Hello!
>
> On Thu, Jan 09, 2003 at 11:20:48PM +0100, Bernd Schubert wrote:
> > this is the second time within 14 days after which I had to run
> > reiserfsck on my IBM Thinkpad R31.
> > This time I lost a directory with 49 files (it seems it were only kernel
> > modules, so probably not so important data).
> > I have attached the error messages from the /var/log/messages file.
>
> Hm. Looks like some blocks have unexpected contents.
> Do you often uncleanly turn-off/run out of battaries prior to
> corruption?
> Try to disable write caching in your harddrive then. (hdparm -W0 /dev/hda)
>

Hello Oleg,

thanks for your help. When I had to run reiserfsck for the very first time, I 
thought this as well, since there where some unexpected crashes in December 
and I run one day before the first fsck out of batteries. But ever since this 
fsck, nothing like this happend again (I found the reason for the crashes and 
never needed to run on accu since this time).

Should I enable reiserfs-debugging within the kernel configuration ? Any other 
possibilities to debug this ? 

Thanks,
	Bernd


  reply	other threads:[~2002-11-10 14:55 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-01-09 22:20 fs errors on thinkpad R31 Bernd Schubert
2003-01-10 14:32 ` Oleg Drokin
2002-11-10 14:55   ` Bernd Schubert [this message]
2003-01-10 15:07     ` Oleg Drokin

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=200211101555.52164.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.