> A new transaction group (TXG) is created at LEAST every
> vfs.zfs.txg.timeout (defaults to 5) seconds.
> f you offline a drive for hours or more, it must have all blocks with a
> 'birth time' newer than the last transaction that was recorded on the
> offlined drive replayed to catch that drive u
On 2016-08-04 07:22, Ultima wrote:
> Hello,
>
> I recently had some issue with a PSU and ran several scrubs on a pool with
> around 35T. Random drives would drop and require a zpool online, this found
> checksum errors. (as expected) However, after all the scrubs I ran, I think
> I may have found
Am 10.08.2016 um 18:53 schrieb Ultima:
> Hello,
>
>> I didn't see any reply on the list, so I thought I might let you know
>
> Sorry, never received this reply (till now) xD
>
>>what I assume is happening:
>
>> ZFS never updates data in place, which affects inode updates, e.g. if
>> a file has
On 2016-08-10 12:53, Ultima wrote:
> Hello,
>
>> I didn't see any reply on the list, so I thought I might let you know
>
> Sorry, never received this reply (till now) xD
>
>> what I assume is happening:
>
>> ZFS never updates data in place, which affects inode updates, e.g. if
>> a file has bee
Hello,
> I didn't see any reply on the list, so I thought I might let you know
Sorry, never received this reply (till now) xD
>what I assume is happening:
> ZFS never updates data in place, which affects inode updates, e.g. if
> a file has been read and access times must be updated. (For that r
Hello,
I recently had some issue with a PSU and ran several scrubs on a pool with
around 35T. Random drives would drop and require a zpool online, this found
checksum errors. (as expected) However, after all the scrubs I ran, I think
I may have found a bug with zpool online resilvering process.
2
