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

Selfhosted

61207 readers
166 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:

Detailed Rules Post

  1. Be civil.

  2. No spam.

  3. Posts are to be related to self-hosting.

  4. Don't duplicate the full text of your blog or readme if you're providing a link.

  5. Submission headline should match the article title.

  6. No trolling.

  7. Promotion posts require active participation, with an account that is at least 30 days old. F/LOSS without a paywall has exceptions, with requirements. See the rules link for details. Tags [CBH] or [AIP] are required, see the links in Rule 8 for details.

  8. AI-related discussions and AI-involved promotional posts have additional requirements for tagging, as noted in Rule 7 and the AI & Promotional Post Expanded Rules post, and find example disclosures here.

Resources:

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

Questions? DM the mods!

founded 3 years ago
MODERATORS
ruud@lemmy.world
Loki@lemmy.world
CannaVet@lemmy.world
devve@lemmy.world
ayyy@sh.itjust.works
curbstickle@anarchist.nexus
curbstickle_lw@lemmy.world
174
RIP my photos from 2017 and contacts from 2005 (lemm.ee)
submitted 2 years ago by summerof69@lemm.ee to c/selfhosted@lemmy.world
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
[โ€“] glasgitarrewelt@feddit.de 11 points 2 years ago* (last edited 2 years 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.

[โ€“] iknowitwheniseeit@lemmynsfw.com 6 points 2 years ago (2 children)

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

[โ€“] derpgon@programming.dev 5 points 2 years ago

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

[โ€“] synapse1278@lemmy.world 5 points 2 years ago

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

[โ€“] evrial@lemmy.world 2 points 2 years ago* (last edited 2 years ago)

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

[โ€“] blackbirdbiryani@lemmy.world 2 points 2 years 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.

[โ€“] zygo_histo_morpheus@programming.dev 2 points 2 years ago

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

[โ€“] nabladabla@sopuli.xyz 2 points 2 years 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.

[โ€“] glasgitarrewelt@feddit.de 3 points 2 years ago

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