IFSCK(1)

🎀 NAME 🎀

Okay bestie, this is IFSCK(1) from the User Commands manual, and the command is ifsck — an iRODS iCommand. It's giving "wellness check but make it filesystem forensics," and honestly? Obsessed. ✨

🦋 SYNOPSIS 🦋

ifsck [-hKrR] srcPhysicalFile|srcPhysicalDirectory

💅 DESCRIPTION 💅

So ifsck checks if a local file or local directory content is consistent in size — and optionally its checksum — with its registered size (and optionally its checksum) in iRODS. Basically it's the vibe check for "does local data still match iRODS?" 🫶

It allows detection of managed data that has been corrupted or modified outside the iRODS framework on the local filesystem. No cap, that's the whole assignment.

srcPhysicalFile or srcPhysicalDirectory must be a fully qualified path. Like, no casual relative-path energy, bestie. 💅

To check files registered to the leaf of a resource hierarchy, use the -R option with a full resource hierarchy (semicolon delimited):

ifsck -R 'pt1;r1;s1' /localdir/full/path/to/file.txt

That's the exact example, semicolons and all. Iconic. 🍓

✨ Options are: ✨

• -K — verify the checksum of the local file against the one registered in iRODS. Important: it's ignored if the checksum has not already been calculated and stored. So if it wasn't already stored, this flag is just gonna sit there, bestie. 💀
• -r — recursive — scan srcPhysicalDirectory and its local subdirectories. We're going deep. 🌀
• -R — rescHier — if provided, will match replicas on this leaf resource, rather than using the hostname of the root of each file's resolved hierarchy. Exact behavior, no improv. 👑
• -h — this help. The classic "help me help you" flag. 🙈

And that's the whole page, periodt. The version banner energy is iRODS Version 5.0.2 with ifsck chilling on the same line, and the footer is ifsck iRODS-5.0.2, dated January 1980 — iconic little timestamp, honestly. 💖🎀