PVFS2-REMOVE-OBJECT(1)

πŸ“¦
version 2.10.1 Β· 2 versions
, in fedora 44

πŸ’– NAME πŸ’–

pvfs2-remove-object β€” ok so bestie, this one removes an internal object from an OrangeFS volume. That's the whole vibe. πŸŽ€


✨ SYNOPSIS ✨

pvfs2-remove-object [-hv] [-f fs_id] [-o handle] [-p handle -d
entry_name]

short and kinda mysterious, honestly iconic πŸ¦‹


🌸 DESCRIPTION 🌸

So pvfs2-remove-object does exactly one thing and it does it very specifically: it removes an object from an OrangeFS volume by handle number. 🫢

When would you even need this? Repairing a corrupt file system. That's the use case. That's it. It's giving "emergency surgery, not a spa day." πŸ’…

⚠️ Real talk: improper use of this utility could corrupt a file system. Not "oops teehee" corrupt. Like, corrupt corrupt. Handle with care, bestie. 😭

Also important, and the manpage is very clear on this: the -p and -d options must be used together to remove a directory entry. They're a package deal. No solo runs. 🀝

And here are the options, as follows:

  • -h β€” displays the synopsis. Just the synopsis. A little peek. πŸ‘€
  • -v β€” prints the version number and then exits. Short king behavior. ✨
  • -f β€” uses fs_id as the file system ID.
  • -o β€” removes the handle handle. This is the main character option, ngl. 🌟
  • -p β€” specifies the parent handle handle.
  • -p β€” specifies the dirent name entry_name. (yes, the page really does list -p here a second time β€” I'm not out here editing the source material, I just report what it says 🫑)

🌈 ENVIRONMENT 🌈

The environment variables are doing the most, as always:

  • PVFS2_DEBUGFILE β€” if you set this to the path of a local file, the debug output gets redirected into it. Debug juice, contained. πŸ§ƒ
  • PVFS2_DEBUGMASK β€” sets the OrangeFS debug mask. What masks are even possible? That's documented over in pvfs2-set-debugmask(1), go look. πŸ”
  • PVFS2TAB_FILE β€” if set, this is the full pathname for an alternate pvfs2tab file. Fancy. πŸŽ€

πŸ’œ FILES πŸ’œ

  • /etc/pvfs2tab

the classic. the standard. the default bestie. 🌸


⭐ EXAMPLES ⭐

Okay so here's the example. Copy the file /etc/motd to /mnt/bar. And if /mnt is an OrangeFS volume, then this will copy the file into OrangeFS. Simple as that. πŸ¦‹

pvfs2-cp /etc/motd /mnt/bar
tiny note: this is literally the example printed on the page, even though the page is about removing objects. Copy-paste energy. I don't make the rules, I just slay them. πŸ’…

πŸ’€ CAVEATS πŸ’€

When dst_file is a directory, this utility does not work. Like, at all. Not a "try harder" situation, it's a "no" situation. πŸ™ˆ

And in this respect, it is different than the cp(1) utility. So don't come in expecting cp(1) behavior, because you will be humbled. 😌


πŸ› BUGS πŸ›

Found something broken? Please submit bug reports to devel@lists.orangefs.org. They're lovely, they'll read it. Be nice, be specific, include the details. 🫢


πŸ‘‘ SEE ALSO πŸ‘‘


and that's the whole page, bestie β€” no cap, every single detail preserved, every flag accounted for, nothing skipped. you understood the assignment. πŸŽ€

this page came from the General Commands Manual, dated 2017-07-03, and it's the PVFS2-REMOVE-OBJECT(1) page itself. okay bye, go repair that file system carefully, mwah πŸ’–βœ¨

πŸ“¦ where this page comes from
  • fedora 44: orangefs 2.10.1-3.fc44 Β· LicenseRef-Callaway-LGPLv2+ AND LicenseRef-Callaway-LGPLv2 AND LicenseRef-Callaway-BSD AND LicenseRef-Callaway-MIT AND Zlib
  • fedora 44: orangefs 2.10.1-3.fc44 Β· LicenseRef-Callaway-LGPLv2+ AND LicenseRef-Callaway-LGPLv2 AND LicenseRef-Callaway-BSD AND LicenseRef-Callaway-MIT AND Zlib
  • πŸ’– girlified by deepseek-ai/DeepSeek-V4.1-Flash on : a language model's rewrite of the original, under its terms