From: Sander <sander@humilis.net>
To: Esben Stien <b0ef@esben-stien.name>
Cc: sander@humilis.net,
Matthias Andree <ma@dt.e-technik.uni-dortmund.de>,
hihone@bigpond.net.au, reiserfs-list@namesys.com
Subject: Re: Congratulations! we have got hash function screwed up
Date: Thu, 30 Dec 2004 20:21:11 +0100 [thread overview]
Message-ID: <20041230192111.GF5206@favonius> (raw)
In-Reply-To: <87d5wroc9a.fsf@quasar.esben-stien.name>
Esben Stien wrote (ao):
> Sander <sander@humilis.net> writes:
> > I'm sure a friend of mine disagrees with you after paying big bucks
> > to a Norway based disk recovery company after a disk crash and zero
> > backups. A Dutch recovery company couldn't recover the disk.
>
> Probably IBAS;). What was the problem of the hd then?. Why couldn't
> the dutchies do the job?
Maybe the Dutch company is not that good :-)
It could be IBAS, but they didn't mention a company name. It has to be a
well know one. And your mention of gold in your other mail is very true
of course :-)
> When a file gets deleted, a proper procedure to retrieve it would be
> to umount the filesystem, scan it for the data which was removed and
> then put it back in the tree again. It's not like reiserfs overwrites
> this data, it's still there, so why should there be an artificial
> barrier to getting this data back?.
I did recover data that way several times back when I didn't do backups.
The problem is though that one file does not occupy one spot on the
harddisk. It might be spread all over the place. While the data might
still be there (on an idle disk), you miss the much needed pointers to
the data.
next prev parent reply other threads:[~2004-12-30 19:21 UTC|newest]
Thread overview: 67+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-30 11:52 Congratulations! we have got hash function screwed up Yiannis Mavroukakis
2004-12-30 12:40 ` Matthias Andree
2004-12-30 12:59 ` Cal
2004-12-30 14:18 ` Matthias Andree
2004-12-30 16:40 ` Hans Reiser
2004-12-30 16:51 ` Matthias Andree
2005-01-18 21:17 ` Grzegorz Jaśkiewicz
2005-01-19 16:06 ` Hans Reiser
2005-01-19 22:41 ` David Masover
2005-01-20 13:18 ` Edward Shishkin
2005-01-20 23:43 ` Grzegorz Jaśkiewicz
2005-01-21 9:31 ` Edward Shishkin
2004-12-30 17:07 ` Esben Stien
2004-12-30 17:15 ` Christian Iversen
2004-12-30 17:47 ` Sander
2004-12-30 17:59 ` Esben Stien
2004-12-30 18:30 ` Sander
2004-12-30 18:46 ` Esben Stien
2004-12-30 18:49 ` Chris Dukes
2004-12-30 19:21 ` Sander [this message]
2004-12-30 19:29 ` Esben Stien
2004-12-30 18:16 ` Esben Stien
2004-12-30 18:26 ` Spam
2004-12-30 20:41 ` Tom Vier
2004-12-30 23:14 ` Matthias Andree
2004-12-30 23:25 ` Spam
2004-12-31 4:11 ` Hans Reiser
2004-12-31 8:36 ` Matthias Andree
2004-12-30 20:08 ` Hans Reiser
2004-12-30 21:55 ` Esben Stien
2004-12-31 4:05 ` David Masover
2004-12-31 4:26 ` Hans Reiser
2004-12-31 5:59 ` David Masover
2004-12-30 20:57 ` Adrian Ulrich
2004-12-30 21:01 ` Stefan Traby
2004-12-30 21:20 ` brianmas
2004-12-30 17:09 ` Lehmann
2004-12-30 20:11 ` Hans Reiser
-- strict thread matches above, loose matches on Subject: below --
2004-12-30 18:16 Burnes, James
2004-12-30 18:36 ` Esben Stien
2004-12-30 19:26 ` Matthias Andree
2004-12-30 19:24 ` Matthias Andree
2004-12-30 20:25 ` Hans Reiser
2004-12-30 17:22 Yiannis Mavroukakis
2004-12-30 13:24 Yiannis Mavroukakis
2004-12-30 14:11 ` Matthias Andree
2004-12-28 22:12 Lehmann
2004-12-29 18:55 ` Stefan Traby
2004-12-29 21:04 ` Lehmann
2004-12-29 21:05 ` Hans Reiser
2004-12-29 21:43 ` Lehmann
2004-12-29 21:46 ` Christian Iversen
2004-12-29 22:27 ` Lehmann
2004-12-30 2:05 ` Hans Reiser
2004-12-30 10:22 ` Matthias Andree
2004-12-30 17:02 ` Lehmann
2005-01-06 12:45 ` Alex Zarochentsev
2005-01-06 14:27 ` Lehmann
2005-01-06 15:56 ` Hans Reiser
2005-01-06 16:13 ` Spam
2005-01-06 16:26 ` Chris Dukes
2005-01-06 16:29 ` Spam
2005-01-06 16:56 ` Chris Dukes
2005-01-07 17:22 ` Hans Reiser
2005-01-07 17:28 ` Chris Dukes
2005-01-06 18:55 ` Edward Shishkin
2005-01-07 17:26 ` Lehmann
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=20041230192111.GF5206@favonius \
--to=sander@humilis.net \
--cc=b0ef@esben-stien.name \
--cc=hihone@bigpond.net.au \
--cc=ma@dt.e-technik.uni-dortmund.de \
--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.