this post was submitted on 10 Nov 2024
31 points (100.0% liked)

Linux

48344 readers
529 users here now

From Wikipedia, the free encyclopedia

Linux is a family of open source Unix-like operating systems based on the Linux kernel, an operating system kernel first released on September 17, 1991 by Linus Torvalds. Linux is typically packaged in a Linux distribution (or distro for short).

Distributions include the Linux kernel and supporting system software and libraries, many of which are provided by the GNU Project. Many Linux distributions use the word "Linux" in their name, but the Free Software Foundation uses the name GNU/Linux to emphasize the importance of GNU software, causing some controversy.

Rules

Related Communities

Community icon by Alpár-Etele Méder, licensed under CC BY 3.0

founded 5 years ago
MODERATORS
AgreeableLandscape@lemmy.ml
nooter692@lemmy.ml
MarcellusDrum@lemmy.ml
cypherpunks@lemmy.ml
cyclohexane@lemmy.ml
d3Xt3r@lemmy.nz
31
Unreliable samba transfers - common issue? (lemmy.ml)
submitted 2 weeks ago* (last edited 2 weeks ago) by cyberwolfie@lemmy.ml to c/linux@lemmy.ml
27 comments fedilink hide all child comments
 

I'm running Jellyfin on a Debian-server in my home, and I have the associated media folders set up as samba shares so that I can transfer any new media from my laptop to the server through Dolphin (KDE file manager).

This has for the most part worked very well (except slow speeds), but I've had an issue recently where the files are not copied over properly. This resulted in glitches in for example music files that would stop playback. I checked the checksums of some of these files, and they were different from source. Seems like the glitchy files are missing some data, but at no point were I notified about this. It works fine after I removed the files and transferred again, and now the checksums match.

Is this a common issue with samba, or could it be a sign that my HDD is acting up?

you are viewing a single comment's thread
view the rest of the comments
[–] Bldck@beehaw.org 3 points 2 weeks ago (3 children)

rysnc might be a faster and more reliable option. It can compress the files for transfer and does checksums after the transfer is complete

I used something like this to transfer 12 TB from offsite to onsite with zero failures


rsync -arvzip --progress /path/to/host /path/to/destination

You can set up a screen and let this run in the background all the time

[–] eldavi@lemmy.ml 4 points 2 weeks ago (2 children)

and since op is using kde, they can use a konsole with dolphin to drag and drop /path/to/host and /path/to/destination as well.

[–] Bldck@beehaw.org 3 points 2 weeks ago (1 children)

Thanks for sharing! I’m a pure headless Linux user, so I don’t know much about desktop environments

[–] eldavi@lemmy.ml 2 points 2 weeks ago

i'm headless for servers too; but i'm foolish enough to use the x server as my daily driver. lol

[–] cyberwolfie@lemmy.ml 2 points 2 weeks ago

Oh, I didn't know that. Neat!

[–] cyberwolfie@lemmy.ml 2 points 2 weeks ago

I tried to resync now, and had to pass the -c flag to make sure it checked the cheksums to see if they should be updated. Then it worked. Looks like that does not affect the after-transfer checksum check though, so that's good (from documentation):

Note that rsync always verifies that each transferred file was correctly reconstructed on the receiving side by checking a whole-file checksum that is generated as the file is transferred, but that automatic after-the-transfer verification has nothing to do with this option's before-the-transfer lqDoes this file need to be updated?rq check.
[–] cyberwolfie@lemmy.ml 2 points 2 weeks ago (1 children)

Thanks! Glad to know rsync includes check after transfer, as I've just recently used it to backup everything on these drives to another hard drive that will not always be spinning. But I did not consider using it to transfer new media onto these hard drives.

I'll try to use it to resync the files that were acting up.

[–] Bldck@beehaw.org 1 points 2 weeks ago (1 children)

Depending on your file structure, you could probably keep this running all the time so you don’t have to manually intervene in the future

[–] cyberwolfie@lemmy.ml 1 points 2 weeks ago (1 children)

How would I achieve that? With cron?

[–] Bldck@beehaw.org 2 points 2 weeks ago
  1. Open a screen
  2. Start an rsync job to maintain parity between source and destination
  3. Exit the screen, but keep it running
  4. Now rsync will be running in the background until you kill it

You can reattach the screen whenever you want to check on status, change parameters or kill it