Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > comp.os.linux.misc > #95764 > unrolled thread

Optical Disc Long Term Storage

Started byLeroy H <lh@somewhere.net>
First post2026-11-18 19:21 +0000
Last post2026-11-22 02:58 +0000
Articles 20 on this page of 35 — 11 participants

Back to article view | Back to comp.os.linux.misc


Contents

  Optical Disc Long Term Storage Leroy H <lh@somewhere.net> - 2026-11-18 19:21 +0000
    Re: Optical Disc Long Term Storage c186282 <c186282@nnada.net> - 2026-11-18 19:31 -0500
      Re: Optical Disc Long Term Storage Leroy H <lh@somewhere.net> - 2026-11-19 02:30 +0000
        Re: Optical Disc Long Term Storage c186282 <c186282@nnada.net> - 2026-11-18 22:36 -0500
          Re: Optical Disc Long Term Storage Robert Riches <spamtrap42@jacob21819.net> - 2026-11-19 04:24 +0000
            Re: Optical Disc Long Term Storage Leroy H <lh@somewhere.net> - 2026-11-19 12:49 +0000
              Re: Optical Disc Long Term Storage Charlie Gibbs <cgibbs@kltpzyxm.invalid> - 2026-11-19 18:36 +0000
                Re: Optical Disc Long Term Storage Leroy H <lh@somewhere.net> - 2026-11-19 19:20 +0000
                  Re: Optical Disc Long Term Storage "Carlos E.R." <robin_listas@es.invalid> - 2026-11-19 20:42 +0100
                  Re: Optical Disc Long Term Storage Rich <rich@example.invalid> - 2026-11-19 21:10 +0000
                    Re: Optical Disc Long Term Storage Charlie Gibbs <cgibbs@kltpzyxm.invalid> - 2026-11-19 23:11 +0000
                      Re: Optical Disc Long Term Storage c186282 <c186282@nnada.net> - 2026-11-19 20:40 -0500
                Re: Optical Disc Long Term Storage Lawrence D’Oliveiro <ldo@nz.invalid> - 2026-11-20 02:47 +0000
                  Re: Optical Disc Long Term Storage c186282 <c186282@nnada.net> - 2026-11-20 00:41 -0500
            Re: Optical Disc Long Term Storage c186282 <c186282@nnada.net> - 2026-11-19 17:48 -0500
    Re: Optical Disc Long Term Storage John Bokma <contact@johnbokma.com> - 2026-11-19 11:51 +0100
      Re: Optical Disc Long Term Storage The Natural Philosopher <tnp@invalid.invalid> - 2026-11-19 15:43 +0000
      Re: Optical Disc Long Term Storage c186282 <c186282@nnada.net> - 2026-11-19 18:00 -0500
      Re: Optical Disc Long Term Storage mechanicjay@sol.smbfc.net (Mechanicjay) - 2026-11-20 06:07 +0000
        Re: Optical Disc Long Term Storage c186282 <c186282@nnada.net> - 2026-11-20 21:03 -0500
          Re: Optical Disc Long Term Storage Leroy H <lh@somewhere.net> - 2026-11-21 02:32 +0000
            Re: Optical Disc Long Term Storage c186282 <c186282@nnada.net> - 2026-11-20 22:20 -0500
              Re: Optical Disc Long Term Storage mechanicjay@sol.smbfc.net (Mechanicjay) - 2026-11-21 07:10 +0000
    Re: Optical Disc Long Term Storage Rich <rich@example.invalid> - 2026-11-19 21:06 +0000
      Re: Optical Disc Long Term Storage Leroy H <lh@somewhere.net> - 2026-11-19 22:22 +0000
        Re: Optical Disc Long Term Storage c186282 <c186282@nnada.net> - 2026-11-19 18:07 -0500
        Re: Optical Disc Long Term Storage ant@zimage.comANT (Ant) - 2026-11-20 01:39 +0000
          Re: Optical Disc Long Term Storage Leroy H <lh@somewhere.net> - 2026-11-20 01:59 +0000
            Re: Optical Disc Long Term Storage ant@zimage.comANT (Ant) - 2026-11-22 02:38 +0000
          Re: Optical Disc Long Term Storage c186282 <c186282@nnada.net> - 2026-11-19 21:21 -0500
        Re: Optical Disc Long Term Storage "Carlos E.R." <robin_listas@es.invalid> - 2026-11-21 21:14 +0100
          Re: Optical Disc Long Term Storage Rich <rich@example.invalid> - 2026-11-21 21:07 +0000
            Re: Optical Disc Long Term Storage "Carlos E.R." <robin_listas@es.invalid> - 2026-11-21 22:22 +0100
        Re: Optical Disc Long Term Storage "Carlos E.R." <robin_listas@es.invalid> - 2026-11-21 21:38 +0100
          Re: Optical Disc Long Term Storage ant@zimage.comANT (Ant) - 2026-11-22 02:58 +0000

Page 1 of 2  [1] 2  Next page →


#95764 — Optical Disc Long Term Storage

FromLeroy H <lh@somewhere.net>
Date2026-11-18 19:21 +0000
SubjectOptical Disc Long Term Storage
Message-ID<18e93a0392f47eda$691$3385385$802601b3@news.usenetexpress.com>
Recently, I had a reason to pull out of storage some DVD-RAM optical
discs that I burned in 2003:

<https://en.wikipedia.org/wiki/DVD-RAM>

They were flawless.  All data was spotless.

I did the same for some CD/DVD-R (not RW) discs with the same results.

After 23 years, my data is pristine and will likely remain so for
another 23 years.

All the burning was originally done with GNU/Linux utilities and,
furthermore, with $49.95 burners from Newegg, BestBuy, or equivalent
retailers.

Currently, I burn all my data onto Blu-Ray M-Discs which putatively
have a lifespan of 100+ years:

<https://en.wikipedia.org/wiki/M-DISC>

I post this message because there are many claims that state that
optical disc data becomes corrupted after just a few years.  I say
"screw you" to such claims.

Give me GNU/Linux, M-Disc, and a $49.95 burner and I shall preserve
my data forever.

[toc] | [next] | [standalone]


#95772

Fromc186282 <c186282@nnada.net>
Date2026-11-18 19:31 -0500
Message-ID<W9ScnQ9HgeDi3mP3nZ2dnZfqn_adnZ2d@giganews.com>
In reply to#95764
On 11/18/26 14:21, Leroy H wrote:
> Recently, I had a reason to pull out of storage some DVD-RAM optical
> discs that I burned in 2003:
> 
> <https://en.wikipedia.org/wiki/DVD-RAM>
> 
> They were flawless.  All data was spotless.
> 
> I did the same for some CD/DVD-R (not RW) discs with the same results.
> 
> After 23 years, my data is pristine and will likely remain so for
> another 23 years.
> 
> All the burning was originally done with GNU/Linux utilities and,
> furthermore, with $49.95 burners from Newegg, BestBuy, or equivalent
> retailers.
> 
> Currently, I burn all my data onto Blu-Ray M-Discs which putatively
> have a lifespan of 100+ years:
> 
> <https://en.wikipedia.org/wiki/M-DISC>
> 
> I post this message because there are many claims that state that
> optical disc data becomes corrupted after just a few years.  I say
> "screw you" to such claims.
> 
> Give me GNU/Linux, M-Disc, and a $49.95 burner and I shall preserve
> my data forever.

   Optical disks are "almost forever" unless you
   play hockey with them.

   Have BR burner and, every few months, burn my
   most important stuff. Still not 'very much'
   storage but, organize properly, and it's
   "enough".

[toc] | [prev] | [next] | [standalone]


#95774

FromLeroy H <lh@somewhere.net>
Date2026-11-19 02:30 +0000
Message-ID<18e9516c7a85a146$1192$3385385$802601b3@news.usenetexpress.com>
In reply to#95772
On Wed, 18 Nov 2026 19:31:03 -0500, c186282 wrote:

> 
>    Have BR burner and, every few months, burn my
>    most important stuff. Still not 'very much'
>    storage but, organize properly, and it's
>    "enough".
>

Excellent!  A wise activity!

The only problem with burning to optical disk is that it requires
a huge amount of time.  For example, I burn BDR 25 Gb disks at
the slowest speed (growisofs -speed=2 ...) and it takes about
2 hours to complete.

Of course, I could burn at a much higher speed but slower speeds
give better results.

However, the longevity of the results certainly negates any concern
about the burn time.

[toc] | [prev] | [next] | [standalone]


#95776

Fromc186282 <c186282@nnada.net>
Date2026-11-18 22:36 -0500
Message-ID<Te-cnfkEp-0g82P3nZ2dnZfqn_idnZ2d@giganews.com>
In reply to#95774
On 11/18/26 21:30, Leroy H wrote:
> On Wed, 18 Nov 2026 19:31:03 -0500, c186282 wrote:
> 
>>
>>     Have BR burner and, every few months, burn my
>>     most important stuff. Still not 'very much'
>>     storage but, organize properly, and it's
>>     "enough".
>>
> 
> Excellent!  A wise activity!
> 
> The only problem with burning to optical disk is that it requires
> a huge amount of time.  For example, I burn BDR 25 Gb disks at
> the slowest speed (growisofs -speed=2 ...) and it takes about
> 2 hours to complete.

   Yep, close to 2 hours.

   But ...

> Of course, I could burn at a much higher speed but slower speeds
> give better results.
> 
> However, the longevity of the results certainly negates any concern
> about the burn time.

   Some burner apps give you the choice of the
   burn speed. It IS better to drop down at
   least one level from the assumed max.

   Anyway, power surges, lightning, maybe not
   even tornado, are gonna ruin those optical
   backups. Won't have to start from scratch
   if the worst happens.

   We HOPED for holographic crystals with
   terabyte+ capacity - but, obviously, they
   are not in the pipeline. So, gotta
   make do. Blu-Ray is the nearest hardcore
   fix.

   Removable drives are also a fix, sometimes.
   They won't hold stuff for 1000 years or
   under flood waters though.

[toc] | [prev] | [next] | [standalone]


#95778

FromRobert Riches <spamtrap42@jacob21819.net>
Date2026-11-19 04:24 +0000
Message-ID<slrn11fsug1.hg1.spamtrap42@one.localnet>
In reply to#95776
On 2026-11-19, c186282 <c186282@nnada.net> wrote:
> On 11/18/26 21:30, Leroy H wrote:
>> On Wed, 18 Nov 2026 19:31:03 -0500, c186282 wrote:
>> 
>>>
>>>     Have BR burner and, every few months, burn my
>>>     most important stuff. Still not 'very much'
>>>     storage but, organize properly, and it's
>>>     "enough".
>>>
>> 
>> Excellent!  A wise activity!
>> 
>> The only problem with burning to optical disk is that it requires
>> a huge amount of time.  For example, I burn BDR 25 Gb disks at
>> the slowest speed (growisofs -speed=2 ...) and it takes about
>> 2 hours to complete.
>
>    Yep, close to 2 hours.
>
>    But ...

Takes me about 30 minutes to burn ~24.8GB to a BD-R with a
Pioneer burner at default speed.

I use PlexDisc brand media.  I had been using Verbatim brand but
was making lots of coasters.  I bought one spindle of each of 3-4
brands and tested them.  Verbatim made ~20% coasters.  The others
made vastly fewer or none at all.

Because I'm paranoid, after I burn each disc I verify it with
both the drive that burned it and with a second drive.

-- 
Robert Riches
spamtrap42@jacob21819.net
(Yes, that is one of my email addresses.)

[toc] | [prev] | [next] | [standalone]


#95785

FromLeroy H <lh@somewhere.net>
Date2026-11-19 12:49 +0000
Message-ID<18e97334329955ad$2731$3691736$802601b3@news.usenetexpress.com>
In reply to#95778
On 19 Nov 2026 04:24:33 GMT, Robert Riches wrote:

> 
> Because I'm paranoid, after I burn each disc I verify it with
> both the drive that burned it and with a second drive.
>

Real paranoia requires making ECC recovery files using dvdisaster:

<https://github.com/speed47/dvdisaster>

I just settle for multiple copies.

[toc] | [prev] | [next] | [standalone]


#95787

FromCharlie Gibbs <cgibbs@kltpzyxm.invalid>
Date2026-11-19 18:36 +0000
Message-ID<ukHLS.587$3zk7.558@fx17.iad>
In reply to#95785
On 2026-11-19, Leroy H <lh@somewhere.net> wrote:

> On 19 Nov 2026 04:24:33 GMT, Robert Riches wrote:
>
>> Because I'm paranoid, after I burn each disc I verify it with
>> both the drive that burned it and with a second drive.
>
> Real paranoia requires making ECC recovery files using dvdisaster:
>
> <https://github.com/speed47/dvdisaster>
>
> I just settle for multiple copies.

I make PAR2 files.

-- 
/~\  Charlie Gibbs                  |  In this world there are
\ /  <cgibbs@kltpzyxm.invalid>      |  two kinds of people:
 X   I'm really at ac.dekanfrus     |  1. Those who can extrapolate
/ \  if you read it the right way.  |  from incomplete data.

[toc] | [prev] | [next] | [standalone]


#95788

FromLeroy H <lh@somewhere.net>
Date2026-11-19 19:20 +0000
Message-ID<18e988812fc0b5b6$1548$1163114$802601b3@news.usenetexpress.com>
In reply to#95787
On Thu, 19 Nov 2026 18:36:10 GMT, Charlie Gibbs wrote:

> 
> I make PAR2 files.
>

PAR2 is not recommended for optical media.  That's why dvdisaster
was developed.

The exact reason for this is beyond me.

[toc] | [prev] | [next] | [standalone]


#95789

From"Carlos E.R." <robin_listas@es.invalid>
Date2026-11-19 20:42 +0100
Message-ID<t204tmx2ek.ln2@Telcontar.valinor>
In reply to#95788
On 2026-11-19 20:20, Leroy H wrote:
> On Thu, 19 Nov 2026 18:36:10 GMT, Charlie Gibbs wrote:
> 
>>
>> I make PAR2 files.
>>
> 
> PAR2 is not recommended for optical media.  That's why dvdisaster
> was developed.
> 
> The exact reason for this is beyond me.
> 

