public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Diego Calleja <grundig@teleline.es>
To: linux-kernel@vger.kernel.org
Cc: green@namesys.com, reiserfs-list@namesys.com
Subject: Re: Reiserfs corruption on 2.4.17-rc1!
Date: Thu, 20 Dec 2001 01:20:46 +0100	[thread overview]
Message-ID: <20011220012046.A1866@diego> (raw)
In-Reply-To: <20011217025856.A1649@diego> <13425.1008580831@nova.botz.org> <20011218003359.A555@diego> <20011218125852.A1159@namesys.com> <20011218224848.C377@diego> <20011219095303.A11409@namesys.com>
In-Reply-To: <20011219095303.A11409@namesys.com>; from green@namesys.com on Wed, Dec 19, 2001 at 07:53:03 +0100

On Wed, 19 Dec 2001 07:53:03 Oleg Drokin wrote:
> Hello!
> 
> So why didn't you run reiserfsck --rebuild-tree then?
I've done it, under 2.4.17-rc2, It seems it's solved (although I can't know
what happened). reiserfsck -l -->

####### Pass 0 #######
"r5" got 142629 hits
####### Pass 1 #######
####### Pass 2 #######
####### Pass 3 #########
name "rpc" in directory 2 4160 points to nowhere 4160 68722 - removed
name "mtab" in directory 2 4160 points to nowhere 4160 68669 - removed
name "t1lib" in directory 2 4160 points to nowhere 4160 64508 - removed
name "hotplug" in directory 2 4160 points to nowhere 4160 63049 - removed
name "serial.conf" in directory 2 4160 points to nowhere 4160 68673 -
removed
name "sprucesig" in directory 2 4160 points to nowhere 4160 68377 - removed
dir 2 4160 has wrong sd_size 5792, has to be 5632
dir 1 2 has wrong sd_size 480, has to be 512
####### Pass 3a (lost+found pass) #########


Version 3.x.0K-pre13 (the last I found)
It seems all is working correctly). I'll try to reproduce the bug, althouh
I think it's no possible

Diego Calleja
> 
> Bye,
>     Oleg
> 



  parent reply	other threads:[~2001-12-20  0:18 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-12-16 17:48 Reiserfs corruption on 2.4.17-rc1! Diego Calleja
2001-12-16 17:57 ` Diego Calleja
2001-12-16 20:12 ` Ragnar Kjørstad
2001-12-17  1:58   ` Diego Calleja
2001-12-17 21:01     ` Sakari Ailus
     [not found]     ` <13425.1008580831@nova.botz.org>
2001-12-17 23:33       ` Diego Calleja
2001-12-18  5:01         ` Ross Vandegrift
2001-12-18  6:19           ` Jurgen Botz
2001-12-18 21:45           ` Diego Calleja
     [not found]         ` <15391.12150.650359.33792@laputa.namesys.com>
     [not found]           ` <20011218220828.A381@diego>
2001-12-18 21:11             ` [grundig@teleline.es: Re: Reiserfs corruption on 2.4.17-rc1!] Diego Calleja
2001-12-19  9:18               ` Nikita Danilov
     [not found]           ` <3C1F3FDA.5050601@namesys.com>
2001-12-18 21:35             ` [reiserfs-list] Re: Reiserfs corruption on 2.4.17-rc1! Diego Calleja
     [not found]         ` <20011218125852.A1159@namesys.com>
     [not found]           ` <20011218224848.C377@diego>
     [not found]             ` <20011219095303.A11409@namesys.com>
2001-12-20  0:20               ` Diego Calleja [this message]
     [not found] <20011217002350.D418@diego>
2001-12-17  1:45 ` Diego Calleja
2001-12-19 16:56   ` Edward Muller
2001-12-19 22:17     ` Diego Calleja

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=20011220012046.A1866@diego \
    --to=grundig@teleline.es \
    --cc=green@namesys.com \
    --cc=linux-kernel@vger.kernel.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox