[HowTo] SnapRAID in OMV

Zitat von ryecoaaron

All of your questions are about @Solo0815 diff script. I don't use it or snapraid. So, I will try to answer the best I can. Everything done in Windows should work on the plugin. I refer to the snapraid manual a lot when working on this plugin.

It is automatic once you start it. So, you just need to start it at boot.

Scrub frequency is how often it runs since the script is always run. It is meant to be a scrub because you don't need a script to run sync. sync can be done with a scheduled job. All of the paraments in the diff script frame are used in the script and nowhere else. The settings are defaulted to whatever solo0815 uses.

Scrub percentage is the -p parameter. Once again, it is just a default. Maybe solo isn't using it on large files so it is fast.

Alles anzeigen

Thank you for your help. Based on the comments at the beginning of the script, it sounds like it will automatically run a sync for me (unless too many files are missing, at which point I am alerted). So in that case, I wouldn't need to schedule a sync in the Scheduled Jobs, because I can choose how often to run the script by editing "Scrub Frequency" and the Sync will happen automatically. Also, is there anything else I need to do in order to make it start at boot? Or does this happen automatically as long as the plugin is enabled?

Snapraid hat in der 2.1 OMV Version so seine Problem in Kombination mit den Unionfilesystem.
Ich habe 2 neue Platten im Unionfilesystem (Anfs) hinzugefügt und wollte diese dann in Snapraid syncen (1 Parity, 1 Data) - der Sync brach jedes Mal mit ein "Kill" Error ab. In der Syslog sah man nur einen ewig langen Kernel Fehler.

Ich habe daraufhin Snapraid neuinstalliert und die alten Sicherungs Daten von Snapraid entfernt um das ganze neu syncen zu lassen. Das hat funktioniert, hat aber 1 Verzeichnis nicht lesen wollen. Daraufhin fiel mir auf dass das Anfs Verzeichnis (da wo alle Daten von Unionfilesystem zusammengelisten werden) komplett "leer" war und dass der betroffene Ordner auf einer der Platten nur noch als "Lesbar" markiert war, aber sonst ging nix mehr. Weder löschen, noch Rechte ändern usw.

Ich habe dann OMV neugestartet und daraufhin war nun alles wieder da und auch das besagte Verzeichnis. Das syncen klappt nun komplett.
Ich vermute mal das UFS da wohl ins Schwitzen kommt wenn da plötzlich große neue snapraid.content Dateien in jeden seiner zugewiesenen Platten erscheinen. Wieso auch immer.

