From: Alain Knaff <alain@knaff.lu>
To: vitaly@namesys.com
Cc: reiserfs-list@namesys.com
Subject: Re: fatal "not directory found" error at pass 3a of reiserfsck
Date: Tue, 14 Mar 2006 20:35:59 +0100 [thread overview]
Message-ID: <44171B1F.5070809@knaff.lu> (raw)
In-Reply-To: <200603142220.39344.vitaly@namesys.com>
Vitaly Fertman wrote:
> Hi Alain,
>
> the fixed reiserfsprogs version is attched, it contains
> some bugfixes, please run it and report about the result.
>
> Thank you.
Actually, the problem happened with reiserfs-3.6.18-5 (as shipped by
SuSE 9.3. and 10.0.).
Later, I downloaded 3.6.19 from namesys, and that one already
successfully restored the disk (but due to size and slowness of our
hardware this took several hours and terminated just now a quarter of an
hour ago).
Now, we'll first do a backup (yeah, we learned that lesson!), and after
that I'll re-run your 3.6.20 and report back (will probably take until
next morning, though)
Thanks,
Alain
next prev parent reply other threads:[~2006-03-14 19:35 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-14 15:51 fatal "not directory found" error at pass 3a of reiserfsck Alain Knaff
2006-03-14 19:18 ` Vitaly Fertman
[not found] ` <200603142220.39344.vitaly@namesys.com>
2006-03-14 19:35 ` Alain Knaff [this message]
2006-03-14 19:39 ` Vitaly Fertman
2006-03-15 14:11 ` Alain Knaff
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=44171B1F.5070809@knaff.lu \
--to=alain@knaff.lu \
--cc=reiserfs-list@namesys.com \
--cc=vitaly@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.