mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Oleg Drokin <green@linuxhacker.ru>
To: linux-kernel@vger.kernel.org, nettings@folkwang-hochschule.de
Subject: Re: severe FS corruption w/ reiserfs and 2.5.72-bk3
Date: Sun, 22 Jun 2003 00:21:16 +0400	[thread overview]
Message-ID: <200306212021.h5LKLGdv004822@car.linuxhacker.ru> (raw)
In-Reply-To: <3EF4C0CC.6090100@folkwang-hochschule.de>

Joern Nettingsmeier <nettings@folkwang-hochschule.de> 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.

JN> unfortunately i did a number of things at once: upgrade the kernel from 
JN> .72 (which has worked for me quite well), add an ide drive (i didn't 
JN> have ide in my kernel before, and geez! is that module code broken :)) 
JN> and shuffle partitions around. which makes the problem hard to pinpoint.

Not sure what bk3 is for, I have yesterday's bk snapshot and it works for me,
I seem to be unable to reach bkbits.net for today.

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?

Bye,
    Oleg

  reply	other threads:[~2003-06-21 20:09 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-06-21 20:32 Joern Nettingsmeier
2003-06-21 20:21 ` Oleg Drokin [this message]
2003-06-21 22:36   ` Joern Nettingsmeier
2003-06-22  8:03     ` 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=200306212021.h5LKLGdv004822@car.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

all inboxes | Powered by JetHome®