Invalid state: not enough usable space for parity!

This message usually tells of configuration or data issues.

Configuration issues
Here are some things to keep in mind:

  • Your parity drives must be larger than your largest data drive.
  • When spanning your data drives (if you are), ensure than the combined space is less or equal to the parity space.
  • On Windows, verify that your OS is not putting VSS (Volume Shadow Copy Service) data or system restore data on your PPU. This is not usually obvious as that type of data is hidden.

Silent data changes
If the above checklist does not apply to your case, here is what you can try (starting with FlexRAID 2.0 Update 11):

  1. Elevate the Change Detection Level. The default is 0. Set it to 1 for medium or 2 for high (high will greatly increase processing time)
  2. Run the Update task

If the operation succeeds, this means that you have silent data changes, which is something you should take very seriously.
A silent data change means that the content of a file changed without its modification timestamp being updated.
If you set the Change Detection Level to medium (this is not necessary if you had it at high), it is recommended that you run the Validate task and take note of all the files marked as changed.
Then, touch the flagged files to update their timestamps so that they are re-processed:
- On Linux use the touch command, on Windows download http://download.openegg.org/temp/touch-for-windows.zip
- Run the Update operation again

Be Sociable, Share!

Revisions

8 Responses to “Invalid state: not enough usable space for parity!”

  1. Dohm May 17, 2012 at 5:35 AM #

    Why do I HAVE to use a drive for parity ? And why does it have to be formatted?

    • Brahim May 17, 2012 at 9:27 AM #

      You do not have to make use of a parity drive. However, without parity, you will have not data protection.
      To configure a pool only configuration (with RAID), use the Expert option.

      The drives have to be formatted because FlexRAID implements RAID over filesystem (RAID-F).
      So, you pick your favorite filesystem and format your drives with it and then FlexRAID takes over.
      The beauty of RAID of filesystem is that your drives are readable in any system that can read the filesystem you chose.

  2. ali77 May 17, 2012 at 12:08 PM #

    Looking at this requirement: “When spanning your data drives (if you are), ensure than the combined space is less or equal to the parity space.”

    If I have four 2TB drives, 3 for data and one for parity, if I pool the 3 data drives, i will most likely get errors? If this is not the recommended setup? What would you suggest?

    • admin May 19, 2012 at 4:25 PM #

      You would not be spanning in your case. Each one of your data drive would be its own DRU.

      • Ali77 May 19, 2012 at 6:26 PM #

        So no pooling. 3 DRUs and one parity drive. How many disks can fail without losing anything?

  3. Ali77 May 19, 2012 at 6:18 PM #

    To be completely sure, is spanning the same thing is pooling? i was planning on pooling actually.

  4. Mark September 24, 2012 at 1:33 PM #

    I have been running into issues with Snapshot RAID and now RealTime RAID with the Parity Space running low…
    How much smaller does each DRU have to be compared to the PPU?
    I have the partitions on my DRU already set to be about 30GB smaller per DRU than the PPU on my last try now and because of this some hard drives I added into the RTR had only a few 100 MB free and after I created the RTR I moved data off the pool to free up space and back into the pool (I have set it to Auto-Space-Priority…that seemed the most logical choice to avoid parity space issues) and I am having issues again that I can’t Reconcile because it says “Out of real-time parity space error”.
    DRU1 has 50.55GB free out of 2.6978125TB, DRU2 has 731.17GB free of 894.89GB and the PPU has only 250.8MB free of 2.73TB.
    So now I am looking at he the xth re-creation that’ll take 14+ hours again.
    So my questions:
    How much smaller do the DRUs have to be compared to the PPU?
    Can I make the partitions smaller and then fill up the drives fully?
    How do I stop the PPU from filling up no matter if I move files onto or off the pool?

  5. AJ December 10, 2012 at 9:49 PM #

    I have the following setup:
    DRU1 (3TB) + DRU2 (3TB) + PPU1 (500GB+1TB+1.5TB)
    However, I keep getting the error above. I have disabled shadow copy on every drive. I even reduced the partitions of each 3TB drive by 100GB. I also tried this “detection level” thing. But I still get the “not enough parity space” problem. Can anyone help?

Leave a Reply

12 + 8 =