Activity for TooMeeK User
-
TooMeeK User posted a comment on discussion Help
Try RECYCLE.BIN method, move deleted files into bin. Then issue sync. Purge bin only when ready to do so. New & deleted files will be still under protection. Of course, the bin folder have to be included in snapraid config and best would be unlimited capacity.
-
snapraid status always reports failures, either missing/broken disks or files, best would be implement script that outputs that to e-mail on daily basis. It will inform You when it cannot eg. read content file, something bad is reported from the drive, it's missing, etc. However, you should still implement smartctl --test=short /dev/sdX and smartctl --test=long /dev/sdX scripts because the way how SnapRAID works it's up to You to first detect failure before it escalates and consume more disks. You...
-
Probably caused due to protection mechanism that detect buffer overflow errors, but dunno the cause, Out-of-memory during recover? Try fixing independent disks one by one. snapraid fix -d1 -l/tmp/snapraid-disk1-fix.log snapraid fix -d13 -l/tmp/snapraid-disk13-fix.log
-
There should be no problem as executable file detectes if any other process is running and simply refuse to proceed, At least on Linux.. so generally single instance of the process is allowed, that's why lock files are used for. What's the snapraid.content.lock file? It's a file used by SnapRAID to check if another SnapRAID instance is already running. It's created where the first content file is placed.
-
I belive You cannot remove parity-1 as it's needed for parity-2 and parity-3 to work as intended. So remove parity-3, issue sync, copy all files from parity-1 to parity-3 drive, sync again, remove original parity-1 drive,
-
There should be no problem as executable file detectes if any other process is running and simply refuse to proceed, At least on Linux.. so generally single instance of the process is allowed, that's why lock files are used for.
-
Use --log switch and collect these files to track all changes, my sync script looks like this: #!/bin/bash #vars data=$(date +'%Y%m%d') #echo Today is $data ! snapraid diff --log $data.diff; snapraid status --log $data.status; snapraid sync --log $data.sync; snapraid scrub -p new --log $data.scrub; snapraid touch --log $data.touch;snapraid status --log $data.status after revieving them I just gzip them. For data recovery usually procedure is: 1. replace failed drive, note which one was that (d1,...
-
snapraid diff will return differences between current state of the array and last successful sync. It will also return path of changed or missing files. If files are silently corrupted, snapraid scrub -p 100 should find them. Restore depends on failure itself - if entire drive dies, single parity drive and all remaining data drives are required to recover. If two drives die at once - double parity and all remaining drives must be heatlhy. Generally speaking, if You don't miss something in "exclude...
-
I don't understand this question, SnapRAID works differently. All secret is that parity calculations are delayed to planned window by the admin by issued command: snapraid sync. If You have let's say 3 drives and set them into pool (ex. MergerFS) and set this pool to read/write from in sequentional order then You'll get max speed from 3 drives if files are spreaded across them. If all files reside on single drive then You'll get single drive's speed. Spreading files equaly depends on MergerFS mount...
-
I was about to ask the same until I got VM running and tested how it works. Recovery worked perfectly fine every time - except permissions and extended attributes of recovered files, which are gone. I had multiple disk failure in my set due controller failure and they were all BTRFS; FS was unable to recover at that time. Only small amount of latest data without parity was lost. So in worst case scenario D1 fails: recovery depends on failure itself - if there are media errors and it's partially readable...
-
What I did to fix this.. first one is that status in the log must be: msg:status: Everything OK Turns out that each disk must be separately removed: snapraid sync -E make # on disk4 snapraid sync -E make # on disk3 snapraid sync -E then: snapraid sync
-
Here's the situation: Pool of 4 data disks have been consolidated to 2 larger data disks. 2-parity array remained the same - still have 2 parity drives for protection. According to instructions here I'm putting: disk data3 /tmp disk data4 /tmp2 pointing to 2 different UUIDs (empty dirs) instead of 2 missing disks and issuing: snapraid sync -E which ends with: Everything OK however, I'm still unable to remove these disks from /etc/snapraid.conf due: msg:fatal: Decoding error in '/srv/dev-disk-by-label-data1/snapraid.content'...
-
Here's the situation: Pool of 4 data disks have been consolidated to 2 larger data disks. 2-parity array remained the same - still have 2 parity drives for protection. According to instructions here I'm putting: disk data3 /tmp disk data4 /tmp2 pointing to 2 different UUIDs (empty dirs) instead of 2 missing disks and issuing: snapraid sync -E which ends with: Everything OK however, I'm still unable to remove these disks from /etc/snapraid.conf due: msg:fatal: Decoding error in '/srv/dev-disk-by-label-data3/snapraid.content'...
-
Here's the situation: Pool of 4 data disks have been consolidated to 2 larger data disks. 2-parity array remained the same - still have 2 parity drives for protection. According to instructions here I'm putting: disk data3 /tmp disk data4 /tmp2 pointing to 2 different UUIDs (empty dirs) instead of 2 missing disks and issuing: snapraid sync -E which ends with: Everything OK however, I'm still unable to remove these disks from /etc/snapraid.conf due: msg:fatal: Decoding error in '/srv/dev-disk-by-label-data3/snapraid.content'...
-
I belive for iproute2 it will be something like this: ip link add link bond0 name bond0.100 type vlan id 123 ip link set dev bond0.123 up ip addr add 10.0.0.22/24 brd 10.0.0.255 dev bond0.100 For other bond modes it may be tricky as they requires additional values: downdelay updelay primary (The primary option is only valid for active-backup(1), balance-tlb (5) and balance-alb (6) modes) xmit_hash_policy (for 802.3ad) so I think bond modes 0 - balance-rr 1 - active-backup 2 - balance-xor 4 - 802.3ad...
-
Hello, I'm running following version: clonezilla-live-20201102-groovy-amd64.iso During network configuration there's no choice for use tagged VLAN on choosen interface. Also created bonded interface has no choice for its type - it's assuming LACP only. I'm currently trying to configure network on a bare metal server with Intel X520 SFP+ double port NIC (reported as Intel Corporation 82599ES 10-Gigabit SFI/SFP+ Networ Connection by Clonezilla's linux kernel). Because of missing VLAN configuration...
-
Hello, I'm running following version: clonezilla-live-20201102-groovy-amd64.iso During network configuration there's no choice for use tagged VLAN on choosen interface. Also created bonded interface has no choice for its type - it's assuming LACP only. I'm currently trying to configure network on a bare metal server with Intel X520 SFP+ double port NIC (reported as Intel Corporation 82599ES 10-Gigabit SFI/SFP+ Networ Connection by Clonezilla's linux kernel). Because of missing VLAN configuration...
1