Package Details: snapraid 14.4-1

Git Clone URL: https://aur.archlinux.org/snapraid.git (read-only, click to copy)
Package Base: snapraid
Description: tool for Snapshot RAID: generate parity files, maintain checksums on data, restore lost data
Upstream URL: http://www.snapraid.it/
Licenses: GPL3
Submitter: ice9
Maintainer: Sparticuz
Last Packager: Sparticuz
Votes: 31
Popularity: 0.000136
First Submitted: 2012-01-02 06:42 (UTC)
Last Updated: 2026-04-23 20:07 (UTC)

Dependencies (4)

Required by (2)

Sources (1)

Pinned Comments

Sparticuz commented on 2025-01-30 16:17 (UTC) (edited on 2025-01-30 16:17 (UTC) by Sparticuz)

AUR Changelog 20250130:

Update to Snapraid 12.4, Added a notice and a 5 second hold before running make check, Added smartmontools to optdepends

Latest Comments

« First ‹ Previous 1 2 3 4 5 6 7 8 Next › Last »

ice9 commented on 2016-09-24 15:52 (UTC)

I think SnapRAID will automatically check if the libblkid library is present when it builds. So you should just need to make sure that the library is present on your system, and then rebuild SnapRAID. On Archlinux, libblkid is part of the core libutil-linux package. Try installing that package and then rebuilding SnapRAID. If it solves your problem, please leave feedback, and I will add libutil-linux to the dependencies list for this package.

lockheed commented on 2016-09-11 07:20 (UTC)

Quoting SnapRAID FAQ about BTRFS: "Btrfs OK. But ensure to build SnapRAID with the libblkid library to get UUID support. You will be warned at every run if this doesn't happen." I am using BTRFS and every time I do sync, I get this error. Does this package build with libblkid?

alfalco commented on 2016-03-30 01:16 (UTC)

Thanks for your work!

ice9 commented on 2016-02-29 02:25 (UTC)

v10.0

ice9 commented on 2016-01-18 23:08 (UTC)

v9.3 "Fixes an invalid assumption in the copy detection mechanism that could result in an internal inconsistency, and with the impossibility to run the 'sync' and 'diff' commands. This was triggered by a very specific pattern of identical files. At least three of them, with one already in the parity, and at a higher disk number than the others that should be instead new ones. This had no bad effect, if not preventing the 'sync' command to run. A workaround was to just run 'sync' one time with the -N, --force-nocopy option to disable the copy detection."

ice9 commented on 2016-01-09 16:23 (UTC)

v9.2

ice9 commented on 2015-11-20 21:45 (UTC)

v9.1 : fixes a bug in 9.0 that can cause content file to not be read properly

ice9 commented on 2015-11-13 23:23 (UTC)

v9.0

ice9 commented on 2015-05-15 21:02 (UTC)

v8.1

ice9 commented on 2015-04-26 09:49 (UTC)

v8.0

« First ‹ Previous 1 2 3 4 5 6 7 8 Next › Last »