mirror of
https://github.com/amadvance/snapraid.git
synced 2026-10-26 10:51:54 -04:00
Update TODO and HISTORY
This commit is contained in:
parent
0c624dd431
commit
be84bbffe4
2 changed files with 3 additions and 8 deletions
4
HISTORY
4
HISTORY
|
|
@ -1,7 +1,7 @@
|
|||
SnapRAID HISTORY
|
||||
================
|
||||
|
||||
10.1 2016/04
|
||||
11.0 2016/05
|
||||
============
|
||||
* In the Windows version allow to use the escape char '^' to handle
|
||||
file patterns containing real characters matching the globbing '*?[]'
|
||||
|
|
@ -9,6 +9,8 @@ SnapRAID HISTORY
|
|||
'\'.
|
||||
* Fixed running in Windows platforms that miss the RtlGenRandom
|
||||
function.
|
||||
* Added a new 'hashsize' configuration option. It could be useful in
|
||||
systems with low memory, to reduce the memory usage.
|
||||
* Added the --test-io-cache=1 option to disable the multithread IO
|
||||
mode.
|
||||
|
||||
|
|
|
|||
7
TODO
7
TODO
|
|
@ -5,13 +5,6 @@ This is the list of TODO items for SnapRAID.
|
|||
|
||||
- Next
|
||||
|
||||
* 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:
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue