#xfs

Thorsten Leemhuis (acct. 1/4)2/ Another article about a feature recently added to the <a href="https://hachyderm.io/tags/XFS" class="mention hashtag" rel="nofollow noopener" target="_blank">#XFS</a> filesystem that is not considered experimental any more since <a href="https://hachyderm.io/tags/Linux" class="mention hashtag" rel="nofollow noopener" target="_blank">#Linux</a> 6.16-rc1 (the text was also written by the responsible developers):""In this blog post, we discuss a new XFS feature [with] the ability to exchange arbitrary file contents atomically. […]What Problems Does This Solve?The first problem is that the Linux file I/O interface does not specify that writes to multiple ranges of a file must be persisted in an all or nothing fashion, which means that file contents can be inconsistent after a crash. […]The second problem is that some external readers of a structured file must never see an update in progress.A third problem in this space concerns software defined storage. […]""<a href="https://blogs.oracle.com/linux/post/xfs-atomic-file-content-exchange-in-uek8" rel="nofollow noopener" translate="no" target="_blank">https://blogs.oracle.com/linux/post/xfs-atomic-file-content-exchange-in-uek8</a><a href="https://hachyderm.io/tags/kernel" class="mention hashtag" rel="nofollow noopener" target="_blank">#kernel</a> <a href="https://hachyderm.io/tags/LinuxKernel" class="mention hashtag" rel="nofollow noopener" target="_blank">#LinuxKernel</a>

Thorsten Leemhuis (acct. 1/4)<a href="https://hachyderm.io/tags/XFS" class="mention hashtag" rel="nofollow noopener" target="_blank">#XFS</a> Directory Parent Pointers since <a href="https://hachyderm.io/tags/Linux" class="mention hashtag" rel="nofollow noopener" target="_blank">#Linux</a> 6.16-rc1 are not considered experimental in the <a href="https://hachyderm.io/tags/kernel" class="mention hashtag" rel="nofollow noopener" target="_blank">#kernel</a> any more[1]. They allow constructing a file path from a file descriptor or a file handle, which should result in better redundancy and reporting. In case your want to know more about it, checkout the recently published text "<a href="https://hachyderm.io/tags/XFS" class="mention hashtag" rel="nofollow noopener" target="_blank">#XFS</a> - Directory Parent Pointers in UEK8"[2], which was written by Allison Henderson and Darrick Wong, who developed and upstreamed the feature.[1] Just like online fsck and the exchange-range syscall: <a href="https://git.kernel.org/linus/ca43b74ac3040a" rel="nofollow noopener" translate="no" target="_blank">https://git.kernel.org/linus/ca43b74ac3040a</a>[2] just ignoring the Oracle/UEK specific bits<a href="https://hachyderm.io/tags/LinuxKernel" class="mention hashtag" rel="nofollow noopener" target="_blank">#LinuxKernel</a>

samWould anyone happen to know how to stop XFS using up to 100MB of memory on my 256MB RAM Raspberry Pi and causing apps to get OOMKilled? This isn’t cache, this is actual used RAM. Searching online is coming up blank. I’m happy to move to a different filesystem if necessary. <a href="https://cablespaghetti.dev/fedi?t=linux" class="mention hashtag" rel="nofollow noopener" target="_blank">#linux</a> <a href="https://cablespaghetti.dev/fedi?t=xfs" class="mention hashtag" rel="nofollow noopener" target="_blank">#xfs</a>

SvenIs using <a href="https://mastodon.social/tags/shred" class="mention hashtag" rel="nofollow noopener" target="_blank">#shred</a> on an encrypted drive overkill? This time I'm thinking <a href="https://mastodon.social/tags/XFS" class="mention hashtag" rel="nofollow noopener" target="_blank">#XFS</a>, but in the future?

Pete Orrall<a href="https://mastodon.bsd.cafe/@stefano" class="u-url mention" rel="nofollow noopener" target="_blank">@stefano</a> This was also <a href="https://mastodon.bsd.cafe/tags/xfs" class="mention hashtag" rel="nofollow noopener" target="_blank">#xfs</a>. I am aware that when it has problems, it *really* has problems lol. But, I've also used XFS on <a href="https://mastodon.bsd.cafe/tags/rhel" class="mention hashtag" rel="nofollow noopener" target="_blank">#rhel</a> and <a href="https://mastodon.bsd.cafe/tags/centos" class="mention hashtag" rel="nofollow noopener" target="_blank">#centos</a> 6 and 7 and <a href="https://mastodon.bsd.cafe/tags/Debian" class="mention hashtag" rel="nofollow noopener" target="_blank">#Debian</a> without any issues. You are probably correct that it was <a href="https://mastodon.bsd.cafe/tags/suse" class="mention hashtag" rel="nofollow noopener" target="_blank">#suse</a>.When I ran Tumbleweed and Leap 15 on an older laptop, I purposely went with ext4 and it was unquestionably a smoother experience.Just curious, which version of openSUSE did you use?

