FSCK.EROFS(1)

💖 FSCK.EROFS(1) 💖

okay so bestie, welcome to the General Commands Manual, section 1, where we're talking about fsck.erofs — yes that's the actual command name, no I will not be abbreviating it, it's iconic and it knows it. 🎀

---

✨ NAME ✨

fsck.erofs — the tool that checks an EROFS filesystem's integrity. it's literally the vibe check for your filesystem, no cap. 🦋

---

✨ SYNOPSIS ✨

fsck.erofs [OPTIONS] IMAGE

that's it. that's the whole summoning ritual. OPTIONS go in the front, your IMAGE goes in the back, and the fsck does its thing. 💅

---

✨ DESCRIPTION ✨

so what does fsck.erofs actually do? it scans an EROFS filesystem IMAGE and checks the integrity of it. that's the whole job. it looks at your image, it's like "hmm let me see", and it tells you if everything's chill or not. main character energy honestly. 👑

---

✨ OPTIONS ✨

here's where it gets juicy. every single one, in order, no skips:

• -V, --version — prints the version number of fsck.erofs and then exits. like "hi, here's who I am, bye". 💖
• -d # — sets the level of debugging messages. the default is 2, which shows you basic warning messages. turn it up if you want the tea, turn it down if you want peace. 🔥
• -p — prints the total compression ratio of all files, including both the compressed and the non-compressed ones. receipts for your compression. ✨
• --device=path — specify an extra blob device to be used together with your image. and listen, you can give multiple --device options, but they have to be in the correct order. order matters bestie, don't play. 🎀
• --extract[=directory] — tests by extracting the whole file system. it scans all inode data, including compressed inode data, which means more I/O and more CPU load, so depending on how big your image is, this might take a long time. 😭

optionally, it'll extract the contents of the IMAGE to directory. so --extract alone is just the test, --extract=somewhere actually drops the files there. 🫶

• --no-sbcrc — bypasses the on-disk superblock checksum verification. like skipping the bouncer at the door. sometimes you gotta. 🙈
• --nid=# — specify the target inode by its NID, for checking or for extraction. the default target is the root inode. ⭐
• --path=path — specify the target inode by its path, for checking or for extraction. and heads up: if you specify both --nid and --path, then --path takes precedence. path wins, always, periodt. 💅
• --[no-]xattrs — whether to dump extended attributes during extraction. this is default off, so don't come for me when your xattrs aren't there. 🌸
• --xattr-inode-digest — verifies the per-inode digests that get recorded as extended attributes during image creation with mkfs.erofs --xattr-inode-digest. it's giving detective work. 🧚
• -h, --help — displays the help string and exits. the classic. 💜
• -a, -A, -y — okay so real talk: these options do nothing at all. zero. nada. they're provided only for compatibility with the fsck programs of other filesystems. they're here for the vibes and the vibes alone. 💀

lowkey important: --extract is the one that'll eat your time and your CPU. it scans everything, including compressed inode data. more I/O, more load, potentially a very long wait depending on image size. plan accordingly bestie. ⏳

---

✨ AUTHOR ✨

this version of fsck.erofs was written by Daeho Jeong <daehojeong@google.com>. absolute legend, we stan. 👑

---

✨ AVAILABILITY ✨

fsck.erofs is part of the erofs-utils package and is available from:

git://git.kernel.org/pub/scm/linux/kernel/git/xiang/erofs-utils.git

go get it, it's free, it's open, it's iconic. 🌈

---

✨ SEE ALSO ✨

• fsck(8) — the og. the blueprint. iykyk. 💖

---

okay that's the whole page bestie, we did it, we made it to the end 🎉 this was the FSCK.EROFS(1) manual page from the General Commands Manual (section 1), part of the erofs-utils package — love that for us. now go check your filesystem's integrity, you deserve it. 🦋✨💅