mirror of
https://github.com/amadvance/snapraid.git
synced 2026-10-26 02:49:02 -04:00
Update TODO
This commit is contained in:
parent
7d5182acb7
commit
7c910af3f9
1 changed files with 8 additions and 10 deletions
18
TODO
18
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
|
||||
=============
|
||||
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue