tenchiken

I appreciate that the anarchists are canonically the fire. Warms my little heart.

Unlike Dump I actually would want to see Bama’s wife naked.

Not really a strong conviction here, but she seems like she’s not all plastic yet. A mind up there, too… Always good in my list

Also, she at least looks like someone who’s actually had an orgasm in the past 40 years or so.

Conglomerated with DarkStar Industries and featured through Pegged Productions

Can he run for vice Pres if Musk actually creates this party?

Mmm kickbacks!

“self-flagellate”… No I want them to stop sitting on their asses, self fellating.

The positive for Sengled is the option of some sizes that I’ve not found in other brands.

My recommendation is based on use case. Not every device needs to be a router, and OP might be perfectly fine with this.

It is good to know, but I’d not call them the worst since they still are inexpensive and function in all other ways well for my needs.

I use both Sengled and Innr bulbs with zha. Mqtt worked well with these also.

No issues from the few models I have from both. Innr has a decently bright tone controllable bulb, 270 series I think, easily the brightest I have. 260 series are bright enough and super cheap at about $7.50 each in packs.

Such an insult to Bane!

Stand alone complex!

DeEducation

If it’s not from the sweeping fields of Russia, it’s only sparkling gulag.

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

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!

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.

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.

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.

With extra scabs and puss discharge!

What are the odds he had someone torch a few cars just so he could try involving militia, etc?

The old “look look antifa!”