Login

Recent searches

No recent searches

Search options

Not available on mastodon.xyz.
mastodon.xyz is one of the many independent Mastodon servers you can use to participate in the fediverse.
A Mastodon instance, open to everyone, but mainly English and French speaking.

Administered by:

Server stats:

790
active users

mastodon.xyz: AboutProfiles directoryPrivacy policy

Mastodon: AboutGet the appKeyboard shortcutsView source codev4.3.4

#zfs

11 posts10 participants1 post today
Public
Emory

i wonder if i could move my NVME #zfs zpool to a Thunderbolt-equipped NAS like the #ugreen models, install #trueNAS Scale, and slide my NVME flash storage pool to a filer, instead of my creative workstation, which would free up 4-8 lanes on PCI-E for me?

current mood: pool compatibility flags for zfs-on-#macOS

Public
Dan Langille

This is a typical FreshPorts daily database backup being rsync'd from AWS to the #homelab :

It just so happens the the output of pg_dump for the #PostgreSQL database more-or-less keeps the data in the same order each time. So the actual daily transfer SEEMS to be only the new data.

On disk, I rely upon #ZFS compression to do the disk savings for me. That compression also speeds up disk throughput - the CPU can uncompressed faster than the disk can provide the data.

In today's case, the amount copied down seems to be 360MB.

This speed-up by rsync, which recognizes what has and has not been transferred, is also why do not dump in compressed mode.

dumping freshports.org
receiving incremental file list
postgresql/
postgresql/freshports.org.dump
3,621,784,708 100% 77.73MB/s 0:00:44 (xfr#1, to-chk=1/4)
postgresql/globals.sql
3,963 100% 58.64kB/s 0:00:00 (xfr#2, to-chk=0/4)

Number of files: 4 (reg: 2, dir: 2)
Number of created files: 0
Number of deleted files: 0
Number of regular files transferred: 2
Total file size: 3,621,788,671 bytes
Total transferred file size: 3,621,788,671 bytes
Literal data: 355,867,046 bytes
Matched data: 3,265,921,625 bytes
File list size: 142
File list generation time: 0.001 seconds
File list transfer time: 0.000 seconds
Total bytes sent: 481,559
Total bytes received: 356,171,297

sent 481,559 bytes received 356,171,297 bytes 6,925,298.17 bytes/sec
total size is 3,621,788,671 speedup is 10.15

Public
SLIMBOOK (Official)

🔁 RAID vs ZFS

RAID: tecnología que agrupa discos para mejorar rendimiento o seguridad según el nivel que elijas (RAID 0, 1, etc.). Es simple, útil y eficiente para muchas tareas.

ZFS : sistema de archivos + gestor de volúmenes que incluye su propio tipo de RAID, snapshots, compresión, verificación de integridad...

¿Lo básico? RAID.
¿Potencia y control? ZFS es el camino.

🔗 Descubre más en nuestra sección de tutoriales en la web:

slimbook.com/blog/tutoriales-2

#RAID#ZFS#TechTips
Replied in thread
Public *
ax6761

@vermaden @justine
Addendum: prefix "pkg upgrade" with "make-snapshots" to be able to rollback the file systems(s) without fuss ...

make-snapshots \
&& pkg upgrade && make-snapshots \
&& pkg autoremove && make-snapshots \
&& pkg clean && make-snapshots

... I had made the change before the issue of {missing,disappearing}-packages-on-upgrade that various other peoples are experiencing currently.

#FreeBSD#ZFSEverywhere_possible#ZFS
Replied in thread
Public
Jason Tubnor 🇦🇺
@ianthetechie @feld I can confirm that #Python on #FreeBSD behaves as one would expect. It consumes all RAM (with #ZFS releasing ARC as expected) and then dips into swap. As soon as Python releases memory after the ingestion routine, the swap is purged to near zero and the RAM then becomes available (and used) by the system. Far more predictable and reliable.

If you have big, vertical workloads, FreeBSD is where it is at.
Public
echo ✨

fuckkkk ZFS why you do this. guess i know what i'm spending tonight doing.

any #zfs experts out there able to help me recover my pool? i apparently broke things quite significantly lol

Public
Juno

Today, out of nowhere, my shell started to misbehave. My prompt suddenly reverted to default. Some unexpected "command not found" errors started popping up. Something was off.

I went to check my shell configuration. The directory was not there. I then went look into ~/.config. Half of the directories inside were simply gone.

I immediately flipped into what the fuck is happening mode.

This system is an Alpine root-on-ZFS. I have a script called by cron every 20 minutes that snapshots everything.

First I went into the snapshot directory and started copying some things. I soon noticed it was just too much missing. How to map out what was gone in the first place? Even so, copying would only go so far because I was duplicating things.

I looked to my left at the resource monitor. I had less than 1 GB left of free space. That was not going to work.

I flip some pages, looking for an incantation...

% zfs rollback zroot/home@20m

A long second hanged in the air. Then all the resource monitor's bars flipped at once to green: 53% free space.

"Blessed be the ZFS Daemons and the Authors who conjured Them."

The system was still confused, so I rebooted. It let its conscience drift - as it is used to -, uncertainty still heavy in the air. Then it resurfaced... every line of output unconcerned.

Back up, no trace was left of the seconds leading up to the warp. The only suspicion came from a cryptography guardian, who noticed something was wrong about the timestamps. "Please re-enter the passcodes", it asked. Every other blob was either unconcerned or unimpressed with the glitch.

Like any time travel, the only trace left was in my memory. No history anywhere has me looking for that spell. I booted 20 minutes into the past and that's from when I am writing to you.

#ZFS
ExploreLive feeds
About