toad.social is one of the many independent Mastodon servers you can use to participate in the fediverse.
Mastodon server operated by David Troy, a tech pioneer and investigative journalist addressing threats to democracy. Thoughtful participation and discussion welcome.

Administered by:

Server stats:

274
active users

#filesystem

1 post1 participant0 posts today
Patrick Wu :neocat_flag_bi:<p><b>One Open-source Project Daily</b><span><br><br>Manage filesystem snapshots and allow undo of system modifications <br><br></span><a href="https://github.com/openSUSE/snapper" rel="nofollow noopener" target="_blank">https://github.com/openSUSE/snapper</a><span><br><br></span><a href="https://hatoya.cafe/tags/1ospd" rel="nofollow noopener" target="_blank">#1ospd</a> <a href="https://hatoya.cafe/tags/opensource" rel="nofollow noopener" target="_blank">#opensource</a> <a href="https://hatoya.cafe/tags/fs" rel="nofollow noopener" target="_blank">#fs</a> <a href="https://hatoya.cafe/tags/filesystem" rel="nofollow noopener" target="_blank">#filesystem</a> <a href="https://hatoya.cafe/tags/snapshots" rel="nofollow noopener" target="_blank">#snapshots</a> <a href="https://hatoya.cafe/tags/linux" rel="nofollow noopener" target="_blank">#linux</a> <a href="https://hatoya.cafe/tags/suse" rel="nofollow noopener" target="_blank">#suse</a> <a href="https://hatoya.cafe/tags/opensuse" rel="nofollow noopener" target="_blank">#opensuse</a></p>
ax6761<p>... <a href="https://freeradical.zone/tags/BetrFS" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>BetrFS</span></a> <a href="https://www.betrfs.org/" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://www.</span><span class="">betrfs.org/</span><span class="invisible"></span></a> ...</p><p>『… in-kernel file system that uses Bε trees to organize on-disk storage. Bε trees are a write-optimized dictionary, and offer the same asymptotic behavior for sequential I/O and point queries as a B-tree. The advantage of a B ε tree is that it can also ingest small, random writes 1-2 orders of magnitude faster than B-trees and other standard on-disk data structures.』</p><p><a href="https://freeradical.zone/tags/fileSystem" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>fileSystem</span></a></p>
ax6761btrfs mention
ax6761<p><a href="https://freeradical.zone/tags/ZFS" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>ZFS</span></a> Right Now! c 2007,<br>by Jeff B,<br>(only slides) <a href="https://www.usenix.org/legacy/event/lisa07/htgr_files/bonwick_htgr.pdf" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://www.</span><span class="ellipsis">usenix.org/legacy/event/lisa07</span><span class="invisible">/htgr_files/bonwick_htgr.pdf</span></a><br><a href="https://www.usenix.org/conference/lisa-07/zfs" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://www.</span><span class="ellipsis">usenix.org/conference/lisa-07/</span><span class="invisible">zfs</span></a></p><p>-- introduction to ZFS of Sun Microsystems vintage</p><p><a href="https://freeradical.zone/tags/fileSystem" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>fileSystem</span></a> <a href="https://freeradical.zone/tags/trawlingUSENIX" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>trawlingUSENIX</span></a></p>
ax6761<p>Black-Box Problem Diagnosis in Parallel File Systems, c 2010,<br>by Michael P K, Jiaqi T, Rajeev G, Priya N,<br><a href="https://www.usenix.org/conference/fast-10/black-box-problem-diagnosis-parallel-file-systems" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://www.</span><span class="ellipsis">usenix.org/conference/fast-10/</span><span class="invisible">black-box-problem-diagnosis-parallel-file-systems</span></a></p><p>-- compares the metric histograms of the nodes</p><p><a href="https://freeradical.zone/tags/parallelVirtualFileSystem" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>parallelVirtualFileSystem</span></a> <a href="https://freeradical.zone/tags/PVFS" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>PVFS</span></a> <a href="https://freeradical.zone/tags/parallelFileSystem" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>parallelFileSystem</span></a> <a href="https://freeradical.zone/tags/fileSystem" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>fileSystem</span></a> <a href="https://freeradical.zone/tags/trawlingUSENIX" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>trawlingUSENIX</span></a></p>
SciPunkIn the movie Hackers (1995), a group of nerds hack into computer networks to outsmart corrupt authorities and uncover a conspiracy. <br> <br> The film features a mix of retro computing aesthetics, cyberpunk themes, and real-life cybersecurity concepts like sudo and root access.<br> <br> <br> <br> <a href="https://pixelfed.social/discover/tags/hackers?src=hash" class="u-url hashtag" rel="nofollow noopener" target="_blank">#hackers</a> <a href="https://pixelfed.social/discover/tags/retro?src=hash" class="u-url hashtag" rel="nofollow noopener" target="_blank">#retro</a> <a href="https://pixelfed.social/discover/tags/computing?src=hash" class="u-url hashtag" rel="nofollow noopener" target="_blank">#computing</a> <a href="https://pixelfed.social/discover/tags/cybersecurity?src=hash" class="u-url hashtag" rel="nofollow noopener" target="_blank">#cybersecurity</a> <a href="https://pixelfed.social/discover/tags/cyberpunk?src=hash" class="u-url hashtag" rel="nofollow noopener" target="_blank">#cyberpunk</a> <a href="https://pixelfed.social/discover/tags/movies?src=hash" class="u-url hashtag" rel="nofollow noopener" target="_blank">#movies</a> <a href="https://pixelfed.social/discover/tags/sudo?src=hash" class="u-url hashtag" rel="nofollow noopener" target="_blank">#sudo</a> <a href="https://pixelfed.social/discover/tags/root?src=hash" class="u-url hashtag" rel="nofollow noopener" target="_blank">#root</a> <a href="https://pixelfed.social/discover/tags/god?src=hash" class="u-url hashtag" rel="nofollow noopener" target="_blank">#god</a> <a href="https://pixelfed.social/discover/tags/cyberspace?src=hash" class="u-url hashtag" rel="nofollow noopener" target="_blank">#cyberspace</a> <a href="https://pixelfed.social/discover/tags/datasecurity?src=hash" class="u-url hashtag" rel="nofollow noopener" target="_blank">#datasecurity</a> <a href="https://pixelfed.social/discover/tags/hacking?src=hash" class="u-url hashtag" rel="nofollow noopener" target="_blank">#hacking</a> <a href="https://pixelfed.social/discover/tags/computers?src=hash" class="u-url hashtag" rel="nofollow noopener" target="_blank">#computers</a> <a href="https://pixelfed.social/discover/tags/network?src=hash" class="u-url hashtag" rel="nofollow noopener" target="_blank">#network</a> <a href="https://pixelfed.social/discover/tags/blackhat?src=hash" class="u-url hashtag" rel="nofollow noopener" target="_blank">#blackhat</a> <a href="https://pixelfed.social/discover/tags/whitehat?src=hash" class="u-url hashtag" rel="nofollow noopener" target="_blank">#whitehat</a> <a href="https://pixelfed.social/discover/tags/cyberpunkaesthetic?src=hash" class="u-url hashtag" rel="nofollow noopener" target="_blank">#cyberpunkaesthetic</a> <a href="https://pixelfed.social/discover/tags/computers?src=hash" class="u-url hashtag" rel="nofollow noopener" target="_blank">#computers</a> <a href="https://pixelfed.social/discover/tags/filesystem?src=hash" class="u-url hashtag" rel="nofollow noopener" target="_blank">#filesystem</a> <a href="https://pixelfed.social/discover/tags/fisherstevens?src=hash" class="u-url hashtag" rel="nofollow noopener" target="_blank">#fisherstevens</a> <a href="https://pixelfed.social/discover/tags/pennjillette?src=hash" class="u-url hashtag" rel="nofollow noopener" target="_blank">#pennjillette</a>
argv minus one<p>I wanted to store some <a href="https://mastodon.sdf.org/tags/BorgBackup" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>BorgBackup</span></a> archives on an <a href="https://mastodon.sdf.org/tags/exFAT" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>exFAT</span></a> disk so that any operating system (not just <a href="https://mastodon.sdf.org/tags/Linux" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Linux</span></a>) could easily read it, but Borg needs a journaling <a href="https://mastodon.sdf.org/tags/filesystem" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>filesystem</span></a>. 😢</p><p>In theory, there isn't any reason why journaling can't be implemented on FAT 🤔 but everybody probably doesn't consider it worth the effort.</p><p><a href="https://mastodon.sdf.org/tags/NTFS" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>NTFS</span></a> would work too, except some of the <a href="https://mastodon.sdf.org/tags/Linux" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Linux</span></a> machines I run Borg on are running Debian Stable, whose old kernel lacks the ntfs3 driver. 🤦‍♂️</p>
Grumpy Old Techie 🕊️<p>Things I like about FreeBSD:</p><p> "You can tune a file system, but you cannot tune a fish."</p><p>is still listed as a bug in the tunefs man page on FreeBSD 14.3<br>I first saw it more that 30 years ago on SunOS that was BSD based at the time.</p><p><a href="https://hostux.social/tags/FreeBSD" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>FreeBSD</span></a> <a href="https://hostux.social/tags/filesystem" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>filesystem</span></a> <a href="https://hostux.social/tags/unix" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>unix</span></a> <a href="https://hostux.social/tags/sunos" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>sunos</span></a></p>
Orhun Parmaksız 👾<p>Found a handy CLI tool for Git &gt;_</p><p>🔍 **git-statuses** — Display the status of multiple Git repositories in a clear, tabular format.</p><p>🌀 Scans directories recursively for Git repositories</p><p>🦀 Written in Rust!</p><p>⭐ GitHub: <a href="https://github.com/bircni/git-statuses" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://</span><span class="">github.com/bircni/git-statuses</span><span class="invisible"></span></a></p><p><a href="https://fosstodon.org/tags/rustlang" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>rustlang</span></a> <a href="https://fosstodon.org/tags/git" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>git</span></a> <a href="https://fosstodon.org/tags/repository" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>repository</span></a> <a href="https://fosstodon.org/tags/scan" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>scan</span></a> <a href="https://fosstodon.org/tags/filesystem" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>filesystem</span></a> <a href="https://fosstodon.org/tags/commandline" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>commandline</span></a> <a href="https://fosstodon.org/tags/vcs" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>vcs</span></a> <a href="https://fosstodon.org/tags/terminal" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>terminal</span></a></p>
Blake Patterson<p>My daughter has a friend whose sibling is no longer alive, as of recently. The family wants to access their MacBook Pro which is password protected. It's a fairly recent model, apparently, and it's unclear whether the disk is encrypted -- prob safe to assume it is (?). </p><p>Is there something Apple can/will do to help the family gain access, given proof of the situation? </p><p><a href="https://oldbytes.space/tags/Apple" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Apple</span></a> <a href="https://oldbytes.space/tags/macOS" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>macOS</span></a> <a href="https://oldbytes.space/tags/Mac" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Mac</span></a> <a href="https://oldbytes.space/tags/filesystem" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>filesystem</span></a> <a href="https://oldbytes.space/tags/encryption" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>encryption</span></a> <a href="https://oldbytes.space/tags/FileVault" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>FileVault</span></a> <a href="https://oldbytes.space/tags/password" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>password</span></a> <a href="https://oldbytes.space/tags/access" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>access</span></a></p>
Ariadna Vigo<p>Don't forget that your filesystem is a database you can use as such. I've been writing a diary of sorts, where each entry is just a text file, with the current date as its filename.</p><p><a href="https://social.tchncs.de/tags/tips" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>tips</span></a> <a href="https://social.tchncs.de/tags/filesystem" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>filesystem</span></a> <a href="https://social.tchncs.de/tags/diary" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>diary</span></a> <a href="https://social.tchncs.de/tags/sysadmin" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>sysadmin</span></a></p>
xoron :verified:<p>File encryption with a browser.</p><p>I've been exploring the <a href="https://infosec.exchange/tags/WebCryptoAPI" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>WebCryptoAPI</span></a> and I'm impressed!</p><p>When combined with the <a href="https://infosec.exchange/tags/FileSystemAPI" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>FileSystemAPI</span></a>, it offers a seemingly secure way to <a href="https://infosec.exchange/tags/encrypt" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>encrypt</span></a> and <a href="https://infosec.exchange/tags/store" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>store</span></a> files directly on your device. Think <a href="https://infosec.exchange/tags/localstorage" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>localstorage</span></a>, but with <a href="https://infosec.exchange/tags/encryption" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>encryption</span></a>!</p><p>I know <a href="https://infosec.exchange/tags/webapps" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>webapps</span></a> can have <a href="https://infosec.exchange/tags/security" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>security</span></a> vulnerabilities since the code is served over the web, so I've <a href="https://infosec.exchange/tags/OpenSourced" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>OpenSourced</span></a> my demo! You can check it out, and it should even work if <a href="https://infosec.exchange/tags/selfhosted" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>selfhosted</span></a> on <a href="https://infosec.exchange/tags/GitHubPages" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>GitHubPages</span></a>.</p><p>Live Demo: <a href="https://dim.positive-intentions.com/?path=/story/usefs--encrypted-demo" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">dim.positive-intentions.com/?p</span><span class="invisible">ath=/story/usefs--encrypted-demo</span></a></p><p>Demo Code: <a href="https://github.com/positive-intentions/dim/blob/staging/src/stories/05-Hooks-useFS.stories.js" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">github.com/positive-intentions</span><span class="invisible">/dim/blob/staging/src/stories/05-Hooks-useFS.stories.js</span></a></p><p>Hook Code: <a href="https://github.com/positive-intentions/dim/blob/staging/src/hooks/useFS.js" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">github.com/positive-intentions</span><span class="invisible">/dim/blob/staging/src/hooks/useFS.js</span></a></p><p>IMPORTANT NOTES (PLEASE READ!):<br> * This is NOT a product. It's for <a href="https://infosec.exchange/tags/testing" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>testing</span></a> and <a href="https://infosec.exchange/tags/demonstration" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>demonstration</span></a> purposes only.<br> * It has NOT been reviewed or audited. Do NOT use for sensitive data.<br> * The "password encryption" currently uses a hardcoded password. This is for demonstration, not security.<br> * This is NOT meant to replace robust solutions like <a href="https://infosec.exchange/tags/VeraCrypt" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>VeraCrypt</span></a>. It's just a <a href="https://infosec.exchange/tags/proofofconcept" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>proofofconcept</span></a> to show what's possible with <a href="https://infosec.exchange/tags/browser" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>browser</span></a> <a href="https://infosec.exchange/tags/APIs" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>APIs</span></a>.</p><p><a href="https://infosec.exchange/tags/Encryption" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Encryption</span></a> <a href="https://infosec.exchange/tags/Cryptography" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Cryptography</span></a> <a href="https://infosec.exchange/tags/JavaScript" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>JavaScript</span></a> <a href="https://infosec.exchange/tags/Frontend" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Frontend</span></a> <a href="https://infosec.exchange/tags/Privacy" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Privacy</span></a> <a href="https://infosec.exchange/tags/Security" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Security</span></a> <a href="https://infosec.exchange/tags/WebDevelopment" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>WebDevelopment</span></a> <a href="https://infosec.exchange/tags/Coding" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Coding</span></a> <a href="https://infosec.exchange/tags/Developer" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Developer</span></a> <a href="https://infosec.exchange/tags/Tech" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Tech</span></a> <a href="https://infosec.exchange/tags/FOSS" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>FOSS</span></a> <a href="https://infosec.exchange/tags/OpenSource" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>OpenSource</span></a> <a href="https://infosec.exchange/tags/GitHub" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>GitHub</span></a> <a href="https://infosec.exchange/tags/MastodonDev" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>MastodonDev</span></a> <a href="https://infosec.exchange/tags/Programming" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Programming</span></a> <a href="https://infosec.exchange/tags/WebStandards" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>WebStandards</span></a> <a href="https://infosec.exchange/tags/FileSystem" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>FileSystem</span></a> <a href="https://infosec.exchange/tags/WebAPI" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>WebAPI</span></a> <a href="https://infosec.exchange/tags/ProofOfConcept" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>ProofOfConcept</span></a></p>
Peter N. M. Hansteen<p>Next at <a href="https://mastodon.social/tags/bsdcan" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>bsdcan</span></a>, in the plenary room - "A distributed filesystem for OpenBSD" by Rob Keizer <a href="https://indico.bsdcan.org/event/5/contributions/115/" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">indico.bsdcan.org/event/5/cont</span><span class="invisible">ributions/115/</span></a> <a href="https://mastodon.social/tags/conference" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>conference</span></a> <a href="https://mastodon.social/tags/bsd" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>bsd</span></a> <a href="https://mastodon.social/tags/filesystem" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>filesystem</span></a> <a href="https://mastodon.social/tags/openbsd" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>openbsd</span></a> <a href="https://mastodon.social/tags/freesoftware" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>freesoftware</span></a> <a href="https://mastodon.social/tags/libresoftware" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>libresoftware</span></a></p>
Jonathan Matthews<p>Folks who know "rsync -F" because they already use it -- am I right in thinking that it adds these behaviours to a sync:</p><p>- recursively look for .rsync-filter files in every directory in the copy source, including the top-level</p><p>- apply the filters they each contain to the directory and subdirectories rooted at the same level that each file was found</p><p>- exclude those .rsync-filter files from being copied to the destination </p><p>Is that right? <a href="https://fosstodon.org/tags/rsync" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>rsync</span></a> <a href="https://fosstodon.org/tags/sync" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>sync</span></a> <a href="https://fosstodon.org/tags/data" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>data</span></a> <a href="https://fosstodon.org/tags/sysadmin" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>sysadmin</span></a> <a href="https://fosstodon.org/tags/filesystem" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>filesystem</span></a> <a href="https://fosstodon.org/tags/filesystems" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>filesystems</span></a></p>
Dendrobatus Azureus<p>Today I learned the following. Journaling and journaling are two separate distinctly separate manners of keeping file systems in Sync.</p><p>When microsoft talks about journaling in NTFS you should never, ever think about the robust journaling system that Ext4 has</p><p>In comparison EXT4 journaling is a god while en NTFS journaling is not even an ant</p><p>I have EXT4 file systems connected to an extremely unstable machine. This thing crashes to green screens more than 64 times a day.</p><p>{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}</p><p>I've not even lost one bit of data on those EXT4 file systems.</p><p>Those NTFS file systems with journaling? I lost all of them. All NTFS file systems were lost</p><p>I didn't lose data because I have backups the file systems just keeled over simply because the machine kept rebooting </p><p>Thank you for being so robust EXT4 </p><p><a href="https://mastodon.bsd.cafe/tags/Journal" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Journal</span></a> <a href="https://mastodon.bsd.cafe/tags/filesystem" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>filesystem</span></a> <a href="https://mastodon.bsd.cafe/tags/EXT4" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>EXT4</span></a> <a href="https://mastodon.bsd.cafe/tags/OpenSource" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>OpenSource</span></a> <a href="https://mastodon.bsd.cafe/tags/NTFS" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>NTFS</span></a> <a href="https://mastodon.bsd.cafe/tags/ClosedSource" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>ClosedSource</span></a></p>
Aptivi<p><strong>Linux 6.16 yields improved EXT4&nbsp;performance!</strong></p><p>As part of the changes that are done in Linux 6.16, there are some of the very interesting changes that are done to the EXT4 filesystem. Those changes yield improved performance, causing you to have a faster EXT4 filesystem compared to the recently released Linux 6.15.</p><p>Those changes have been made to improve the filesystem performance, which will be pushed to the v6.16 development branch from <a href="https://lore.kernel.org/lkml/20250527200206.GA2433735@mit.edu/" rel="nofollow noopener" target="_blank">this PR</a>, including:</p><ul><li>Fast commit performance improvements</li><li>Multi-fsblock atomic write support for bigalloc file systems</li><li>Large folio support for regular files</li></ul><p>The large folio support for regular files was, in itself, a factor of the improvements, along with all other changes, which yielded over 37% performance increase according to the kernel test robot that made <a href="https://lore.kernel.org/all/202505161418.ec0d753f-lkp@intel.com/" rel="nofollow noopener" target="_blank">this report you can see here</a>. According to the test robot, it has reported that it had noticed a 37.7% improvement on <code>fsmark.files_per_sec</code>.</p><p>The large folio support for regular files has been added with <a href="https://lore.kernel.org/all/20250512063319.3539411-9-yi.zhang@huaweicloud.com/" rel="nofollow noopener" target="_blank">this patch</a>, which checks for the following conditions in the <code>ext4_should_enable_large_folio()</code> function before enabling such support:</p><ul><li>If <code>i_mode</code> on an inode is a regular file using the <code><a href="https://man7.org/linux/man-pages/man7/inode.7.html" rel="nofollow noopener" target="_blank">S_ISREG()</a></code> macro</li><li>If either the data flags on the superblock or the inode flags has the journal data flags</li><li>If the superblock has no verity and has no encryption support</li></ul><p>Also, Linux 6.16 fixes some corruption bugs on an EXT4 file system caused by race conditions in the extent status tree. Those race conditions were potentially manifested from the heavy simultaneous allocation and deallocation to a single file.</p><p><strong>Expect the first release candidate of Linux 6.16 in the next two weeks!</strong></p><p><span></span></p><p><a rel="nofollow noopener" class="hashtag u-tag u-category" href="https://officialaptivi.wordpress.com/tag/ext4/" target="_blank">#EXT4</a> <a rel="nofollow noopener" class="hashtag u-tag u-category" href="https://officialaptivi.wordpress.com/tag/filesystem/" target="_blank">#Filesystem</a> <a rel="nofollow noopener" class="hashtag u-tag u-category" href="https://officialaptivi.wordpress.com/tag/linux/" target="_blank">#Linux</a> <a rel="nofollow noopener" class="hashtag u-tag u-category" href="https://officialaptivi.wordpress.com/tag/linux-6-16/" target="_blank">#Linux616</a> <a rel="nofollow noopener" class="hashtag u-tag u-category" href="https://officialaptivi.wordpress.com/tag/linux-kernel/" target="_blank">#LinuxKernel</a> <a rel="nofollow noopener" class="hashtag u-tag u-category" href="https://officialaptivi.wordpress.com/tag/news/" target="_blank">#news</a> <a rel="nofollow noopener" class="hashtag u-tag u-category" href="https://officialaptivi.wordpress.com/tag/tech/" target="_blank">#Tech</a> <a rel="nofollow noopener" class="hashtag u-tag u-category" href="https://officialaptivi.wordpress.com/tag/technology/" target="_blank">#Technology</a> <a rel="nofollow noopener" class="hashtag u-tag u-category" href="https://officialaptivi.wordpress.com/tag/update/" target="_blank">#update</a></p>
Benjamin Carr, Ph.D. 👨🏻‍💻🧬<p><a href="https://hachyderm.io/tags/Linux" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Linux</span></a> Might Drop The <a href="https://hachyderm.io/tags/Apple" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Apple</span></a> <a href="https://hachyderm.io/tags/HFS" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>HFS</span></a> / HFS+ <a href="https://hachyderm.io/tags/FileSystem" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>FileSystem</span></a> Kernel Driver Support<br><a href="https://hachyderm.io/tags/Apple" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Apple</span></a> no longer supports the Hierarchical File System on the latest versions of <a href="https://hachyderm.io/tags/macOS" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>macOS</span></a> itself and in prior releases was read-only support since macOS 10.6 for HFS itself. The newer HFS+ file-system does continue to be supported by Apple. Linux support for HFS has been poor and ill-maintained and it looks like the kernel drivers could be on their way out. <br><a href="https://www.phoronix.com/news/Linux-2025-Sad-State-HFS" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://www.</span><span class="ellipsis">phoronix.com/news/Linux-2025-S</span><span class="invisible">ad-State-HFS</span></a></p>
Thorsten Leemhuis (acct. 1/4)<p>Highlights from the main <a href="https://hachyderm.io/tags/bcachefs" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>bcachefs</span></a> merge for <a href="https://hachyderm.io/tags/Linux" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Linux</span></a> 6.16: <a href="https://git.kernel.org/torvalds/c/522544fc71c27b4b432386c7919f71ecc79a3bfb" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">git.kernel.org/torvalds/c/5225</span><span class="invisible">44fc71c27b4b432386c7919f71ecc79a3bfb</span></a></p><p>- Incompatible features may now be enabled at runtime, via "opts/version_upgrade" in sysfs.</p><p>- Various changes to support deployable disk images</p><p>- Major error message improvements for btree node reads, data reads, and elsewhere.</p><p>- New option, 'rebalance_on_ac_only'.</p><p>- Repair/self healing:</p><p> - We can now kick off recovery passes and run them in the background if we detect errors. </p><p>- Performance:</p><p> - Faster snapshot deletion<br> <br> - Faster device removal<br> <br> - We're now coalescing redundant accounting updates prior to transaction commit, taking some pressure off the journal.<br> <br> - Stack usage improvements: All allocator state has been moved off the stack</p><p><a href="https://hachyderm.io/tags/kernel" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>kernel</span></a> <a href="https://hachyderm.io/tags/LinuxKernel" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>LinuxKernel</span></a> <a href="https://hachyderm.io/tags/Linux616" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Linux616</span></a> <a href="https://hachyderm.io/tags/Filesystem" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Filesystem</span></a></p>
🔘 G◍M◍◍T 🔘<p>💡 Kernel Linux 6.15: driver Rust, exFAT veloce e supporto ampliato</p><p><a href="https://gomoot.com/kernel-linux-6-15-driver-rust-exfat-veloce-e-supporto-ampliato/" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">gomoot.com/kernel-linux-6-15-d</span><span class="invisible">river-rust-exfat-veloce-e-supporto-ampliato/</span></a></p><p><a href="https://mastodon.uno/tags/arm" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>arm</span></a> <a href="https://mastodon.uno/tags/blog" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>blog</span></a> <a href="https://mastodon.uno/tags/driver" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>driver</span></a> <a href="https://mastodon.uno/tags/filesystem" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>filesystem</span></a> <a href="https://mastodon.uno/tags/kernel" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>kernel</span></a> <a href="https://mastodon.uno/tags/linux6" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>linux6</span></a>.15 <a href="https://mastodon.uno/tags/news" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>news</span></a> <a href="https://mastodon.uno/tags/nova" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>nova</span></a> <a href="https://mastodon.uno/tags/opensource" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>opensource</span></a> <a href="https://mastodon.uno/tags/picks" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>picks</span></a> <a href="https://mastodon.uno/tags/rust" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>rust</span></a> <a href="https://mastodon.uno/tags/tech" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>tech</span></a> <a href="https://mastodon.uno/tags/tecnologia" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>tecnologia</span></a></p>
Aptivi<p><strong>Linux 6.16 will see more btrfs&nbsp;improvements</strong></p><p>The btrfs filesystem in Linux 6.16 has undergone many improvements that make its performance faster than before. It has already been improved across Linux releases, but the upcoming version of Linux sees even more improvements to this filesystem. Any system that uses this filesystem can now benefit from those improvements.</p><p>The buffer conversion work underwent some throughput and runtime improvements for metadata heavy operations, backed by several commits in a pull request made to the 6.16 branch, such as “extent buffer conversion to xarray gains throughput and runtime improvements on metadata heavy operations doing writeback (sample test shows +50% throughput, -33% runtime).”</p><p>The tree cleanups have been improved to avoid repeated or unnecessary searches. This improves the I/O performance, should any operation rely on tree cleanups. As for committing transactions, the extent unpinning action has become more efficient than before, yielding a 3-5% performance improvement in runtime.</p><p>You can find more about this pull request by clicking on the below button:</p> <a class="" href="https://lore.kernel.org/lkml/cover.1747826882.git.dsterba@suse.com/T/#u" rel="nofollow noopener" target="_blank">Learn more</a> <p><a href="https://www.freepik.com/free-photo/happy-female-student-sitting-bench-using-laptop-outdoors_4530166.htm" rel="nofollow noopener" target="_blank">Cover image credit.</a></p><p><span></span></p><p><a rel="nofollow noopener" class="hashtag u-tag u-category" href="https://officialaptivi.wordpress.com/tag/btrfs/" target="_blank">#Btrfs</a> <a rel="nofollow noopener" class="hashtag u-tag u-category" href="https://officialaptivi.wordpress.com/tag/filesystem/" target="_blank">#Filesystem</a> <a rel="nofollow noopener" class="hashtag u-tag u-category" href="https://officialaptivi.wordpress.com/tag/linux/" target="_blank">#Linux</a> <a rel="nofollow noopener" class="hashtag u-tag u-category" href="https://officialaptivi.wordpress.com/tag/linux-kernel/" target="_blank">#LinuxKernel</a> <a rel="nofollow noopener" class="hashtag u-tag u-category" href="https://officialaptivi.wordpress.com/tag/news/" target="_blank">#news</a> <a rel="nofollow noopener" class="hashtag u-tag u-category" href="https://officialaptivi.wordpress.com/tag/tech/" target="_blank">#Tech</a> <a rel="nofollow noopener" class="hashtag u-tag u-category" href="https://officialaptivi.wordpress.com/tag/technology/" target="_blank">#Technology</a> <a rel="nofollow noopener" class="hashtag u-tag u-category" href="https://officialaptivi.wordpress.com/tag/update/" target="_blank">#update</a></p>