....
Jul  6 20:38:42 NAS-PC kernel: [87824.289379] Out of memory: Kill process 12608 (snapraid) score 680 or sacrifice child
Jul  6 20:38:42 NAS-PC kernel: [87824.289433] Killed process 12608 (snapraid) total-vm:8874212kB, anon-rss:4433400kB, file-rss:604kB
Jul  6 20:38:42 NAS-PC kernel: [87824.289591] snapraid: page allocation failure: order:0, mode:0x2005a
Jul  6 20:38:42 NAS-PC kernel: [87824.289595] Pid: 12608, comm: snapraid Tainted: G         C O 3.2.0-4-amd64 #1 Debian 3.2.68-1+deb7u2
Jul  6 20:38:42 NAS-PC kernel: [87824.289597] Call Trace:
Jul  6 20:38:42 NAS-PC kernel: [87824.289603]  [<ffffffff810b9480>] ? warn_alloc_failed+0x11f/0x134
Jul  6 20:38:42 NAS-PC kernel: [87824.289607]  [<ffffffff8134fd7c>] ? _cond_resched+0x7/0x1c
Jul  6 20:38:42 NAS-PC kernel: [87824.289610]  [<ffffffff810bc1b1>] ? __alloc_pages_nodemask+0x705/0x7ab
Jul  6 20:38:42 NAS-PC kernel: [87824.289626]  [<ffffffffa01244f9>] ? start_this_handle+0x430/0x448 [jbd2]
Jul  6 20:38:42 NAS-PC kernel: [87824.289630]  [<ffffffff810e5ccb>] ? alloc_pages_current+0xc7/0xe4
Jul  6 20:38:42 NAS-PC kernel: [87824.289634]  [<ffffffff810b5cbd>] ? grab_cache_page_write_begin+0x4f/0xae
Jul  6 20:38:42 NAS-PC kernel: [87824.289643]  [<ffffffffa013b982>] ? ext4_da_write_begin+0x11a/0x1e0 [ext4]
Jul  6 20:38:42 NAS-PC kernel: [87824.289650]  [<ffffffffa013d83c>] ? ext4_da_write_end+0x1f1/0x232 [ext4]
Jul  6 20:38:42 NAS-PC kernel: [87824.289653]  [<ffffffff810b57db>] ? generic_file_buffered_write+0x10f/0x259
Jul  6 20:38:42 NAS-PC kernel: [87824.289659]  [<ffffffff810b6618>] ? __generic_file_aio_write+0x248/0x278
Jul  6 20:38:42 NAS-PC kernel: [87824.289662]  [<ffffffff81036638>] ? should_resched+0x5/0x23
Jul  6 20:38:42 NAS-PC kernel: [87824.289665]  [<ffffffff810b66a5>] ? generic_file_aio_write+0x5d/0xb5
Jul  6 20:38:42 NAS-PC kernel: [87824.289672]  [<ffffffffa0136bd7>] ? ext4_file_write+0x1e4/0x235 [ext4]
Jul  6 20:38:42 NAS-PC kernel: [87824.289678]  [<ffffffffa0136bd4>] ? ext4_file_write+0x1e1/0x235 [ext4]
Jul  6 20:38:42 NAS-PC kernel: [87824.289681]  [<ffffffff810fae68>] ? do_sync_write+0xb4/0xec
Jul  6 20:38:42 NAS-PC kernel: [87824.289685]  [<ffffffff811656d1>] ? security_file_permission+0x16/0x2d
Jul  6 20:38:42 NAS-PC kernel: [87824.289687]  [<ffffffff810fb559>] ? vfs_write+0xa2/0xe9
Jul  6 20:38:42 NAS-PC kernel: [87824.289690]  [<ffffffff810fb736>] ? sys_write+0x45/0x6b
Jul  6 20:38:42 NAS-PC kernel: [87824.289692]  [<ffffffff813561b2>] ? system_call_fastpath+0x16/0x1b
Jul  6 20:38:42 NAS-PC kernel: [87824.289694] Mem-Info:
Jul  6 20:38:42 NAS-PC kernel: [87824.289695] Node 0 DMA per-cpu:
Jul  6 20:38:42 NAS-PC kernel: [87824.289697] CPU    0: hi:    0, btch:   1 usd:   0
Jul  6 20:38:42 NAS-PC kernel: [87824.289699] CPU    1: hi:    0, btch:   1 usd:   0
Jul  6 20:38:42 NAS-PC kernel: [87824.289700] CPU    2: hi:    0, btch:   1 usd:   0
Jul  6 20:38:42 NAS-PC kernel: [87824.289702] CPU    3: hi:    0, btch:   1 usd:   0
Jul  6 20:38:42 NAS-PC kernel: [87824.289703] Node 0 DMA32 per-cpu:
Jul  6 20:38:42 NAS-PC kernel: [87824.289705] CPU    0: hi:  186, btch:  31 usd:   0
Jul  6 20:38:42 NAS-PC kernel: [87824.289707] CPU    1: hi:  186, btch:  31 usd:   0
Jul  6 20:38:42 NAS-PC kernel: [87824.289708] CPU    2: hi:  186, btch:  31 usd:   0
Jul  6 20:38:42 NAS-PC kernel: [87824.289710] CPU    3: hi:  186, btch:  31 usd:   0
Jul  6 20:38:42 NAS-PC kernel: [87824.289711] Node 0 Normal per-cpu:
Jul  6 20:38:42 NAS-PC kernel: [87824.289713] CPU    0: hi:  186, btch:  31 usd:   0
Jul  6 20:38:42 NAS-PC kernel: [87824.289714] CPU    1: hi:  186, btch:  31 usd:   0
Jul  6 20:38:42 NAS-PC kernel: [87824.289716] CPU    2: hi:  186, btch:  31 usd:   0
Jul  6 20:38:42 NAS-PC kernel: [87824.289717] CPU    3: hi:  186, btch:  31 usd:   0
Jul  6 20:38:42 NAS-PC kernel: [87824.289721] active_anon:993612 inactive_anon:198683 isolated_anon:0
Jul  6 20:38:42 NAS-PC kernel: [87824.289722]  active_file:6303 inactive_file:55056 isolated_file:32
Jul  6 20:38:42 NAS-PC kernel: [87824.289723]  unevictable:563 dirty:55073 writeback:0 unstable:0
Jul  6 20:38:42 NAS-PC kernel: [87824.289723]  free:25174 slab_reclaimable:17098 slab_unreclaimable:13952
Jul  6 20:38:42 NAS-PC kernel: [87824.289724]  mapped:639738 shmem:899 pagetables:8236 bounce:0
Jul  6 20:38:42 NAS-PC kernel: [87824.289726] Node 0 DMA free:15360kB min:128kB low:160kB high:192kB active_anon:0kB inactive_anon:0kB active_file:0kB inactive_file:0kB unevictable:0kB isolated(anon):0kB isolated(file):0kB present:15136kB mlocked:0kB dirty:0kB writeback:0kB mapped:0kB shmem:0kB slab_reclaimable:0kB slab_unreclaimable:0kB kernel_stack:0kB pagetables:0kB unstable:0kB bounce:0kB writeback_tmp:0kB pages_scanned:0 all_unreclaimable? yes
Jul  6 20:38:42 NAS-PC kernel: [87824.289734] lowmem_reserve[]: 0 3216 7735 7735
Jul  6 20:38:42 NAS-PC kernel: [87824.289737] Node 0 DMA32 free:45936kB min:28044kB low:35052kB high:42064kB active_anon:2525392kB inactive_anon:553052kB active_file:10412kB inactive_file:95048kB unevictable:0kB isolated(anon):0kB isolated(file):0kB present:3293764kB mlocked:0kB dirty:95112kB writeback:20kB mapped:35524kB shmem:56kB slab_reclaimable:9776kB slab_unreclaimable:2868kB kernel_stack:88kB pagetables:8408kB unstable:0kB bounce:0kB writeback_tmp:0kB pages_scanned:163756 all_unreclaimable? yes
Jul  6 20:38:42 NAS-PC kernel: [87824.289747] lowmem_reserve[]: 0 0 4519 4519
Jul  6 20:38:42 NAS-PC kernel: [87824.289749] Node 0 Normal free:39400kB min:39404kB low:49252kB high:59104kB active_anon:1449056kB inactive_anon:241680kB active_file:14800kB inactive_file:125176kB unevictable:2252kB isolated(anon):0kB isolated(file):128kB present:4627820kB mlocked:2252kB dirty:125180kB writeback:0kB mapped:2523428kB shmem:3540kB slab_reclaimable:58616kB slab_unreclaimable:52940kB kernel_stack:2304kB pagetables:24536kB unstable:0kB bounce:0kB writeback_tmp:0kB pages_scanned:266069 all_unreclaimable? yes
Jul  6 20:38:42 NAS-PC kernel: [87824.289758] lowmem_reserve[]: 0 0 0 0
Jul  6 20:38:42 NAS-PC kernel: [87824.289761] Node 0 DMA: 0*4kB 0*8kB 0*16kB 0*32kB 0*64kB 0*128kB 0*256kB 0*512kB 1*1024kB 1*2048kB 3*4096kB = 15360kB
Jul  6 20:38:42 NAS-PC kernel: [87824.289767] Node 0 DMA32: 118*4kB 363*8kB 353*16kB 259*32kB 139*64kB 34*128kB 21*256kB 2*512kB 1*1024kB 2*2048kB 1*4096kB = 46176kB
Jul  6 20:38:42 NAS-PC kernel: [87824.289774] Node 0 Normal: 299*4kB 1258*8kB 530*16kB 182*32kB 139*64kB 8*128kB 1*256kB 0*512kB 0*1024kB 0*2048kB 1*4096kB = 39836kB
Jul  6 20:38:42 NAS-PC kernel: [87824.289780] 124717 total pagecache pages
Jul  6 20:38:42 NAS-PC kernel: [87824.289782] 61913 pages in swap cache
Jul  6 20:38:42 NAS-PC kernel: [87824.289784] Swap cache stats: add 18841236, delete 18779323, find 12817172/14007691
Jul  6 20:38:42 NAS-PC kernel: [87824.289785] Free swap  = 0kB
Jul  6 20:38:42 NAS-PC kernel: [87824.289786] Total swap = 4789244kB
Jul  6 20:38:42 NAS-PC kernel: [87824.315045] 2024944 pages RAM
Jul  6 20:38:42 NAS-PC kernel: [87824.315047] 693420 pages reserved
Jul  6 20:38:42 NAS-PC kernel: [87824.315049] 73919 pages shared
Jul  6 20:38:42 NAS-PC kernel: [87824.315050] 1238708 pages non-shared

