freenas-user2016
Cadet
- Joined
- Mar 12, 2016
- Messages
- 3
Hello,
from what i found out just today, there is a bug that was introduced a while back and is to my knowledge still affecting all (relatively) new FreeNAS versions, as it was only fixed in the last week(s). 9.3.x should, i guess, at least be affected.
This bug would be concerning a feature named "hole_birth", which is part of newer zfs pool versions. As far as I was able to ascertain, deactivating this feature after data has been placed and or zfs send/resv was used, could further worsen matters.
From what i could gather, it pertains to incremental zfs sends, where, instead of a set of zeros, data from older versions of files is included, thus creating data corruption in certain cases for the incremental backups.
Someone from the #freebsd channel said, that the issue was fixed in 10.3-RC2, although unconfirmed.
It should be part of the next zfs versions released by illumos and zfs on linux.
What i hope someone can answer me is this: When and exactly how is the team behind FreeNAS planning to resolve this - from my perspective rather problematic - issue?
Thank you in advance for your help.
Best regards.
from what i found out just today, there is a bug that was introduced a while back and is to my knowledge still affecting all (relatively) new FreeNAS versions, as it was only fixed in the last week(s). 9.3.x should, i guess, at least be affected.
This bug would be concerning a feature named "hole_birth", which is part of newer zfs pool versions. As far as I was able to ascertain, deactivating this feature after data has been placed and or zfs send/resv was used, could further worsen matters.
From what i could gather, it pertains to incremental zfs sends, where, instead of a set of zeros, data from older versions of files is included, thus creating data corruption in certain cases for the incremental backups.
Someone from the #freebsd channel said, that the issue was fixed in 10.3-RC2, although unconfirmed.
It should be part of the next zfs versions released by illumos and zfs on linux.
What i hope someone can answer me is this: When and exactly how is the team behind FreeNAS planning to resolve this - from my perspective rather problematic - issue?
Thank you in advance for your help.
Best regards.
