All of lore.kernel.org
 help / color / mirror / Atom feed
From: jeff leads <jleads@yahoo.com>
To: Oleg Drokin <green@namesys.com>
Cc: reiserfs-list@namesys.com
Subject: Re: File Corruption
Date: Tue, 1 Oct 2002 21:07:34 -0700 (PDT)	[thread overview]
Message-ID: <20021002040734.30121.qmail@web10501.mail.yahoo.com> (raw)
In-Reply-To: <20021001101050.A5833@namesys.com>

Hi!  Below is the abbreviated version of my output
from --check.  Is it safe to run --fix-fixable?
 What do the bad nlink numbers mean?  Should I be
concerned about the dirty buffers?

Thanks again in advance!

Jeff 

], SD has bad nlink number
/  4 (of 143)bad_stat_data: block 46863, [124457 36663
0x0 SD (0)], SD has bad n
link number
/  5 (of 143)bad_stat_data: block 44550, [124457
101732 0x0 SD (0)], SD has bad
nlink number
bad_stat_data: block 44550, [124457 114743 0x0 SD
(0)], SD has bad nlink number
bad_stat_data: block 44550, [124457 124458 0x0 SD
(0)], SD has bad nlink number
bad_stat_data: block 44550, [124457 124469 0x0 SD
(0)], SD has bad nlink number
/  6 (of 143)bad_stat_data: block 63760, [124457
151128 0x0 SD (0)], SD has bad
nlink number
/125 (of 160)/ 32 (of 163)bad_stat_data: block 47631,
[143160 155080 0x0 SD (0)]
, SD has bad nlink number
bad_stat_data: block 47631, [143160 155192 0x0 SD
(0)], SD has bad nlink number
ok
Comparing bitmaps..ok
Checking Semantic tree...
/tmp/recover.2.30031file 9 106855 has wrong sd_size
56377344, has to be 60522496
file 9 106855 has wrong sd_blocks 0, has to be 118208
ok
There were found 102 corruptions which can be fixed
with --fix-fixable
check_and_free_buffer_mem: dirty buffer (3 16) found
###########
reiserfsck finished at Tue Oct  1 19:32:45 2002
--- Oleg Drokin <green@namesys.com> wrote:
> Hello!
> 
> On Mon, Sep 30, 2002 at 12:52:27PM -0700, jeff leads
> wrote:
> > Ok, I'm running RedHat 7.1, gcc 2.96-85, kernel
> > 2.4.9-21 (redhat's version) and ReiserFSProgs
> 3.6.3 (
> 
> I do not know what is included into 2.4.9-21, but
> can you upgrade to
> 2.4.18-10 (I think this is latest RedHat errata
> kernel for 7.x series of
> their distro).
> 
> > I'm starting to get file corruption here and
> there. 
> > My next question is, where do I go from here? 
> What
> 
> You need to upgrade kernel to something that
> includes all of our fixes at least
> up to 2.4.18.
> 
> > can I do to rectify this issue?  Do I run a
> rebuild at
> > this point?  What caused this?  
> 
> This is hard to tell what have caused this.
> Can you please send us reiserfsck output from the
> same partition,
> but take reiserfsck from ReiserFSProgs 3.6.3?
> 
> > Sep 30 14:03:11 goku kernel: is_tree_node: node
> level
> > 64680 does not match to the expected one 1
> 
> This is on disk metadata corruption, but the reason
> is unknown
> 
> > [root@goku /root]# reiserfsck /dev/ida/c0d0p5
> > <-------------reiserfsck, 2001------------->
> > reiserfsprogs 3.x.0j
> 
> This is too old to be used today.
> 
> Bye, 
>     Oleg 


__________________________________________________
Do you Yahoo!?
New DSL Internet Access from SBC & Yahoo!
http://sbc.yahoo.com

  reply	other threads:[~2002-10-02  4:07 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-09-30 19:52 File Corruption jeff leads
2002-10-01  6:10 ` Oleg Drokin
2002-10-02  4:07   ` jeff leads [this message]
2002-10-02  6:30     ` Oleg Drokin
     [not found] <19990622032859.B6955@thepuffingroup.com>
     [not found] ` <19990622152145.A1059@uni-koblenz.de>
1999-06-22 23:49   ` File corruption Ulf Carlsson
1999-06-24 22:28     ` Ralf Baechle
1999-06-25 13:31       ` Ulf Carlsson
1999-06-25 18:08         ` Thomas Bogendoerfer
1999-06-25 14:34       ` Andrew Linfoot
1999-06-25 14:34         ` Andrew Linfoot
1999-06-25 16:59         ` Ulf Carlsson
1999-06-25 17:11           ` Andrew Linfoot
1999-06-25 17:11             ` Andrew Linfoot
1999-06-28 10:39             ` Ralf Baechle
1999-06-28  9:34         ` Ralf Baechle

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=20021002040734.30121.qmail@web10501.mail.yahoo.com \
    --to=jleads@yahoo.com \
    --cc=green@namesys.com \
    --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.