Hi,

So do we have to add snapraid-diff in the schedule tasks?
Because today I have a 7 day frequency, but nothing happens in the syslog or mail since the 17 july.
Thanks

Hi,

Is it possible to extend the snapraid-diff script to accept a custom email recepient?
I'd like to have the result of snapraid sent to Pushbullet, but I don't want every notification from OMV sent there, so I can't set pushbullet as recepient in the generic notifications setup.

I'm quite sure I know where to tweak the script + config, but I don't know how to get the tweaks merged into the plugin..

Hi All,

I've been (poorly) using snapraid for a while now, running regular sync through a cron job. But I realized I need to get set up using the diff script today, as last night's sync ran after I mass re-nammed an entire series of TV (i.e. over 100 deleted files) -- this could cause some problems in the future.

I was reading through the post about the two places the omv-snapraid-diff script was (/usr/local/bin) and (/usr/sbin) -- however, there is not a file by that name in either location. /usr/local/bin is empty -- /usr/sbin has a lot in it, but nothing relating to snapraid that I could see.

I'm running:
omv 2.1.13
openmediavault-snapraid 1.5 plugin

I can see where to change the diff script options in the gui, but cannot find this file to try running manually and get the error (No such file or directory) when trying to run from cron/scheduled jobs. Do I need to download the script manually and place in one of these directories? I don't see the file on the github omv-snapraid-scrips, so am assuming it should have been created automatically by the plugin?

