From: steve.simon@snellwilcox.com
To: 9fans@cse.psu.edu
Subject: Re[2]: [9fans] fs partwrite
Date: Tue, 5 Mar 2002 12:51:50 +0000 [thread overview]
Message-ID: <1893340736@snellwilcox.com> (raw)
>...Or probably I could take the fs portdat.h data structures (basically
>just for: block = data + tag), and built my own dedicated tag searcher
>to look for temp superblock etc, maybe that's an idea...
Brings back memories... rebuilding a Unix sys-V database disk that had
been burnt (The machine went on fire!) It had vital data for a
haulage firm (Where all the goods and trucks where); the backup
QIC tapes had been stored on top of the machine.
Marvelous fun :-)
-Steve
----------------------------------------------------------------------
The contents of this communication are confidential to the normal user of
the email address to which it was sent. If you have received this email
in error, any use, dissemination, forwarding, printing or copying of this
email is strictly prohibited. If this is the case, please notify the
sender and delete this message.
----------------------------------------------------------------------
next reply other threads:[~2002-03-05 12:51 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-05 12:51 steve.simon [this message]
2002-03-05 15:36 ` Boyd Roberts
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=1893340736@snellwilcox.com \
--to=steve.simon@snellwilcox.com \
--cc=9fans@cse.psu.edu \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).