solnet-array-test-v2.sh update for scale (Debian: no camcontrol)

[simonmcnair]

Hi,
I'm trying to stress test but when I run the script camcontrol doesn't work (
Linux truenas 5.10.142+truenas #1 SMP Mon Sep 26 18:20:46 UTC 2022 x86_64 GNU/Linux
)
.

I don't suppose there is a work around for the please ?
Cheers.

 

[jgreco]

You'll hopefully forgive me that I sound annoyed; it is absolutely NOT you I am annoyed at, but rather the whole Linux ecosystem of reinventing the wheel. What I hoped to be a two hour project turned into a messy five hour thing, and it still isn't thoroughly tested (takes lots of time).

Please see if ftp://snarchive.sol.net/incoming/solnet-array-test-v3.sh is more to your liking. Yes I realize the forumware has probably massacred the URL. If you figured out how to get v2, v3 is in the same place, just the one character version number change. Do whatever you previously did to acquire v2.

Please do report any errors or unexpected output.

 

[simonmcnair]

You'll hopefully forgive me that I sound annoyed; it is absolutely NOT you I am annoyed at, but rather the whole Linux ecosystem of reinventing the wheel. What I hoped to be a two hour project turned into a messy five hour thing, and it still isn't thoroughly tested (takes lots of time).

Please see if ftp://snarchive.sol.net/incoming/solnet-array-test-v3.sh is more to your liking. Yes I realize the forumware has probably massacred the URL. If you figured out how to get v2, v3 is in the same place, just the one character version number change. Do whatever you previously did to acquire v2.

Please do report any errors or unexpected output.

Thankfully you don't sound annoyed, for which I am grateful as I didn't mean to cause aggravation.
I appreciate the response and understand that anything you have done is for free out of the kindness of community sharing, which I appreciate. Thank you

 

[simonmcnair]

It took me longer than it should have done to find an ftp client and log on anonymously but that is done now, and I am running it now, thank you.

My only 2 points, and they're intended as constructive criticism of your awesome work is that it would be nice if it was clever enough to know to exclude the volume that was booted from (in my case I don't want to stress test a USB key ;-) ) and also if it did some testing of the zfs array as well as the disks individually and in parallel.

I know it's a lot to ask, but I figure if you don't ask, you don't get.

Thanks again for the effort, it's appreciated.

 

[jgreco]

Thankfully you don't sound annoyed,

Damnit, I should have tried harder to sound annoyed. I meant to sound annoyed. Just not at you.

It took me longer than it should have done to find an ftp client and log on anonymously but that is done now, and I am running it now, thank you.

It might be a bit of a "D'oh!" moment, but you have wget at your fingertips on TrueNAS.

if it did some testing of the zfs array as well as the disks individually and in parallel.

Well, in fairness, it's a tool from ... 1999? Predates ZFS.

it would be nice if it was clever enough to know to exclude the volume that was booted from (in my case I don't want to stress test a USB key ;-)

We had that problem twenty-odd years ago too. This is why there is an option to display the list of disks, and also to select a subset based on a grep.

Code:

sol.net disk array test v3

This is a nondestructive (read-only) full disk test designed to help
diagnose performance irregularities and to assist with disk burn-in

1) Use all disks (from lsblk)
2) Use selected disks (from lsblk|grep)
3) Specify disks
4) Show lsblk list

Option: 4
                               disk fd0
HGST_HTS725050A7E630           disk sda
HGST_HTS725050A7E630           disk sdb
HGST_HTS725050A7E630           disk sdc
HGST_HTS725050A7E630           disk sdd
HGST_HTS725050A7E630           disk sde
ST95005620AS                   disk sdf
HGST_HTS725050A7E630           disk sdg
HGST_HTS725050A7E630           disk sdh
Virtual_disk                   disk sdi
VMware_Virtual_IDE_CDROM_Drive rom  sr0
Press Return:

1) Use all disks (from lsblk)
2) Use selected disks (from lsblk|grep)
3) Specify disks
4) Show lsblk list

Option: 2

Enter grep match pattern (e.g. ST150176): 72505

Selected disks: sda sdb sdc sdd sde sdg sdh
HGST_HTS725050A7E630           465.8G disk sda
HGST_HTS725050A7E630           465.8G disk sdb
HGST_HTS725050A7E630           465.8G disk sdc
HGST_HTS725050A7E630           465.8G disk sdd
HGST_HTS725050A7E630           465.8G disk sde
HGST_HTS725050A7E630           465.8G disk sdg
HGST_HTS725050A7E630           465.8G disk sdh
Is this correct? (y/N):

In this case the VMware Virtual Disk is the boot drive (sdi) and yes it's fair to say that there's no easy way to get the Seagate into the list (sdf) although you could search for "S" I guess.

Anyways, mapping back and forth between ZFS and the native disk identifiers on Linux and FreeBSD, which I think would require different approaches, is probably more work than I'm looking for. I am, however, continuing to see if there are small improvements to be made. I am partway through providing some in-band guidance and explanation of the various phases of the tool, and I may add a burn-in mode.