From: "Philipp Gühring" <p.guehring@futureware.at>
To: reiserfs-list@namesys.com
Subject: Re: A couple of questions
Date: Fri, 17 May 2002 02:45:19 +0200 [thread overview]
Message-ID: <200205170048.g4H0mI402129@linux1.futureware.at> (raw)
In-Reply-To: <3CE4476E.8070101@namesys.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Dear Hans,
> I am a filesystems developer, and I don't know enough to do more than
> press y with most fscks.
There is one case, in which I know that I have to say no: If the partition
that a fsck tries to correct has a different type than the fsck thinks.
(Running e2fsck against a reiserfs partition for example)
And those things happens when someone changes harddisks, ...
> I think that for the most part, if one is
> going to ask the user to help, one needs to provide a real interface, a
> filesystem structure editor.....
Well, debugfs (ext2) was an approach into that direction, isn't it?
Now I stumbled across debugreiserfs, but it lacks interactive mode.
> which no FS has ever done.... but
> right now we need to get what we have debugged thoroughly. It is on the
> list of things I would like to add someday.
What I would like to see is a tool to do the following:
(And I don't think that I will find a sponsor for that tool :-(
After a crash, I make a dd from the crashed partition, into a normal file in
another partition, that's perhaps on a differnt harddisk.
Then I want to run a dumping utility, that tries to restore every bit that
still can be found in the crashed partition, and tries to resemble all the
files in it, and even creating a lost&found directory ...
That dumping utility should take an output directory as argument, in which it
recreates the contents.
Something like "The Coroners Kit", but more for recovery than for
investigation.
What is important for that tool:
* It must not crash under any circumstances. Even if every bit of the
filesystem is currupted, it has to do its work, and try to recover as much as
possible.
* It has to assume that every bit of the filesystem can be corrupt, so it has
to try to semantically verify the bits, pointers, ...
* It should try different ways to restore access to lost data, if it stumbles
across problems in the filesystems.
* There must not be any assertions that would not allow the tool to run over
the whole partiton, and search everywhere for lost data
* It has to be designed to work on files which are dumps from partition based
filesystems.
* It should be able to detect and correct common hardware or crash related
problems in the filesystem:
* Files that are not statable or accessible, because there only exists an
entry in the directory, but nothing in the reiserfs tree
* Transactions that are open
* Corrupted directory entries like filenames with special charakters that
can not be used from the system, or rights with undefined bits, ...
* ...
* It must not change any data on the partition, instead it writes everything
to an output directory
Many greetings,
- --
~ Philipp Gühring p.guehring@futureware.at
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: For info see http://www.gnupg.org
iD8DBQE85FKjlqQ+F+0wB3oRAlT3AJ9/2t5pDirnnLs/4daKrSKWD2msxQCeIHZx
BU+PvfxKKbojRtdnLPerfMY=
=dohB
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2002-05-17 0:45 UTC|newest]
Thread overview: 50+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-16 18:44 A couple of questions Steve Pratt
2002-05-16 18:55 ` Oleg Drokin
2002-05-16 20:33 ` Hans Reiser
2002-05-16 21:23 ` Kuba Ober
2002-05-16 21:44 ` Lehmann
2002-05-16 23:57 ` Hans Reiser
2002-05-17 0:45 ` Philipp Gühring [this message]
2002-05-17 1:06 ` Manuel Krause
2002-05-17 15:21 ` Kuba Ober
2002-05-17 0:17 ` Manuel Krause
2002-05-17 15:04 ` Kuba Ober
2002-05-18 20:40 ` Hans Reiser
2002-05-17 15:05 ` Kuba Ober
2002-05-16 21:44 ` Lehmann
2002-05-17 13:10 ` Valdis.Kletnieks
2002-05-17 15:35 ` Kuba Ober
-- strict thread matches above, loose matches on Subject: below --
2010-05-27 13:39 Paul Millar
2010-05-27 14:56 ` Hubert Kario
2010-05-31 17:59 ` Paul Millar
2010-06-02 16:19 ` Hubert Kario
2010-05-27 16:00 ` Chris Mason
2010-05-31 18:06 ` Paul Millar
2010-05-31 20:33 ` Mike Fedyk
2010-06-02 11:56 ` Paul Millar
2010-06-01 13:39 ` Martin K. Petersen
2010-06-02 13:40 ` Paul Millar
2010-06-04 1:17 ` Martin K. Petersen
2005-04-18 11:51 Imre Simon
2005-04-18 15:31 ` Linus Torvalds
2005-04-18 16:23 ` Paul Jackson
2002-05-17 15:27 Steve Pratt
2002-05-17 13:11 berthiaume_wayne
2002-05-17 16:03 ` Kuba Ober
2002-05-16 18:48 Steve Pratt
2002-05-16 15:11 Steve Pratt
2002-05-16 15:35 ` Oleg Drokin
2002-05-16 14:52 Steve Pratt
2002-05-16 15:13 ` Hans Reiser
2002-05-15 21:22 Steve Pratt
2002-05-16 5:20 ` Oleg Drokin
2002-05-16 9:42 ` Hans Reiser
2002-05-16 11:40 ` Oleg Drokin
2002-05-16 11:54 ` Hans Reiser
2001-10-10 11:28 Adil EL YOUSSEFI
2001-10-10 12:11 ` David Woodhouse
1999-03-02 13:11 Neil Booth
1999-03-15 18:58 ` Stephen C. Tweedie
1999-03-15 22:46 ` neil
1999-03-16 12:22 ` Stephen C. Tweedie
1999-03-16 2:11 ` Andrea Arcangeli
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=200205170048.g4H0mI402129@linux1.futureware.at \
--to=p.guehring@futureware.at \
--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.