Mastodon 🐘

Runtime ArgumentsIt's another new episode of the <a href="https://hachyderm.io/tags/RuntimeArguments" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#RuntimeArguments</a> <a href="https://hachyderm.io/tags/Podcast" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Podcast</a> hosted by <a href="https://hachyderm.io/@jammcq" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@jammcq</a> and <a href="https://hachyderm.io/@YesJustWolf" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@YesJustWolf</a>.The topic of this episode is <a href="https://hachyderm.io/tags/FileSystems" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#FileSystems</a>. In this one, Jim did the research and Wolf asks the questions. Jim covers <a href="https://hachyderm.io/tags/Linux" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Linux</a> (where there are many filesystem choices, and you actually get to make them!), <a href="https://hachyderm.io/tags/Windows" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Windows</a>, and <a href="https://hachyderm.io/tags/macOS" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#macOS</a>. By the end, whatever your OS, you'll know better what to choose and why!I (Wolf) **definitely** learned from this discussion. We both hope this episode is as fun and informative for you as it was for us. I will say though, that while some of our topics cover a broad audience, this one is a little more focused. I hope you'll give it a try: it may be more fun than you expected.Get it wherever you get your podcasts: "Runtime Arguments". And please send your feedback, questions, and suggestions to <mailto:feedback@RuntimeArguments.fm>, on on Mastodon to <a href="https://hachyderm.io/@RuntimeArguments" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@RuntimeArguments</a>, <a href="https://hachyderm.io/@jammcq" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@jammcq</a>, or <a href="https://hachyderm.io/@YesJustWolf" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@YesJustWolf</a>.

Deekshith AllamaneniExcited for Btrfs RAID1's "preferred read device" feature in Linux 6.14. This allows to have one fast device, example SSD backed bcache device and other slow cheap hard drive. We can set the bcache deice as preferred read device so reads are always fast. It also wears down only one disk reducing the chance of both the disks evenly wearing out which increases the chances of both of them failing around the same time.From the pull request: > more read IO balancing strategies (experimental config), add two new ways how to select a device for read if the profiles allow that (all RAID1*), the current default selects the device by pid which is good on average but less performant for single reader workloads - select preferred device for all reads (namely for testing) - round-robin, balance reads across devices relevant for the requested IO rangeSource: <a href="https://lore.kernel.org/lkml/cover.1737393999.git.dsterba@suse.com/" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://lore.kernel.org/lkml/cover.1737393999.git.dsterba@suse.com/</a><a href="https://techhub.social/tags/btrfs" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#btrfs</a> <a href="https://techhub.social/tags/linux" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#linux</a> <a href="https://techhub.social/tags/linux_6_14" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#linux_6_14</a> <a href="https://techhub.social/tags/filesystems" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#filesystems</a> <a href="https://techhub.social/tags/bcache" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#bcache</a> <a href="https://techhub.social/tags/raid" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#raid</a> <a href="https://techhub.social/tags/raid1" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#raid1</a> <a href="https://techhub.social/tags/nas" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#nas</a> <a href="https://techhub.social/tags/selfhosting" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#selfhosting</a> <a href="https://techhub.social/tags/selfhost" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#selfhost</a>

Coop<a href="https://www.youtube.com/watch?v=ncwn8O70YVg" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://www.youtube.com/watch?v=ncwn8O70YVg</a><a href="https://fosstodon.org/tags/linux" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#linux</a> <a href="https://fosstodon.org/tags/filesystems" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#filesystems</a>

