this post was submitted on 21 Feb 2024
174 points (95.8% liked)

Selfhosted

40059 readers
691 users here now

A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.

Rules:

  1. Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.

  2. No spam posting.

  3. Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.

  4. Don't duplicate the full text of your blog or github here. Just post the link for folks to click.

  5. Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).

  6. No trolling.

Resources:

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 1 year ago
MODERATORS
ruud
Loki
CannaVet
devve
HybridSarcasm
[email protected]
174
RIP my photos from 2017 and contacts from 2005 (lemm.ee)
submitted 8 months ago by [email protected] to c/selfhosted
62 comments fedilink hide all child comments
 

I recently decided to replace the SD card in my Raspberry Pi and reinstall the system. Without any special backups in place, I turned to rsync to duplicate /var/lib/docker with all my containers, including Nextcloud.

Step #1: I mounted an external hard drive to /mnt/temp.

Step #2: I used rsync to copy the data to /mnt/tmp. See the difference?

Step #3: I reformatted the SD card.

Step #4: I realized my mistake.

Moral: no one is immune to their own stupidity πŸ˜‚

you are viewing a single comment's thread
view the rest of the comments
[–] [email protected] 11 points 8 months ago* (last edited 8 months ago) (6 children)

Sorry to hear, I feel you:

I wanted to delete all .m3u-files in my music collection when I learned:

find ./ -name "*.m3u" -delete -> this would have been the right way, all .m3u in the current folder would have been deleted.

find ./ -delete -name "*.m3u" -> WRONG, this just deletes the current folder and everything in it.

Who would have known, that the position of -delete actually matters.

[–] [email protected] 6 points 8 months ago (2 children)

I didn't know there was a -delete option to find! I've been piping to xargs -0 for decades!

[–] [email protected] 5 points 8 months ago

Probably because it's easier to fuck up. With piping to xargs, you are forced to put the delete command last.

[–] synapse1278 5 points 8 months ago

I did this sort of mistakes too, luckily BTRFS snapshots are always here to save the day !

[–] [email protected] 2 points 8 months ago

I can recommend fd to everyone frustrated with find, it has a much more intuitive interface imo, and it's also significantly faster.

[–] blackbirdbiryani 2 points 8 months ago

I use GNU find every day and still have to google about the details. Only learnt about - delete the other day, good to know the position matters.

[–] [email protected] 2 points 8 months ago (1 children)

The first one would have deleted nothing as it needs to match the whole name. I recommend running find with an explicit -print before replacing it in place with -delete or -exec. It's good to remember that find has a complex order dependent language with -or and -and, but not maybe the best idea to try to use those features.

[–] [email protected] 3 points 8 months ago

Lemmy interpreted the * as something cursive. I try to edit it like I mean it.

[–] evrial 2 points 8 months ago* (last edited 8 months ago)

fd -tf -e m3u -x rm loads all cores and nothing works faster