Any help would be appreciated!

Zitat von ryecoaaron

omv-snapraid-diff is in /usr/sbin/

I don't see it in my /usr/sbin folder -- in that directory I've tried ls and don't see it, and have tried running it (omv-snapraid-diff and ./omv-snapraid-diff) but it still comes back "No such file or directory."

What's the best way for me to get it back? Can I download it from somewhere, or maybe should I delete my info from snapraid, uninstall the plugin, and reinstall the plugin?

Thanks in advance for the suggestions!

Got it, thank you ryecoaaron!

Need some advises.
I'm currently using soft RAID10, should I use Snap Raid or USB Backup for my data backup?
I read both guides, and they're looking similar...
Thanks.

Hi,

I played a lil bit with snapraid and now i would like to use it for real. But when i try to add my new HDDs, then it says that the old hdds are missing. A look into the snapraid.conf: the old HDDs are still there. But i deleted them out of snapraid?

When i try to name the new HDDs to the testing names, make snapraid --force-uuid sync, it says "too many files changes. Try --force-empty sync. When i do this, it says "too many uuids have changed, try --force-uuid sync....

How can i delete the old testing HDDs from the snapraid.conf? and where is the .conf located? i have one on each hdd i had in snapraid...

The working copy of the config file is in:

/etc/snapraid.conf

The files with the same name located on your data and parity disks are copies.

okay thanks.

Strange: in this copy (and on the new HDDs) are the new HDDs mentioned in the .conf. But there is an old "HDD-Folder" with an older snapraid.conf with the old names. How can I delete this?

This is what i get when i try to sync:

Self test...
Loading state from /media/91379b51-142a-4b38-b8aa-4a46dd89324d/snapraid.content...
Decoding error in '/media/91379b51-142a-4b38-b8aa-4a46dd89324d/snapraid.content' at offset 90
The file CRC is correct!
Disk named '3TBb' not present in the configuration file!
If you have removed it from the configuration file, please restore it

the only thing i can do: Fix the array... Is there not other way???

Use the plugin to properly configure the Drives Tab

What do you mean?

The UUID has changed. That's why it doesn't work. I cannot delete the HDDs from Snapraid. There is something left that dominates the normal snapraid.conf

Post your /etc/snapraid.conf file.

Which drives are in the system and which drives are gone?

# this file was automatically generated from
# openmediavault Stone burner 2.1.17
# and 'openmediavault-snapraid' 1.5

block_size 256
autosave 0

#####################################################################
# OMV-Name: Data1 Drive Label: 3TBb
content /media/91379b51-142a-4b38-b8aa-4a46dd89324d/snapraid.content
disk Data1 /media/91379b51-142a-4b38-b8aa-4a46dd89324d

#####################################################################
# OMV-Name: Data2 Drive Label: Test
content /media/21932ab4-4775-4201-acb3-fff454ed70c4/snapraid.content
disk Data2 /media/21932ab4-4775-4201-acb3-fff454ed70c4

#####################################################################
# OMV-Name: Parity1 Drive Label: Parity1
parity /media/14f6363d-8b9a-40a0-9e41-89789f124f50/snapraid.parity

exclude *.bak
exclude *.unrecoverable
exclude /tmp/
exclude lost+found/
exclude .content
exclude aquota.group
exclude aquota.user
exclude snapraid.conf*

this are the now installed HDDs.
Gone are: "3TBb" and "Test" (as OMV-Name. The HDDs are the same, but formated even the parity HDD is the same, but formated). all have now new UUID

The Old HDD UUID are:
/7e21d208-310b-44b9-9216-5ad292482c07/
/7cd31492-0dab-4111-b424-dac0fbeb164b

About all I can suggest is to use the SnapRaid plugin to delete all drives, and then save the configuration, and perhaps reboot the machine.

Then start over and use the plugin to configure it from scratch.