mirror of
https://github.com/versity/scoutfs.git
synced 2026-01-03 02:45:20 +00:00
v1.7 Release
Finish the release notes for the 1.7 release. Signed-off-by: Zach Brown <zab@versity.com>
This commit is contained in:
@@ -1,6 +1,29 @@
|
|||||||
Versity ScoutFS Release Notes
|
Versity ScoutFS Release Notes
|
||||||
=============================
|
=============================
|
||||||
|
|
||||||
|
---
|
||||||
|
v1.7
|
||||||
|
\
|
||||||
|
*Aug 26, 2022*
|
||||||
|
|
||||||
|
* **Fixed possible persistent errors moving freed data extents**
|
||||||
|
\
|
||||||
|
Fixed a case where the server could hit persistent errors trying to
|
||||||
|
move a client's freed extents in one commit. The client had to free
|
||||||
|
a large number of extents that occupied distant positions in the
|
||||||
|
global free extent btree. Very large fragmented files could cause
|
||||||
|
this. The server now moves the freed extents in multiple commits and
|
||||||
|
can always ensure forward progress.
|
||||||
|
|
||||||
|
* **Fixed possible persistent errors from freed duplicate extents**
|
||||||
|
\
|
||||||
|
Background orphan deletion wasn't properly synchronizing with
|
||||||
|
foreground tasks deleting very large files. If a deletion took long
|
||||||
|
enough then background deletion could also attempt to delete inode items
|
||||||
|
while the deletion was making progress. This could create duplicate
|
||||||
|
deletions of data extent items which causes the server to abort when
|
||||||
|
it later discovers the duplicate extents as it merges free lists.
|
||||||
|
|
||||||
---
|
---
|
||||||
v1.6
|
v1.6
|
||||||
\
|
\
|
||||||
|
|||||||
Reference in New Issue
Block a user