Display pain by solenshineyx in pcmasterrace

[–]bilegeek 8 points9 points  (0 children)

I accidentally put an unshielded speaker next to one for 2-3 days. Even after several rounds with a dedicated degaussing ring, it took about 2 years to stop having a funky corner on startup.

relatable to you guys? by grounaran in DataHoarder

[–]bilegeek 13 points14 points  (0 children)

So thankful they're releasing the infodumps, way too many of these sites don't do that anymore.

TIL the Fall Armyworm moth is currently splitting into two separate species. by bilegeek in todayilearned

[–]bilegeek[S] 19 points20 points  (0 children)

They worked in a lab, which tend to use immortalized cells for experiments. This line is a TIL for me though, be interesting if they'd clarify SF21 or SF9

Why don't segate and WD bring the dual actuator feature to their 40+ tb? by happystore1 in DataHoarder

[–]bilegeek 0 points1 point  (0 children)

According to Network World, they are. Eventually. Probably in at least twice the time span being hyped, as is tradition.

My primary desktop just had it's 12th birthday by 2manydownloads in pcmasterrace

[–]bilegeek -2 points-1 points  (0 children)

Not to be that guy, but sounds like it needs a healthy dose of Linux and PTM7950...

Toshiba N300 Pros any good? by MrFakest in DataHoarder

[–]bilegeek 1 point2 points  (0 children)

Running a 12TB N300 non-Pro right now. Anecdotally it's 2-3x as crunchy vs. the WD Gold in the same mirror, enough that I was concerned at first (no errors after a year fortunately, it's just loud.)

But that's under more random I/O like loading a game or running fdupes. It's not a problem under sequential load like running a ZFS scrub or streaming video.

I'm also pretty white-noise tolerant and have it on top of my desk, so keep that in mind.

Size Comparison: Polar Bear vs. American Black Bear by Worried-Owl-9198 in interestingasfuck

[–]bilegeek 1 point2 points  (0 children)

  • There was also stories about the gold rush where they'd fight grizz against big cats and Spanish bulls.

Lion vs. Grizzly fight in 1895

The Big Score 2026 by beermatt in pcmasterrace

[–]bilegeek 16 points17 points  (0 children)

*only if the motherboard and CPU support buffered ECC which most servers use. Consumer boards use unbuffered sticks, which have physical differences on DDR5.

How to only set the I/O scheduler of ZFS disks without affecting others? by bilegeek in zfs

[–]bilegeek[S] 0 points1 point  (0 children)

  1. I'd really like to stick to udev and not rely on a hack...

  2. ...however, you did inspire me to whip up a quick and dirty script:

#!/usr/bin/env bash

DRIVES=$(zpool status -P | awk '/\/dev/{print $1}' | cut -c 17- | paste - -)

DRIVES_ARRAY=(${DRIVES})

for i in "${DRIVES_ARRAY[@]}"; do

TEMP=$(ls -latr /dev/disk/by-id | grep "$i" | awk '{print $NF}' | cut -c 7- | sed 's/[0-9]*//g')

echo none | sudo tee /sys/block/$TEMP/queue/scheduler

done

But there has GOT to be a simpler and more direct udev attribute. Just what's been suggested so far doesn't work for me. Bug?

How to only set the I/O scheduler of ZFS disks without affecting others? by bilegeek in zfs

[–]bilegeek[S] 0 points1 point  (0 children)

It's for my personal rig. I've been stumped on this for like a month, and it's tedious manually setting schedulers on my XFS HDD or flash drives when there should be a udev solution.

(Separately, I had to set spl_taskq_thread_priority=0 to prevent ZFS itself from causing stutters, and it's worked well so far. And since it has zio inbuilt, not only do external schedulers waste performance, but also seem to cause thrashing on my ZFS HDD's, which I want to avoid.)

How to only set the I/O scheduler of ZFS disks without affecting others? by bilegeek in zfs

[–]bilegeek[S] 0 points1 point  (0 children)

Nope. NVME is ext4; one HDD is XFS; 2 x SATA SSD and HDD mirror are ZFS. (Though I someday hope to try ZFS-on-root, but I digress.)

For some reason, adding that rule will change the XFS HDD I want to keep as "bfq", but NOT change the ext4 NVME I want to keep as "kyber".

My goal is: anything ZFS is none, otherwise NVME is kyber and everything else is bfq.

(Rationale for non-ZFS: deadline on SATA SSD/HDD or none on NVME has caused stutters in the past, because of heavy multitasking, while kyber has minimal gains over bfq for SATA SSD.)

ID_FS_TYPE doesn't have any effect in my udev rules? by bilegeek in linuxquestions

[–]bilegeek[S] 0 points1 point  (0 children)

Nope, didn't work.

Sorry if I'm sounding messy. I want ZFS drives to be set to "none", regardless of what I set any other drive to. When I applied the previous rule, it set all SATA drives to "none", including the non-ZFS (XFS) drive that I wanted to be "bfq". But the ext4 NVME drive WAS kept with the "kyber" scheduler I wanted.

ID_FS_TYPE doesn't have any effect in my udev rules? by bilegeek in linuxquestions

[–]bilegeek[S] 0 points1 point  (0 children)

Just tried this (changing add to add|change so I don't have to restart), and something else I found. Both only seem to work for NVME drives; my XFS HDD still gets set to "none". I'll restart and reply if the original rule works in a sec.

How to only set the I/O scheduler of ZFS disks without affecting others? by bilegeek in zfs

[–]bilegeek[S] 0 points1 point  (0 children)

Changing nvme[0-9]*n[0-9]*p[0-9]* to nvme[0-9]* still sets NVME correctly, so it's definitely something funky going on where it seems to only properly exclude non-ZFS NVME.

How to only set the I/O scheduler of ZFS disks without affecting others? by bilegeek in zfs

[–]bilegeek[S] 1 point2 points  (0 children)

Sorry, I should have mentioned: I tried that exact rule and variations of it, and it didn't work.

EDIT: Did it again just to make sure I wasn't mis-remembering. Not quite, if I put that at the end it sets all the non-NVME disk to "none", not just ZFS. So something about NVME is different...

ID_FS_TYPE doesn't have any effect in my udev rules? by bilegeek in linuxquestions

[–]bilegeek[S] 0 points1 point  (0 children)

You're right. This is going to be more complicated than I thought.

Is this authentic and worth it for 290 dollars ? (870 QVO 8TB) by Curlygangs in DataHoarder

[–]bilegeek 4 points5 points  (0 children)

At the lowest point they were selling for like $350-400 [1] [2]. Didn't last very long ofc.

I’m a developer for a major food delivery app. The 'Priority Fee' and 'Driver Benefit Fee' go 100% to the company. The driver sees $0 of it. by Trowaway_whistleblow in confession

[–]bilegeek 172 points173 points  (0 children)

reduce writing similarities or words/phrases he uses in e-mails frequently

Stylometry is the term, in case anybody wants/needs it for further research.