Conversation

; git commit -m "Here's all that stuff I've been working on for the last month" error: file write error: No space left on device fatal: unable to write loose object file ; rm -rf ~/.cargo ~/.rustup ; git commit -m "Here's all that stuff I've been working on for the last month"

178

This Tweet was deleted by the Tweet author. Learn more

Teoh Han Hui

@teohhanhui

Sep 9

Replying to @snargleplax and

@thingskatedid

not relevant... they're running out of disk space 🥹

Replying to

@snargleplax and

Can definitely save a ton of space used by Git though: git config --global core.compression 9 && find / -type d -name .git -exec git -C {} gc --aggressive \;

Replying to

and @snargleplax

ooh. thank you!

Replying to

and @snargleplax

Git history gets ridiculously bloated over time. Compacting it all with git gc --aggressive helps a lot. Setting core.compression to 9 gets a little bit more out of the zlib compression. Most size wins come from converting loose objects and smaller packs into unified packs.

Replying to

I'm chronically low on disk space from working on multiple different trees based on Linux, Chromium and the Android Open Source Project. Stuck with this puny 2TB Samsung 980 Pro until they release the 4TB Samsung 990 Pro next year. Have learned lots of ways to save disk space...

Replying to

Can also save tons of space with `cp --reflink` if your filesystem has support (XFS and Btrfs but not ext4). It's essentially fork(...) for files. It uses block-based copy-on-write at the destination. Can copy an identical file over another to deduplicate without sharing writes.

Replying to

and

oh wow, that’s finally the first good reason I’ve seen to use XFS. also dupremove looks useful for this:

github.com

GitHub - markfasheh/duperemove: Tools for deduping file systems

Tools for deduping file systems. Contribute to markfasheh/duperemove development by creating an account on GitHub.

Replying to

and

XFS genuinely performs substantially better than ext4 for highly parallel I/O on an NVMe drive. f2fs is nicer in some situations and Android makes great use of f2fs being a log structured fs via the checkpoint disable feature to allow rolling back updates after data was mounted.

Replying to

f2fs automatically moves to new data formats in kernel upgrades and doesn't officially support downgrading to a lower major kernel version so it's not really a reasonable fs for a workstation. Has better performance than ext4 but not sure how it compares with XFS for high end hw.

1:41 AM · Sep 10, 2022Twitter Web App

Replying to

f2fs works well for Android because OS releases are tested on exact hardware they'll be running on and there's automatic rollback if boot fails followed by the update being locked in with rollback protection. Not really developed in a way that works for traditional distros (yet).