#fstab — Public Fediverse posts

Brauche mal Hilfe für #linux #debian #trixie #nas #usbraid #nfs #usb #rsync #bash.

Ich habe ein #Script das nicht funktioniert und doch funktioniert *grrrr*

(Script Begin)
#!/bin/bash

set -ex

# check for mount
grep /backup /etc/mtab > /dev/null || exit 1

# directory to backup
BDIR=/home/wilma_wein/

# Destination dir for rsync
DDIR=/media/backup

# excludes file - this contains a wildcard pattern per line of files to exclude
EXCLUDES=/root/rsy.excl

# BACKUPDIR=${1:-`date +%A`}
BACKUPDIR=${1:-"day"`date +%d`}

OPTS="--force
--ignore-errors \
--delete-excluded \
--exclude-from=$EXCLUDES
--delete --backup --backup-dir=$DDIR/$BACKUPDIR -a -v"

export PATH=$PATH:/bin:/usr/bin:/usr/local/bin

# if destination does not exist, make it;-)
[ -d $DDIR ] || mkdir $DDIR

# write logfile
echo oooooooooooooooooooooooooooooooooooooooooooo >> /root/rsy.log
date >> /root/rsy.log

# delete existing backup dir
[ -d $DDIR/$BACKUPDIR ] && (echo remaking $DDIR/$BACKUPDIR >> /root/rsy.log; rm -r $DDIR/$BACKUPDIR)

# now the actual transfer
rsync $OPTS $BDIR $DDIR/current >> /root/rsy.log

(Script Ende)
.
.
Dieses Script soll mir mein komplettes /home sichern und gelöschte dateien in den heutigen Tag (Ordner day20 anlegen) und die gelöschte oder alte Datei (sofern geändert) verschieben. Die geänderte neue Datei im BackUp Ordner belassen.

Folgende Laufwerke sind in meiner #fstab gemountet:

# Angeschlossenes USB RAID Laufwerk.
/dev/sdb1 /media/USBRaid ext4 auto,nouser,exec,async,noatime 0 0
# Network Attached Storage Synology
192.168.2.120:/volume1/backup /media/synology223j/backup nfs auto,user,exec,async,noatime 0 0
.
.
Das Script funktioniert einwandfrei mit dem #USBRaid Laufwerk (RAID 0 - Striping)
aber nicht mit dem #Synology #NAS (RAID 1 - Mirroring), dort wird mir mein /home auch im Tagesordner gespeichert.
.
.
??? Kann sich hier wer vorstellen oder weiß warum das mit der #NAS nicht funzt ???

Brauche mal Hilfe für #linux #debian #trixie #nas #usbraid #nfs #usb #rsync #bash.

Ich habe ein #Script das nicht funktioniert und doch funktioniert *grrrr*

(Script Begin)
#!/bin/bash

set -ex

# check for mount
grep /backup /etc/mtab > /dev/null || exit 1

# directory to backup
BDIR=/home/wilma_wein/

# Destination dir for rsync
DDIR=/media/backup

# excludes file - this contains a wildcard pattern per line of files to exclude
EXCLUDES=/root/rsy.excl

# BACKUPDIR=${1:-`date +%A`}
BACKUPDIR=${1:-"day"`date +%d`}

OPTS="--force
--ignore-errors \
--delete-excluded \
--exclude-from=$EXCLUDES
--delete --backup --backup-dir=$DDIR/$BACKUPDIR -a -v"

export PATH=$PATH:/bin:/usr/bin:/usr/local/bin

# if destination does not exist, make it;-)
[ -d $DDIR ] || mkdir $DDIR

# write logfile
echo oooooooooooooooooooooooooooooooooooooooooooo >> /root/rsy.log
date >> /root/rsy.log

# delete existing backup dir
[ -d $DDIR/$BACKUPDIR ] && (echo remaking $DDIR/$BACKUPDIR >> /root/rsy.log; rm -r $DDIR/$BACKUPDIR)

# now the actual transfer
rsync $OPTS $BDIR $DDIR/current >> /root/rsy.log

(Script Ende)
.
.
Dieses Script soll mir mein komplettes /home sichern und gelöschte dateien in den heutigen Tag (Ordner day20 anlegen) und die gelöschte oder alte Datei (sofern geändert) verschieben. Die geänderte neue Datei im BackUp Ordner belassen.

Folgende Laufwerke sind in meiner #fstab gemountet:

