LFS-MIRROR-RESYNC(1)

πŸ“¦ version 2.17.58, in ubuntu stonking

πŸ’– LFS-MIRROR-RESYNC πŸ’–

okay bestie, so this one is the manual page for lfs-mirror-resync β€” it's a Lustre User Utilities situation (Lustre girlies stay winning πŸ‘‘), and it does exactly one extremely important thing: it resynchronizes an out-of-sync mirrored file. that's it. that's the whole job. slay. ✨


🌸 NAME 🌸

lfs-mirror-resync β€” resynchronize an out-of-sync mirrored file πŸ’…


✨ SYNOPSIS ✨

lfs mirror resync [--only MIRROR_ID[,...]]  [--bandwidth=|-W
                  BANDWIDTH_MB] [--force-resync|-f] [--stats] [--stats-
                  interval=INTERVAL_SECONDS] MIRRORED_FILE
                  [MIRRORED_FILE2 ...]

πŸ¦‹ DESCRIPTION πŸ¦‹

bestie, this command resynchronizes the out-of-sync mirrored file(s) you point at with the path name MIRRORED_FILE. iconic behavior honestly.

so here's the vibe check on what actually goes down:

  • if there's no stale mirror for the MIRRORED_FILE(s)? the command does nothing. it's giving "nothing to see here" πŸ’€
  • if the mirrors are inconsistent but no components are marked as stale, the command will fail with an error message suggesting you use --force-resync. noted. πŸ“
  • otherwise? it copies data from the synced mirror to the stale mirror(s), and marks all the successfully copied mirror(s) as SYNC. periodt. πŸ’–

if the --only option is not specified, the nosync mirror(s) β€” like, the components that have this flag set β€” will not be synced. lowkey rude of them but okay.

if the --only MIRROR_ID[,...] option is specified, then the command will resynchronize the mirror(s) specified by the MIRROR_ID(s), and even nosync mirror(s) will be resynchronized as well. chaotic, but we respect it. πŸ”₯

⚠️ this option cannot be used when multiple mirrored files are specified. like, pick a lane bestie.

πŸ’… OPTIONS πŸ’…

  • --only MIRROR_ID[,...] β€” this option says which mirror(s), specified by MIRROR_ID(s), need to be resynchronized. the MIRROR_ID is the numerical unique identifier for a mirror. multiple *MIRROR_ID*s are separated by commas. and no, this option cannot be used when multiple mirrored files are specified. πŸ™ˆ
  • -f, --force-resync β€” force resynchronization of the specified mirrors even when they're not marked as stale. this option requires the --only option to say which mirrors to resync. when mirrors are inconsistent but no components are marked as stale, normal resync will fail with an error message suggesting the use of this option. it's the "fine, I'll do it myself" button. 😀
  • --stats β€” enables progress updates every 5 seconds, in YAML format. we love a little progress moment. πŸ“Š
  • --stats-interval=STATS_INTERVAL β€” enables progress updates every STATS_INTERVAL seconds, in YAML format. you get to choose your own interval, main character energy fr fr. ⏱️
  • -W, --bandwidth BANDWIDTH_MB[MG] β€” limit the read and write bandwidth a mirror resync consumes to no more than BANDWIDTH_MB MiB/s. an optional suffix can be used to specify units in Megabytes or Gigabytes per second. throttle it, we're being polite to the filesystem. 🌈

πŸŽ€ EXAMPLES πŸŽ€

resynchronize all of the stale and sync-able mirror(s) for /mnt/lustre/file1 and /mnt/lustre/file2:

# lfs mirror resync /mnt/lustre/file1 /mnt/lustre/file2

resynchronize mirrors with mirror ID 4 and 5 for /mnt/lustre/file1 even if they are not marked as STALE:

# lfs mirror resync --only 4,5 /mnt/lustre/file1

force resynchronization of mirror 2 when mirrors are inconsistent but not marked as stale:

# lfs mirror resync --only 2 --force-resync /mnt/lustre/file1

⭐ AVAILABILITY ⭐

the lfs mirror resync command is part of the lustre(7) filesystem package since release 2.11.0. she's been here a minute, and she's been serving the whole time. πŸ’œ


πŸ‘‘ SEE ALSO πŸ‘‘

lfs(1), lfs-mirror-create(1), lfs-mirror-extend(1), lfs-mirror-split(1), lfs-mirror-verify(1), lfs-setstripe(1)


okay that's the whole page bestie, go resync something and be free πŸ¦‹ β€” this was the Lustre manual page for LFS-MIRROR-RESYNC(1), dated 2025-05-23, and yes I'm mentioning it in the sign-off because that's the rules πŸ’–βœ¨πŸŽ€

πŸ“¦ where this page comes from