r/SysAdminBlogs • • 10h ago

How I Added 250GB of Storage to a Linux VPS for €4/Month Using S3 and ext4

Post image
0 Upvotes

I recently ran into a shortage of disk space on my VPS. I currently rent a VPS for €7 a month with this configuration: 4 vCPUs, 8 GB of RAM, and a 120 GB NVMe drive. It has 50 GB of free space left. But I need to run a Docker container whose image is 76 GB. I could upgrade my current VPS to get a 240 GB disk, but that would cost €30 a month. That’s steep. I noticed that my hosting provider offers 250 GB of S3 storage for just €4 a month, accessible over its internal network. So I started wondering how I could turn it into a filesystem and have Docker store files there.

First, I tried rclone. It lets you create a FUSE filesystem from your S3 storage. To speed things up, you can cache frequently used files on a local SSD using the --vfs-cache-max-size flag. Unfortunately, Docker uses overlay2, which requires filesystem operations that rclone mount does not guarantee: atomic renames, correct chmod and chown behavior, hard links, and extended attributes. In short, a full POSIX filesystem is needed.

And I found a solution: s3backer. It has 600+ stars on GitHub and provides a full-fledged ext4 filesystem. I set a 20 GB cache on my local SSD using the --blockCacheSize option, mounted it at /mnt/s3, and reconfigured Docker to store images, containers, and volumes there. As a result, the most frequently used files are cached locally instead of being pulled over the network from S3. What do you think? Expanding my virtual machine’s disk space by 250 GB for €4 a month? Pretty great, if you ask me!

By the way, here’s a summary table of the available options:

SolutionHow it worksProsCons
s3backer + ext4S3 as a block deviceFull POSIX filesystem, Docker compatibility, cachingComplex setup, latency, risk of filesystem corruption
rclone mountFUSE over S3Simple setup, local cache, support for multiple cloud providersIncomplete POSIX compatibility, some operations are unsupported
s3fsFUSE over S3Simple mounting, familiar file operationsSlow metadata operations, POSIX limitations
JuiceFSDistributed filesystem on top of S3POSIX, caching, high performanceRequires separate metadata storage
S3QLFilesystem on top of S3POSIX, compression, deduplication, encryptionExtra overhead, complex recovery

Of course, s3backer is far from the only way to turn S3 into a filesystem. There are at least two other interesting projects: JuiceFS and S3QL. Both run on top of S3, support POSIX operations and local caching, but they seemed like overkill for my use case.

JuiceFS is a fairly powerful distributed filesystem. It supports multiple servers working concurrently, caching, POSIX, and much more. But there’s a catch: in addition to S3 itself, it requires a separate metadata store. This could be Redis, PostgreSQL, MySQL, or even a local SQLite database. The last option doesn’t require a separate service, but you still have to keep the metadata database safe and back it up. Overall, it’s an interesting solution, especially if you have a server cluster. But I only have one VPS, and I didn’t want to set up extra infrastructure just to store Docker images.

S3QL is another interesting option. It supports POSIX, local caching, compression, deduplication, and encryption. It doesn’t need a separate database server: metadata is stored in SQLite and synchronized with the object store. But these extra features come at the cost of added complexity. Deduplication requires computing hashes, compression uses CPU time, and recovering the filesystem after a failure may require checking and restoring metadata with specialized tools. These aren’t critical drawbacks, but I didn’t see any particular advantages for my use case, either.

The key difference lies in the approach: JuiceFS and S3QL implement filesystems themselves using FUSE, while s3backer provides virtual block storage on top of which you can create a standard ext4 filesystem. As a result, Docker works with the familiar Linux filesystem, and s3backer translates block operations into requests to S3. No separate metadata databases, no deduplication, and no extra layers of file management.

Of course, this setup has its downsides too. Random reads and writes can be heavily affected by S3 latency, and losing the connection to the storage can bring the containers to a halt. A serious failure could also corrupt the filesystem. So I wouldn’t use this setup for critical databases. But for storing large Docker images that are downloaded once and then mostly read, it seemed perfectly reasonable-especially when S3 is available over the hosting provider’s local network. In short, I wanted an extra 250 GB for €4 a month without building a distributed storage system. From that perspective, s3backer seemed like the best fit.


r/SysAdminBlogs • • 10h ago

We're building a supercomputer

Thumbnail
golem.de
2 Upvotes

r/SysAdminBlogs • • 13h ago

A Linux time travel tool

Thumbnail
github.com
2 Upvotes

About a month ago I asked here if a tool to see ps, ss or lsof output at a past moment was worth building:

https://www.reddit.com/r/linuxadmin/comments/1wyhwfe/is_a_linux_time_travel_tool_worth_building/

I got some fair pushback (sar, atop, below, Prometheus, zabbix) and a few people who were curious. I looked at all of them. They cover a lot, but none of them could tell me which process had which connections open, or what lsof showed for a process at 02:45 last night. So I built it, mostly to find out if it could be done without hurting the server.