# Angeschlossenes USB RAID Laufwerk.
/dev/sdb1 /media/USBRaid ext4 auto,nouser,exec,async,noatime 0 0
# Network Attached Storage Synology
192.168.2.120:/volume1/backup /media/synology223j/backup nfs auto,user,exec,async,noatime 0 0
.
.
Das Script funktioniert einwandfrei mit dem #USBRaid Laufwerk (RAID 0 - Striping)
aber nicht mit dem #Synology #NAS (RAID 1 - Mirroring), dort wird mir mein /home auch im Tagesordner gespeichert.
.
.
??? Kann sich hier wer vorstellen oder weiß warum das mit der #NAS nicht funzt ???

Brauche mal Hilfe für #linux #debian #trixie #nas #usbraid #nfs #usb #rsync #bash.

Ich habe ein #Script das nicht funktioniert und doch funktioniert *grrrr*

(Script Begin)
#!/bin/bash

set -ex

# check for mount
grep /backup /etc/mtab > /dev/null || exit 1

# directory to backup
BDIR=/home/wilma_wein/

# Destination dir for rsync
DDIR=/media/backup

# excludes file - this contains a wildcard pattern per line of files to exclude
EXCLUDES=/root/rsy.excl

# BACKUPDIR=${1:-`date +%A`}
BACKUPDIR=${1:-"day"`date +%d`}

OPTS="--force
--ignore-errors \
--delete-excluded \
--exclude-from=$EXCLUDES
--delete --backup --backup-dir=$DDIR/$BACKUPDIR -a -v"

export PATH=$PATH:/bin:/usr/bin:/usr/local/bin

# if destination does not exist, make it;-)
[ -d $DDIR ] || mkdir $DDIR

# write logfile
echo oooooooooooooooooooooooooooooooooooooooooooo >> /root/rsy.log
date >> /root/rsy.log

# delete existing backup dir
[ -d $DDIR/$BACKUPDIR ] && (echo remaking $DDIR/$BACKUPDIR >> /root/rsy.log; rm -r $DDIR/$BACKUPDIR)

# now the actual transfer
rsync $OPTS $BDIR $DDIR/current >> /root/rsy.log

(Script Ende)
.
.
Dieses Script soll mir mein komplettes /home sichern und gelöschte dateien in den heutigen Tag (Ordner day20 anlegen) und die gelöschte oder alte Datei (sofern geändert) verschieben. Die geänderte neue Datei im BackUp Ordner belassen.

Folgende Laufwerke sind in meiner #fstab gemountet:

# Angeschlossenes USB RAID Laufwerk.
/dev/sdb1 /media/USBRaid ext4 auto,nouser,exec,async,noatime 0 0
# Network Attached Storage Synology
192.168.2.120:/volume1/backup /media/synology223j/backup nfs auto,user,exec,async,noatime 0 0
.
.
Das Script funktioniert einwandfrei mit dem #USBRaid Laufwerk (RAID 0 - Striping)
aber nicht mit dem #Synology #NAS (RAID 1 - Mirroring), dort wird mir mein /home auch im Tagesordner gespeichert.
.
.
??? Kann sich hier wer vorstellen oder weiß warum das mit der #NAS nicht funzt ???

Brauche mal Hilfe für #linux #debian #trixie #nas #usbraid #nfs #usb #rsync #bash.

Ich habe ein #Script das nicht funktioniert und doch funktioniert *grrrr*

(Script Begin)
#!/bin/bash

set -ex

# check for mount
grep /backup /etc/mtab > /dev/null || exit 1

# directory to backup
BDIR=/home/wilma_wein/

# Destination dir for rsync
DDIR=/media/backup

# excludes file - this contains a wildcard pattern per line of files to exclude
EXCLUDES=/root/rsy.excl

# BACKUPDIR=${1:-`date +%A`}
BACKUPDIR=${1:-"day"`date +%d`}

OPTS="--force
--ignore-errors \
--delete-excluded \
--exclude-from=$EXCLUDES
--delete --backup --backup-dir=$DDIR/$BACKUPDIR -a -v"

export PATH=$PATH:/bin:/usr/bin:/usr/local/bin

# if destination does not exist, make it;-)
[ -d $DDIR ] || mkdir $DDIR

# write logfile
echo oooooooooooooooooooooooooooooooooooooooooooo >> /root/rsy.log
date >> /root/rsy.log

