mirror of
https://github.com/amadvance/snapraid.git
synced 2026-10-26 19:01:57 -04:00
Adjusts HISTORY.
This commit is contained in:
parent
1b4ebea11b
commit
9fa6964e05
1 changed files with 7 additions and 9 deletions
16
HISTORY
16
HISTORY
|
|
@ -5,19 +5,17 @@ SnapRAID HISTORY
|
|||
=================
|
||||
* The -N, --force-nocopy option now also works if you used previously
|
||||
"sync" commands without it.
|
||||
* Added a new -F, --force-full option that forces a full sync reusing
|
||||
the hash data present in the content file.
|
||||
This may be useful when using an old content file like the backup
|
||||
one.
|
||||
* Auto exclude the lock file.
|
||||
* Don't prints the 'UUID set' message anymore because it's the normal
|
||||
condition for empty disks.
|
||||
* In 'sync' keeps stats about the amount of time spent waiting for
|
||||
each disk and what is spent in CPU computation.
|
||||
* In Windows, if the disk doesn't support reading physical offsets,
|
||||
allows SnapRAID to continue anyway.
|
||||
* Auto exclude the lock file.
|
||||
* A more precise counting of how may block to scrub. Now it's exact
|
||||
regardless the order of the blocks timing.
|
||||
* Don't prints the 'UUID set' message anymore because it's the normal
|
||||
condition for empty disks.
|
||||
* In Windows, if the disk doesn't support reading physical offsets,
|
||||
allows SnapRAID to continue anyway.
|
||||
* Added a new -F, --force-full option that forces a full sync reusing
|
||||
the hash data present in the content file.
|
||||
|
||||
6.2 2014/5
|
||||
==========
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue