Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.os.linux.misc > #95789
| From | "Carlos E.R." <robin_listas@es.invalid> |
|---|---|
| Newsgroups | comp.os.linux.misc |
| Subject | Re: Optical Disc Long Term Storage |
| Date | 2026-11-19 20:42 +0100 |
| Organization | Tebibyte_Retro_Gaming |
| Message-ID | <t204tmx2ek.ln2@Telcontar.valinor> (permalink) |
| References | (3 earlier) <Te-cnfkEp-0g82P3nZ2dnZfqn_idnZ2d@giganews.com> <slrn11fsug1.hg1.spamtrap42@one.localnet> <18e97334329955ad$2731$3691736$802601b3@news.usenetexpress.com> <ukHLS.587$3zk7.558@fx17.iad> <18e988812fc0b5b6$1548$1163114$802601b3@news.usenetexpress.com> |
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🇪🇺;
Back to comp.os.linux.misc | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
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
csiph-web