mirror of
https://github.com/amadvance/snapraid.git
synced 2026-10-26 10:51:54 -04:00
Update TODO
This commit is contained in:
parent
76ce1cbb16
commit
fb051e02c7
1 changed files with 6 additions and 10 deletions
16
TODO
16
TODO
|
|
@ -5,8 +5,6 @@ This is the list of TODO items for SnapRAID.
|
|||
|
||||
- Next
|
||||
|
||||
* Use a memory mapped file to read the content file
|
||||
|
||||
* Integration with MergeFS ?
|
||||
|
||||
* Evaluate use of syscall getdents64() instead of readdir(): https://linux.die.net/man/2/getdents64
|
||||
|
|
@ -15,14 +13,6 @@ This is the list of TODO items for SnapRAID.
|
|||
https://github.com/linuxhw/SMART
|
||||
https://github.com/linuxhw/EnterpriseDrive
|
||||
|
||||
* Support BTRFS subvolumes. Keep track of the subvolumeid, along with the inode,
|
||||
and use it when searching/comparing inodes.
|
||||
The value 0 can be used for the root volume, like a normal filesystem.
|
||||
See: https://github.com/kdave/btrfs-progs/tree/master/libbtrfsutil
|
||||
Check also that other tools are doing:
|
||||
See: https://github.com/automorphism88/snapraid-btrfs
|
||||
See: https://github.com/dim-geo/btrfssnapraid
|
||||
|
||||
* A "dependents" output option to [--test-fmt file|disk|path|dependents] for LIST.
|
||||
Example, snapraid LIST --test-fmt dependents >FileList_with_dependents.txt
|
||||
The goal is a filelist that, for every file, includes full paths to the dependent files
|
||||
|
|
@ -32,6 +22,9 @@ I created a thread about it here: https://sourceforge.net/p/snapraid/discussion/
|
|||
|
||||
- Minor
|
||||
|
||||
* Add a new scrub option for checking recent blocks. Like -n, --newer-than.
|
||||
Working the opposite of -o-, --older-than
|
||||
|
||||
* Add a new -u, --filter-updated command that filters files
|
||||
with a different timestamp, to be able to restore only them to the previous state.
|
||||
See: https://sourceforge.net/p/snapraid/discussion/1677233/thread/e26e787d/
|
||||
|
|
@ -165,6 +158,9 @@ Rejected TODO
|
|||
|
||||
This is a list of rejected TODO items.
|
||||
|
||||
* Use a memory mapped file to read the content file
|
||||
- Tried. No speed gain.
|
||||
|
||||
* Allow multiple parity files and to coexist with data
|
||||
in the same disk.
|
||||
This is possible if the data in the same disk uses parity addresses not
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue