fsck.ocfs2(8)

💖 fsck.ocfs2 — the OCFS2 file system check bestie 💖

okay so this is the fsck.ocfs2 page from the OCFS2 Manual Pages and honestly? it's a lot, but we're gonna get through it together, no cap. 🫶

---

✨ NAME ✨

fsck.ocfs2 — check an OCFS2 file system. that's it, that's the whole vibe. it's the girl who walks in and goes "so… what's going on in here" and then actually fixes it. 💅

---

🌸 SYNOPSIS 🌸

fsck.ocfs2 [ -pafFGnuvVy ] [ -b superblock block ] [ -B block size ]
device

---

🦋 DESCRIPTION 🦋

fsck.ocfs2 is literally the tool you use to check an OCFS2 file system. it looks at your filesystem, finds the mess, and (depending on your flags) cleans it up.

device is the file where the file system is stored, like /dev/sda1 for example. and lowkey, it's almost always gonna be a device file — but a regular file works too, so don't stress. 🎀

---

💅 OPTIONS 💅

• -a — this one does the exact same thing as -p. it's only still here for backwards compatibility, periodt. the docs literally suggest you use -p whenever you can instead of this. so like… use -p. 🙈
• -b superblock block — normally fsck.ocfs2 reads the superblock from the first block of the device, like a good girl. this option lets you specify an alternate block for it to read the superblock from instead. (use -r instead of this option, though — that's the word from on high. 👀)
• -B blocksize — the block size, in bytes, can range from 512 to 4096. a value of 0 — which is the default — means "auto-detect the blocksize for me bestie". ✨
• -D — optimize directories in the filesystem. this makes fsck.ocfs2 coalesce the directory entries so the filesystem performance gets better. glow-up for your directories, fr fr. 🔥
• -f — force checking even if the file system is clean. like, "i don't care that you said you're fine, we're checking anyway." 💀
• -F — by default fsck.ocfs2 checks in with the cluster services to make sure the volume isn't in-use (mounted) on any node in the cluster before it proceeds. -F skips that check entirely and should only be used when you can guarantee the volume isn't mounted on any node in the cluster.

⚠️ WARNING: if the cluster check is disabled and the volume is mounted on one or more nodes, file system corruption is very likely. if you're unsure, do not use this option. i'm so serious, bestie. 😭

• -G — usually fsck.ocfs2 will silently assume that inodes whose generation number doesn't match the generation number of the super block are unused inodes. this option makes it ask you whether those inodes should actually be marked unused. it's giving "let the girl decide." 🧚
• -n — gives the 'no' answer to every question fsck will ask. this guarantees the file system will not be modified and the device will be opened read-only. bonus: the output of fsck.ocfs2 with this option can be redirected to produce a record of a file system's faults. very "just here to observe, not to participate." 👑
• -p — automatically repair ("preen") the file system. this makes fsck.ocfs2 automatically fix any problem that can be safely corrected without human intervention. if there are problems that do require intervention, the descriptions get printed and fsck.ocfs2 exits with the value 4 logically or'd into the exit code. (see the EXIT CODE section, babes.) this option is normally used by the system's boot scripts. 🌈
• -P — show progress. we love a little progress bar moment. ⭐
• -r backup-number — mkfs.ocfs2 makes up to 6 backup copies of the superblock at offsets 1G, 4G, 16G, 64G, 256G and 1T, depending on the size of the volume. use this option to specify which backup — 1 thru 6 — to use to recover the superblock. 🍓
• -t — show I/O statistics. and if you specify this option twice, it shows the statistics on a pass by pass basis. double the flag, double the stats. 💜
• -y — gives the 'yes' answer to all questions that fsck will ask. this will repair all faults that fsck.ocfs2 finds, but it will not give the operator a chance to intervene if fsck.ocfs2 decides that it wants to drastically repair the file system. so like… she's gonna do what she's gonna do. 😳
• -v — this option causes fsck.ocfs2 to produce a very large amount of debugging output. it's giving "verbose" and it is not playing around. 💀
• -V — print version information and exit. bye bestie! 👋

---

👑 EXIT CODE 👑

the exit code returned by fsck.ocfs2 is the sum of the following conditions:

0    - No errors
1    - File system errors corrected
2    - File system errors corrected, system should
       be rebooted
4    - File system errors left uncorrected
8    - Operational error
16   - Usage or syntax error
32   - fsck.ocfs2 canceled by user request
128  - Shared library error

it's math, babe. add 'em up. 🧮✨

---

💖 SEE ALSO 💖

debugfs.ocfs2(8) · fsck.ocfs2.checks(8) · mkfs.ocfs2(8) · mount.ocfs2(8) · mounted.ocfs2(8) · o2cluster(8) · o2image(8) · o2info(1) · tunefs.ocfs2(8)

go read those too, iykyk. 🦋

---

🌟 AUTHORS 🌟

Oracle Corporation. this man page entry derives some text — especially the exit code summary — from e2fsck(8) by Theodore Y. Ts'o <tytso@mit.edu>. shoutout to the originals, respect where respect is due. 🙌

---

🎀 COPYRIGHT 🎀

Copyright © 2004, 2012 Oracle. All rights reserved.

---

and that's the whole thing!! Version 1.8.9, dated January 2012 — written back when some of y'all were literally in diapers, but she still ate and left no crumbs. periodt. 💖✨👑