From 7c910af3f9548aad833b9855a8c4ed996277e652 Mon Sep 17 00:00:00 2001 From: Andrea Mazzoleni Date: Wed, 6 Apr 2016 22:57:01 +0200 Subject: [PATCH] Update TODO --- TODO | 18 ++++++++---------- 1 file changed, 8 insertions(+), 10 deletions(-) diff --git a/TODO b/TODO index f5d9e625..3dcb4c73 100644 --- a/TODO +++ b/TODO @@ -5,15 +5,20 @@ This is the list of TODO items for SnapRAID. - Next -* Allow to disable multithread - -- Minor +* Use smaller hashes to reduce the memory occupation. We can truncate the 128 bits hash +to 32 or 64 bits and reduce the memory usage by a factor of 4 or 2. +ZFS, and Btrfs supports the 32 bit CRCs. To identify bad blocks it should be enough. +But this likely means to drop the dup and --import feature. We cannot trust a 32 bits hash +as a 128 bits one to search for blocks. +It should be optional, only for architectures with very low memory. * Allow to specify more than one partition for each parity disk. Checking the UUID, we can avoid that users mess-up with disk specifications. See discussion at: https://sourceforge.net/p/snapraid/discussion/1677233/thread/02b2a2ae/ +- Minor + * How to handle corrupt copied/moved files ? At now pre-hash checks them, but if a corruption is found, it stops the sync process. This is not optimal, because the 'sync' command is stopped instead to continue. @@ -115,13 +120,6 @@ See Jens's Windows script at: http://sourceforge.net/p/snapraid/discussion/16772 Note that a different between Windows and Unix is that in Windows old snapshots are automatically deleted. -* Use smaller hashes to reduce the memory occupation. We can truncate the 128 bits hash -to 32 or 64 bits and reduce the memory usage by a factor of 4 or 2. -ZFS, and Btrfs supports the 32 bit CRCs. To identify bad blocks it should be enough. -But this likely means to drop the dup and --import feature. We cannot trust a 32 bits hash -as a 128 bits one to search for blocks. -It should be optional, only for architectures with very low memory. - Rejected TODO =============