Data Hoarder

1 readers

1 users here now

We are digital librarians. Among us are represented the various reasons to keep data -- legal requirements, competitive requirements, uncertainty of permanence of cloud services, distaste for transmitting your data externally (e.g. government or corporate espionage), cultural and familial archivists, internet collapse preppers, and people who do it themselves so they're sure it's done right. Everyone has their reasons for curating the data they have decided to keep (either forever or For A Damn Long Time (tm) ). Along the way we have sought out like-minded individuals to exchange strategies, war stories, and cautionary tales of failures.

founded 1 year ago

MODERATORS

communick@selfhosted.forum

Heads up for a data corruption bug in ZFS, few versions affected, might have started at 2.1.x, but many reports on 2.2.x (github.com)

submitted 11 months ago by vitzli-mmc@alien.top to c/datahoarder@selfhosted.forum

28 comments fedilink hide all child comments

you are viewing a single comment's thread
view the rest of the comments

[–] zhiryst@alien.top 1 points 11 months ago (3 children)

Can someone tell a dummy like me, if this impacts truenas core?

[–] iamcts@alien.top 1 points 11 months ago

It's hard to tell because I get this:

root@truenas[~]# zpool get version poolname

NAME PROPERTY VALUE SOURCE

poolname version - default

[–] realitycorp@alien.top 1 points 11 months ago

There is a thread going on at https://www.truenas.com/community/threads/silent-corruption-with-openzfs-ongoing-discussion-and-testing.114390/

Some users are reporting that it does affect Truenas (though it depends on the use case).

[–] EquivalentRisk3069@alien.top 1 points 11 months ago

TrueNAS-13.0-U6 (the current core version)

zfs version reports 2.1.13

so it should be clean.