#OpenZFS

[nixcraft]

Big news for ZFS Linux and Unix users: The latest release, version 2.3.0, finally brings raidz expansion! No more storage headaches and you can easily add a new HDD

[digitalcreationsllc]

Two New Versions of OpenZFS Fix Long-Hidden Corruption Bug

The OpenZFS development team has released two new versions of the open-source cross-platform filesystem. Version 2.2.2 fixes a bug that caused data corruption in file copies and affected FreeBSD 14 and various Linux distros.

[ericvanderburg]

OpenZFS 2.3 is here, with RAID expansion and faster dedup

http://securitytc.com/THX8vp

[hackernewsrobot]

ZFS 2.3.0 released with ZFS raidz expansion

https://github.com/openzfs/zfs/releases/tag/zfs-2.3.0

[rackmount-official-my-ass]

Okay folks, here's the straight dope on used server drives:

Always burn in any drive you get, in case it's on the verge of death. Look at badblocks.

Used server drives can be brand new, lightly used, heavily used, refurbished, or have falsified health data.

You can sometimes find "new old stock" of drives that were never used before they went obsolete, for decent prices.

Check diskprices.com and shucks.top for deals (and labgopher.com if you want a whole server).

As a general rule, enterprise grade drives are more expensive and more reliable than consumer grade drives (applies to most types of hardware really).

As a general rule, 2.5" is more expensive than 3.5", and SSD is more expensive than HDD.

Be careful to buy SATA drives and not SAS drives (unless you have a SAS controller and know what you're doing).

If you don't care that much, having read the above, go for it. If you want to make sure you're not about to lose everything suddenly (i.e. if you're a budding data hoarder looking to build a NAS):

Most drives die either after a long life, or in their early life. This is why the burnin is important, even for a new drive: it should get you past the early mortality hump.

If it's not sealed from the OEM, you really don't know what firmware is running on it. This one is a little paranoid, especially since you wouldn't know anyways, but state actors have demonstrated firmware attacks against drives in the past.

Mirror or RAID your data, if not doing something stronger like Ceph. I have heard from a trusted partner that OpenZFS has declined in quality assurance over recent years.

With modern drives (think O(TB)), RAID 5 is insufficient. Plan for at least two drives of redundancy.

Avoid buying a batch full of the same model/lot of drives. Diversity is key in reducing the likelihood of correlated failures.

Set up FDE from the getgo if you ever want to securely wipe the data. Use software FDE, don't rely on keys stored in the drive.

Prefer CMR over SMR. I don't know if HAMR and the other types are different or what the meta is since we started filling drives with glass and helium...

Let me know if you have any questions or I forgot something!

you know what i wish i had

large amounts of storage

like two-thirds of my only working drive is full already, nobody told me 500GB wouldn't be enough T^T

[datamattsson]

Folks, WASDkeyboards got stock! Got one for my personal workstation. Obligatory OpenZFS key and WASD to match the Ubuntu orange (also the super key).

[illuminarch]

OpenZFS 2.0 será lançado em 2020 com suporte unificado ao Linux e FreeBSD

OpenZFS 2.0 será lançado em 2020 com suporte unificado ao Linux e FreeBSD

Na semana passada, em San Francisco, aconteceu a cúpula anual do desenvolvedor do OpenZFS. Como sempre, Matthew Ahrens, co-fundador do Sun ZFS e atual colaborador do OpenZFS na Delphix, falou sobre o trabalho em relação ao código aberto do ZFS em sua palestra. A grande novidade anunciada é que o OpenZFS 2.0 será lançado em 2020 com suporte unificado ao Linux e FreeBSD.

Alguns dos destaques de sua…

[bulletinwave]

Virtualization platform Proxmox VE 6.4 changes to OpenZFS 2.0

Virtualization platform Proxmox VE 6.4 changes to OpenZFS 2.0

The new Proxmox VE 6.4 is based on Debian GNU / Linux 10.9 “Buster” with a Linux kernel 5.4 (LTS) or optionally 5.11. The HA-enabled virtualization solution manages both virtual machines and Linux containers via a clear WebGUI. The virtual machines provide a combination of QEMU 5.2 with KVM, whereby VMs can be linked to certain QEMU machine versions by “pinning”. Linux containers, provided by…

[f-andrey]

https://www.youtube.com/watch?v=kFuo5bDj8C0

[nixcraft]

I giggled to hard.

[tonkirc]

Setup openzfs on freebsd

Ongoing maintenance and monitoring can also be achieved from the command line or with the tools that you already have in place for maintaining your other FreeBSD systems. In practical terms, NAS configuration is mostly a one-time thing that is easy enough to perform from the command line. While some vendors offer customized hardware builds, if you already know what you want for hardware, you can build it yourself without adding the cost of a middleman to build it for you.Ĭonfiguring a NAS on top of your own FreeBSD installation also means that you don’t have the overhead of running a GUI, or learning where to perform the various configuration options from that GUI. Pre-built NAS solutions will only offer a small selection of hardware choices which may or may not meet your needs. Given that several FreeBSD-based NAS distributions are readily available, ranging from completely open source to pre-built with customer support plans, the question naturally arises: “why not just use a FreeBSD-based NAS distro rather than building your own”? After all, someone else has done the work to tune FreeBSD and most solutions provide a nice GUI for configuring the various NAS options. In this article we take a closer look at the operating system and the configurations, both during and after installation, to fine-tune the system for OpenZFS storage. We’re taking a build-up approach, where we first walk you through the hardware steps, and now we’re bringing up the next layer in our step-up – setting up your FreeBSD operating system. In the first article in this series, we concentrated on selecting suitable hardware for your FreeBSD and OpenZFS-based NAS.

[ericvanderburg]

Two New Versions Of OpenZFS Fix Long-Hidden Corruption Bug

http://i.securitythinkingcap.com/Szkgcj

[hackernewsrobot]

OpenZFS deduplication is good now and you shouldn't use it

https://despairlabs.com/blog/posts/2024-10-27-openzfs-dedup-is-good-dont-use-it/

[thebestgreys]

Zpool send resume openzfs

Applications may be affected.Īction: Restore the file in question if possible. Status: One or more devices has experienced an error resulting in dataĬorruption. When I ran zpool status -v on my file server, I saw irrecoverable errors: The first noticeable problems involved videos cutting off midstream, following by I/O errors. In the end, ZFS saved me from what could have been disastrous amounts of data corruption due to faulty hardware. I took a long journey through ZFS bug reports, attempted to switch to Btrfs and even migrated my storage to a different computer. When I attempted to sync snapshots to the new device, I started to see I/O errors and kernel panics. My storage had outgrown my previous backup drive anyway, so I purchased an additional drive. I didn’t see any SMART errors on the drives, but still assumed that my hard drive could be going bad. Not soon after, I started getting random file corruption issues. Recently I upgraded from Alpine 3.12 to 3.14, which included a ZFS 0.8 to ZFS 2.0 update. I’ve been using ZFS for years on my Linux storage server. ZFS Woes, or how ZFS Saved Me From Data Corruption