All of lore.kernel.org
 help / color / mirror / Atom feed
From: Nick Vahalik <nick@nsanity.com>
To: Vladimir Saveliev <vs@namesys.com>
Cc: reiserfs-list@namesys.com
Subject: Re: Reiserfs Data Recovery
Date: Wed, 10 Mar 2004 10:54:24 -0600	[thread overview]
Message-ID: <404F4840.5090407@nsanity.com> (raw)
In-Reply-To: <1078932372.9476.133.camel@tribesman.namesys.com>

Vladimir Saveliev wrote:

>Are you using reiserfsck from
>ftp://ftp.namesys.com/pub/reiserfsprogs/reiserfsprogs-3.6.13.tar.gz?
>
>If yes - please run
>debugreiserfs -p /dev/problemdevice | bzip2 -c > problemdevice.bz2
>and make problemdevice.bz2 available for downloading.
>
>It should allow us to fix reiserfsck bug.
>
>If you are using older rieserfsck (reiserfsck -V), please try with the
>one of
>ftp://ftp.namesys.com/pub/reiserfsprogs/reiserfsprogs-3.6.13.tar.gz
>  
>
root@bardiel:~/reiserdata# debugreiserfs -V
debugreiserfs 3.6.13 (2003 www.namesys.com)

root@bardiel:~/reiserdata# debugreiserfs -p /dev/sda1 | bzip2 -c > 
devsda1.bz2
debugreiserfs 3.6.13 (2003 www.namesys.com)
 
Loading on-disk bitmap .. 38677079 bits set - done
super block..ok
bitmaps..(1228).. ok
journal (from 18 to 8210)..ok
Super block, bitmaps, journal - 9422 blocks - done, 38667657 blocks left
0%....20%....40%....60%....80%....100%                       left 0, 
15211 /sec
Packed 66463 blocks:
        compessed 63534
        full blocks 2929
                leaves with broken block head 55
                corrupted leaves 83
                internals 672
                descriptors 0
data packed with ratio 0.09

The meta-data info can be downloaded at 
http://24.162.126.168:8080/devsda1.bz2
~5.3 MB

Thanks

Nick Vahalik


  reply	other threads:[~2004-03-10 16:54 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-03-10  3:07 Reiserfs Data Recovery Nick Vahalik
2004-03-10 11:41 ` Vladimir Saveliev
2004-03-10 15:08   ` Nick Vahalik
2004-03-10 15:26     ` Vladimir Saveliev
2004-03-10 16:54       ` Nick Vahalik [this message]
     [not found]         ` <200403111419.31982.vitaly@namesys.com>
2004-03-11 15:48           ` Nick Vahalik
2004-03-13  9:44   ` Stewart Smith
     [not found] ` <200403111936.01548.vitaly@namesys.com>
     [not found]   ` <40509A74.6080703@nsanity.com>
     [not found]     ` <200403130001.57937.vitaly@namesys.com>
2004-03-15 15:48       ` Reiserfs Data Recovery (SOLVED) Nick Vahalik
2004-03-15 16:32         ` Vitaly Fertman
  -- strict thread matches above, loose matches on Subject: below --
2004-03-08 14:22 Reiserfs Data Recovery Nick Vahalik
2004-03-08 14:33 ` Philippe Gramoullé
2004-03-08 14:43   ` Nick Vahalik
2004-03-08 14:59     ` Philippe Gramoullé
2004-03-08 16:06       ` Nick Vahalik
2004-03-09  9:28         ` Vitaly Fertman
2004-03-08 18:41 ` Ryan Underwood
     [not found]   ` <404CC8AA.9020405@nsanity.com>
2004-03-08 21:59     ` Ryan Underwood
     [not found]       ` <404CF46B.10000@nsanity.com>
2004-03-09  1:13         ` Ryan Underwood
2004-03-09 21:24           ` Nick Vahalik
2004-03-09 11:36       ` Hans Reiser
2004-03-09 14:42         ` Nick Vahalik
2004-03-09 15:45           ` Hans Reiser
2004-03-09 16:28             ` Nick Vahalik
2004-03-09 18:08             ` Ryan Underwood
     [not found] <20030727153826-191600041>
2003-07-27 23:22 ` reiserfs data recovery Manuel Krause
     [not found] ` <20030727162537-184400041>
2003-07-28  1:27   ` D. Sen
2003-07-28  1:27     ` D. Sen
2003-07-27 22:38 D. Sen
2003-07-27 22:38 ` D. Sen

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=404F4840.5090407@nsanity.com \
    --to=nick@nsanity.com \
    --cc=reiserfs-list@namesys.com \
    --cc=vs@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.