# delete existing backup dir
[ -d $DDIR/$BACKUPDIR ] && (echo remaking $DDIR/$BACKUPDIR >> /root/rsy.log; rm -r $DDIR/$BACKUPDIR)

# now the actual transfer
rsync $OPTS $BDIR $DDIR/current >> /root/rsy.log

(Script Ende)
.
.
Dieses Script soll mir mein komplettes /home sichern und gelöschte dateien in den heutigen Tag (Ordner day20 anlegen) und die gelöschte oder alte Datei (sofern geändert) verschieben. Die geänderte neue Datei im BackUp Ordner belassen.

Folgende Laufwerke sind in meiner #fstab gemountet:

# Angeschlossenes USB RAID Laufwerk.
/dev/sdb1 /media/USBRaid ext4 auto,nouser,exec,async,noatime 0 0
# Network Attached Storage Synology
192.168.2.120:/volume1/backup /media/synology223j/backup nfs auto,user,exec,async,noatime 0 0
.
.
Das Script funktioniert einwandfrei mit dem #USBRaid Laufwerk (RAID 0 - Striping)
aber nicht mit dem #Synology #NAS (RAID 1 - Mirroring), dort wird mir mein /home auch im Tagesordner gespeichert.
.
.
??? Kann sich hier wer vorstellen oder weiß warum das mit der #NAS nicht funzt ???

Brauche mal Hilfe für #linux #debian #trixie #nas #usbraid #nfs #usb #rsync #bash.

Ich habe ein #Script das nicht funktioniert und doch funktioniert *grrrr*

(Script Begin)
#!/bin/bash

set -ex

# check for mount
grep /backup /etc/mtab > /dev/null || exit 1

# directory to backup
BDIR=/home/wilma_wein/

# Destination dir for rsync
DDIR=/media/backup

# excludes file - this contains a wildcard pattern per line of files to exclude
EXCLUDES=/root/rsy.excl

# BACKUPDIR=${1:-`date +%A`}
BACKUPDIR=${1:-"day"`date +%d`}

OPTS="--force
--ignore-errors \
--delete-excluded \
--exclude-from=$EXCLUDES
--delete --backup --backup-dir=$DDIR/$BACKUPDIR -a -v"

export PATH=$PATH:/bin:/usr/bin:/usr/local/bin

# if destination does not exist, make it;-)
[ -d $DDIR ] || mkdir $DDIR

# write logfile
echo oooooooooooooooooooooooooooooooooooooooooooo >> /root/rsy.log
date >> /root/rsy.log

# delete existing backup dir
[ -d $DDIR/$BACKUPDIR ] && (echo remaking $DDIR/$BACKUPDIR >> /root/rsy.log; rm -r $DDIR/$BACKUPDIR)

# now the actual transfer
rsync $OPTS $BDIR $DDIR/current >> /root/rsy.log

(Script Ende)
.
.
Dieses Script soll mir mein komplettes /home sichern und gelöschte dateien in den heutigen Tag (Ordner day20 anlegen) und die gelöschte oder alte Datei (sofern geändert) verschieben. Die geänderte neue Datei im BackUp Ordner belassen.

Folgende Laufwerke sind in meiner #fstab gemountet:

# Angeschlossenes USB RAID Laufwerk.
/dev/sdb1 /media/USBRaid ext4 auto,nouser,exec,async,noatime 0 0
# Network Attached Storage Synology
192.168.2.120:/volume1/backup /media/synology223j/backup nfs auto,user,exec,async,noatime 0 0
.
.
Das Script funktioniert einwandfrei mit dem #USBRaid Laufwerk (RAID 0 - Striping)
aber nicht mit dem #Synology #NAS (RAID 1 - Mirroring), dort wird mir mein /home auch im Tagesordner gespeichert.
.
.
??? Kann sich hier wer vorstellen oder weiß warum das mit der #NAS nicht funzt ???

Excelente tutorial de @LastDragonMX para aprender a montar usb's y discos duros en #GNU #Linux para uso temporal o permanente.

Montar discos usando el clásico #fstab o el nuevo #systemd
https://youtu.be/VMQU6dmUSlk?si=BTtpDRYJPLrZKqGl

Русская рулетка дедиков: Собираем RAID 1 + LVM на живой системе без Rescue-режима

