GFSPOOLPATH(1)

💖 NAME 💖

gfspoolpath — bestie, this one shows you a pathname on a filesystem node, all about a Gfarm file. That's the whole vibe. ✨

🌸 SYNOPSIS 🌸

gfspoolpath [-s spool_directory] [path...]

gfspoolpath [-I] [inode_number:generation_number...]

Two whole moods, pick your fighter 🫶

🦋 DESCRIPTION 🦋

okay so here's the tea ☕ — this command prints out a pathname of a concrete file sitting on a filesystem node. Which concrete file, you ask? The one that matches the Gfarm file you handed it as a command argument. Literally that simple 💅

And the pathname it gives you? It's relative to the top directory of a spool directory of gfsd. So don't come at it expecting an absolute path, that's not the moment. Keep that in mind, iykyk. ✨

🎀 OPTIONS 🎀

• -I — the moment you drop this flag, the command expects inode_numbers and generation_numbers as your arguments, and they're separated by a colon (:). inode:generation, that's the format, periodt. 🍓
• -s spool_directory — okay so if you invoke this command with a privilege that can actually access the gfsd spool directory, AND you didn't pass -I, then gfspoolpath is gonna do a lil vibe check 🧚: it compares the file size of the metadata against the size of the concrete file, and if those two are different, it throws up a warning. This option is how you tell it which pathname of the gfsd spool directory to use for that check. If you don't specify it, then /var/gfarm-spool is assumed, no questions asked. And if you don't have enough privilege? The check is simply skipped, no drama, we move on. 🙈

💀 BUGS 💀

ngl, there's a lil something: no error is reported if the command argument refers to a directory. So yeah. It just... doesn't say anything. Not a peep. Be aware, bestie 😭

this whole page is brought to you by Gfarm, dated 16 Feb 2016 🎀 thanks for coming to my TED talk, slay, go find your spool paths ✨👑💜