Karl Voit :emacs: :orgmode:<a href="https://narrativ.es/@janl" class="u-url mention" rel="nofollow noopener" target="_blank">@janl</a> The purpose is to warn bystanders to invest in technological <a href="https://graz.social/tags/complexity" class="mention hashtag" rel="nofollow noopener" target="_blank">#complexity</a> that seems to be very attractive for its advanced features without acknowledging the risks or efforts associated.Its learning curve doesn't even allow for an easy start.As with so many awesome tools, this is something for specific experts and not for new/occasional/advanced users.BTDT and I've had my fair share of bad experiences.Current pain in my setup: <a href="https://graz.social/tags/NixOS" class="mention hashtag" rel="nofollow noopener" target="_blank">#NixOS</a>. Instead of providing an abstraction layer to keep away certain OS setup & maintenance problems for good, I got into so many little & bigger troubles that I try to tell people only to use it when they are ready to invest its required learning effort all the way.From my point of view, this also holds true for "advanced" file systems like <a href="https://graz.social/tags/ZFS" class="mention hashtag" rel="nofollow noopener" target="_blank">#ZFS</a>, <a href="https://graz.social/tags/XFS" class="mention hashtag" rel="nofollow noopener" target="_blank">#XFS</a>, ... YMMV.<a href="https://graz.social/tags/PIM" class="mention hashtag" rel="nofollow noopener" target="_blank">#PIM</a> <a href="https://graz.social/tags/technology" class="mention hashtag" rel="nofollow noopener" target="_blank">#technology</a> <a href="https://graz.social/tags/nix" class="mention hashtag" rel="nofollow noopener" target="_blank">#nix</a>

John LeachTIL that xfs has supported copy-on-write reflink copies for years, 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" 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" target="_blank">#xfs</a> <a href="https://mastodon.social/tags/filesystems" class="mention hashtag" rel="nofollow noopener" target="_blank">#filesystems</a> <a href="https://mastodon.social/tags/storage" class="mention hashtag" rel="nofollow noopener" target="_blank">#storage</a>

Asta [AMP]hey hey <a href="https://fire.asta.lgbt/tags/Linux" rel="nofollow noopener" target="_blank">#Linux</a> <a href="https://fire.asta.lgbt/tags/FileSystem" rel="nofollow noopener" target="_blank">#FileSystem</a> <a href="https://fire.asta.lgbt/tags/ZFS" rel="nofollow noopener" target="_blank">#ZFS</a> <a href="https://fire.asta.lgbt/tags/RAID" rel="nofollow noopener" target="_blank">#RAID</a> <a href="https://fire.asta.lgbt/tags/XFS" rel="nofollow noopener" target="_blank">#XFS</a> entities! I'm looking for extremely opinionated discourses on alternatives to ZFS on Linux for slapping together a <a href="https://fire.asta.lgbt/tags/JBOD" rel="nofollow noopener" target="_blank">#JBOD</a> ("Just a Bunch Of Disks", "Just a Buncha Old Disks", "Jesus! Buncha Old Disks!", etc) array. I like ZFS but the fact that it's not in tree in-kernel is an issue for me. What I need most is reliability and stability (specifically regarding parity) here; integrity is the need. Read/write don't have to be blazingly fast (not that I'm mad about it). I also have one <a href="https://fire.asta.lgbt/tags/proxmox" rel="nofollow noopener" target="_blank">#proxmox</a> ZFS array where a raw disk image is stored for a <a href="https://fire.asta.lgbt/tags/Qemu" rel="nofollow noopener" target="_blank">#Qemu</a> <a href="https://fire.asta.lgbt/tags/VirtualMachine;" rel="nofollow noopener" target="_blank">#VirtualMachine;</a> in the VM, it's formatted to XFS. That "seems" fine in limited testing thus far (and seems fast?, so it does seem like the defaults got the striping correct) but I kind of hate how I have multiple levels of abstraction here. I don't think there's been any change on the <a href="https://fire.asta.lgbt/tags/BTRFS" rel="nofollow noopener" target="_blank">#BTRFS</a> front re: raid-like array stability (I like and use BTRFS for single disk filesystems but) although I would love for that to be different. I'm open to <a href="https://fire.asta.lgbt/tags/LVM" rel="nofollow noopener" target="_blank">#LVM</a>, etc, or whatever might help me stay in tree and up to date. Thank you! Boosts appreciated and welcome. <a href="https://fire.asta.lgbt/tags/techPosting" rel="nofollow noopener" target="_blank">#techPosting</a>