Ситуация до боли знакома каждому, кто регулярно арендует выделенные серверы: вы оплачиваете счет, заходите по SSH и видите, что ОС установлена на /dev/sda, а второй диск просто болтается пустым. Никакого RAID, никакой отказоустойчивости. Умрет первый диск — ваши данные исчезнут. Мы в SoftStore идем по пути полного контроля над процессом. В этой статье разбираем пошаговый протокол: как собрать программный RAID 1 и LVM прямо на живой, работающей операционной системе без использования Rescue-режима и переустановки. В качестве бонуса — практика по управлению квотами, снапшотами и замене дисков в Production.

https://habr.com/ru/articles/1029498/

#RAID #LVM #mdadm #Linux #Debian #выделенный_сервер #миграция #системный_администратор #fstab #администрирование

Русская рулетка дедиков: Собираем RAID 1 + LVM на живой системе без Rescue-режима

Ситуация до боли знакома каждому, кто регулярно арендует выделенные серверы: вы оплачиваете счет, заходите по SSH и видите, что ОС установлена на /dev/sda, а второй диск просто болтается пустым. Никакого RAID, никакой отказоустойчивости. Умрет первый диск — ваши данные исчезнут. Мы в SoftStore идем по пути полного контроля над процессом. В этой статье разбираем пошаговый протокол: как собрать программный RAID 1 и LVM прямо на живой, работающей операционной системе без использования Rescue-режима и переустановки. В качестве бонуса — практика по управлению квотами, снапшотами и замене дисков в Production.

https://habr.com/ru/articles/1029498/

#RAID #LVM #mdadm #Linux #Debian #выделенный_сервер #миграция #системный_администратор #fstab #администрирование

Русская рулетка дедиков: Собираем RAID 1 + LVM на живой системе без Rescue-режима

Ситуация до боли знакома каждому, кто регулярно арендует выделенные серверы: вы оплачиваете счет, заходите по SSH и видите, что ОС установлена на /dev/sda, а второй диск просто болтается пустым. Никакого RAID, никакой отказоустойчивости. Умрет первый диск — ваши данные исчезнут. Мы в SoftStore идем по пути полного контроля над процессом. В этой статье разбираем пошаговый протокол: как собрать программный RAID 1 и LVM прямо на живой, работающей операционной системе без использования Rescue-режима и переустановки. В качестве бонуса — практика по управлению квотами, снапшотами и замене дисков в Production.

https://habr.com/ru/articles/1029498/

#RAID #LVM #mdadm #Linux #Debian #выделенный_сервер #миграция #системный_администратор #fstab #администрирование

Русская рулетка дедиков: Собираем RAID 1 + LVM на живой системе без Rescue-режима

Ситуация до боли знакома каждому, кто регулярно арендует выделенные серверы: вы оплачиваете счет, заходите по SSH и видите, что ОС установлена на /dev/sda, а второй диск просто болтается пустым. Никакого RAID, никакой отказоустойчивости. Умрет первый диск — ваши данные исчезнут. Мы в SoftStore идем по пути полного контроля над процессом. В этой статье разбираем пошаговый протокол: как собрать программный RAID 1 и LVM прямо на живой, работающей операционной системе без использования Rescue-режима и переустановки. В качестве бонуса — практика по управлению квотами, снапшотами и замене дисков в Production.

https://habr.com/ru/articles/1029498/

#RAID #LVM #mdadm #Linux #Debian #выделенный_сервер #миграция #системный_администратор #fstab #администрирование

#Linux #Festplatten #mounten & #automatisch einbinden – #fstab einfach erklärt!

In diesem Linux Tutorial zeige ich dir Schritt für Schritt, wie du Festplatten und Partitionen unter Linux mountest und mit fstab dauerhaft ins System einbindest.

Mit dem #mount #Befehl kannst du deine Festplatte überall in deinem Linux Betriebssystem einbinden und mit der fstab Datei kannst du den mount Vorgang automatisieren...

#Linux_Infinite

@LinuxInfinite

https://youtube.com/watch?v=w3gC80RQ0Tk&is=yIWR1bvMKGzThw2n

#Linux #Festplatten #mounten & #automatisch einbinden – #fstab einfach erklärt!

In diesem Linux Tutorial zeige ich dir Schritt für Schritt, wie du Festplatten und Partitionen unter Linux mountest und mit fstab dauerhaft ins System einbindest.

Mit dem #mount #Befehl kannst du deine Festplatte überall in deinem Linux Betriebssystem einbinden und mit der fstab Datei kannst du den mount Vorgang automatisieren...

#Linux_Infinite

