Slashdot Mirror


One Way To Save Digital Archives From File Corruption

storagedude points out this article about one of the perils of digital storage, the author of which "says massive digital archives are threatened by simple bit errors that can render whole files useless. The article notes that analog pictures and film can degrade and still be usable; why can't the same be true of digital files? The solution proposed by the author: two headers and error correction code (ECC) in every file."

5 of 257 comments (clear)

  1. Sun Microsystems..... zfs..... by HKcastaway · · Score: 3, Insightful

    ZFS.

    Next topic....

  2. Re:To much reinvention by paradxum · · Score: 5, Insightful

    It already exists, it's called ZFS on solaris boxxen. Each block uses ECC, it can correct itself on each read, and generally can indicate a failing disk. This truly is the filesystem every other one is playing catchup with.

  3. Re:What files does a single bit error destroy? by Rockoon · · Score: 5, Insightful

    Most modern compression formats will not tolerate any errors. With LZ a single bit error could propagate over a long expanse of the uncompressed output, while with Arithmetic encoding the remainder of the file following the single bit error will be completely unrecoverable.

    Pretty much only the prefix-code style compression schemes (Huffman for one) will isolate errors to short sgements, and then only if the compressor is not of the adaptive variety.

    --
    "His name was James Damore."
  4. Re:To much reinvention by MrNaz · · Score: 5, Insightful

    Ahem. RAID anyone? ZFS? Btrfs? Hello?

    Isn't this what filesystem devs have been concentrating on for about 5 years now?

    --
    I hate printers.
  5. Re:To much reinvention by bertok · · Score: 3, Insightful

    If this type of thing is implemented at the file level every application is going to have to do its own thing. That means to many implementations most of which wont be very good or well tested. It also means applications developers will have to be busy slogging though error correction data in their files rather than the data they actually wanted to persist for their application. I think the article offers a number of good ideas but it would be better to do most of them at the filesystem and perhaps some at the storage layer.

        Also if we can present the same logical file when read to the application even if every 9th byte is parity on the disk that is a plus because it means legacy apps can get the enhanced protection as well.

    Precisely. This is what things like torrents, RAR files with recovery blocks, and filesystems like ZFS are for: so every app developer doesn't have to roll their own, badly.