mathstodon.xyz is one of the many independent Mastodon servers you can use to participate in the fediverse.
A Mastodon instance for maths people. We have LaTeX rendering in the web interface!

Server stats:

2.7K
active users

#filesystem

6 posts6 participants1 post today

Linus Torvalds has proper motivated reasons for really disliking file systems without a case sensitivity.

Read this with me from the kernel lkml, regarding bcachefs.

Re: [GIT PULL] bcachefs fixes for 6.15-rc4 - Linus Torvalds
lore.kernel.org/lkml/CAHk-=wja

🖋️ #bash #sh #zsh #ksh #csh #tcsh #fish #git #Linux #lkml #POSIX #FOSS #100daysofCode #640DaysOfCode #coding #1024DaysOfCode #github #programming #Torvalds #filesystem

Linux might no longer support HFS/HFS+

The antique filesystems, HFS and HFS+, were used in old Macs going back to Septmber 17th, 1985, with the former being used first, then the latter. They also have alternative names, called Mac OS Standard and Mac OS Extended.

During development of Mac OS X 10.6 Snow Leopard released in August 28th, 2009, Apple decided to stop all support for read-write HFS and HFS+ filesystems, making users be unable to write to any file, but they still could read from such volumes. In macOS Catalina, Apple finally removed the filesystem support from the Darwin kernel, making it impossible to use disks that are still formatted with such filesystems.

We appear to have reached the end of support for the two antique filesystems in Linux, too, because, this year, the prominent Linux developer from Microsoft stated that, via Mastodon:

Let’s try and remove #hfs and #hfsplus by the end of 2025. They have been orphaned since 2014 and are turning into a maintenance burden.

If you’re still using those filesystems after the support ending period, there is a chance that you could use those filesystems again via user-space filesystems, except that you won’t have the same experience, including the lack of support of writing to files for HFS+.

Photo by Mimi Thian on Unsplash

Btrfs - Most curious case, is this flaw or not. Can't really tell. - I've got lots of scattered data in dirty write buffers to disk, due to scattered writes and high system memory. I've also got long commit interval to allow efficient flushing (as contiguous as possible) when that scattered data is finally written to disk. It all works fine, if I sync before shutdown. But if I just shutdown the system, the flush process takes longer than the maximum allowed file system unmount time is. Even worse, some of the data is written to SSD and some to HDD. The state data is on SSD and actual data is on HDD. When the flush timeout is encountered, the system shuts down in state where state file says that this data is written to disk, and the data actually isn't on disk yet. - Flaw or not? - Of course this requires this curious combination of things to trigger, but the problem is very real. - Who's fault it is? #btrfs #data #corruption #loss #cow #linux #filesystem #shutdown
Continued thread

I have found that all of the "solutions" I've looked at are just locking you into some more specific ecosystem, so went back to the revolutionary idea of using the #filesystem I have my photos and videos in a folder structure on my laptop by year, trip.

I don't auto backup from my #iPhone or #Sonya6700 anymore, that really just synced a load of cruft I had to delete, or pay to store. I move photos I want to my laptop, where I adjust and edit them in #darktable / #rawtherapee / #digikam

🧵 2/4

#ReleaseWednesday Just pushed a new version of thi.ng/block-fs, now with additional multi-command CLI tooling to convert & bundle a local file system tree into a single block-based binary blob (e.g. for bundling assets, or distributing a virtual filesystem as part of a web app, or for snapshot testing, or as bridge for WASM interop etc.)

Also new, the main API now includes a `.readAsObjectURL()` method to wrap files as URLs to binary blobs with associated MIME types, thereby making it trivial to use the virtual filesystem for sourcing stored images and other assets for direct use in the browser...

(Ps. For more context see other recent announcement: mastodon.thi.ng/@toxi/11426498)