On 1/17/24 02:42, Thomas Schmitt wrote:
Hi,
Gene Heskett wrote:
lsblk, which I've published several times, shows 5 drives.
Duh. Obviously this thread overstretches my mental capacity.
And I've since tried cp in addition to rsync, does the same thing, killing
the sysytem with the OOM but much quicker. cp using all system memory (32Gb)
in 1 minute, another 500K into swap adds another 15 secs, and the OOM kills
the system. So both cp and rsync act broken.
I get the suspicion that your disk set overstretches the mental capacity
of the hardware or the operating system.
Both "cp" and "rsync" are heavily tested by the GNU/Linux community and
quite independently developed. A common memory leak would have to sit
deeper in the software stack, i.e. in kernel or firmware.
kernel. firmware, or terminals scroll back memory, I purposely set this
particular terminals scrollback to 200 lines with that in mind.
rsync, with a --bwlimit=3m set, takes much longer to kill the system but the
amount of data moved is very similar, 13.5G from clean disk to system freeze
for rsync, 13.4G for cp.
This observation might be significant. But i fail to make up a theory.
One of the things I'm fairly good at, they gave all 7nth graders the
Iowa test in 1947, similar to the S/B IQ test but not copyrighted, there
fore a lot cheaper, and I came out of that with an equivalent of 147. I
quit school 2 years later when I could and went to work fixing tv's. Had
my draft number moved up in '52 in the middle of korea to get that out
of the way, drafted was 2 years, volunteered was 4 years, but failed the
AFQT by getting a 98 out of 100, which earned me a 4F classification
because I wouldn't take orders from the Sargent, I find out the next
best score that day among 130+ boys was 36/100 which freed me to let a
girl become my wife in '57, & started making kids, got a 1st phone in
1962 without cracking a book, did the same thing in 1972 to become a
registered CET which I'll readily admit is getting rusty in my dotage at
89 yo. The technology is slowly passing me by since I retired in the
middle of 2002. Because I went diabetic in the '80's, my beer limit is
1, but I'd do it with any of you folks if we ever meet in person. Let
the war stories flow. ;o)> <-smiley with a goatee.
That copy is now up to 4x the data copied in any other try.
root@coyote:~# df && free
Filesystem 1K-blocks Used Available Use% Mounted on
udev 16327704 0 16327704 0% /dev
tmpfs 3272684 1904 3270780 1% /run
/dev/sda1 863983352 22346308 797675396 3% /
tmpfs 16363420 1244 16362176 1% /dev/shm
tmpfs 5120 8 5112 1% /run/lock
/dev/sda3 47749868 612 45291248 1% /tmp
/dev/md0p1 1796382580 335101664 1369955940 20% /home
tmpfs 3272684 3752 3268932 1% /run/user/1000
/dev/sdh1 1967892164 64369552 1803486364 4% /mnt/homevol
total used free shared buff/cache
available
Mem: 32726840 3453372 199708 919044 30336824
29273468
Swap: 111902712 1536 111901176
And swap use has not increased, its stabilized.
gene@coyote:~/src/klipper-docs$ lsblk -d -o NAME,MAJ:MIN,MODEL,SERIAL,WWN
/dev/sd[hijkl]
NAME MAJ:MIN MODEL SERIAL WWN
sdh 8:112 Gigastone SSD GSTD02TB230102
sdi 8:128 Gigastone SSD GST02TBG221146
sdj 8:144 Gigastone SSD GST02TBG221146
sdk 8:160 Gigastone SSD GSTG02TB230206
sdl 8:176 Gigastone SSD GSTG02TB230206
This is just weird.
I still have difficulties to believe that any disk manufacturer would
hand out disks with colliding serial numbers. I googled for this
phenomenon, but except two mails of Gene nothing similar popped up.
One of these mails from a thread in december reveals that the three
unique serial numbers GSTD02TB230102, GST02TBG221146, GSTG02TB230206
each come with a different version of "1C0", "7A0", "5A0", respectively.
Which is why, when I let my imagination out to play w/o a chaperone, my
thoughts run toward some invented date code for a batch number.
https://www.mail-archive.com/debian-user@lists.debian.org/msg799307.html
That's unexpected, too, as the disk properties look identical elsewise.
I guess that it is not possible to identify which disk came with which
of the two separate purchases ?
Once removed from the boxes, no.
How many days were these purchases apart ?
6 weeks or so, as I formulated what to do next. But that isn't carved
even in sandstone.
David Christensen wrote:
I suggest removing one GST02TBG221146 and one GSTG02TB230206. Put them on
the shelf, in other computer(s), or sell them. Then perhaps copying the
/home RAID10 2 TB to one Gigastone 2 TB SSD would work.
I join this proposal.
... and dimly remember to have seen the proposal to attach the disks
one by one without the other four, in order to see whether the serial
numbers are the same as with all five together.
Not as easily tried, the other 4 are in twin mounts in another portion
of the drive cages in this 30" tall tiger direct cage and not too
readily accessible w/o tipping the mobo out on its hinged mount.
Since you got quite some hardware zoo:
Consider to try the Gigastone disks with a different machine.
Do the serial numbers show up as with the machine where you experience
all those difficulties.
Again, that has not been tried.
Have a nice day :)
Thomas
Back at you Tomas, thanks for your patience to you, Felix and David &
pocket. One of you made the remark that seems to be the secret password.
Its still, slowly at 10 megs a second, working. And I appreciate it, a lot.
Cheers, Gene Heskett.
--
"There are four boxes to be used in defense of liberty:
soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author, 1940)
If we desire respect for the law, we must first make the law respectable.
- Louis D. Brandeis
