Recent searches

No recent searches

Search options

Only available when logged in.
eupolicy.social is one of the many independent Mastodon servers you can use to participate in the fediverse.
This Mastodon server is a friendly and respectful discussion space for people working in areas related to EU policy. When you request to create an account, please tell us something about you.

Administered by:

Server stats:

211
active users

eupolicy.social: AboutProfiles directoryPrivacy policy

Mastodon: AboutGet the appKeyboard shortcutsView source codev4.4.1

#filesystems

0 posts0 participants0 posts today
IT Notes<b>Make Your Own Backup System – Part 1: Strategy Before Scripts</b><br><br><a href="https://it-notes.dragas.net/2025/07/18/make-your-own-backup-system-part-1-strategy-before-scripts/" rel="nofollow noopener" target="_blank">https://it-notes.dragas.net/2025/07/18/make-your-own-backup-system-part-1-strategy-before-scripts/</a><br><br><a href="https://snac.it-notes.dragas.net?t=itnotes" class="mention hashtag" rel="nofollow noopener" target="_blank">#ITNotes</a> <a href="https://snac.it-notes.dragas.net?t=notehub" class="mention hashtag" rel="nofollow noopener" target="_blank">#NoteHUB</a> <a href="https://snac.it-notes.dragas.net?t=backup" class="mention hashtag" rel="nofollow noopener" target="_blank">#backup</a> <a href="https://snac.it-notes.dragas.net?t=data" class="mention hashtag" rel="nofollow noopener" target="_blank">#data</a> <a href="https://snac.it-notes.dragas.net?t=filesystems" class="mention hashtag" rel="nofollow noopener" target="_blank">#filesystems</a> <a href="https://snac.it-notes.dragas.net?t=ownyourdata" class="mention hashtag" rel="nofollow noopener" target="_blank">#ownyourdata</a> <a href="https://snac.it-notes.dragas.net?t=series" class="mention hashtag" rel="nofollow noopener" target="_blank">#series</a> <a href="https://snac.it-notes.dragas.net?t=server" class="mention hashtag" rel="nofollow noopener" target="_blank">#server</a> <a href="https://snac.it-notes.dragas.net?t=tutorial" class="mention hashtag" rel="nofollow noopener" target="_blank">#tutorial</a> <a href="https://snac.it-notes.dragas.net?t=vps" class="mention hashtag" rel="nofollow noopener" target="_blank">#vps</a><br>
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>
JdeBP<p><span class="h-card" translate="no"><a href="https://mastodon.social/@cks" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>cks</span></a></span> </p><p>The same thought occurred to me. There have been cute tricks like that played. I've even played some of them on other systems.</p><p>But as far as I know that first entry in the i-node table was just unused.</p><p>I wonder whether fsck even checked it. Modern FreeBSD fsck_ffs does, but that's a very different beast.</p><p><a href="https://tty0.social/tags/Unix" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Unix</span></a> <a href="https://tty0.social/tags/filesystems" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>filesystems</span></a> <a href="https://tty0.social/tags/FFS" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>FFS</span></a> <a href="https://tty0.social/tags/UFS" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>UFS</span></a></p>
JdeBP<p><span class="h-card" translate="no"><a href="https://mastodon.social/@cks" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>cks</span></a></span> </p><p>Off By One Error in your post on this. (-:</p><p>Since 0 means a free directory entry, that's only 65535 i-nodes.</p><p>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.</p><p><a href="https://tty0.social/tags/Unix" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Unix</span></a> <a href="https://tty0.social/tags/filesystems" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>filesystems</span></a></p>
JdeBP<p><span class="h-card" translate="no"><a href="https://teh.entar.net/@spacehobo" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>spacehobo</span></a></span> <span class="h-card" translate="no"><a href="https://mastodon.social/@brouhaha" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>brouhaha</span></a></span> </p><p>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.</p><p>(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.)</p><p>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.</p><p>Putting filesystem *and* swap on tape boggles the mind, though. (-:</p><p><a href="https://mastodonapp.uk/tags/Unix" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Unix</span></a> <a href="https://mastodonapp.uk/tags/magtape" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>magtape</span></a> <a href="https://mastodonapp.uk/tags/filesystems" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>filesystems</span></a> <a href="https://mastodonapp.uk/tags/tar" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>tar</span></a> <a href="https://mastodonapp.uk/tags/DEC" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>DEC</span></a> <a href="https://mastodonapp.uk/tags/retrocomputing" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>retrocomputing</span></a></p>
Peter N. M. Hansteen<p>Making openat(2) and friends more useful in practice <a href="https://www.undeadly.org/cgi?action=article;sid=20250529080623" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://www.</span><span class="ellipsis">undeadly.org/cgi?action=articl</span><span class="invisible">e;sid=20250529080623</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/openat" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>openat</span></a> <a href="https://mastodon.social/tags/open" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>open</span></a> <a href="https://mastodon.social/tags/filesystems" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>filesystems</span></a> <a href="https://mastodon.social/tags/security" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>security</span></a> <a href="https://mastodon.social/tags/development" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>development</span></a> <a href="https://mastodon.social/tags/unveil" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>unveil</span></a> - now also with regression tests, more discussions on tech@</p>
Droppie [infosec] 🐨:archlinux: :kde: :firefox_nightly: :thunderbird: :vegan:​<p><code>BtrFS</code> <em>completely sucks</em> &amp; i shall <em>never again</em> make the error of using it instead of <code>ext4</code>. 😡</p><p><a href="https://infosec.space/tags/BtrFS" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>BtrFS</span></a> <a href="https://infosec.space/tags/ext4" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>ext4</span></a> <a href="https://infosec.space/tags/linux" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>linux</span></a> <a href="https://infosec.space/tags/filesystems" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>filesystems</span></a> <a href="https://infosec.space/tags/ArchInstall" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>ArchInstall</span></a> <a href="https://infosec.space/tags/ArchLinux" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>ArchLinux</span></a> <a href="https://infosec.space/tags/VM" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>VM</span></a></p>
John Leach<p>TIL 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!)</p><p><a href="https://blogs.oracle.com/linux/post/xfs-data-block-sharing-reflink" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">blogs.oracle.com/linux/post/xf</span><span class="invisible">s-data-block-sharing-reflink</span></a></p><p><a href="https://mastodon.social/tags/xfs" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>xfs</span></a> <a href="https://mastodon.social/tags/filesystems" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>filesystems</span></a> <a href="https://mastodon.social/tags/storage" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>storage</span></a></p>
Christian Brauner 🦊🐺<p>Picked backed up the work for VFS {g,u}id squashing. IOW, mapping all {g,u}ids down to a single {g,u}id. Any process that doesn't have that {g,u}id but is still privileged otherwise will write to disk as the squashed {g,u}id. I just finished a draft and selftests that miraculously work.</p><p><a href="https://web.git.kernel.org/pub/scm/linux/kernel/git/vfs/vfs.git/log/?h=work.idmapped.squash" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">web.git.kernel.org/pub/scm/lin</span><span class="invisible">ux/kernel/git/vfs/vfs.git/log/?h=work.idmapped.squash</span></a></p><p>Probably "bugs galore" at this point. Needs more thinking.</p><p><a href="https://mastodon.social/tags/linux" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>linux</span></a> <a href="https://mastodon.social/tags/kernel" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>kernel</span></a> <a href="https://mastodon.social/tags/vfs" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>vfs</span></a> <a href="https://mastodon.social/tags/filesystems" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>filesystems</span></a></p>
Stefano Marinelli

One of the main criticisms I read about ZFS (mainly OpenZFS) in forums and articles is that "it's not well integrated into Linux."
It's true - there is a licensing issue, and that shouldn't be underestimated. However, I believe it's wrong to judge it based on this - on FreeBSD, it is perfectly integrated (not to mention the various illumos-based OSes), and in my opinion, it should be judged for what it is, not for its integration into the different Linux distributions.

#OpenZFS#ZFS#FileSystems
James Young

Surely someone's looked into this: if I wanted to store millions or billions of files on a filesystem, I wouldn't store them in one single subdirectory / folder. I'd split them up into nested folders, so each folder held, say, 100 or 1000 or n files or folders. What's the optimum n for filesystems, for performance or space?
I've idly pondered how to experimentally gather some crude statistics, but it feels like I'm just forgetting to search some obvious keywords.
#BillionFileFS #linux #filesystems #optimization #benchmarking

Dendrobatus Azureus

HDD SSD space should be counted in binary.

1KB in binary is 1024.

A 32 TB hard drive is in fact 30.517578125 TB unpartitioned /unformatted capacity, as the binary system on the computer actually uses it

I know about all those confusing terms that you can find when you go and search on different engines; those are just to confuse and convolute the fact that drives sold are under capacity

Counting storage in decimals is a crime, a marketing scheme which should have been outlawed globally.

#FileSystems#HDD#SSD
SP⟁CED GO⟁T

Been 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.

#Linux #FileSystems #EXT4 #BTRFS #ZFS #XFS

blog.usro.net/2024/10/linux-fi

· 65 people · Closed
Ultimate Systems Blog · Linux File Systems Comparison
Replied in thread
Kingsley Uyi Idehen

@Migueldeicaza @davew,

For years, we’ve offered a personal #DataSpaces platform providing an abstraction layer over data managed by #filesystems (including cloud services) and/or #DBMS.

You can even mount #Dropbox, #OneDrive, #S3, etc., with fine-grained access controls for governance.

In the age of #AI, we’re making this usable via natural language as an extension (e.g., #CustomGPT) for #LLM-based chatbots like #ChatGPT.

TrendingLive feeds
About