Parity disk on snapraid if more full than data disks

    • Parity disk on snapraid if more full than data disks

      Hi,

      my parity disk is much more full than the data disk in my snapraid configuration. The difference is about 1 TiB with 3.58 TiB drives. From what I understand about Snapraid this should not be the case. Is there any way to find out what is going on? It might be that there is some old data on the parity drive from an OMV configuration I was running before the current.

      The filesytems currently look like this:

      https://www.dropbox.com/s/1q84qmsqg8lzt8r/OMV-Filesystems_TiredHornet.JPG?dl=0

      wdrperry it the parity drive and wdrbety and wdratlan are the data drives.

      My Snapraid configuration:

      Source Code

      1. ​# this file was automatically generated from
      2. # OpenMediaVault Kralizec 1.19
      3. # and 'openmediavault-snapraid'
      4. block_size 256
      5. autosave 0
      6. #####################################################################
      7. # OMV-Name: pv_wdrperry Drive Label: wdrperry
      8. parity /media/19c5b4f6-fe28-4b36-806a-eb44d0c02035/snapraid.parity
      9. #####################################################################
      10. # OMV-Name: dv_wdrbetty Drive Label: wdrbetty
      11. content /media/0ac8fcaa-903a-4333-9f8f-c3fe6c23a610/snapraid.content
      12. disk dv_wdrbetty /media/0ac8fcaa-903a-4333-9f8f-c3fe6c23a610
      13. #####################################################################
      14. # OMV-Name: dv_wdratlan Drive Label: wdratlan
      15. content /media/df804a1e-2981-4e19-936a-c05aa41a6336/snapraid.content
      16. disk dv_wdratlan /media/df804a1e-2981-4e19-936a-c05aa41a6336
      17. exclude *.bak
      18. exclude *.unrecoverable
      19. exclude /tmp/
      20. exclude lost+found/
      21. exclude .content
      22. exclude aquota.group
      23. exclude aquota.user
      24. exclude snapraid.conf*
      Display All


      my snapraid status:

      Brainfuck Source Code

      1. ​Self test...
      2. Loading state from /media/0ac8fcaa-903a-4333-9f8f-c3fe6c23a610/snapraid.content...
      3. Using 616 MiB of memory.
      4. SnapRAID status report:
      5. Files Fragmented Excess Wasted Used Free Use Name
      6. Files Fragments GB GB GB
      7. 60334 117 417 1170.7 1864 902 67% dv_wdrbetty
      8. 71403 89 438 1173.6 1784 979 64% dv_wdratlan
      9. --------------------------------------------------------------------------
      10. 131737 206 855 2344.3 3649 1881 66%
      11. 15%|*
      12. |*
      13. |*
      14. |*
      15. |* * *
      16. |* * * +
      17. |* * * * * *
      18. 7%|* * * * * * + + +
      19. |* * * * * * * * *
      20. |* * * * * * * * *
      21. |* * * * * * * * *+
      22. |* * * * * * * * **
      23. |* * * * * * * * **
      24. |* * * * * * * * **
      25. 0%|*_______________*_*__________________*_____+________________*_*_*_*_**
      26. 6 days ago of the last scrub 5
      27. The oldest block was scrubbed 6 days ago, the median 5, the newest 5.
      28. No sync is in progress.
      29. No rehash is in progress or needed.
      30. No error detected.
      Display All
      Supermicro X9SCM-F, Intel Pentium G2030, 8GB DDR3 1600MHz, Toshiba 64 GB SSD, 3x 4TB WD40EFRX (Snapraid)
    • Examine the parity drive contents with ls. The parity file is:

      snapraid.parity

      You may also have the following files, but they are minuscule in size compared to the parity file.

      snapraid.content
      aquota.user
      aquota.group

      If you have other large files there, find out what they are and if you want to keep them or not.
      OMV 4.x - ASRock Rack C2550D4I - 16GB ECC - Silverstone DS380
    • Okay I did that and found two files called:

      parity.file
      parity.file.lock

      The first is about 1 TB in size and both have not be altered for more than 1.5 years so I suppose they belong to the old configuration. Anyway to find out if I need these files? Or does anyone know these kind of files?
      Supermicro X9SCM-F, Intel Pentium G2030, 8GB DDR3 1600MHz, Toshiba 64 GB SSD, 3x 4TB WD40EFRX (Snapraid)

      The post was edited 1 time, last by TiredHornet ().

    • I finally got around to fixing this problem. I asked in the SnapRaid forum and was told to check the snapraid.conf file for any mention of "parity.file" and "parity.file.lock". Since they were not in the config file. it was safe to delete them using - rm -

      Source Code

      1. rm parity.file
      2. rm parity.file.lock

      Now all drives included in my snapraid setup have the same amount of disk space used.
      Supermicro X9SCM-F, Intel Pentium G2030, 8GB DDR3 1600MHz, Toshiba 64 GB SSD, 3x 4TB WD40EFRX (Snapraid)