HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
mxmlnkn
ratarmount
Python2021–2026
mxmlnkn / ratarmount

ratarmount

Access large archives as a filesystem efficiently, e.g., TAR, RAR, ZIP, GZ, BZ2, XZ, ZSTD archives

12Distinct people
18Mentions
0Explicit recommenders
1.3KGitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

Access large archives as a filesystem efficiently, e.g., TAR, RAR, ZIP, GZ, BZ2, XZ, ZSTD archives

GitHub

Where it is used

No documented product use was verified in the last source check.

What people are saying

No recommendation phrase was found in the indexed comments.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

Mentioned in the same Hacker News threads. That is not proof they are substitutes.

This week on Hacker News

Nov 9–Nov 16 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/16/2026, 7:27:27 AM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by year18 dated mentions

Observed mentions: 2021-11-11 07:46:57 UTC to 2026-05-04 01:24:41 UTC.

0123452021-01-01 00:00:00 UTC to 2022-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments20212022-01-01 00:00:00 UTC to 2023-01-01 00:00:00 UTC (exclusive): 3 mentions; 1 submissions, 2 comments2023-01-01 00:00:00 UTC to 2024-01-01 00:00:00 UTC (exclusive): 4 mentions; 2 submissions, 2 comments20232024-01-01 00:00:00 UTC to 2025-01-01 00:00:00 UTC (exclusive): 5 mentions; 3 submissions, 2 comments2025-01-01 00:00:00 UTC to 2026-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2026-01-01 00:00:00 UTC to 2027-01-01 00:00:00 UTC (exclusive): 4 mentions; 1 submissions, 3 comments. Incomplete calendar period.2026*

* An incomplete calendar period is marked with an outlined bar. Its count is not directly comparable with a full period.

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
20212021-01-01 00:00:00 UTC2022-01-01 00:00:00 UTC101
20222022-01-01 00:00:00 UTC2023-01-01 00:00:00 UTC312
20232023-01-01 00:00:00 UTC2024-01-01 00:00:00 UTC422
20242024-01-01 00:00:00 UTC2025-01-01 00:00:00 UTC532
20252025-01-01 00:00:00 UTC2026-01-01 00:00:00 UTC101
2026 (partial)2026-01-01 00:00:00 UTC2027-01-01 00:00:00 UTC413

What Hacker News says

5 sources
mxmlnkn·Nov 1, 2024Submission

Show HN: Ratarmount 1.0.0 – Rapid access to large archives via a FUSE filesystem

Hi HN, Since my first posted introduction of ratarmount [0], 2 years have gone by and many features have been added. To summarize, ratarmount enables working with archived contents exposed as a filesystem without the data having to be extracted to disk: pip install ratarmount ratarmount archive.tar mounted ls -la mounted I started this project after noticing the slowness of archivemount with large TAR files and wondering how this could be because the file contents exist at some offset in the archive file and it should not be difficult to read that data. Turns out, that part was not difficult, however packaging everything nicely, adding tests, and adding many more formats and features such as union mounting and recursive mounting, are the things keeping me busy on this project until today. Since the last Show HN, a libarchive,
Read the rest
SquashFS, fsspec, and many more backends have been added, so that it now should be able to read every format that archivemount can and some more, and even read them remotely. However, performance for any use case besides bzip2/gzip-compressed TARs may vary even though I did my best. Personally, I am using it view to packed folders with many small files that do not change anymore. I pack these folders because else copying to other hard drives takes much longer. I'm also using it when I want to avoid the command line. I have added ratarmount as a Caja user script for mounting via right-click. This way, I can mount an archive and then copy the contents to another drive to effectively do the extraction and copying in one step. Initially, I have also used it to train on the ImageNet TAR archive directly. I probably should have released a 1.0.0 some years ago because I have kept the command line interface and even the index file format compatible as best as possible between the several 0.x versions already. Some larger future features on my wishlist are: - A new indexed_lz4 backend. This should be doable inside my indexed_bzip2 [1] / rapidgzip [2] backend library. - A custom ZIP and SquashFS reader accelerated by rapidgzip and indexed_bzip2 to enable faster seeking inside large files inside those archives. - I am eagerly awaiting the Linux Kernel FUSE BPF support [3], which might enable some further latency reductions for use cases with very small files / very small reads, at least in the case of working with uncompressed archives. I have done comparisons for such archives (100k images a 100 KiB) and noticed that direct access via the Python library ratarmountcore was roughly two times faster than access via ratarmount and FUSE. Maybe I'll even find the time to play around with the existing unmerged FUSE BPF patch set. [0] https://news.ycombinator.com/item?id=30631387 [1] https://news.ycombinator.com/item?id=31875318 [2] https://news.ycombinator.com/item?id=37378411 [3] https://lwn.net/Articles/937433/
76 points · Open discussion
The libfuse github has some good examples for C/C++ in [0] of increasing complexity: - passthrough.c mirrors existing filesystem, "Its performance is terrible." - passthrough_fh.c "performance is not quite as bad." - passthrough_ll.c implemented with low level api and "the least bad among the three" - passthrough_hp.cc high performance version written in C++ Some interesting fuse projects in my notes: [1] splitting large files into segments; [2] show ZFS incremental snapshots as files; [3] transparent filesystem compression; [4] and [5] options for mounting archives as filesytems. - [0] https://github.com/libfuse/libfuse/tree/master/example - [1] https://github.com/seiferma/splitviewfuse - [2] https://github.com/UNFmontreal/zfs_fuse_snapshot - [3] https://github.com/FS-make-simple/fusecompress - [4] https://github.com/google/fuse-archive
Read the rest
In Started a guide to writing FUSE filesystems in Python

Ask HN: A better Criu Alternative for decompression software / Erlang?

So Criu (https://criu.org/) , is a checkpoint restore utility which could be used with docker. Now the main use case of this is docker live migration from which I learned something But I also realised that this allows (atleast on linux) (though you could use wsl on windows) to allow decompression software like winrar , peazip etc. or cli tools like unrar-free to shutdown while the decompression is taking place and also erlang + criu just feels like a very awesome combination Now we could do something like this by taking random access (https://github.com/mxmlnkn/ratarmount) but I was wondering about this if we could have some sort of backup software where it would continue downloading the file right from where its left even the computer shuts down. and though there is dmtcp , I am not exactly sure if that's the right cause since on criu's
Read the rest
website comparing this. It says "Such behavior is very dangerous, as application might see wrong files in the /proc filesystem if it will try to access one via its PID." Now I was wondering if we could have a general sort of Virtual Machine which could run a specific language (especially the erlang , especially erlang with its let it fail approach could be nice) / For decompression software as well. Is criu the best we can get within the linux world , has somebody thought of creating a very lightweight os meant to be as a virtual machine with checkpoint / restore. Or could we rather instead of Criu , actually try to do this without Criu , right in the decompression software tooling ? I am somewhat confused about this , and I would really like it if someone with experience could simplify where I should try to put my efforts into doing such project
2 points · Open discussion

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.