From: Chris Mason <mason@suse.com>
To: spam@perlpimp.com, linux-kernel@vger.kernel.org
Subject: Re: reiserfs autofix?
Date: Mon, 30 Apr 2001 08:02:50 -0400 [thread overview]
Message-ID: <738200000.988632170@tiny> (raw)
In-Reply-To: <20010430000704.A2313@vancouver.yi.org>
On Monday, April 30, 2001 12:07:04 AM -0700 putter <spam@perlpimp.com>
wrote:
> I think I have tracked down the problem to the card itself. My machine is
> on @ graphics mode all the time, like 24hrs a day, and it seems that it
> is somewhat taxing on the cards performance. So now I switch down to text
> mode, everytime I leave the machine. How did I find out? I placed my
> finger of heatsink of my GeForce DDR. It was HOT! Fan works alright, so
> if I was to run computer a while, stress accumilates, and when I run
> GeForce understress of maximum resolutions, it craps out. So much for
> NVidia eh?
Do a search through the kernel arcvhies for nvidia. The crashes could just
be the driver. But heat is always a problem, add fans ;-)
>
> BTW, I don't question graphical subsystem crashes. I question reiserfs
> that suppose to leave my partitions in consistent state, no matter how
> trigger happy with power switch I am, or is my judgement is clouded? >=)
After a crash, reiserfs only cleans up after itself. If someone else went
in and hosed the metadata (nvidia, bad drive, controller, ide fun with
via), you've still got bad blocks.
This is one possible reason that we've seen more reports than ext2 has.
After a crash, ext2fsck fixes _whatever_ was broken. log replay in
reiserfs only fixes the operations that were in progress when the system
crashed.
Anyway, those messages show that you've got metadata corruption. grab the
latest reiserfsprogs from ftp.reiserfs.org and run reiserfsck -x (after
backing things up).
-chris
next prev parent reply other threads:[~2001-04-30 12:03 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-04-29 21:48 reiserfs autofix? putter
2001-04-29 22:55 ` Chris Mason
2001-04-30 7:07 ` putter
2001-04-30 12:02 ` Chris Mason [this message]
2001-04-30 17:09 ` Alan Cox
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=738200000.988632170@tiny \
--to=mason@suse.com \
--cc=linux-kernel@vger.kernel.org \
--cc=spam@perlpimp.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox