IPHYMV(1)

🎀 IPHYMV(1) — User Commands 🎀

✨ NAME ✨

okay so bestie, iphymv is an iRODS iCommand — the whole manual page is IPHYMV(1), and it's giving “physical move, but make it iRODS.” 💅

🌸 SYNOPSIS 🌸

iphymv [-hMrvV] [-n replNum] [-S srcResource] [-R destResource]

🦋 DESCRIPTION 🦋

the thing you're moving can be:

dataObj|collection ...

and the main-character move is: physically move a file in iRODS to another storage resource. ✨

the source replica has to be specified by its full hierarchy, and it must exist at the provided resource hierarchy location. the resource hierarchy for the destination replica also has to be specified in full, but it may or may not exist at the specified location. specifying a leaf resource is acceptable in lieu of a full resource hierarchy because it can be reverse-resolved to the root. like these example usages, fr fr:

iphymv -S demoResc -R 'pt1;r1;s1' /tempZone/home/alice/test.txt
iphymv -S demoResc -R 's1' /tempZone/home/alice/test.txt

if the leaf resource targeted for a phymv refers to the archive of a compound resource hierarchy, DIRECT_ARCHIVE_ACCESS will be returned because direct access to an archive resource is not allowed. 🚨

no cap, bestie: iphymv cannot overwrite a replica which is not marked stale. iphymv cannot move a replica which is not at rest. iphymv cannot move a replica which is part of an already locked data object. 💀

iphymv returns a few unique error codes based on the type of error which occurred within the system:

• 0: Success
• 1: There was a problem with the client configuration or parsing the user input
• 2: There was a problem connecting to the iRODS server (rcConnect failed)
• 3: Historic exit code returned for all errors other than those listed above and below
• 4: There was a mismatch between the source and destination replica's checksums
• 5: There was a problem with the supplied source logical path
• 6: The resource to host the destination replica has run out of space (ENOSPC)
• 7: The source or destination replica failed to be opened for any other reason

note that if the source copy has a checksum value associated with it, a checksum will be computed for the replicated copy and compared with the source value for verification. 🫶

💅 Options are: 💅

• -r — recursive — phymove the whole subtree
• -M — admin — admin user uses this option to phymove other users files
• -n replNum — the replica to be phymoved, typically not needed
• -S srcResource — specifies the source resource for the move. If specified, the replica stored on this resource will be moved.
• -R destResource — specifies the destination resource for the move. This can also be specified, in your environment or via a rule set up by the administrator.
• -v — verbose
• -V — Very verbose
• -h — this help

also, this page is stamped iRODS Version 5.0.2 / iphymv — periodt. 🧚

mwah 💋 — iphymv from iRODS-5.0.2, dated January 1980, page IPHYMV(1), signing off fr fr 💖