MinoruIs 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 <code>fio</code> 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?<a href="https://functional.cafe/tags/mdadm" class="mention hashtag" rel="nofollow noopener" target="_blank">#mdadm</a> <a href="https://functional.cafe/tags/raid" class="mention hashtag" rel="nofollow noopener" target="_blank">#raid</a> <a href="https://functional.cafe/tags/ext4" class="mention hashtag" rel="nofollow noopener" target="_blank">#ext4</a> <a href="https://functional.cafe/tags/xfs" class="mention hashtag" rel="nofollow noopener" target="_blank">#xfs</a> <a href="https://functional.cafe/tags/AskFedi" class="mention hashtag" rel="nofollow noopener" target="_blank">#AskFedi</a>

Richard "RichiH" Hartmann<a href="https://chaos.social/tags/Debian" class="mention hashtag" rel="nofollow noopener" target="_blank">#Debian</a> question: my systems are all using the... not-non-user-hostile... defaults of encrypted LVM partitions, so I have ~250MB of /boot with <a href="https://chaos.social/tags/ext4" class="mention hashtag" rel="nofollow noopener" target="_blank">#ext4</a>. My / is <a href="https://chaos.social/tags/XFS" class="mention hashtag" rel="nofollow noopener" target="_blank">#XFS</a> so I can't move /boot. I have closed <a href="https://chaos.social/tags/nvidia" class="mention hashtag" rel="nofollow noopener" target="_blank">#nvidia</a> drivers via <a href="https://chaos.social/tags/dkms" class="mention hashtag" rel="nofollow noopener" target="_blank">#dkms</a>, 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 <a href="https://chaos.social/tags/linux" class="mention hashtag" rel="nofollow noopener" target="_blank">#linux</a> <a href="https://chaos.social/tags/kernel" class="mention hashtag" rel="nofollow noopener" target="_blank">#kernel</a> footprint in /boot?I can find old stuff, empty stuff, and whataboutism, no docs...

SP⟁CED GO⟁TBeen reading up a bit trying to decide which file system I want to use when I redo my home server soon. Think I'm leaning towards giving btrfs a go. Curious what the splits are on fedi. I've only ever used ext4 on Linux. I'm guessing for desktop/home server use, xfs isn't very popular. Just including it here since it's in this article. <a href="https://appdot.net/tags/Linux" class="mention hashtag" rel="nofollow noopener" target="_blank">#Linux</a> <a href="https://appdot.net/tags/FileSystems" class="mention hashtag" rel="nofollow noopener" target="_blank">#FileSystems</a> <a href="https://appdot.net/tags/EXT4" class="mention hashtag" rel="nofollow noopener" target="_blank">#EXT4</a> <a href="https://appdot.net/tags/BTRFS" class="mention hashtag" rel="nofollow noopener" target="_blank">#BTRFS</a> <a href="https://appdot.net/tags/ZFS" class="mention hashtag" rel="nofollow noopener" target="_blank">#ZFS</a> <a href="https://appdot.net/tags/XFS" class="mention hashtag" rel="nofollow noopener" target="_blank">#XFS</a><a href="https://blog.usro.net/2024/10/linux-file-systems-comparison/" rel="nofollow noopener" translate="no" target="_blank">https://blog.usro.net/2024/10/linux-file-systems-comparison/</a>

Thorsten Leemhuis (acct. 1/4)2/ Ohh, <a href="https://fosstodon.org/tags/Btrfs" class="mention hashtag" rel="nofollow noopener" target="_blank">#Btrfs</a> maintainer Josef Bacik replied and among others addressed the many rude remarks from Kent: <a href="https://lore.kernel.org/all/20241007145847.GA1898642@perftesting/" rel="nofollow noopener" translate="no" target="_blank">https://lore.kernel.org/all/20241007145847.GA1898642@perftesting/</a>Josef among others praises the <a href="https://fosstodon.org/tags/XFS" class="mention hashtag" rel="nofollow noopener" target="_blank">#XFS</a> and <a href="https://fosstodon.org/tags/Ext4" class="mention hashtag" rel="nofollow noopener" target="_blank">#Ext4</a> developers and criticises dragging other people and their projects down – and calls the latter a sort of behaviour that he thinks should have no place in this community.Go and read it in full, quoting from it would not do this great post justice. Many thx for it, <a href="https://fosstodon.org/@josefbacik" class="u-url mention" rel="nofollow noopener" target="_blank">@josefbacik</a>! 👏 <a href="https://fosstodon.org/tags/Linux" class="mention hashtag" rel="nofollow noopener" target="_blank">#Linux</a> <a href="https://fosstodon.org/tags/kernel" class="mention hashtag" rel="nofollow noopener" target="_blank">#kernel</a> <a href="https://fosstodon.org/tags/LinuxKernel" class="mention hashtag" rel="nofollow noopener" target="_blank">#LinuxKernel</a>

