RECOVERMOV(1)

📦
version 2.6.3 · 5 versions
, in debian trixie, ubuntu noble, ubuntu questing

👑 recovermov — the manual, but make it a group chat 💖

okay so bestie, you know that one friend who's like obsessed with rescuing your deleted vacation videos? That's recovermov, and this is section 1 of the manual, so buckle up 🎀

✨ NAME ✨

recovermov — recover movies from a filesystem image 🎬🦋

Basically: your camera card is a mess, and this little icon pulls the movies back out. no cap.

🌸 SYNOPSIS 🌸

recovermov [options] device

That's it. You give it a device, it does the thing. 💅

💜 DESCRIPTION 💜

So recovermov tries to identify mov movies from a filesystem image. To do that, it scans the filesystem image and goes looking for a mov structure at blocks starting at 512 byte boundaries. Like, it's just out here vibe-checking every 512-byte line, hoping one of them is giving movie 🎥✨

Now — where do your rescued movies go? recovermov stores the recovered movies into the current directory. Want them somewhere else? Two options, both valid, pick your main character moment:

  • just cd into the directory you want recovermov to save the movies into (at the shell prompt, bestie) and start recovermov from there, or
  • use the -o option 🫶
⚠️ important tea: device is not necessarily a physical device. It may also be a file containing a copy of the faulty device, which is actually the smart move — it reduces the actual processing time and the stress imposed on an already defective hardware. Like, don't keep poking the dying thing?? 😭

dd(1) or ddrescue(1) may be used to create such a working copy. (yes those are real, go look them up, iykyk 💀)

🔥 OPTIONS 🔥

  • -h — Display an help message. short king behavior, honestly 🙈
  • -b blocksize — Set the size of blocks in bytes. On most file systems, setting it to 512 (the default) will work fine, because any large file will be stored on 512 bytes boundaries. Setting it to 1 maximizes the chances of finding very small files if the filesystem aggregates them (UFS for example) — but at the expense of a much longer running time. it's giving "worth it but pack a snack" 🍓
  • -i integerindex — Set the initial index value for image numbering (default: 0).
  • -n basename — Basename to use to create the salvaged files. Default is video_.
  • -o directory — Change the working directory before restoring files. Use this option to restore files into a directory with enough space instead of the current directory. This option can be repeated. ✨ (stack them like bracelets, bestie)
  • -V — Display program version and exit. bye 👋

and now, the size suffix lore:

All the sizes may be suffixed by a k, m, g, or t letter to indicate KiB, MiB, GiB, or TiB. For example, 6m correspond to 6 MiB (6291456 bytes). math is math 🧮💅

🦋 EXAMPLES 🦋

Recover as many movies as possible from the memory card located in /dev/sdc:

recovermov /dev/sdc

Recover as many movies as possible from a crashed ReiserFS file system (which does not necessarily store files at block boundaries) in /dev/hdb1:

recovermov -b 1 /dev/hdb1

see? -b 1 for the ReiserFS chaos. iconic 🌈

Copyright (c) 2010-2016 Samuel Tardieu <sam@rfc1149.net> and Jan Funke <jan.funke@inf.tu-dresden.de>. This is free software; see the source for copying conditions.

🚨 There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. like, zero. none. nada. 💀

🌟 SEE ALSO 🌟

(its sibling, go say hi 👑)

💖 AUTHORS 💖

Jan Funke <jan.funke@inf.tu-dresden.de> and Samuel Tardieu <sam@rfc1149.net>. legends, fr fr 🫶

okay and that's the whole page!! brought to you by the Recovermov User Manuals, dated November 12, 2016, filed under section RECOVERMOV(1) ⭐ go recover some memories bestie, you got this 💜🎬

📦 where this page comes from