photog.social is one of the many independent Mastodon servers you can use to participate in the fediverse.
A place for your photos and banter. Photog first is our motto Please refer to the site rules before posting.

Administered by:

Server stats:

246
active users

#ext4

0 posts0 participants0 posts today

Liberado el kernel #linux 6.16! 👏 👏

Por lo poco que vi parece que hay varias mejoras en rendimiento y seguridad!

* Se mejora de rendimiento en #ext4 (entre otros fs)
* Se mejora el soporte para #rust en más subsistemas
* Mejora la optimización de CPU al momento de compilar el kernel en #x86
* Se incorpora el zero-copy en #TCP

Cositas interesantes en el mundo #linux !

kernelnewbies.org/Linux_6.16

kernelnewbies.orgLinux_6.16 - Linux Kernel NewbiesSummary of the changes and new features merged in the Linux kernel during the 6.16 development cycle
Replied in thread

@Klimakipppunkt@troet.cafe @CrazyIT@freiburg.social @alexantemachina@mastodon.social

Um Backups auf ein
#Samba oder #NFS #Share auszulagern, braucht es gar kein Addon. Das geht otb mit Bordmitteln.

Ich würde gern, nach der Erfahrung, dass die komplette Konfiguration sowie
#Datenbank weg waren (komplett leerer Ordner /homeassistant) gerne diese auf ein vernünftiges #Dateisystem wie #ext4 oder #ZFS auslagern.

#exFat ist, basierend auf #Fat32 einfach #FailByDesign und nicht zeitgemäß.

Ich wiederhole mich hier:
Wie man auf die Schnapsidee kommen kann, ein
#Linux basiertes System mit einem exFat Dateisystem auszuliefern, ist einfach komplett unverständlich und 🤡🤡🤡

#Homeassistant #HA

Ich wollte heute eine alte 500GB Festplatte als Musikspeicher für möglichst alle #Betriebssysteme formatieren. Stellt sich mal wieder raus: #FAT32 und #NTFS sind immer noch ungeeignet.
Jede Menge "Sonderzeichen", wie z.B. "?" im Dateinamen werfen Fehler und die Dateien werden nicht gespeichert.
Tjo nun, dann nehm ich eben wieder #Ext4. #Linux kommt damit klar, #MacOS glaube ich auch. Wenn ich die Platte mal an einem #Windows anschließe und sie nicht gelesen werden kann - Pech gehabt.

Today I learned the following. Journaling and journaling are two separate distinctly separate manners of keeping file systems in Sync.

When microsoft talks about journaling in NTFS you should never, ever think about the robust journaling system that Ext4 has

In comparison EXT4 journaling is a god while en NTFS journaling is not even an ant

I have EXT4 file systems connected to an extremely unstable machine. This thing crashes to green screens more than 64 times a day.

{It's a Gigabyte Mini PC in case you're interested never buy those. The machine came with overheating errors from the beginning. The factory installed a fan for the APU which is not even suitable for a GPU that was made a decade ago}

I've not even lost one bit of data on those EXT4 file systems.

Those NTFS file systems with journaling? I lost all of them. All NTFS file systems were lost

I didn't lose data because I have backups the file systems just keeled over simply because the machine kept rebooting

Thank you for being so robust EXT4

so been using arch for the past few days...
couple things I like and don't like...

  1. boot times are nuts, like way faster than any other os I've run on this particular laptop (t480s)
  2. latest gnome, latest kernel and maybe updates are too often? I know there is a testing phase but I've heard horror stories of arch breaking.....might just be a user thing
  3. I already run majority of my apps as flatpaks, so system is light and quick
  4. battery life seems slightly improved, likely due to less resources and background processes

I don't do much gaming, theming, tweaks, no custom kernels, no extra fonts, none of that for me, so I am interested on the longevity and stability going forward. So far I am impressed. Using ext4 so backups should be pretty basic.

