From: Thomas Raschbacher <lordvan@lordvan.com>
To: Reiserfs List <reiserfs-list@namesys.com>
Subject: [Fwd: Re: Reiserfsck can't fix FS]
Date: Fri, 14 Oct 2005 23:26:46 +0100 [thread overview]
Message-ID: <1129328806.6906.5.camel@desktop> (raw)
[-- Attachment #1: Type: text/plain, Size: 2549 bytes --]
forgot to CC the list. sorry
-------- Forwarded Message --------
From: Thomas Raschbacher <lordvan@lordvan.com>
To: Vitaly Fertman <vitaly@namesys.com>
Subject: Re: Reiserfsck can't fix FS
Date: Fri, 14 Oct 2005 20:32:09 +0100
Hi!
The check on the image worked out fine.
I didn't see a failed block read so far. I'll maybe try to dd
if=/dev/... of=/dev/null tomorrow to see if there are failed block
reads .. but if not .. any idea what else it could be? (or at least how
to fix it?)
Thanks
On Fri, 2005-10-14 at 20:08 +0400, Vitaly Fertman wrote:
> Hello Thomas!
>
> On Friday 14 October 2005 19:21, Thomas Raschbacher wrote:
> > Hi,
> >
> > I had to run reiserfsck on my usb hdd because there were some problems.
> > It told me to rebuild the tree (because I couldn't mount it I coudlnt'
> > backup things and I didn't have enough space (50GB) spare for a disk
> > image).
> >
> > attached my logfiles and (where i remembered to save it the stdout
> > output)
> >
> > It alwasy aborts at the same place.
> >
> > (i did the same for another partition and there after running reiserfsck
> > --rebuild-tree about 10 times it worked out ok but this one seems to be
> > a problem ..)
> >
> > reiserfsck 3.6.19 (2003 www.namesys.com)
> > Linux version 2.6.12-gentoo-r6 (root@desktop) (gcc version
> > 3.4.3-20050110 (Gentoo 3.4.3.20050110-r2, ssp-3.4.3.20050110-0,
> > pie-8.7.7)) #1 Thu Jul 21 20:21:20 BST 2005
> > (i can provide kernel config file if needed)
> >
> > Please let me know if ther'es anything I can do as there's quite a bit
> > of data on that drive.
>
> it is possible to check how reiserfsck works, you can extract
> the fs metadata and fsck them on another compter. this does
> not require you to have 50M as there are not real data:
> debugreiserfs -p /dev/discs/disc2/part6 | bzip2 -c > part6.bz2
> go to another computer:
> touch part6.image
> bunzip2 -c part6.bz2 | debugreiserfs -u part6.image
> reiserfsck --rebuild-tree part6.image -l logfile
>
> if it finishes successfully, the problem is in your hardware.
> As the same block number repeats and there is also a failed
> block read, the problem is likely to be IO related.
>
> it fsck fails on your metadata, I would like to have a look
> at part6.bz2.
>
--
-----BEGIN GEEK CODE BLOCK-----
GCS/CC/E/M/MU/S d- s: a--- C++++(++) UL++++ P+ L++++ E W+++ N+++ o-- K
w-- O
M-- V- PS+ PE-- Y++ PGP+++ t+++ 5+ X- R tv b++++ DI- D+ G++ e-->+++++
h-- !r
z-
------END GEEK CODE BLOCK------
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
reply other threads:[~2005-10-14 22:26 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1129328806.6906.5.camel@desktop \
--to=lordvan@lordvan.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.