I wanted to name it "command line time travel" but then a though about the consequences of such a name and It's called clifr instead (command line flight recorder) and has two parts:

  • clifrd runs as a service and records processes, process starts and exits (through eBPF, so a process that lives 5 ms still shows up), TCP connections with the process that owns them, files held open, mounts, kernel messages and the usual system counters. It keeps 72 hours in /var/lib/clifr, 2 GB max.
  • clifr rebuilds the output of the normal commands for a past moment or a time range. It doesn't run the command, it rebuilds the output from the recording.clifr --at "02:45" "ps aux" clifr --since "02:00" --until "03:00" "ss -tanp dst 10.0.4.21 and dport = :5432" clifr --since "1 hour ago" events # starts, exits, OOM kills, mounts clifr diff --at "14:00" --at "14:20" "ss -ltnp"

There are about 40 commands so far: ps, top, pidstat, lsof, ss, netstat, free, vmstat, iostat, mpstat, df, ip, dmesg, systemctl list-units, lsblk, and more and all are 100% accurate.

The first thing people asked last time was the cost, so here are the numbers:

Quiet serverMixed loadBusy server
CPU0.35% of one core0.5-0.6% of one core1.9% of one core
RAM~90 MiB~80-120 MiB~290 MiB (335 max)
Disk~`20 MiB/day~100 MiB/day~4 GiB/day
Networknone, no ports opennonenone

Disk use depends heavily on how busy the server is.

clifr is not a monitoring tool and has no alerts. It's not a security audit tool either: it doesn't record file reads or writes, and root can stop it. It's for the "what was going on at 02:45" question, after the fact.

Status: it's a prototype, version 0.1.0. It hasn't run on a real production server yet (a friend starts one this week), and all the load has been synthetic. AGPL-3.0, no telemetry, nothing leaves the box.

So if you have a test or dev box (RHEL 8/9, Rocky, Alma), I'd really appreciate it if you tried it and told me what breaks or what looks wrong. The most useful thing for me is comparing what clifr shows with what you know was really happening.

I appreciate all your comments even if they are harsh


r/SysAdminBlogs • • 21h ago

Global Secure Access - Device Access is here!

Thumbnail
blog.sonnes.cloud
4 Upvotes

Another Global Secure Access update - Device Access is here!

Bringing pre-logon connectivity back to Windows devices using device identity instead of user identity like we know from the old days!

Think on password changes, first-time sign-ins, domain controller connectivity, Group Policy processing and on-premises device management - all before a user signs in to Windows!

I've been following and testing this feature since its earlier preview in June 2026, and it's great to finally see it reach Public Preview at Microsoft Ignite.

In my latest blog post, I cover a lot - check it out!

#Microsoft #EntraID #GlobalSecureAccess #GSA #ZeroTrust #MSecurity #MSIgnite #MVP #MVPBuzz


r/SysAdminBlogs • • 23h ago

Entra Privilege Identity Management (PIM) - Role activation and more now possible at MyAccess

Thumbnail
blog.sonnes.cloud
7 Upvotes

From a feature request to Microsoft Ignite announcement – almost a year in the making!

Back in November 2025, I sent a feature suggestion directly to the Microsoft Entra engineering team: Why not bring Privileged Identity Management (PIM) role activation into the My Access portal?

An idea partly inspired by my findings around the hidden PIM URLs and undocumented UI experiences:

https://blog.sonnes.cloud/the-hidden-microsoft-entra-pim-urls-microsoft-never-documented-even-when-restrict-access-to-microsoft-entra-admin-center-is-enabled/

Fast forward almost a year… and here we are! 😎

I've had the opportunity to participate in the Private Preview, test the capabilities, share feedback and work closely with the team. Now it's officially announced in the Microsoft Ignite 2026 Book of News!

In my latest blog post, I share the story, hands-on testing, technical findings and a complete walkthrough, covering:
> PIM activation for Entra ID, Azure RBAC and Groups
> Just-in-Time (JIT) privileged access
> Remote Resource Access, Azure Bastion and Cloud Shell
> Requirements, limitations and findings not previously covered!

It's incredibly rewarding to see an idea evolve into an actual Microsoft product capability.

Sometimes, it's worth sending that email. You never know where it might lead! 😉

#Microsoft #EntraID #PIM #IdentitySecurity #MSIgnite #MicrosoftMVP #MVPBuzz #Community


r/SysAdminBlogs • • 11h ago

Every service desk demo this quarter was AI, so we built a test from our own queue

1 Upvotes

Four service desk demos in six weeks and every one led with AI. We're about 3,500 people across three regions, so leadership wants a number before anything gets budget.

The one with the boldest claim was Atera's Robin, pitched as an AI technician that resolves up to 92% of tier 1 and complex tier 2 incidents. What sets it apart from the others is that it runs the fix itself, checks the result, and closes the ticket with notes on what it did. Hardware still comes back to us, and the approval rules for what it can touch are ours to write.

So we picked three categories from last quarter, password lockouts, print queues, and VPN client errors, and set one rule. A ticket only counts as resolved if no tech touched it and it wasn't reopened. That's the test every vendor gets on our data.