From: Martin Harriss <martin@Princeton.EDU>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] writable optical media
Date: Tue, 18 Sep 2001 12:03:30 -0400 [thread overview]
Message-ID: <3BA77052.C4E620DA@princeton.edu> (raw)
In-Reply-To: <20010918130425.E9EC219A7C@mail.cse.psu.edu>
presotto@plan9.bell-labs.com wrote:
>
[ stuff deleted... ]
>
> I guess the moral is: optical is nice, but when the lifetime of
> each round of technology is around 5 years, you have to recopy
> every few years anyways since the devices to read the indestructible
> media atrophy. Also, the density goes up fast enough that
> copying every few years means that you can always have everything
> on line.
Has anyone done any work on integrating "old dumps" into a new file
server? I know the dumps are supposed to be immutable, but it would be
nice to set up a new file server using the latest technology and be ably
to migrate one's old dumps seamlessly into the new server. This would
be particularly useful when migrating to a bigger dump device. Can this
maybe be done just by copying the data and then fudging the size in the
superblock?
Martin
next prev parent reply other threads:[~2001-09-18 16:03 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-09-18 13:04 presotto
2001-09-18 13:16 ` Matt
2001-09-18 14:16 ` [9fans] OT but you gotta laugh Matt
2001-09-18 16:03 ` Martin Harriss [this message]
2001-09-18 16:07 [9fans] writable optical media rob pike
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=3BA77052.C4E620DA@princeton.edu \
--to=martin@princeton.edu \
--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).