disParity » General Discussion

Not enough disk space error

(5 posts)
  • Started 3 months ago by romwarrior
  • Latest reply from romwarrior

  1. romwarrior
    Member

    I think this is a different issue than the other disk space thread, but if not you can delete this.

    I am trying to update a set that I have been updating fine for a few months now. During the last update it would not add one of my files to parity (a 40GB single-file rip of a Blu-ray that I own). The exact error is "Error writing parity data: There is not enough space on the disk."

    However, my parity disk is the biggest disk. Here is what Windows shows:

    Drive - Capacity - Free Space

    Media1 - 1397.26GB - 22.99GB
    Media2 - 1397.26GB - 60.34GB
    Media3 - 1397.26GB - 220.42GB
    Media4 - 1863.01GB - 202.76GB
    Media5 - 1863.01GB - 48.41GB
    Parity - 1863.01GB - 28.23GB

    Right now the file is on the Media4 drive but it was originally on the Media5 drive.

    I am running just a basic WinXP Pro install. I have moved the offending file to a different media drive and get the same error. Windows has no problem moving the file so I assume it is not a file problem. Any ideas? I'd rather not recreate the parity info as that takes about 40 hours.

    Posted 3 months ago #

  2. Roland
    Key Master

    I believe this error is occurring when disParity is trying to write the 40GB of modified parity data to a temp file during the update, before it copies the final data back to the parity drive. So the drive that is running out of space in this case is the drive that contains the temp data, not the parity drive.

    By default, disParity writes temp date to its own folder, so this drive would be whatever drive disParity is installed on. You can override the temp location to whatever you like in the config.txt file:

    temp=D:\Some\Folder\disParityTemp\

    Try setting temp to a drive that you know has more than 40GB free. It can be one of the protected drives, but for performance reasons I wouldn't recommend that unless you have no other choice.

    Posted 3 months ago #

  3. romwarrior
    Member

    Thanks, Roland. I freed up some space on my C drive and the update went through with no errors. However, the free space numbers I listed in my first post have not changed at all after the update. So my parity drive has 20 GB more data on it than any of my media drives. I know there's an overhead but I didn't think there was that much. One of my drives has about 18000 audio files, but the rest have a considerably fewer number of files.

    So should I be concerned that the free space did not change at all with the inclusion of a 40 GB file? I did delete some files before adding the file, but those went through on a separate update. Does disParity reserve disk space? What about the 20 GB more data on the parity drive? Anything to be worried about?

    Posted 3 months ago #

  4. Roland
    Key Master

    The amount of parity used is only determined by the largest drive in your array... or rather, the drive with the largest amount of used space. So in your case, the media5 drive is the one that is determining that mount of parity used. Even if the other 4 drives were empty, since media5 is almost full, the parity drive would still also be almost full. Since you added the 40GB file on the media4 drive, it makes sense that no additional parity space was used by that file, since it was able to combine the data of that file with parity data already in use.

    The extra 20GB used on your parity drive is probably due to fragmentation; if you've done a few rounds of deleting/moving/editing files, especially large ones, that could easily chew up an additional 20GB. DisParity will attempt to re-use that fragmented space when it can, but it can't always fit a large file into a small hole. Eventually, with enough updates, you could run out of parity space (especially if you add more data to media5.) If that happens, unfortunately right now the only thing you can do is re-create the parity from scratch, which will remove the fragmentation.

    Posted 3 months ago #

  5. romwarrior
    Member

    Thanks for the info, Roland.

    Posted 3 months ago #

RSS feed for this topic

Reply

You must log in to post.