@LinuxInfinite

https://youtube.com/watch?v=w3gC80RQ0Tk&is=yIWR1bvMKGzThw2n

#Linux #Festplatten #mounten & #automatisch einbinden – #fstab einfach erklärt!

In diesem Linux Tutorial zeige ich dir Schritt für Schritt, wie du Festplatten und Partitionen unter Linux mountest und mit fstab dauerhaft ins System einbindest.

Mit dem #mount #Befehl kannst du deine Festplatte überall in deinem Linux Betriebssystem einbinden und mit der fstab Datei kannst du den mount Vorgang automatisieren...

#Linux_Infinite

@LinuxInfinite

https://youtube.com/watch?v=w3gC80RQ0Tk&is=yIWR1bvMKGzThw2n

#Linux #Festplatten #mounten & #automatisch einbinden – #fstab einfach erklärt!

In diesem Linux Tutorial zeige ich dir Schritt für Schritt, wie du Festplatten und Partitionen unter Linux mountest und mit fstab dauerhaft ins System einbindest.

Mit dem #mount #Befehl kannst du deine Festplatte überall in deinem Linux Betriebssystem einbinden und mit der fstab Datei kannst du den mount Vorgang automatisieren...

#Linux_Infinite

@LinuxInfinite

https://youtube.com/watch?v=w3gC80RQ0Tk&is=yIWR1bvMKGzThw2n

#Linux #Festplatten #mounten & #automatisch einbinden – #fstab einfach erklärt!

In diesem Linux Tutorial zeige ich dir Schritt für Schritt, wie du Festplatten und Partitionen unter Linux mountest und mit fstab dauerhaft ins System einbindest.

Mit dem #mount #Befehl kannst du deine Festplatte überall in deinem Linux Betriebssystem einbinden und mit der fstab Datei kannst du den mount Vorgang automatisieren...

#Linux_Infinite

@LinuxInfinite

https://youtube.com/watch?v=w3gC80RQ0Tk&is=yIWR1bvMKGzThw2n

@garyhtech

Operation not permitted probably because the ESP-related mount was unnecessary (it already existed).

Check the default /etc/fstab

This 2021 commit might be the milestone first of a series of commits that simplified things:

https://github.com/freebsd/freebsd-src/commit/0b7472b3d8d2f1e90fade5236b44fd98d8e396c2

#FreeBSD #boot #loader #EFI #UEFI #ESP #fstab

@garyhtech

Operation not permitted probably because the ESP-related mount was unnecessary (it already existed).

Check the default /etc/fstab

This 2021 commit might be the milestone first of a series of commits that simplified things:

https://github.com/freebsd/freebsd-src/commit/0b7472b3d8d2f1e90fade5236b44fd98d8e396c2

#FreeBSD #boot #loader #EFI #UEFI #ESP #fstab

@garyhtech

Operation not permitted probably because the ESP-related mount was unnecessary (it already existed).

Check the default /etc/fstab

This 2021 commit might be the milestone first of a series of commits that simplified things:

https://github.com/freebsd/freebsd-src/commit/0b7472b3d8d2f1e90fade5236b44fd98d8e396c2

#FreeBSD #boot #loader #EFI #UEFI #ESP #fstab

@garyhtech

Operation not permitted probably because the ESP-related mount was unnecessary (it already existed).

Check the default /etc/fstab

This 2021 commit might be the milestone first of a series of commits that simplified things:

https://github.com/freebsd/freebsd-src/commit/0b7472b3d8d2f1e90fade5236b44fd98d8e396c2

#FreeBSD #boot #loader #EFI #UEFI #ESP #fstab

@garyhtech

Operation not permitted probably because the ESP-related mount was unnecessary (it already existed).

Check the default /etc/fstab

This 2021 commit might be the milestone first of a series of commits that simplified things:

https://github.com/freebsd/freebsd-src/commit/0b7472b3d8d2f1e90fade5236b44fd98d8e396c2

#FreeBSD #boot #loader #EFI #UEFI #ESP #fstab

A question for my knowledgeable friends:

I have an LVM with two VGs, one on each disk. VG1 has swap, / and a large empty LV (say, VG1-LV3). VG2 has my /home. I want to store my dropbox folder in VG1-LV3 (VG1 is my slower, replaceable storage). Question:

How do I mount it to /home/X/Dropbox so that it ONLY mounts for user X, and works on any login (ssh, shell, DE).

