SnapRAID - Outofparity

luckyzor · 13. Juli 2022

Hello,

I have this config on snapRAID:

3 x 4 TB for data

1 x 4 TB for parity

status of the filesystem:

When running the sync on snapRAID I got: outofparity disk space

Code

Self test...
Loading state from /srv/dev-disk-by-uuid-33b0457f-fc58-43c6-817b-42e1320157ec/snapraid.content...
Scanning disk data1...
Scanning disk data2...
Scanning disk data3...
WARNING! Ignoring special 'block-device' file '/srv/dev-disk-by-uuid-6dd5a9d3-7e22-40bc-99f9-c4ae68440b98/docker/volumes/backingFsBlockDev'
Using 1094 MiB of memory for the file-system.
Initializing...
Resizing...
Failed to allocate all the required parity space. You miss 99209183232 bytes.

Should I delete the snapraid.parity file and resync again?

Concerning the snapRAID, what are the best cronjobs to be sure everything is ok on SNAPRAID because I have this on the snaRAID status:

Code

Self test...
Loading state from /srv/dev-disk-by-uuid-33b0457f-fc58-43c6-817b-42e1320157ec/snapraid.content...
Using 832 MiB of memory for the file-system.
SnapRAID status report:

   Files Fragmented Excess  Wasted  Used    Free  Use Name
            Files  Fragments  GB      GB      GB
   90747      91     145    15.7    3428     549  86% data1
   88414      67     106    16.2    3425     551  86% data2
  103507     112     168    18.4    3364     610  84% data3
 --------------------------------------------------------------------------
  282668     270     419    50.4   10218    1712  85%


 78%|*                                                                     
    |*                                                                     
    |*                                                                     
    |*                                                                     
    |*                                                                     
    |*                                                                     
    |*                                                                     
 39%|*                                                                     
    |*                                                                     
    |*                                                                     
    |*                                                                     
    |*                                                                     
    |*                                                                    *
    |*       o                                                            *
  0%|*o______o____________________________________________________________*
    65                    days ago of the last scrub/sync                 0

The oldest block was scrubbed 65 days ago, the median 65, the newest 0.

No sync is in progress.
The 9% of the array is not scrubbed.
You have 138629 files with zero sub-second timestamp.
Run the 'touch' command to set it to a not zero value.
No rehash is in progress or needed.
No error detected.

END OF LINE

Alles anzeigen

thank you for your help

luckyzor · 14. Juli 2022

Anyone?

gderf · 14. Juli 2022

The requirement for the size of a parity drive is actually a bit more than the size of the largest data drive in the array. The first thing to try is to be sure you don't have the standard 5% of the drive space set aside as reserved blocks. I don't know if OMV formats drives with the 5% reserved or not but you can check and see.

luckyzor · 14. Juli 2022

Zitat von gderf

The requirement for the size of a parity drive is actually a bit more than the size of the largest data drive in the array. The first thing to try is to be sure you don't have the standard 5% of the drive space set aside as reserved blocks. I don't know if OMV formats drives with the 5% reserved or not but you can check and see.

how can I check that?

johnvick · 14. Juli 2022

Not sure what the answer to that question is but this is from the SnapRAID manual:

In Linux, to get more space for the parity, it's recommended to format the parity file-system with the -m 0 -T largefile4 options. Like:

Code

mkfs.ext4 -m 0 -T largefile4 DEVICE

On a 8 TB disk you can save about 400 GB. This is also expected to be as fast as the default, if not faster.

luckyzor · 14. Juli 2022

Zitat von johnvick
Not sure what the answer to that question is but this is from the SnapRAID manual:

In Linux, to get more space for the parity, it's recommended to format the parity file-system with the -m 0 -T largefile4 options. Like:
Code
mkfs.ext4 -m 0 -T largefile4 DEVICE
On a 8 TB disk you can save about 400 GB. This is also expected to be as fast as the default, if not faster.

if I do that the parity disk will be formated, no risk of losing any data?

johnvick · 14. Juli 2022

You'll lose the parity info but gain disk space, assuming the parity drive was formatted in standard ext4 manner first time. You can then recreate the parity but you're taking a risk if a data disk fails during parity recreation, unless the data is backed up elsewhere?