JdeBP<a href="https://mastodon.social/@cks" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@cks</a> Which in turn then prompts the question of whether one with suitable chicanery could set it up as a correct i-node which fsck would consider allocated, but that would be unfixable.Presumably the reference counting checks would detect it as an an orphan, but putting a directory entry referencing it in lost+found would not work.Assuming that the reference counting pass does not also have a < ROOTINO short-circuit in the code too. (-:<a href="https://tty0.social/tags/Unix" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Unix</a> <a href="https://tty0.social/tags/filesystems" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#filesystems</a> <a href="https://tty0.social/tags/FFS" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#FFS</a> <a href="https://tty0.social/tags/UFS" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#UFS</a> <a href="https://tty0.social/tags/FreeBSD" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#FreeBSD</a>

JdeBP<a href="https://mastodon.social/@cks" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@cks</a> The same thought occurred to me. There have been cute tricks like that played. I've even played some of them on other systems.But as far as I know that first entry in the i-node table was just unused.I wonder whether fsck even checked it. Modern FreeBSD fsck_ffs does, but that's a very different beast.<a href="https://tty0.social/tags/Unix" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Unix</a> <a href="https://tty0.social/tags/filesystems" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#filesystems</a> <a href="https://tty0.social/tags/FFS" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#FFS</a> <a href="https://tty0.social/tags/UFS" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#UFS</a>

JdeBP<a href="https://mastodon.social/@cks" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@cks</a> Off By One Error in your post on this. (-:Since 0 means a free directory entry, that's only 65535 i-nodes.Mind you, at 8 i-nodes per block, you'd come close to the size of some contemporary discs with a maximally sized i-node table.<a href="https://tty0.social/tags/Unix" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Unix</a> <a href="https://tty0.social/tags/filesystems" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#filesystems</a>

JdeBP<a href="https://teh.entar.net/@spacehobo" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@spacehobo</a> <a href="https://mastodon.social/@brouhaha" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@brouhaha</a> Yes. Berkeley FFS broke things up into cylinder groups and had an allocation policy of putting various things in the same CG and other things not, because much the same idea was also useful for reducing seeks on discs.(Even OS/2 got in on the act. (-: Its FAT filesytem driver put the extended attributes record for every file in front of the file data where it could. Which was why it was a bad idea to defragment the "EA DATA. SF" file so that it ended up stuffed all at the start of the volume.)And the elevator algorithm in the block cache would at least make the tape do straight runs in one direction and then rewind, where it could.Putting filesystem *and* swap on tape boggles the mind, though. (-:<a href="https://mastodonapp.uk/tags/Unix" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Unix</a> <a href="https://mastodonapp.uk/tags/magtape" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#magtape</a> <a href="https://mastodonapp.uk/tags/filesystems" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#filesystems</a> <a href="https://mastodonapp.uk/tags/tar" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#tar</a> <a href="https://mastodonapp.uk/tags/DEC" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#DEC</a> <a href="https://mastodonapp.uk/tags/retrocomputing" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#retrocomputing</a>

Peter N. M. HansteenMaking openat(2) and friends more useful in practice <a href="https://www.undeadly.org/cgi?action=article;sid=20250529080623" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://www.undeadly.org/cgi?action=article;sid=20250529080623</a> <a href="https://mastodon.social/tags/openbsd" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#openbsd</a> <a href="https://mastodon.social/tags/openat" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#openat</a> <a href="https://mastodon.social/tags/open" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#open</a> <a href="https://mastodon.social/tags/filesystems" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#filesystems</a> <a href="https://mastodon.social/tags/security" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#security</a> <a href="https://mastodon.social/tags/development" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#development</a> <a href="https://mastodon.social/tags/unveil" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#unveil</a> - now also with regression tests, more discussions on tech@

JdeBP<a href="https://fosstodon.org/@atoponce" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@atoponce</a> There seem to be no answers matching "back". Both options match "up".I think that you've overlooked an even more important poll that might be the shibboleth of our time: Does one go up and down a tree? Or does one go back and forth a tree?Has the tree been chopped down?(-:<a href="https://tty0.social/tags/shell" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#shell</a> <a href="https://tty0.social/tags/POSIX" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#POSIX</a> <a href="https://tty0.social/tags/filesystems" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#filesystems</a>

Anselm "Two Sheds" SchülerPSA: If your software intended for <a href="https://ieji.de/tags/Linux" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Linux</a> cannot deal with filenames that contain - spaces - command line flags - non-ASCII - newlines - control characters - invalid UTF-8 then YOUR SOFTWARE IS WRONG AND BAD and when it breaks IT IS YOUR FAULT and you DO NOT GET TO BLAME THE PEOPLE WHO NAMED THE FILES<a href="https://ieji.de/tags/filesystems" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#filesystems</a>

dragotinThis blog <a href="https://0pointer.de/blog/projects/locking.html" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://0pointer.de/blog/projects/locking.html</a> draws a pretty bad situation about file <a href="https://indieweb.social/tags/locking" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#locking</a> on <a href="https://indieweb.social/tags/Linux" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Linux</a> <a href="https://indieweb.social/tags/filesystems" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#filesystems</a>. But it is from 2010 - does anybody know if the situation has technically improved since than?

Droppie [infosec] 🐨:archlinux: :kde: :firefox_nightly: :thunderbird: :vegan:<code>BtrFS</code> completely sucks & i shall never again make the error of using it instead of <code>ext4</code>. 😡<a href="https://infosec.space/tags/BtrFS" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#BtrFS</a> <a href="https://infosec.space/tags/ext4" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#ext4</a> <a href="https://infosec.space/tags/linux" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#linux</a> <a href="https://infosec.space/tags/filesystems" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#filesystems</a> <a href="https://infosec.space/tags/ArchInstall" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#ArchInstall</a> <a href="https://infosec.space/tags/ArchLinux" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#ArchLinux</a> <a href="https://infosec.space/tags/VM" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#VM</a>

Paolo Redaelli<a href="https://mastodon.uno/tags/Linus" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Linus</a> <a href="https://mastodon.uno/tags/Torvalds" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Torvalds</a> Expresses His Hatred For <a href="https://mastodon.uno/tags/CaseInsensitive" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#CaseInsensitive</a> <a href="https://mastodon.uno/tags/FileSystems" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#FileSystems</a> - <a href="https://mastodon.uno/tags/Slashdot" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Slashdot</a> " Dammit. Case sensitivity is a BUG. The fact that filesystem people *still* think it's a feature, I cannot understand. It's like they revere the old FAT filesystem _so_ much that they have to recreate it — badly." I do like his direct approach! Even if I grew on <a href="https://mastodon.uno/tags/AmigaFFS" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#AmigaFFS</a> which was "almost case-insensitive" <a href="https://linux.slashdot.org/story/25/04/27/0547245/linus-torvalds-expresses-his-hatred-for-case-insensitive-file-systems" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://linux.slashdot.org/story/25/04/27/0547245/linus-torvalds-expresses-his-hatred-for-case-insensitive-file-systems</a>

b00010111"The Impact of Microsoft’s ReFS on DFIR" -> comparing NTFS evidences with ReFS. What stays, what changes and what will be gone. Recommended read! <a href="https://medium.com/@mathias.fuchs/the-impact-of-microsofts-refs-on-dfir-cdb78f401bfd" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://medium.com/@mathias.fuchs/the-impact-of-microsofts-refs-on-dfir-cdb78f401bfd</a> <a href="https://ioc.exchange/tags/DFIR" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#DFIR</a> <a href="https://ioc.exchange/tags/ReFS" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#ReFS</a> <a href="https://ioc.exchange/tags/NTFS" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#NTFS</a> <a href="https://ioc.exchange/tags/filesystems" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#filesystems</a>

Diane BruceSeeing this toot <a href="https://mstdn.social/@elfin/114371800122912697" rel="nofollow noopener noreferrer" target="_blank">https://mstdn.social/@elfin/114371800122912697</a>Reminded me of the time at BNR their SUNOS filesystems suddenly had '/' in filenames due to a buggy MAC link. Yes it took fsdb to fix the problem.<a href="https://bsd.network/tags/Filesystems" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Filesystems</a> <a href="https://bsd.network/tags/BSD" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#BSD</a> <a href="https://bsd.network/tags/BNR" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#BNR</a>

Hacker NewsAn Intro to DeepSeek's Distributed File System<a href="https://maknee.github.io/blog/2025/3FS-Performance-Journal-1/" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://maknee.github.io/blog/2025/3FS-Performance-Journal-1/</a><a href="https://mastodon.social/tags/HackerNews" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#HackerNews</a> <a href="https://mastodon.social/tags/DeepSeek" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#DeepSeek</a> <a href="https://mastodon.social/tags/Distributed" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Distributed</a> <a href="https://mastodon.social/tags/File" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#File</a> <a href="https://mastodon.social/tags/System" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#System</a> <a href="https://mastodon.social/tags/Intro" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Intro</a> <a href="https://mastodon.social/tags/FileSystems" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#FileSystems</a> <a href="https://mastodon.social/tags/TechInnovation" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#TechInnovation</a> <a href="https://mastodon.social/tags/DataStorage" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#DataStorage</a>

Hacker NewsUnix files have (at least) two sizes<a href="https://utcc.utoronto.ca/~cks/space/blog/unix/UnixFilesTwoSizes" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://utcc.utoronto.ca/~cks/space/blog/unix/UnixFilesTwoSizes</a><a href="https://mastodon.social/tags/HackerNews" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#HackerNews</a> <a href="https://mastodon.social/tags/UnixFiles" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#UnixFiles</a> <a href="https://mastodon.social/tags/UnixSizes" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#UnixSizes</a> <a href="https://mastodon.social/tags/FileSystems" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#FileSystems</a> <a href="https://mastodon.social/tags/TechBlog" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#TechBlog</a> <a href="https://mastodon.social/tags/HackerNews" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#HackerNews</a>

John LeachTIL that xfs has supported copy-on-write reflink copies for years (Kernel 4.9.1 in 2017!), where as zfs only got it last year (and it is not considered stable!)<a href="https://blogs.oracle.com/linux/post/xfs-data-block-sharing-reflink" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://blogs.oracle.com/linux/post/xfs-data-block-sharing-reflink</a><a href="https://mastodon.social/tags/xfs" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#xfs</a> <a href="https://mastodon.social/tags/filesystems" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#filesystems</a> <a href="https://mastodon.social/tags/storage" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#storage</a>

N-gated Hacker News🥴 Ah, the 2019 classic where we learned that file systems are apparently incapable of managing distributed storage—because who knew they weren't designed for it? But first, make sure you enable <a href="https://mastodon.social/tags/JavaScript" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#JavaScript</a> and <a href="https://mastodon.social/tags/cookies" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#cookies</a>, because reading this revelation requires a digital permission slip. 🍪🔑 <a href="https://dl.acm.org/doi/pdf/10.1145/3341301.3359656" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://dl.acm.org/doi/pdf/10.1145/3341301.3359656</a> <a href="https://mastodon.social/tags/fileSystems" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#fileSystems</a> <a href="https://mastodon.social/tags/distributedStorage" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#distributedStorage</a> <a href="https://mastodon.social/tags/techNews" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#techNews</a> <a href="https://mastodon.social/tags/digitalPermissions" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#digitalPermissions</a> <a href="https://mastodon.social/tags/HackerNews" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#HackerNews</a> <a href="https://mastodon.social/tags/ngated" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#ngated</a>

Hacker NewsFile Systems Unfit as Distributed Storage Back Ends (2019)<a href="https://dl.acm.org/doi/pdf/10.1145/3341301.3359656" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://dl.acm.org/doi/pdf/10.1145/3341301.3359656</a><a href="https://mastodon.social/tags/HackerNews" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#HackerNews</a> <a href="https://mastodon.social/tags/FileSystems" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#FileSystems</a> <a href="https://mastodon.social/tags/DistributedStorage" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#DistributedStorage</a> <a href="https://mastodon.social/tags/TechResearch" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#TechResearch</a> <a href="https://mastodon.social/tags/ACM2023" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#ACM2023</a> <a href="https://mastodon.social/tags/StorageSolutions" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#StorageSolutions</a>

Recent searches

Search options

Administered by:

Server stats:

#filesystems