public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Oleg Drokin <green@linuxhacker.ru>
To: Joern Nettingsmeier <nettings@folkwang-hochschule.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: severe FS corruption w/ reiserfs and 2.5.72-bk3
Date: Sun, 22 Jun 2003 12:03:01 +0400	[thread overview]
Message-ID: <20030622080301.GA17062@linuxhacker.ru> (raw)
In-Reply-To: <3EF4DDF1.2010101@folkwang-hochschule.de>

Hello!

On Sun, Jun 22, 2003 at 12:36:33AM +0200, Joern Nettingsmeier wrote:

> >JN> i just completely and utterly trashed my filesystems with 2.5.72-bk2 
> >and JN> reiserfs. there are metric shitloads of errors on journal replay 
> >and i JN> end up in repair mode. did a couple of --rebuild-tree's, but new 
> >errors JN> cropped up after every reboot.
> >JN> happens both on scsi and ide drives and ate almost all of my machine...
> >Hm. Can I ask for your kernel config, and kernel logs (if possible),
> >reiserfsck /dev/device -l /somewhere/device.log , and send those logs to
> >me too.
> sorry, i can't really get anything in and out of that box.
> i've been able to extract some parts of the fsck log, they look like this:
> vpf-10680: The file [2406 26400] has the wrong block count in the 
> (8), should be (1)

These are not looking dangerous, probably some symlinks created long ago.
(we changed block accounting for symlinks some time ago).

> it tells me it can fix it with the --fixable option, done that a couple 
> of times, new errors after that.

You mean new errors of the same kind?

> it's an smp box with 2 p3s, intel bx chipset, aic7xxx scsi, ide and scsi 
> compiled into the kernel, reiserfs too. tagged queuing enabled, ignore 

Well, TQ was broken on IDE some time ago, but then Jens Axboe said he
fixed that, anyway that does not explain why all the disks got eaten.

> >JN> if anyone wants me to do some forensics on the machine, speak up. 
> >JN> otherwise i'll swipe it clean and start over from scratch.
> >I wonder if you can create clean fs, copy some stuff there with 2.5.72-mm2
> >and see what happens?
> /var is totally FUBAR, the system won't boot into my fallback kernel. i 
> don't have a second machine around to compile another kernel on... sorry.

Sigh.

> i might be able to put the ide disk into another box tomorrow and try 
> another reiserfsck with proper logging, but i have no place to check the 
> scsi disks. i'll keep you posted when i get it done.

Ok, perhaps you can put some kind of rescue system on that IDE disk,
and try to boot it in original box?

Bye,
    Oleg

      reply	other threads:[~2003-06-22  7:50 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-06-21 20:32 severe FS corruption w/ reiserfs and 2.5.72-bk3 Joern Nettingsmeier
2003-06-21 20:21 ` Oleg Drokin
2003-06-21 22:36   ` Joern Nettingsmeier
2003-06-22  8:03     ` Oleg Drokin [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=20030622080301.GA17062@linuxhacker.ru \
    --to=green@linuxhacker.ru \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nettings@folkwang-hochschule.de \
    /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