All of lore.kernel.org
 help / color / mirror / Atom feed
From: Chris Mason <mason@suse.com>
To: Jens Benecke <jens@spamfreemail.de>
Cc: reiserfs-list@namesys.com
Subject: Re: Errors requiring --rebuild-tree in 2.4.23
Date: Thu, 11 Dec 2003 13:24:41 -0500	[thread overview]
Message-ID: <1071167080.10849.127.camel@tiny.suse.com> (raw)
In-Reply-To: <bra6s2$9ug$1@sea.gmane.org>

On Thu, 2003-12-11 at 11:43, Jens Benecke wrote:
> Chris Mason wrote:
> 
> > On Thu, 2003-12-11 at 08:51, Jens Benecke wrote:
> >> Hi,
> >> 
> >> I posted earlier about quota problems. WE updated to 2.4.23 b ecause of
> >> the logging patches because some power failures made our /home partition
> >> spew out these: (QUESTIONS at the end of the mail)
> > 
> > Sorry, before we got to the questions, what was the order of the events
> > above?
> 
> Oops. I guess I was a bit too confused myself. :)
> 
> 1. Errors on /home in syslog, cron jobs running wild with i/o failures
>      system kept running for a couple days because nobody was there 
>      to fix it, though
>      Those errors were probably caused by power outages and 
>      a non-data-logging ReiserFS kernel.
> 2. Backup what's left of /home to firewire harddisk.
> 3. Update to 2.4.23 with Chris' patches for data logging/quota
> 4. Repartition hda2..4 (was needed anyway for drbd), 
>      reformat new /home (drbd), restore /home on drbd device
> 5. crash of the server overnight, reboot (don't know why yet)

Ok, we need to better understand step 5 here.

> 6. couldn't reboot because root partition was totally b0rken
> 7. reiserfsck --rebuild-tree under Knoppix, killed a couple files
> 8. still running Knoppix, secondary server took over and is running now
> 
> btw: Is there a "reiserfs stress test" kind of thing to make sure a
> configuration works before sending it two time zones away for production? I
> plan on doing that in the next couple weeks. =;)
> Would bonnie++ accomplish this or are there better tests?

The best test is whatever that environment is going to use in
production.  I've got a ton of different scripts that get used based on
different situations, most are ugly hacks.

-chris



  reply	other threads:[~2003-12-11 18:24 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-12-11 13:51 Errors requiring --rebuild-tree in 2.4.23 Jens Benecke
2003-12-11 14:22 ` Chris Mason
2003-12-11 16:43   ` Jens Benecke
2003-12-11 18:24     ` Chris Mason [this message]
2003-12-11 19:20     ` Hans Reiser
2003-12-13 17:38       ` Jens Benecke
2003-12-14 12:05         ` Hans Reiser
2003-12-11 16:45   ` Jens Benecke
2003-12-11 17:27 ` Vitaly Fertman

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=1071167080.10849.127.camel@tiny.suse.com \
    --to=mason@suse.com \
    --cc=jens@spamfreemail.de \
    --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.