gderf · 14. Juli 2022

There is no need to format the disk and lose all the data. Use the tune2fs program.

https://ma.ttias.be/change-res…t3-ext4-filesystem-linux/

luckyzor · 15. Juli 2022

Zitat von gderf

There is no need to format the disk and lose all the data. Use the tune2fs program.

https://ma.ttias.be/change-res…t3-ext4-filesystem-linux/

I'm using XFS.

I deleted some files (500GB) I don't need anymore and the sync worked out.

now my 2nd question:

Concerning the snapRAID, what are the best cronjobs to be sure everything is ok on SNAPRAID

is this script working on OMV6?

Externer Inhalt gist.github.com

Inhalte von externen Seiten werden ohne Ihre Zustimmung nicht automatisch geladen und angezeigt.

Durch die Aktivierung der externen Inhalte erklären Sie sich damit einverstanden, dass personenbezogene Daten an Drittplattformen übermittelt werden. Mehr Informationen dazu haben wir in unserer Datenschutzerklärung zur Verfügung gestellt.

johnvick · 15. Juli 2022

There's a script already in OMV6 and you'll find similar elsewhere.

auanasgheps · 17. Juli 2022

luckyzor use my script (link in the signature). As far as I know is the best, simply because many are broken or not updated.

I know it's not nice to say but: my friend you need new drives, you're almost out of space! That red bar...

luckyzor · 18. Juli 2022

Zitat von johnvick

There's a script already in OMV6 and you'll find similar elsewhere.

where can I find that script on OMV6?

gderf · 19. Juli 2022

Zitat von luckyzor

where can I find that script on OMV6?

/usr/sbin/omv-snapraid-diff

luckyzor · 19. Juli 2022

Zitat von gderf

/usr/sbin/omv-snapraid-diff

is this a good script for what we need with Snapraid?

diff / sync / scrub?

gderf · 19. Juli 2022

I don't use it. I use this one with some changes:

Externer Inhalt gist.github.com

Inhalte von externen Seiten werden ohne Ihre Zustimmung nicht automatisch geladen und angezeigt.

Durch die Aktivierung der externen Inhalte erklären Sie sich damit einverstanden, dass personenbezogene Daten an Drittplattformen übermittelt werden. Mehr Informationen dazu haben wir in unserer Datenschutzerklärung zur Verfügung gestellt.

Changes:

1) Install the discount package.

2) Make this change in line 432 (change python -m markdown to markdown)

#$MAIL_BIN -a 'Content-Type: text/html' -s "$SUBJECT" "$EMAIL_ADDRESS" < <(python -m markdown $TMP_OUTPUT)

$MAIL_BIN -a 'Content-Type: text/html' -s "$SUBJECT" "$EMAIL_ADDRESS" < <(markdown $TMP_OUTPUT)

johnvick · 19. Juli 2022

The inbuilt script can be configured from the SnapRAID plugin. I modified my one slightly as doing 100% scrub takes a long time, longer than my device is powered up daily.

auanasgheps · 19. Juli 2022

Zitat von luckyzor

is this a good script for what we need with Snapraid?

diff / sync / scrub?

As I said above, if you want more features you can use my script linked in the signature.

johnvick · 20. Juli 2022

luckyzor

Trying your script I get this:

Please update your config file to the latest version. The current file is not compatible with this script!

/bin/python3: No module named markdown

I got the latest zip from Github.

apt install python-markdown does not work but

apt install python3-markdown does, but still an error message minus the python bit.

auanasgheps · 20. Juli 2022

Zitat von johnvick

luckyzor

Trying your script I get this:

Please update your config file to the latest version. The current file is not compatible with this script!
/bin/python3: No module named markdown

I got the latest zip from Github.
<span style="font-family:Arial, Helvetica, sans-serif;"><br></span>
apt install python-markdown does not work but
apt install python3-markdown does, but still an error message minus the python bit.

Alles anzeigen

The script is not updated for Debian 11 - actually is very old.

You can try my script instead, it won't show an error.

johnvick · 20. Juli 2022

Sorry my mistake it was the auanasgheps script I tried and it gave the above error messages. OMV6.

SnapRAID - Outofparity

Jetzt mitmachen!

Tags