A simple fstab with uid,gid makes it visible to all.

#sysadmin #LVM #linux #advice #fstab #dropbox

A question for my knowledgeable friends:

I have an LVM with two VGs, one on each disk. VG1 has swap, / and a large empty LV (say, VG1-LV3). VG2 has my /home. I want to store my dropbox folder in VG1-LV3 (VG1 is my slower, replaceable storage). Question:

How do I mount it to /home/X/Dropbox so that it ONLY mounts for user X, and works on any login (ssh, shell, DE).

A simple fstab with uid,gid makes it visible to all.

#sysadmin #LVM #linux #advice #fstab #dropbox

A question for my knowledgeable friends:

I have an LVM with two VGs, one on each disk. VG1 has swap, / and a large empty LV (say, VG1-LV3). VG2 has my /home. I want to store my dropbox folder in VG1-LV3 (VG1 is my slower, replaceable storage). Question:

How do I mount it to /home/X/Dropbox so that it ONLY mounts for user X, and works on any login (ssh, shell, DE).

A simple fstab with uid,gid makes it visible to all.

#sysadmin #LVM #linux #advice #fstab #dropbox

A question for my knowledgeable friends:

I have an LVM with two VGs, one on each disk. VG1 has swap, / and a large empty LV (say, VG1-LV3). VG2 has my /home. I want to store my dropbox folder in VG1-LV3 (VG1 is my slower, replaceable storage). Question:

How do I mount it to /home/X/Dropbox so that it ONLY mounts for user X, and works on any login (ssh, shell, DE).

A simple fstab with uid,gid makes it visible to all.

#sysadmin #LVM #linux #advice #fstab #dropbox

A question for my knowledgeable friends:

I have an LVM with two VGs, one on each disk. VG1 has swap, / and a large empty LV (say, VG1-LV3). VG2 has my /home. I want to store my dropbox folder in VG1-LV3 (VG1 is my slower, replaceable storage). Question:

How do I mount it to /home/X/Dropbox so that it ONLY mounts for user X, and works on any login (ssh, shell, DE).

A simple fstab with uid,gid makes it visible to all.

#sysadmin #LVM #linux #advice #fstab #dropbox

@dvl

Retrospective. From @david_chisnall in June 2025:

https://lists.freebsd.org/archives/freebsd-hackers/2025-June/004631.html

"… raw device nodes. Nothing in the system appears to check the underlying partition type when enabling swap on these devices, so if you plug in another device and things are renumbered then swapping will write nonsense over a different partition …

"I think I have filed bugs about all of these issues. It would be great if folks looking to improve the installer could consider some of them. …"

Nothing open for swap with the 'install' keyword:

https://bugs.freebsd.org/bugzilla/buglist.cgi?keywords=install%2C%20&keywords_type=allwords&list_id=888775&order=Bug%20Number&query_format=advanced&short_desc=swap&short_desc_type=allwordssubstr

#FreeBSD #dataloss #swap #fstab

@dvl

Retrospective. From @david_chisnall in June 2025:

https://lists.freebsd.org/archives/freebsd-hackers/2025-June/004631.html

"… raw device nodes. Nothing in the system appears to check the underlying partition type when enabling swap on these devices, so if you plug in another device and things are renumbered then swapping will write nonsense over a different partition …

"I think I have filed bugs about all of these issues. It would be great if folks looking to improve the installer could consider some of them. …"

Nothing open for swap with the 'install' keyword:

https://bugs.freebsd.org/bugzilla/buglist.cgi?keywords=install%2C%20&keywords_type=allwords&list_id=888775&order=Bug%20Number&query_format=advanced&short_desc=swap&short_desc_type=allwordssubstr

#FreeBSD #dataloss #swap #fstab

@dvl

Retrospective. From @david_chisnall in June 2025:

https://lists.freebsd.org/archives/freebsd-hackers/2025-June/004631.html

"… raw device nodes. Nothing in the system appears to check the underlying partition type when enabling swap on these devices, so if you plug in another device and things are renumbered then swapping will write nonsense over a different partition …

"I think I have filed bugs about all of these issues. It would be great if folks looking to improve the installer could consider some of them. …"

Nothing open for swap with the 'install' keyword:

https://bugs.freebsd.org/bugzilla/buglist.cgi?keywords=install%2C%20&keywords_type=allwords&list_id=888775&order=Bug%20Number&query_format=advanced&short_desc=swap&short_desc_type=allwordssubstr