ricardo :mastodon:An Initial Benchmark Of <a href="https://fosstodon.org/tags/Bcachefs" class="mention hashtag" rel="nofollow noopener" target="_blank">#Bcachefs</a> vs. <a href="https://fosstodon.org/tags/Btrfs" class="mention hashtag" rel="nofollow noopener" target="_blank">#Btrfs</a> vs. <a href="https://fosstodon.org/tags/EXT4" class="mention hashtag" rel="nofollow noopener" target="_blank">#EXT4</a> vs. <a href="https://fosstodon.org/tags/F2FS" class="mention hashtag" rel="nofollow noopener" target="_blank">#F2FS</a> vs. <a href="https://fosstodon.org/tags/XFS" class="mention hashtag" rel="nofollow noopener" target="_blank">#XFS</a> On <a href="https://fosstodon.org/tags/Linux" class="mention hashtag" rel="nofollow noopener" target="_blank">#Linux</a> 6.11<a href="https://www.phoronix.com/review/linux-611-filesystems" rel="nofollow noopener" translate="no" target="_blank">https://www.phoronix.com/review/linux-611-filesystems</a>

ricardo :mastodon:<a href="https://fosstodon.org/tags/XFS" class="mention hashtag" rel="nofollow noopener" target="_blank">#XFS</a> Expanding Its Online Repair Capabilities In <a href="https://fosstodon.org/tags/Linux" class="mention hashtag" rel="nofollow noopener" target="_blank">#Linux</a> 6.10<a href="https://www.phoronix.com/news/Linux-6.10-XFS" rel="nofollow noopener" translate="no" target="_blank">https://www.phoronix.com/news/Linux-6.10-XFS</a>

Paul Wilde :dontpanic2: :smeghead: :archlinux: :freebsd:PSA: I may disagree with you on one thing, but that does not mean I won't agree with you on another Please calm down, we can still be friends. xx<a href="https://notnull.space/tags/rust" class="mention hashtag" rel="nofollow noopener" target="_blank">#Rust</a> <a href="https://notnull.space/tags/wayland" class="mention hashtag" rel="nofollow noopener" target="_blank">#Wayland</a> <a href="https://notnull.space/tags/docker" class="mention hashtag" rel="nofollow noopener" target="_blank">#Docker</a> <a href="https://notnull.space/tags/ubuntu" class="mention hashtag" rel="nofollow noopener" target="_blank">#Ubuntu</a> <a href="https://notnull.space/tags/javascript" class="mention hashtag" rel="nofollow noopener" target="_blank">#JavaScript</a> <a href="https://notnull.space/tags/windows" class="mention hashtag" rel="nofollow noopener" target="_blank">#Windows</a> <a href="https://notnull.space/tags/macos" class="mention hashtag" rel="nofollow noopener" target="_blank">#MacOS</a> <a href="https://notnull.space/tags/footterminal" class="mention hashtag" rel="nofollow noopener" target="_blank">#footTerminal</a> <a href="https://notnull.space/tags/kde" class="mention hashtag" rel="nofollow noopener" target="_blank">#KDE</a> <a href="https://notnull.space/tags/gnome" class="mention hashtag" rel="nofollow noopener" target="_blank">#Gnome</a> <a href="https://notnull.space/tags/sway" class="mention hashtag" rel="nofollow noopener" target="_blank">#Sway</a> <a href="https://notnull.space/tags/xfs" class="mention hashtag" rel="nofollow noopener" target="_blank">#XFS</a> <a href="https://notnull.space/tags/notputtingalttextonimages" class="mention hashtag" rel="nofollow noopener" target="_blank">#NotPuttingAltTextOnImages</a> <a href="https://notnull.space/tags/excessiveuseofhashtags" class="mention hashtag" rel="nofollow noopener" target="_blank">#ExcessiveUseOfHashTags</a> <a href="https://notnull.space/tags/callinghashtagshashtags" class="mention hashtag" rel="nofollow noopener" target="_blank">#CallingHashtagsHashtags</a>

Recent searches

Search options

Administered by:

Server stats: