From 6daaafc17b6902bc874d54621e23bbdffd00fb38 Mon Sep 17 00:00:00 2001 From: Andrea Mazzoleni Date: Mon, 20 Oct 2025 15:01:18 +0200 Subject: [PATCH] Update TODO --- TODO | 41 +++++++++++++++++++++-------------------- snapraid.1 | 2 ++ snapraid.d | 2 ++ snapraid.txt | 2 ++ 4 files changed, 27 insertions(+), 20 deletions(-) diff --git a/TODO b/TODO index 062216a6..600f3f65 100644 --- a/TODO +++ b/TODO @@ -37,10 +37,6 @@ It would be interesting to compare performance with the hand-written assembler functions. Eventually we can convert them to use intrinsic also. https://sourceforge.net/p/snapraid/discussion/1677233/thread/9dbd7581/ -* Extend haspdeep to support the SnapRAID hash : -https://github.com/jessek/hashdeep/ -https://sourceforge.net/p/snapraid/discussion/1677233/thread/90b0e9b2/?limit=25 - * Add a "noaccessdenied" config option to exclude not readable files/dirs. Like the "nohidden". See: https://sourceforge.net/p/snapraid/discussion/1677233/thread/1409c26a/ @@ -141,25 +137,10 @@ File with the same name will get an extra extension like ".1", ".2". - Major -* Uses a separated file for storing hashes, to allow to use a memory -mapped file to decrease memory utilization. -The file can contains hashes stored in the same order they are accessed -in sync/check/scrub. -+ A lot less memory utilization -- It will be slow in --pre-hash as the files are accessed in another order, -but no much slow. -- How to handle multiple .content file copy ? When working we can have -only a single file. When storing the .content we'll have to copy it -in all the places. -* Can we mix the existing and new approach ? We can create this -hash file at startup in a memory mapped "temporary" file. -It may takes some time to create it, but then it will be fast. -See: https://sourceforge.net/p/snapraid/discussion/1677233/thread/cdea773f/ - * Allocate parity minimizing concurrent use of it Each parity allocation should check for a parity range with less utilization by other disks. -We need to take care do disable this mechanism when the parity space +We need to take care to disable this mechanism when the parity space is near to fillup the parity partition. See: https://sourceforge.net/p/snapraid/discussion/1677233/thread/1797bf7d/ + This increase the possibility of recovering with multiple failures with not @@ -373,4 +354,24 @@ The risk would be instead to miss some recovery opportunity. So, makes sense to have it a little slower but trying any possible recovery strategy. +* Extend haspdeep to support the SnapRAID hash. +- Not possible, because now SnapRAID uses a hash see that makes the hash unique +for each array +https://github.com/jessek/hashdeep/ +https://sourceforge.net/p/snapraid/discussion/1677233/thread/90b0e9b2/?limit=25 +* Uses a separated file for storing hashes, to allow to use a memory +mapped file to decrease memory utilization. +- Now it's expected to have machines with big memory. +The file can contains hashes stored in the same order they are accessed +in sync/check/scrub. ++ A lot less memory utilization +- It will be slow in --pre-hash as the files are accessed in another order, +but no much slow. +- How to handle multiple .content file copy ? When working we can have +only a single file. When storing the .content we'll have to copy it +in all the places. +* Can we mix the existing and new approach ? We can create this +hash file at startup in a memory mapped "temporary" file. +It may takes some time to create it, but then it will be fast. +See: https://sourceforge.net/p/snapraid/discussion/1677233/thread/cdea773f/ diff --git a/snapraid.1 b/snapraid.1 index 55fda0f6..3e6a69f6 100644 --- a/snapraid.1 +++ b/snapraid.1 @@ -925,6 +925,8 @@ Nothing is modified. Lists all the files contained in the array at the time of the last \[dq]sync\[dq]. .PP +With \-v or \-\-verbose, the subsecond time is also shown. +.PP Nothing is modified. .SS dup Lists all duplicate files. Two files are assumed equal if their diff --git a/snapraid.d b/snapraid.d index 7aac8e13..0630adf3 100644 --- a/snapraid.d +++ b/snapraid.d @@ -641,6 +641,8 @@ Commands Lists all the files contained in the array at the time of the last "sync". + With -v or --verbose, the subsecond time is also shown. + Nothing is modified. dup diff --git a/snapraid.txt b/snapraid.txt index 5074bb27..c2a0a987 100644 --- a/snapraid.txt +++ b/snapraid.txt @@ -687,6 +687,8 @@ Nothing is modified. Lists all the files contained in the array at the time of the last "sync". +With -v or --verbose, the subsecond time is also shown. + Nothing is modified. 5.12 dup