tenchiken

joined 2 years ago
MODERATOR OF
[–] [email protected] 16 points 1 day ago

lol I love how these always do the "We'll get them all this time for sure!"

[–] [email protected] 9 points 2 days ago (2 children)

This one was trying to get in the minors, but hadn't got there yet

[–] [email protected] 4 points 4 days ago

"in that mere fraction of a second, regret set in as Rolf realized the zipper had snagged his beans"

[–] [email protected] 2 points 4 days ago (1 children)

The orange wrapper means that cheese is gonna be the oldest and stinkiest variety.

The ol' Camembert '69.

They'll both need new dentures after tonight!

[–] [email protected] 9 points 5 days ago (1 children)
[–] [email protected] 5 points 5 days ago

A twist: the birthday was OP, and the present was to himself via girlfriend later that night.

[–] [email protected] 1 points 6 days ago (1 children)

Awesome, so that's good news. Disks probably just fine.

My next thoughts are on the service itself then... Your service providing the share might be getting throttled or not getting direct access to kernel hooks for performance.

Simplest test I would think is set up Samba or NFS in the host itself, not a container. Try a large transfer there. If speed isn't an issue that way, then something at the container level is hindering you.

[–] [email protected] 3 points 6 days ago (3 children)

Hmm, at a glance those all look to be CMR.

To rule this out ideally, a tool like iostat (part of sysstat tools) can help. While moving data, and with the problem happening, if you run something like "iostat 1 -mx" and watch for a bit, you might be able to find an outlier or see evidence of if the drives are overloaded or of data is queueing up etc.

Notably watch the %util on the right side.

https://www.golinuxcloud.com/iostat-command-in-linux/ can help here a bit.

The %util is how busy the communication to the drive is.. if maxed out, but the written per second is junk, then you may have a single bad disk. If many are doing it, you may have a design issue.

If %util doesn't stay pegged, and you just see small bursts, then you know the disks are NOT the issue and can then focus on more complex diagnosis with networking etc.

[–] [email protected] 6 points 1 week ago (6 children)

What drives? If they are shingled, your performance will be terrible and the array runs a high risk of failing.

CMR is the way to go.

SMR behavior is about like what you describe... Fast until the drive cache is filled then plummets to nothing.

[–] [email protected] 4 points 1 week ago

With extra scabs and puss discharge!

[–] [email protected] 4 points 1 week ago

Garak's expression in the last frame always gets my upvote.

[–] [email protected] 53 points 1 week ago (1 children)

The story so far: In the beginning the Web was created. This has made a lot of people very angry and been widely regarded as a bad move.

view more: next ›