home.social

#filesystem — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #filesystem, aggregated by home.social.

fetched live
  1. Have published new -rc3 of #foxing ; the tl;dr is I fixed a selinux and permisions/gid:uid preservation behavior that differed from #rsync / expected outcome in the standalone fxcp tool, and did a crap-load more testing over the last month or so in real-world situations. Other than that a couple of other doc/code hygiene things only. codeberg.org/aenertia/foxing/r #linux #filesystem

  2. Have published new -rc3 of #foxing ; the tl;dr is I fixed a selinux and permisions/gid:uid preservation behavior that differed from #rsync / expected outcome in the standalone fxcp tool, and did a crap-load more testing over the last month or so in real-world situations. Other than that a couple of other doc/code hygiene things only. codeberg.org/aenertia/foxing/r #linux #filesystem

  3. 🥝 kiwifs/kiwifs

    Markdown filesystem for agents and teams.

    Turns markdown files into a searchable, versioned filesystem with a built-in web UI and agent integration

    ⭐ Stars: 620
    📅 Last Update: Jul 22, 2026

    github.com/kiwifs/kiwifs

    #selfhosted #homelab #selfhost #selfhosting #opensource #markdown #filesystem

  4. #TIL that the #FAT #filesystem doesn't really store anywhere whether it's #FAT12, #FAT16 and #FAT32. What you're supposed to do is to look at the number of clusters, and determine which range it falls into. More specifically, you're supposed to look at the partition size and divide it by the number of sectors per cluster (which is stored in consistent position irrespective of FAT type).

    The obvious implication of that is that the volume sizes are limited by possible cluster size ranges. There's some overlap here, though: you get more clusters (and therefore use a "longer" FAT) by using a smaller cluster size, or fewer clusters by using a larger cluster size.

    elm-chan.org/docs/fat_e.html#f

    However, there's a curious trick: there's a 16-bit "FAT size" field that indicates how many sectors are used for FAT on FAT12/FAT16 filesystems. On FAT32 this field is zero (there is a separate field for 32-bit FAT size there), and apparently some tools recognize the filesystem as FAT32 in that case, irrespective of number of clusters. This is what mkfs.vfat does when you force FAT32 on a small block device.

    github.com/torvalds/linux/blob

    Why did I learn all this? Because a friend tried to make a very small EFI partition and was surprised it didn't work. I was compelled to get to a bottom of this!

  5. #TIL that the #FAT #filesystem doesn't really store anywhere whether it's #FAT12, #FAT16 and #FAT32. What you're supposed to do is to look at the number of clusters, and determine which range it falls into. More specifically, you're supposed to look at the partition size and divide it by the number of sectors per cluster (which is stored in consistent position irrespective of FAT type).

    The obvious implication of that is that the volume sizes are limited by possible cluster size ranges. There's some overlap here, though: you get more clusters (and therefore use a "longer" FAT) by using a smaller cluster size, or fewer clusters by using a larger cluster size.

    elm-chan.org/docs/fat_e.html#f

    However, there's a curious trick: there's a 16-bit "FAT size" field that indicates how many sectors are used for FAT on FAT12/FAT16 filesystems. On FAT32 this field is zero (there is a separate field for 32-bit FAT size there), and apparently some tools recognize the filesystem as FAT32 in that case, irrespective of number of clusters. This is what mkfs.vfat does when you force FAT32 on a small block device.

    github.com/torvalds/linux/blob

    Why did I learn all this? Because a friend tried to make a very small EFI partition and was surprised it didn't work. I was compelled to get to a bottom of this!

  6. Dear Fedi, I'm looking (and have been looking) for some time for a simple way to mount a transparent local cache for a remote filesystem (preferably sshfs) that is known to be "append only" (i.e. files are never modified after creation). This seems like a very trivial task to implement with libfuse, but I haven't found anything before. Overlayfs and other kernel options seem to be overly finicky and create more issues than they solve. I might write something myself but really hoping I don't have to. Pls boost :blobcatupsidedown:

    #Linux #filesystem #sshfs #fuse

  7. Dear Fedi, I'm looking (and have been looking) for some time for a simple way to mount a transparent local cache for a remote filesystem (preferably sshfs) that is known to be "append only" (i.e. files are never modified after creation). This seems like a very trivial task to implement with libfuse, but I haven't found anything before. Overlayfs and other kernel options seem to be overly finicky and create more issues than they solve. I might write something myself but really hoping I don't have to. Pls boost :blobcatupsidedown:

    #Linux #filesystem #sshfs #fuse

  8. Open-source replacement for the Amiga's CD file system: ODFileSystem 0.6

    Version 0.6 is a performance release: On the cdbench fixture (68020 -O2 release build) sequential read throughput climbs from 46,262 KiB/s to 197,673 KiB/s — a 4.3× increase (+327%) — and now runs 27% faster than the original AmigaOS 3.2.x CDFileSystem it replaces. This release also adds High Sierra, ISO 9660 Level 3, and native symlink support.

    amiga-news.de/en/news/AN-2026-

  9. Open-source replacement for the Amiga's CD file system: ODFileSystem 0.6

    Version 0.6 is a performance release: On the cdbench fixture (68020 -O2 release build) sequential read throughput climbs from 46,262 KiB/s to 197,673 KiB/s — a 4.3× increase (+327%) — and now runs 27% faster than the original AmigaOS 3.2.x CDFileSystem it replaces. This release also adds High Sierra, ISO 9660 Level 3, and native symlink support.

    amiga-news.de/en/news/AN-2026-

    #Amiga #AmigaOS4 #CD #filesystem

  10. I'm not the only, and definitely not the first one to (re)consider the #filesystem for #database use.

    The #BeFS documentation (from #HaikuOS website) clearly states - and does that - already (2004):

    > "[key/value metadata attributes] add considerable power to a file system and endow the file system with many of the features normally associated with a database."

    haiku-os.org/legacy-docs/pract

    #AHAlodeck

  11. I'm not the only, and definitely not the first one to (re)consider the #filesystem for #database use.

    The #BeFS documentation (from #HaikuOS website) clearly states - and does that - already (2004):

    > "[key/value metadata attributes] add considerable power to a file system and endow the file system with many of the features normally associated with a database."

    haiku-os.org/legacy-docs/pract

    #AHAlodeck

  12. Can't rename "File" to "file" on an exFAT drive in Linux? Learn why case-only renames fail, how exFAT compares filenames, and the simple workaround.

    Full guide here: ostechnix.com/why-case-only-re

    #exfat #filesystem #linux #rename #troubleshooting #linuxhowto #linuxcommands #linuxbasics

  13. Can't rename "File" to "file" on an exFAT drive in Linux? Learn why case-only renames fail, how exFAT compares filenames, and the simple workaround.

    Full guide here: ostechnix.com/why-case-only-re

    #exfat #filesystem #linux #rename #troubleshooting #linuxhowto #linuxcommands #linuxbasics

  14. Ah, yes, just what the world needed: a #filesystem that turns your storage into a Rube Goldberg machine 🤹‍♂️. Who wouldn’t want to "log-structure" their S3 buckets until they can't recognize them from a block of Swiss cheese 🧀? And let's not forget the dream of using #Docker to turn your cloud storage into a pretentious art installation that only runs in 17 easy steps! 🚀
    zerofs.net/ #RubeGoldberg #cloudstorage #techhumor #HackerNews #ngated

  15. Ah, yes, just what the world needed: a #filesystem that turns your storage into a Rube Goldberg machine 🤹‍♂️. Who wouldn’t want to "log-structure" their S3 buckets until they can't recognize them from a block of Swiss cheese 🧀? And let's not forget the dream of using #Docker to turn your cloud storage into a pretentious art installation that only runs in 17 easy steps! 🚀
    zerofs.net/ #RubeGoldberg #cloudstorage #techhumor #HackerNews #ngated

  16. I am experiencing this with #OpenZFS

    ➜  ~ sudo zpool status -x
    pool: ughetto
    state: DEGRADED
    status: One or more devices could not be used because the label is missing or
    invalid. Sufficient replicas exist for the pool to continue
    functioning in a degraded state.
    action: Replace the device using 'zpool replace'.
    see: https://openzfs.github.io/openzfs-docs/msg/ZFS-8000-4J
    scan: scrub in progress since Sat Jun 27 18:44:31 2026
    141G / 141G scanned, 11.8G / 141G issued at 184M/s
    0B repaired, 8.39% done, 00:12:00 to go
    config:

    NAME STATE READ WRITE CKSUM
    ughetto DEGRADED 0 0 0
    mirror-0 DEGRADED 0 0 0
    653332104939013944 UNAVAIL 0 0 0 was /dev/sdb1
    sdc ONLINE 0 0 0
    cache
    sda FAULTED 0 0 0 corrupted data

    errors: No known data errors

    This has already happened, but at a point where I didn’t mind losing the data, so I destroyed the pool and I recreated it from scratch, with no errors. Now, I would like to try to repair the corrupted data… Any tips? I would hate it if I have to throw away the hard disk, it’s less than one year old and I have been using it only for a couple of months… Is replacing the disk my only option?

    #ZFS #systemAdministration #help #sysAd #techSupport #dataLoss #storage #partition #hardDisk #HDD #Linux #filesystem #data #storage

  17. I am experiencing this with #OpenZFS

    ➜  ~ sudo zpool status -x
    pool: ughetto
    state: DEGRADED
    status: One or more devices could not be used because the label is missing or
    invalid. Sufficient replicas exist for the pool to continue
    functioning in a degraded state.
    action: Replace the device using 'zpool replace'.
    see: https://openzfs.github.io/openzfs-docs/msg/ZFS-8000-4J
    scan: scrub in progress since Sat Jun 27 18:44:31 2026
    141G / 141G scanned, 11.8G / 141G issued at 184M/s
    0B repaired, 8.39% done, 00:12:00 to go
    config:

    NAME STATE READ WRITE CKSUM
    ughetto DEGRADED 0 0 0
    mirror-0 DEGRADED 0 0 0
    653332104939013944 UNAVAIL 0 0 0 was /dev/sdb1
    sdc ONLINE 0 0 0
    cache
    sda FAULTED 0 0 0 corrupted data

    errors: No known data errors

    This has already happened, but at a point where I didn’t mind losing the data, so I destroyed the pool and I recreated it from scratch, with no errors. Now, I would like to try to repair the corrupted data… Any tips? I would hate it if I have to throw away the hard disk, it’s less than one year old and I have been using it only for a couple of months… Is replacing the disk my only option?

    #ZFS #systemAdministration #help #sysAd #techSupport #dataLoss #storage #partition #hardDisk #HDD #Linux #filesystem #data #storage

  18. OpenZFS is more than a filesystem. It is a filesystem and volume manager designed to simplify storage administration. #zfs #filesystem #encryption #compression

    tomsitcafe.com/2026/06/25/use-

  19. OpenZFS is more than a filesystem. It is a filesystem and volume manager designed to simplify storage administration. #zfs #filesystem #encryption #compression

    tomsitcafe.com/2026/06/25/use-

  20. This guide to deleting a file in Linux unravels the historical weight of Unix design, the psychological burden of permanent data loss, and the systemic implications of reclaiming storage space through kernel intervention.

    the-kalvin-blog.obulou.xyz/how

    #Linux #tutorial #guide #command #technology #filesystem #terminal #deletion #parody #philosophy #computing #systems #howto #development #coding

  21. This guide to deleting a file in Linux unravels the historical weight of Unix design, the psychological burden of permanent data loss, and the systemic implications of reclaiming storage space through kernel intervention.

    the-kalvin-blog.obulou.xyz/how

    #Linux #tutorial #guide #command #technology #filesystem #terminal #deletion #parody #philosophy #computing #systems #howto #development #coding

  22. This guide to creating a new folder in Linux examines the historical evolution of file systems, the structural necessity of hierarchical organization, and the deep philosophical implications of digital space management.

    the-kalvin-blog.obulou.xyz/how

    #Linux #command #terminal #howto #technology #tutorial #coding #development #unix #mkdir #filesystem #learning #guide #documentation #storage

  23. This guide to creating a new folder in Linux examines the historical evolution of file systems, the structural necessity of hierarchical organization, and the deep philosophical implications of digital space management.

    the-kalvin-blog.obulou.xyz/how

    #Linux #command #terminal #howto #technology #tutorial #coding #development #unix #mkdir #filesystem #learning #guide #documentation #storage

  24. Ah, yet another groundbreaking file system just dropped: #UTFS, AKA "TAR 2.0," because clearly the future of technology lies in reinventing the wheel...in a different shade of beige. 🚀💾 Prepare to be dazzled by the revolutionary concept of organizing data with strings—truly, we are not worthy! 🙄✨
    clisystems.com/article-UTFS-in #TAR2.0 #fileSystem #dataOrganization #techInnovation #HackerNews #ngated

  25. Ah, yet another groundbreaking file system just dropped: #UTFS, AKA "TAR 2.0," because clearly the future of technology lies in reinventing the wheel...in a different shade of beige. 🚀💾 Prepare to be dazzled by the revolutionary concept of organizing data with strings—truly, we are not worthy! 🙄✨
    clisystems.com/article-UTFS-in #TAR2.0 #fileSystem #dataOrganization #techInnovation #HackerNews #ngated

  26. Corrupting a ZFS File: Fun exploration of figuring out how to bash the bits on a raw disk to deliberately trigger file corruption for ZFS to detect and correct
    oshogbo.com/blog/90/
    #filesystem #hacking #disk #zfs #+

  27. Corrupting a ZFS File: Fun exploration of figuring out how to bash the bits on a raw disk to deliberately trigger file corruption for ZFS to detect and correct
    oshogbo.com/blog/90/
    #filesystem #hacking #disk #zfs #+

  28. 🚀 Behold, the latest tech marvel: a #filesystem from Philip that manages to store absolutely NOTHING. 😂 Just what the developer world needed: another empty innovation to complicate GitHub's menu jungle! 🌳🔍
    github.com/philipl/pifs #techmarvel #emptyinnovation #GitHub #humor #developerworld #HackerNews #ngated

  29. 🚀 Behold, the latest tech marvel: a #filesystem from Philip that manages to store absolutely NOTHING. 😂 Just what the developer world needed: another empty innovation to complicate GitHub's menu jungle! 🌳🔍
    github.com/philipl/pifs #techmarvel #emptyinnovation #GitHub #humor #developerworld #HackerNews #ngated

  30. Finally! The upgraded adaptive #filesystem I have been looking for. Abstracted from #FreeBSD, #linuxbased, #MacOS, #iOS, and #Windows OSes.

    This layout should be sufficient to simplify the app packaging process making the entire production pipeline clean and tidy.

    Enjoy!

    github.com/ChewKeanHo/research

    DOI: doi.org/10.5281/zenodo.17864564

  31. Building on FUSE in Rust tends to involve a lot of boilerplate. libfuse-fs is an attempt to change that - trait-based abstractions, async I/O, overlay and passthrough support out of the box.

    At Oxidize 2026, Ruiji Yu (Nanjing University) covers the design and lessons from real integrations: monorepo access and container image building.

    🔗 oxidizeconf.com/sessions/libfu

    #Oxidize2026 #RustLang #FUSE #Filesystem #AsyncRust #SystemsProgramming

  32. Ah yes, the mystical lost+found folder: where forgotten files meet their afterlife 🤔. Apparently, Linux and Unix enthusiasts need a sacred space to store their digital socks 🧦. Who knew that missing bits would have their own VIP lounge in the filesystem? 🎉
    unix.stackexchange.com/questio #lostfound #digitalfiles #LinuxUnix #filesystem #techhumor #HackerNews #ngated

  33. I spent a whole blog post doing #ZFS on-disk math by hand - just to corrupt one byte and watch #OpenZFS healing process.

    Interested?

    Feel free to join the journey into the on-disk jungle.

    oshogbo.com/blog/90/

    #storage #FreeBSD #Linux #Storage #Filesystem