ChatGPT blurb:

The distinction is mainly about how optical-disc errors behave, and when 
you discover them.

PAR2 and dvdisaster both use redundancy (error-correcting information) 
to recover damaged data, but they approach the problem differently.

The statement you quoted is a little too categorical: PAR2 can certainly 
be used with data originating from optical discs. However, dvdisaster 
was designed specifically around the failure characteristics and usage 
patterns of CD, DVD and Blu-ray media.

## 1. How PAR2 works

PAR2 (Parity Volume Set) creates additional recovery files from a 
collection of original files.

For example, suppose you have:

- `archive1.zip`
- `archive2.zip`
- `archive3.zip`

You generate 10% PAR2 recovery data. If one of the archives subsequently 
becomes corrupted, PAR2 may be able to reconstruct the missing or 
damaged data, provided enough recovery data remains available.

The important characteristics are:

- It works on files, rather than directly on physical sectors of a disc.
- It normally needs the original files and PAR2 recovery files to be 
available together.
- Recovery is performed after corruption has been detected.
- You need to have generated and preserved the recovery files beforehand.

This works very well for archives, backups and collections of files.

## 2. The important problem: filesystem metadata

This is the main reason dvdisaster was developed.

An optical disc has more than just file contents. It also contains 
filesystem metadata, including:

- Directory structures.
- File names.
- File locations and lengths.
- Filesystem allocation information.

Imagine a DVD containing:

text

```text
DVD
  ├── Photos/
  │    ├── photo1.jpg
  │    └── photo2.jpg
  └── Documents/
       └── report.pdf
```

Suppose you generate PAR2 files for all three data files.

Now imagine that a scratch damages a sector containing the directory 
information for `Photos`.

Even if `photo1.jpg` and `photo2.jpg` are completely intact, the 
filesystem might no longer be able to locate them.

Your PAR2 files cannot necessarily help: they protect the contents of 
the files, not the filesystem structures needed to find those files.

This is the central argument made in the dvdisaster documentation. See 
its explanation of file-based versus image-based recovery.

dvdisaster.jcea.es

+1

## 3. How dvdisaster solves this

dvdisaster works at the ISO image level rather than the individual-file 
level.

GitHub - speed47/dvdisaster: A tool providing additional ECC protection 
for optical media (unofficial version)