Нечаянно удалил все файлы в папке сайта на сервере. В прошлый раз я потерял очень ценный рабочий скрипт-файл и это было в позапрошлом году. Extundelete и testdisk ни черта не помогли. Не тогда, не в этот раз. Пришлось опять через grep искать по подстроке на всём жёстком диске содержимое файла.

Вот примерная строка запуска, если кому надо:
grep --binary-files=text --context=1350 'SELECT * FROM posts WHERE post_hidden < 2' /dev/sda1 > found_data1

Ext4 конечно плоха в этом плане. ReiserFS 3.6 раньше позволяла почти все удалённые файлы восстановить. Интересно как в этом плане дела обстоят у BtrFS и XFS?

Continued thread

Anyway, I was having big issues with trying to create an #EXT4 file system and the same problem was occurring on multiple devices, indicating that it wasn’t the device that was at fault and I concluded that it must be something to do with #mkfs.ext4.

So, I'm currently installing WSL in an attempt to get Windows 11 to view various ext4 filesystems, as I do a lot of stuff with Rasperry Pi machines. This feels...kinda wrong. I hope it works though. I know just enough to be dangerous, but not enough to be a true expert.

#WSL#Linux#Windows

I wonder if anyone can help me with a #Linux #USB issue. I’ve got a new flash drive on which I want to put a Linux directory structure on {with #EXT4, encrypted if possible). However, using the #GNOME #disks utility to #Format it apparently works but when I go into the disk’s root directory, I can’t create any files – I get an input/output error. If I reformat the disk as a #FAT (windows(disk then it works again and so I’m thinking there must be some problem with the utility I’m using.

Replied in thread

System Administration

Week 3, Additional Reading

GUID Partition Table (GPT)
uefi.org/specs/UEFI/2.10/05_GU

The Security War in File Systems: An Empirical Study from A Vulnerability-centric Perspective
dl.acm.org/doi/10.1145/3606020

And to dive a bit deeper into #ext4 and FFS.

Understanding ext4 Disk Layout:
blogs.oracle.com/linux/post/un

ext4 Data Structures and Algorithms:
kernel.org/doc/html/latest/fil

A Brief History of the BSD Fast Filesystem:
freebsdfoundation.org/wp-conte

Is there any know-how about creating filesystems on top of RAID1? Both XFS and ext4 top out at 35 MB/s for me even though the block device below it is capable of 135 MB/s (yes, 4x difference!) This even with an absurdly large I/O request sizes like 512KB.

The disks are old-ish SATA drives with 512-byte sectors. XFS seem to use 512b sectors while ext4 picked 4k. They're connected via USB DAS, with dm-integrity on top of each disk, which are then combined into mdadm raid1, and encrypted with LUKS.

I confirmed with fio that the slowdown happens on the filesystem level, not LUKS or anywhere below it.

The only advice I found online is about alignment, but with 512KB requests it shouldn't be an issue because that's way larger than any of the block/sector sizes involved. I must be missing something, but what is it?

#mdadm#raid#ext4

As someone who lost data before (multiple times) I went for a overkill solution. 😎

Currently in the works:
- #ZFS Mirror 2 x 4TB SSD
- Directly attached 2TB SSD via a USB adapter (Running backup leveraging #rsync every day)
- Offsite 4TB spinning disk that get's plugged in every week (Also using #rsync here)

#FreeBSD and #ZFS keeps my data safe and a disaster strategy is also in place.

Btw, three different filesystems used (#ZFS, #EXT4, #UFS) :freebsd:

Better safe than sorry I'd say! 😉

#Debian question: my systems are all using the... not-non-user-hostile... defaults of encrypted LVM partitions, so I have ~500MB of /boot with #ext4. My / is #XFS so I can't move /boot. I have closed #nvidia drivers via #dkms, maybe that matters.

I used to be able to juggle two kernels, one installed, one to be installed. That fails now, I am stuck.

Are there any good and modern docs on reducing #linux #kernel footprint in /boot?

I can find old stuff, empty stuff, and whataboutism, no docs...