All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jean Jordaan <jean@upfrontsystems.co.za>
To: reiserfs-list@namesys.com
Subject: Re: reiserfs corruption: --rebuild-tree bug report
Date: Tue, 20 Jan 2004 17:14:20 +0200	[thread overview]
Message-ID: <400D45CC.4070004@upfrontsystems.co.za> (raw)
In-Reply-To: <200401201603.11653.bernd-schubert@web.de>

> You didn't mention that you used the wrong commands 

OK, OK, I'm on a solid diet of crow for the next two weeks!

Still, the initial error that downed the box showed reiserfs
complaining about an inode, and the Seagate disk diagnostics
showed no hardware failure. I might not have been as good to
my filesystem as I should have been while recovering, but the
event that started this saga was the box failing to come up
because of a corrupt reiserfs.

We're running reiserfs on all our desktops here, and on many
servers at clients, and have never experienced the same thing
before.

-- 
Jean Jordaan
http://www.upfrontsystems.co.za


      reply	other threads:[~2004-01-20 15:14 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-01-20 14:11 reiserfs corruption: --rebuild-tree bug report Jean Jordaan
2004-01-20 15:03 ` Bernd Schubert
2004-01-20 15:14   ` Jean Jordaan [this message]

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=400D45CC.4070004@upfrontsystems.co.za \
    --to=jean@upfrontsystems.co.za \
    --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.