Aussie Zone

2,424 readers
157 users here now

If you'd like a community created, request it in [email protected]

Please provide an email address, it is required for password resets and account notifications.

Find federated communities with Feddit.de's community Browser

Rules
  1. Golden rule - don't be a dick. If you wouldn't say it in front of your grandmother, don't post it.
  2. No bigotry - including racism, sexism, ableism, homophobia, transphobia, or xenophobia.
  3. Be respectful. Everyone should feel welcome here.
  4. No porn.
  5. No Ads / Spamming.
  6. Nothing illegal in Australia.

Please, nothing that may be considered offensive in post titles, including strong language.

Server Info
Support

If you'd like to contribute to ongoing running costs, you can do so here. More details on current setup and costs are here.

founded 1 year ago
ADMINS
admin
lodion
dLz
Nath
listing: all - local
search
1
1
FreeBSD OpenZFS bug patch (www.freebsd.org)
 
 

II. Problem Description

A check did not test both the dnode itself and its data for dirtiness. This provides a very small window of time while a file is being modified where the dirtiness check can falsely report that the dnode is clean. If this happens a hole may incorrectly be reported where data was written.

III. Impact

If an access occurs while a file is being modified and a hole is incorrectly reported, the data may instead be interpreted as zero bytes. Any application which checks for holes may be affected by this issue; if this occurs during a file copy it will result in a corrupt copy that retains the incorrect data. Note that the source file remains intact (a subsequent read will return the correct data).

IV. Workaround

Setting the vfs.zfs.dmu_offset_next_sync sysctl to 0 disables forcing TXG sync to find holes. This is an effective workaround that greatly reduces the likelihood of encountering data corruption, although it does not completely eliminate it. Note that with the workaround holes will not be reported in recently dirtied files. See the zfs(4) man page for more information of the impact of this sysctl setting.

The workaround should be removed once the system is updated to include the fix described in this notice.

2
117
BUG: OpenZFS data corruption (www.freebsd.org)
submitted 11 months ago by TheHolm to c/[email protected]
14 comments fedilink
 
 

Unless you are missed the news. Bug found in OpenZFS causing data corruption, FreeBSD, Linux and illumos are all affected.

Good description of the bug

Some good news from bug tracker on OpenZFS

OpenZFS 2.2.2 and 2.1.14 released with fix in place. If you don't get your OpenZFS direct from here, point your vendor at it.

Patch your systems!!

view more: next ›