#FreeBSD #dataloss #swap #fstab

@dvl

Retrospective. From @david_chisnall in June 2025:

https://lists.freebsd.org/archives/freebsd-hackers/2025-June/004631.html

"… raw device nodes. Nothing in the system appears to check the underlying partition type when enabling swap on these devices, so if you plug in another device and things are renumbered then swapping will write nonsense over a different partition …

"I think I have filed bugs about all of these issues. It would be great if folks looking to improve the installer could consider some of them. …"

Nothing open for swap with the 'install' keyword:

https://bugs.freebsd.org/bugzilla/buglist.cgi?keywords=install%2C%20&keywords_type=allwords&list_id=888775&order=Bug%20Number&query_format=advanced&short_desc=swap&short_desc_type=allwordssubstr

#FreeBSD #dataloss #swap #fstab

@dvl

Retrospective. From @david_chisnall in June 2025:

https://lists.freebsd.org/archives/freebsd-hackers/2025-June/004631.html

"… raw device nodes. Nothing in the system appears to check the underlying partition type when enabling swap on these devices, so if you plug in another device and things are renumbered then swapping will write nonsense over a different partition …

"I think I have filed bugs about all of these issues. It would be great if folks looking to improve the installer could consider some of them. …"

Nothing open for swap with the 'install' keyword:

https://bugs.freebsd.org/bugzilla/buglist.cgi?keywords=install%2C%20&keywords_type=allwords&list_id=888775&order=Bug%20Number&query_format=advanced&short_desc=swap&short_desc_type=allwordssubstr

#FreeBSD #dataloss #swap #fstab

#arch community: I want to mount a #webdav storage to my filesystem. I want to follow the #davfs2 wiki as described here https://wiki.archlinux.org/title/Davfs2. I'm a bit confused over the #systemd section. Do I really have to configure mount units manually? Like I would have expected that it takes whatever is configured in #fstab?

#linux @arch_linux

#arch community: I want to mount a #webdav storage to my filesystem. I want to follow the #davfs2 wiki as described here https://wiki.archlinux.org/title/Davfs2. I'm a bit confused over the #systemd section. Do I really have to configure mount units manually? Like I would have expected that it takes whatever is configured in #fstab?

#linux @arch_linux

#arch community: I want to mount a #webdav storage to my filesystem. I want to follow the #davfs2 wiki as described here https://wiki.archlinux.org/title/Davfs2. I'm a bit confused over the #systemd section. Do I really have to configure mount units manually? Like I would have expected that it takes whatever is configured in #fstab?

#linux @arch_linux

#arch community: I want to mount a #webdav storage to my filesystem. I want to follow the #davfs2 wiki as described here https://wiki.archlinux.org/title/Davfs2. I'm a bit confused over the #systemd section. Do I really have to configure mount units manually? Like I would have expected that it takes whatever is configured in #fstab?

#linux @arch_linux

#arch community: I want to mount a #webdav storage to my filesystem. I want to follow the #davfs2 wiki as described here https://wiki.archlinux.org/title/Davfs2. I'm a bit confused over the #systemd section. Do I really have to configure mount units manually? Like I would have expected that it takes whatever is configured in #fstab?

#linux @arch_linux

I'm now able to:
- create #btrfs subvolume
- Ensure entry in #fstab
- mount it
- create, init & enable #swapfile
- Ensure entry in fstab

\o/

#Ansible #ConfigurationManagement

I'm now able to:
- create #btrfs subvolume
- Ensure entry in #fstab
- mount it
- create, init & enable #swapfile
- Ensure entry in fstab

\o/

#Ansible #ConfigurationManagement

I'm now able to:
- create #btrfs subvolume
- Ensure entry in #fstab
- mount it
- create, init & enable #swapfile
- Ensure entry in fstab

\o/

#Ansible #ConfigurationManagement

I'm now able to:
- create #btrfs subvolume
- Ensure entry in #fstab
- mount it
- create, init & enable #swapfile
- Ensure entry in fstab

\o/

#Ansible #ConfigurationManagement

I'm now able to:
- create #btrfs subvolume
- Ensure entry in #fstab
- mount it
- create, init & enable #swapfile
- Ensure entry in fstab

\o/

#Ansible #ConfigurationManagement

Less than a week into my first foray into #Linux and I am already contemplating a different flavour. I spent yesterday backing everything up to my NAS and will try reinstalling the #mint #cinnamon version I started out with.