[github.com](<https://github.com/speed47/dvdisaster?utm_source=chatgpt.com>)

In simplified terms:

1. You create an ISO image of your DVD.
2. dvdisaster generates additional error-correction information for the 
entire image.
3. You either store the ECC information separately or incorporate it 
into an augmented image.
4. You burn the resulting image to optical media.
5. If the disc develops damaged sectors, dvdisaster can reconstruct the 
damaged image, including filesystem metadata.

This is a significant difference: the error correction covers the 
complete disc image, not just the files stored in its filesystem.

xgiovio git server

+1

## 4. But can't you simply use PAR2 on an ISO image?

Yes\! And this is an important qualification.

You could do something like:

bash

```bash
# Create an ISO image
genisoimage -o backup.iso /path/to/data

# Generate PAR2 recovery information
par2 create -r10 backup.par2 backup.iso
```

Here, PAR2 protects the entire ISO file, including its filesystem metadata.

If the ISO is damaged, PAR2 can potentially reconstruct it.

So the original statement that PAR2 is unsuitable for optical media is 
not entirely accurate.

There are, however, some practical differences:

| Feature | PAR2 on individual files | PAR2 on ISO | dvdisaster |
| --- | --- | --- | --- |
| Protects file contents | Yes | Yes | Yes |
| Protects filesystem metadata | No | Yes | Yes |
| Works with damaged disc images | Indirectly | Yes | Yes |
| Can store ECC inside the disc image | No | No | Yes (RS02/RS03) |
| Designed specifically for optical media | No | No | Yes |

One additional consideration: if you store PAR2 recovery files on 
another optical disc, that disc can suffer from the same aging and 
damage problems as the original. Your recovery data needs protection too.

xgiovio git server

## 5. What I would recommend under Linux

For long-term optical-disc archiving, I'd consider these approaches:

- dvdisaster: If you want to protect complete CD/DVD/Blu-ray images, 
including filesystem metadata.
- PAR2 on ISO images: If you prefer a general-purpose recovery tool and 
are happy to maintain separate recovery files.
- PAR2 on individual files: If your objective is recovering individual 
files rather than guaranteeing recovery of an entire optical disc.

My preference for optical-disc archival would be dvdisaster, because its 
design addresses the particular failure modes of optical media.

One final distinction worth remembering: neither solution prevents 
physical deterioration. They give you a chance to reconstruct data after 
damage, provided the damage stays within the recovery capacity.

Useful documentation:

- [dvdisaster User 
Manual](<https://dvdisaster.jcea.es/downloads/manual.pdf?utm_source=chatgpt.com>) 
— particularly section 1.5, explaining file-based versus image-based 
recovery.
- [dvdisaster Linux man 
page](<https://manpages.debian.org/unstable/dvdisaster/dvdisaster.1.en.html?utm_source=chatgpt.com>) 
— command-line usage and examples.

The user manual is especially worth reading: it explains the reasoning 
behind dvdisaster's design much better than a simple comparison of PAR2 
and Reed-Solomon error correction.

-- 
Cheers, Carlos.
ES🇪🇸, EU🇪🇺;

[toc] | [prev] | [next] | [standalone]


#95791

FromRich <rich@example.invalid>
Date2026-11-19 21:10 +0000
Message-ID<11dnojm$2kh7t$2@dont-email.me>
In reply to#95788
Leroy H <lh@somewhere.net> wrote:
> On Thu, 19 Nov 2026 18:36:10 GMT, Charlie Gibbs wrote:
> 
>> 
>> I make PAR2 files.
>>
> 
> PAR2 is not recommended for optical media.  That's why dvdisaster
> was developed.
> 
> The exact reason for this is beyond me.

PAR2 operates at the file level, within the filesystem.  If you can not 
read the disk, because filesystem metadata is corrupted, you cannot 
retreive the files, so you have no PAR2 files (nor the protected files) 
with which to perform a par repair.

DVDisaster operates at the level of the optical disk sectors.  It 
repairs the stored files (if they are corrupted), and the filesystem 
metadata needed to read off those files, so what you get back (assuming 
enough redundancy to fix any issues) is an ISO image file with all the 
stored files inside intact and readable.

[toc] | [prev] | [next] | [standalone]


#95796

FromCharlie Gibbs <cgibbs@kltpzyxm.invalid>
Date2026-11-19 23:11 +0000
Message-ID<qmLLS.104365$ATB4.95052@fx12.iad>
In reply to#95791
On 2026-11-19, Rich <rich@example.invalid> wrote:

> Leroy H <lh@somewhere.net> wrote:
>
>> On Thu, 19 Nov 2026 18:36:10 GMT, Charlie Gibbs wrote:
>> 
>>> I make PAR2 files.
>> 
>> PAR2 is not recommended for optical media.  That's why dvdisaster
>> was developed.
>> 
>> The exact reason for this is beyond me.
>
> PAR2 operates at the file level, within the filesystem.  If you can not 
> read the disk, because filesystem metadata is corrupted, you cannot 
> retreive the files, so you have no PAR2 files (nor the protected files) 
> with which to perform a par repair.
>
> DVDisaster operates at the level of the optical disk sectors.  It 
> repairs the stored files (if they are corrupted), and the filesystem 
> metadata needed to read off those files, so what you get back (assuming 
> enough redundancy to fix any issues) is an ISO image file with all the 
> stored files inside intact and readable.

Good point.  Recently I tried reading some DVD-Rs that I burned
20 years ago.  Most of them are fine.  One or two have errors
which the PAR2 files are able to repair.  But you're right,
if it was the directory blocks that got corrupted I'd be screwed.
I don't burn many discs anymore - my backups are now on pairs
of terabyte drives, and I keep one of each pair offsite.
But if I do get back into burning archival discs,
I'll definitely give DVDisaster a look.

-- 
/~\  Charlie Gibbs                  |  In this world there are
\ /  <cgibbs@kltpzyxm.invalid>      |  two kinds of people:
 X   I'm really at ac.dekanfrus     |  1. Those who can extrapolate
/ \  if you read it the right way.  |  from incomplete data.

[toc] | [prev] | [next] | [standalone]


#95798

Fromc186282 <c186282@nnada.net>
Date2026-11-19 20:40 -0500
Message-ID<XCWdnXUboeKgOGL3nZ2dnZfqnPWdnZ2d@giganews.com>
In reply to#95796
On 11/19/26 18:11, Charlie Gibbs wrote:
> On 2026-11-19, Rich <rich@example.invalid> wrote:
> 
>> Leroy H <lh@somewhere.net> wrote:
>>
>>> On Thu, 19 Nov 2026 18:36:10 GMT, Charlie Gibbs wrote:
>>>
>>>> I make PAR2 files.
>>>
>>> PAR2 is not recommended for optical media.  That's why dvdisaster
>>> was developed.
>>>
>>> The exact reason for this is beyond me.
>>
>> PAR2 operates at the file level, within the filesystem.  If you can not
>> read the disk, because filesystem metadata is corrupted, you cannot
>> retreive the files, so you have no PAR2 files (nor the protected files)
>> with which to perform a par repair.
>>
>> DVDisaster operates at the level of the optical disk sectors.  It
>> repairs the stored files (if they are corrupted), and the filesystem
>> metadata needed to read off those files, so what you get back (assuming
>> enough redundancy to fix any issues) is an ISO image file with all the
>> stored files inside intact and readable.
> 
> Good point.  Recently I tried reading some DVD-Rs that I burned
> 20 years ago.  Most of them are fine.  One or two have errors
> which the PAR2 files are able to repair.  But you're right,
> if it was the directory blocks that got corrupted I'd be screwed.
> I don't burn many discs anymore - my backups are now on pairs
> of terabyte drives, and I keep one of each pair offsite.
> But if I do get back into burning archival discs,
> I'll definitely give DVDisaster a look.

   Blu-Ray dual-layer are 'big enough' for archival
   backups, but not for indiscriminate mass backups.
   Hugely faster than tapes though.

   These days, removable HDDs are by far the best
   daily backup media. However NOT sure how well
   they will hold up for 25+ years, many things
   can go wrong.

   For 'offsite', yer probably best off using cloud
   storage (encrypt first !). At my last job I
   did another sort of 'offsite', a little box and
   drive in another building - slow, but it copied
   selected main backups from the night before and
   thus could spend all day. Pi3+usbHDD+wifi airgap ...
   the nightly backups were already encrypted so
   it wasn't important if anybody stole/accessed
   the Pi (never happened though).

   A pity nobody ever made 8-inch Blu-Ray drives,
   250gb maybe :-)

   Anyway, if you are into legal or govt stuff,
   something approaching "forever" backups of
   certain docs may be required by law. So,
   it's paper or optical for now.

   Hey, clay tablets hold up for 6000 years !
   We can still read Sumerian tax records.
   Alas the data density is, well, kinda low.
   Gall ink on parchment/papyrus holds up
   fairly well though it will fade.

   Now ways to READ optical in the future may
   be kinda iffy ... won't be any 'drives' around.
   Kinda like all those big spinney tapes from the
   old sci-fi movies ... are there ANY working
   units that'll read them, and how to interface ???

   Remember when those big tape drives were NOT
   obsolete. Alas every maker, every model,
   sometimes sub-models, the FORMAT was not
   the same. No standards, the makers kinda
   trapped you into using THEIR stuff.

   Anyway, my last few years on the job, 'redundant
   backups' kinda became one of my big things. First
   scripts, then smarter programs that'd multi-
   distribute and deal with old/moved copies and such.
   The new guy just sends it to M$ cloud and feels
   sure it's all safe. M$ disaster, well, it's NOT
   HIS FAULT - that's the current thinking  :-)

   Until somebody comes up with 'holo-crystal' petabyte
   storage media that's so good it'll never become
   obsolete we've gotta kind of wing it. Eggs, baskets.

[toc] | [prev] | [next] | [standalone]


#95802

FromLawrence D’Oliveiro <ldo@nz.invalid>
Date2026-11-20 02:47 +0000
Message-ID<11docc4$2qp30$1@dont-email.me>
In reply to#95787
On Thu, 19 Nov 2026 18:36:10 GMT, Charlie Gibbs wrote:

> I make PAR2 files.

Erasure codes are a neat concept for adding an extra layer of
tolerance against failures, but they should be an addition to
redundant backups, not a replacement for them.

[toc] | [prev] | [next] | [standalone]


#95803

Fromc186282 <c186282@nnada.net>
Date2026-11-20 00:41 -0500
Message-ID<eeucnUgtIMX2QGL3nZ2dnZfqnPudnZ2d@giganews.com>
In reply to#95802
On 11/19/26 21:47, Lawrence D’Oliveiro wrote:
> On Thu, 19 Nov 2026 18:36:10 GMT, Charlie Gibbs wrote:
> 
>> I make PAR2 files.
> 
> Erasure codes are a neat concept for adding an extra layer of
> tolerance against failures, but they should be an addition to
> redundant backups, not a replacement for them.

   For most backups there are TWO things to look for.

   The first is OLD data that no longer exists on
   the source. 'rsync' can kinda deal with that.

   The second is MOVED data on the source, but
   copied, not copy-pasted, so you now have two
   or more nearly-identical folders.

   DID write apps that dealt with both things ...
   but the latter case IS touchy, be SURE of
   your active mounts. Check early and often.
   Linux CAN drop mounts without warning.

[toc] | [prev] | [next] | [standalone]


#95793

Fromc186282 <c186282@nnada.net>
Date2026-11-19 17:48 -0500
Message-ID<n5-dnScReYw64WL3nZ2dnZfqnPudnZ2d@giganews.com>
In reply to#95778
On 11/18/26 23:24, Robert Riches wrote:
> On 2026-11-19, c186282 <c186282@nnada.net> wrote:
>> On 11/18/26 21:30, Leroy H wrote:
>>> On Wed, 18 Nov 2026 19:31:03 -0500, c186282 wrote:
>>>
>>>>
>>>>      Have BR burner and, every few months, burn my
>>>>      most important stuff. Still not 'very much'
>>>>      storage but, organize properly, and it's
>>>>      "enough".
>>>>
>>>
>>> Excellent!  A wise activity!
>>>
>>> The only problem with burning to optical disk is that it requires
>>> a huge amount of time.  For example, I burn BDR 25 Gb disks at
>>> the slowest speed (growisofs -speed=2 ...) and it takes about
>>> 2 hours to complete.
>>
>>     Yep, close to 2 hours.
>>
>>     But ...
> 
> Takes me about 30 minutes to burn ~24.8GB to a BD-R with a
> Pioneer burner at default speed.
> 
> I use PlexDisc brand media.  I had been using Verbatim brand but
> was making lots of coasters.  I bought one spindle of each of 3-4
> brands and tested them.  Verbatim made ~20% coasters.  The others
> made vastly fewer or none at all.
> 
> Because I'm paranoid, after I burn each disc I verify it with
> both the drive that burned it and with a second drive.

   My stuff comes out to like 40-45 GB ... but the burner
   is attached to my mini-NAS so I just cherry pick the
   desired files and let it run while I do other stuff.
   Eventually you hear the disk pop out.

   Verbatim at least USED to be a blue-ribbon media maker.
   Maybe you got a bad batch ? Mine are TDK I think, indeed
   gotta start looking for where I stashed the box as it's
   about time for a big backup.

   I see PleXDisc BD-R/DL on Amazon - $50 for 25. Maybe
   I'll give 'em a try.

   Don't think anybody ever made rewritable BD's in the
   dual-layer 50gb format - but you can get 'em for 25gb

   Anyway, hard to go wrong with an optical hardcopy.
   Alas only Blu-Ray have useful capacity.

[toc] | [prev] | [next] | [standalone]


#95784

FromJohn Bokma <contact@johnbokma.com>
Date2026-11-19 11:51 +0100
Message-ID<11dmkbc$25qcs$1@dont-email.me>
In reply to#95764
On 18/11/2026 20:21, Leroy H wrote:

> I post this message because there are many claims that state that
> optical disc data becomes corrupted after just a few years.  I say
> "screw you" to such claims.

I had several CDs with holes in the data layer. Burned those in the late 
90's. If I recall correctly they were all made by Sony.

-- 
Static tumblelog generator: https://github.com/john-bokma/tumblelog/
Available as Python or Perl. Example tumblelog: https://plurrrr.com/

[toc] | [prev] | [next] | [standalone]


#95786

FromThe Natural Philosopher <tnp@invalid.invalid>
Date2026-11-19 15:43 +0000
Message-ID<11dn5e5$2cijt$3@dont-email.me>
In reply to#95784
On 19/11/2026 10:51, John Bokma wrote:
> On 18/11/2026 20:21, Leroy H wrote:
> 
>> I post this message because there are many claims that state that
>> optical disc data becomes corrupted after just a few years.  I say
>> "screw you" to such claims.
> 
> I had several CDs with holes in the data layer. Burned those in the late 
> 90's. If I recall correctly they were all made by Sony.
> 
My twin hard drives have mirrored data going back to the 1990s.
I rejected DVDs as not being large enough in volume size
-- 
In theory, there is no difference between theory and practice.
In practice, there is.
-- Yogi Berra

[toc] | [prev] | [next] | [standalone]


#95794

Fromc186282 <c186282@nnada.net>
Date2026-11-19 18:00 -0500
Message-ID<AOydnb7FfsEY4mL3nZ2dnZfqnPidnZ2d@giganews.com>
In reply to#95784
On 11/19/26 05:51, John Bokma wrote:
> On 18/11/2026 20:21, Leroy H wrote:
> 
>> I post this message because there are many claims that state that
>> optical disc data becomes corrupted after just a few years.  I say
>> "screw you" to such claims.
> 
> I had several CDs with holes in the data layer. Burned those in the late 
> 90's. If I recall correctly they were all made by Sony.

   That was part of a copy-prevention scheme popular
   at the time. Phillipe Khan of Borland offered
   a bounty to the first person to bust the system
   and it only took a day or two :-)

[toc] | [prev] | [next] | [standalone]


#95804

Frommechanicjay@sol.smbfc.net (Mechanicjay)
Date2026-11-20 06:07 +0000
Message-ID<slrn11fvote.42l.mechanicjay@sol.smbfc.net>
In reply to#95784
On Thu, 19 Nov 2026 11:51:21 +0100, John Bokma <contact@johnbokma.com> wrote:
>On 18/11/2026 20:21, Leroy H wrote:
>
>> I post this message because there are many claims that state that
>> optical disc data becomes corrupted after just a few years.  I say
>> "screw you" to such claims.
>
>I had several CDs with holes in the data layer. Burned those in the late 
>90's. If I recall correctly they were all made by Sony.
>

Same.  

I have a cd-case full of burned media going back about 25 years.  Some of
them have bit-rotted in place to the point where when holding the disk up to a
light, it looks likes a starfield.

Others, you can see the dye dis-coloring from the outside edge in.

Others are fine...so far.

This is a mix of brands, some cheap, some good, with no real correlation between
the stuff that's gone bad and the stuff that's stayed good.  Regardless, it's
a clear physical failure of the media.

Each year, another couple go bad.

These are not backups -- at least not any more.  (Storage and backups are done
with multi-drive ZFS arrays at this point.)  

These are burned discs of convenience, such as a set of Layered Products CDs for
my VAX or a Polish Bootleg of Office 97 which helpfully slipstreams the licence
key.  Well, I found that one had bit the dust when I did fresh Windows 98
build last year.  

Anyway.  Would I trust a burned disk 5 years? 100%
10 years?  probably.  
20? I'd be making sure I had that data safely stored away somewhere else.  

YMMV

--
Sent from my Decstation 5000/25

[toc] | [prev] | [next] | [standalone]


#95813

Fromc186282 <c186282@nnada.net>
Date2026-11-20 21:03 -0500
Message-ID<RBadncn9TNpjZp32nZ2dnZfqnPadnZ2d@giganews.com>
In reply to#95804
On 11/20/26 01:07, Mechanicjay wrote:
> On Thu, 19 Nov 2026 11:51:21 +0100, John Bokma <contact@johnbokma.com> wrote:
>> On 18/11/2026 20:21, Leroy H wrote:
>>
>>> I post this message because there are many claims that state that
>>> optical disc data becomes corrupted after just a few years.  I say
>>> "screw you" to such claims.
>>
>> I had several CDs with holes in the data layer. Burned those in the late
>> 90's. If I recall correctly they were all made by Sony.
>>
> 
> Same.
> 
> I have a cd-case full of burned media going back about 25 years.  Some of
> them have bit-rotted in place to the point where when holding the disk up to a
> light, it looks likes a starfield.
> 
> Others, you can see the dye dis-coloring from the outside edge in.
> 
> Others are fine...so far.
> 
> This is a mix of brands, some cheap, some good, with no real correlation between
> the stuff that's gone bad and the stuff that's stayed good.  Regardless, it's
> a clear physical failure of the media.
> 
> Each year, another couple go bad.
> 
> These are not backups -- at least not any more.  (Storage and backups are done
> with multi-drive ZFS arrays at this point.)
> 
> These are burned discs of convenience, such as a set of Layered Products CDs for
> my VAX or a Polish Bootleg of Office 97 which helpfully slipstreams the licence
> key.  Well, I found that one had bit the dust when I did fresh Windows 98
> build last year.
> 
> Anyway.  Would I trust a burned disk 5 years? 100%
> 10 years?  probably.
> 20? I'd be making sure I had that data safely stored away somewhere else.

   Replication is the ONLY safe tactic for true archival
   data storage. Put it on mag disks, put it on optical
   disks, put it on the 'cloud' too. Move it to new disks
   every so often.

   The National Archives and Smithsonian are already
   freaking because there are no living devices to
   READ old data tapes/drums/gen-1-disks. Every maker
   used different encoding too. Esp for NASA stuff
   much equipment tended to be one-off, and docs
   seem hard to find.

   So far we don't have any Trekkie storage media - like
   holocrystals or whatever. You CAN burn 1's and 0s into
   diamond film at very high density, but the equipment
   to read and write is insane and 'optical'. Do see
   progress in boron nitride electronics, but the support
   circuitry will be the weak point unless it too can
   all be done in BN.

   So, until we have a read/write 'chip' that can stand
   2000 years near Jupiter or a nasty black hole ...
   REPLICATE.

   Problem - replication requires EFFORT and ATTENTION.
   The older the data, the less you see of either even
   though, ultimately, that very old info will be more
   coveted. CAN something 'electronic' be made that
   someone/thing can dig up 25,000 years, or 250,000
   years, from now and figure out how to read ?

[toc] | [prev] | [next] | [standalone]


Page 1 of 2  [1] 2  Next page →

Back to top | Article view | comp.os.linux.misc


csiph-web