Учимся безболезненно переносить и клонировать серверы

Привет! Меня зовут Ваня, я системный администратор

https://habr.com/ru/companies/selectel/articles/917574/

#selectel #zfs #перенос_сервера #btrfs

Got a problem with upgrading and timeshift-autosnap on Manjaro with btrfs.
After getting "failed to run transaction hooks" every time, I could get it to work with

$ sudo timeshift-autosnap

and selected a new (the old) backup drive.
No clue why it lost the previous settings.
After that I could upgrade my system again.

I should have gone with ext4 instead of #btrfs I'll guess.

Anaconda on the Fedora Server install ISO doesn’t offer btrfs. Confusing.. Do I need to use the Workstation ISO to get btrfs in Anaconda..?
( And yes, I do want Anaconda in this instance. )
#Fedora #Anaconda #btrfs

Abandoné mi estrategia de respaldos con #Timeshift Btrfs+Rsync y opté por #Btrbk que crea instantáneas #Btrfs locales y realiza respaldos externos incrementales. Además, permite manejar diferentes subvolumenes al mismo tiempo a distinta frecuencia. Por ejemplo, puedo programar instantáneas globales del sistema de forma diaria, y al mismo tiempo, varios respaldos por hora de un directorio de trabajo, una base de datos, en particular. No tiene interfaz gráfica, pero su potencia es increíble 🤩

Which Linux file system do you prefer using?

#Linus #file #system #ZFS #Btrfs

Both ZFS and Btrfs are advance file systems designed for Linux. They both offer features like RAID, compression, and snapshots.

But ZFS is generally considered more mature, reliable, and robust. ZFS is also a popular solution for enterprise.

Btrfs is more Linux-centric solution. Btrfs tends to be easier to integration and use with the Linux kernel.

#ZFS #Btrfs #file #system #RAID #compression #snapshots #Linux #kernel

I have a bunch of old documents on my computer separated in an "old documents" folder. Currently they are not compressed.
If I compress my "old documents" into a tar.zst archive, will I increase to decrease the probability of them becoming corrupted?

My home partition is using BTRFS if it matters. #BTRFS

Some refinements to "oops" including not only finding deleted files in Snapper snapshots but also finding previous versions of existing files.
https://codeberg.org/joatca/oops
#Snapper #btrfs #backups

Archinstall 3.0.7: Easy BTRFS Snapshots Make Arch Linux Beginner-Friendly

https://video.fosshq.org/w/djq8fMUtxqiGbDbMpFsJhz

I'm thinking of trying again some other filesystem that is not ext4. I'm not sure if #btrfs would allow me to have multiple drives of different types and sizes as one filesystem. Right now I'm using #mergerfs with a bunch of ext4 drives. I don't care about RAID, I just want to use all the space available in storage.

Is BTRFS the right alternative?

@karlggestd It is at /mnt/ramdisk. And I know it is in RAM, because the transfer is at 3GiB/s.

Also I don't use #BTRFS. It's all #EXT4. 🙂

Introducere în sistemul de fișiere Linux

https://comunitatealinux.ro/introducere-in-sistemul-de-fisiere-linux/

A few months ago I wrote a script for work to help users recover files they accidentally deleted from our VAST storage system (using snapshots). I finally re-wrote it for home use with #Snapper snapshots on #btrfs

https://codeberg.org/joatca/oops

@yianpap thanks. I love Garuda, but ditched it on my work machine as it was too slow. Arch is much, much faster (e.g. compiling source code).

The two big differences between my Garuda and Arch installs were the zen kernel Vs the regular Arch kernel and btrfs Vs ext4. All other things were AFAiCT the same (i3, javac version, mount options). Of the two, I suspect btrfs to be the culprit. Haven't dug into it more, though. Reinstalling using Arch, with disk encryption, yielded an instant performance boost when developing large java applications.

#archlinux #btrfs #GarudaLinux

Really impressive: I enabled compression for #btrfs on the #docker host (docker is using btrfs as storage driver) this instance runs on, ran "btrfs filesystem defragment -r -v -czstd /" and the disk space usage got reduced from 65GB to 39GB.

#Manjaro up and running... clean. Data all transferred flawlessly.
Now the week long configuration to my needs begins.

My first time with #btrfs
Feels weird using something else than ext4. I hope this wasn't a mistake.

"some performance improvements and one minor mount option update" are among the main #Btrfs changes merged for #Linux 6.16:

https://git.kernel.org/torvalds/c/5e82ed5ca4b510e0ff53af1e12e94e6aa1fe5a93

A few highlights:

Performance:

- extent buffer conversion to xarray gains throughput and runtime improvements on metadata heavy operations doing writeback (sample test shows +50% throughput, -33% runtime)

- extent io tree cleanups lead to performance improvements by avoiding unnecessary searches or repeated searches

- more efficient extent unpinning when committing transaction (estimated run time improvement 3-5%)

User visible changes:

- remove standalone mount option 'nologreplay', deprecated in 5.9, replacement is 'rescue=nologreplay'

- in scrub, update reporting, add back device stats message after detected errors (accidentally removed during recent refactoring)

Core:

- convert extent buffer radix tree to xarray

- continued preparations for large folios

#kernel #LinuxKernel #Linux616 #Filesystem

Adding a hard drive to enable raid1.
#btrfs #raid