I’m going to have to try and figure out how to mount my NAS properly in #fstab based on this post: https://forums.linuxmint.com/viewtopic.php?t=326160

Currently it’s invisible unless I enable Time Machine functionality on the NAS. Then it’s inexplicably visible on network.

yay

Less than a week into my first foray into #Linux and I am already contemplating a different flavour. I spent yesterday backing everything up to my NAS and will try reinstalling the #mint #cinnamon version I started out with.

I’m going to have to try and figure out how to mount my NAS properly in #fstab based on this post: https://forums.linuxmint.com/viewtopic.php?t=326160

Currently it’s invisible unless I enable Time Machine functionality on the NAS. Then it’s inexplicably visible on network.

yay

Less than a week into my first foray into #Linux and I am already contemplating a different flavour. I spent yesterday backing everything up to my NAS and will try reinstalling the #mint #cinnamon version I started out with.

I’m going to have to try and figure out how to mount my NAS properly in #fstab based on this post: https://forums.linuxmint.com/viewtopic.php?t=326160

Currently it’s invisible unless I enable Time Machine functionality on the NAS. Then it’s inexplicably visible on network.

yay

Less than a week into my first foray into #Linux and I am already contemplating a different flavour. I spent yesterday backing everything up to my NAS and will try reinstalling the #mint #cinnamon version I started out with.

I’m going to have to try and figure out how to mount my NAS properly in #fstab based on this post: https://forums.linuxmint.com/viewtopic.php?t=326160

Currently it’s invisible unless I enable Time Machine functionality on the NAS. Then it’s inexplicably visible on network.

yay

Less than a week into my first foray into #Linux and I am already contemplating a different flavour. I spent yesterday backing everything up to my NAS and will try reinstalling the #mint #cinnamon version I started out with.

I’m going to have to try and figure out how to mount my NAS properly in #fstab based on this post: https://forums.linuxmint.com/viewtopic.php?t=326160

Currently it’s invisible unless I enable Time Machine functionality on the NAS. Then it’s inexplicably visible on network.

yay

This mornings "lets do some quick updates and reboot while staying in the bed"-session got me out of the bed, because the server did not come online again.

Turns out: If you mount thin-provisioned #LVM logical volumes with #fstab you need thin-provisioning-tools, otherwise the #systemd unit fails during boot. And that package is not a dependency, only recommended on #Debian #Trixie and for some reason wasn't installed on my system.

Longer version: https://swagspace.org/blog/lvm-thin-provisioning-tools/

This mornings "lets do some quick updates and reboot while staying in the bed"-session got me out of the bed, because the server did not come online again.

Turns out: If you mount thin-provisioned #LVM logical volumes with #fstab you need thin-provisioning-tools, otherwise the #systemd unit fails during boot. And that package is not a dependency, only recommended on #Debian #Trixie and for some reason wasn't installed on my system.

Longer version: https://swagspace.org/blog/lvm-thin-provisioning-tools/

This mornings "lets do some quick updates and reboot while staying in the bed"-session got me out of the bed, because the server did not come online again.

Turns out: If you mount thin-provisioned #LVM logical volumes with #fstab you need thin-provisioning-tools, otherwise the #systemd unit fails during boot. And that package is not a dependency, only recommended on #Debian #Trixie and for some reason wasn't installed on my system.

Longer version: https://swagspace.org/blog/lvm-thin-provisioning-tools/

This mornings "lets do some quick updates and reboot while staying in the bed"-session got me out of the bed, because the server did not come online again.

Turns out: If you mount thin-provisioned #LVM logical volumes with #fstab you need thin-provisioning-tools, otherwise the #systemd unit fails during boot. And that package is not a dependency, only recommended on #Debian #Trixie and for some reason wasn't installed on my system.

Longer version: https://swagspace.org/blog/lvm-thin-provisioning-tools/

New 𝗖𝗿𝘂𝗰𝗶𝗮𝗹 𝗙𝗿𝗲𝗲𝗕𝗦𝗗 𝗧𝗼𝗼𝗹𝗸𝗶𝘁 [Crucial FreeBSD Toolkit] article on the blog.

https://vermaden.wordpress.com/2025/07/08/crucial-freebsd-toolkit/

#verblog #beadm #bectl #devfs #diskinfo #free #freebsd #fstab #gstat #jails #linux #lsblk #sensors #sockstat #systat #tar #truss #truncate #zfs