On 1/16/24 00:56, Felix Miata wrote:
gene heskett composed on 2024-01-15 17:56 (UTC-0500):
Thanks for that composition: but it will be word wrapped:
root@coyote:~# for j in /dev/disk/by-id/* ; do printf '%s\t%s\n'
"$(realpath "$j")" "$j" ; done
/dev/sr0 /dev/disk/by-id/ata-ATAPI_iHAS424_B_3524253_327133504865
/dev/sdi /dev/disk/by-id/ata-Gigastone_SSD_GST02TBG221146
/dev/sdj1 /dev/disk/by-id/ata-Gigastone_SSD_GST02TBG221146-part1
/dev/sdh /dev/disk/by-id/ata-Gigastone_SSD_GSTD02TB230102
/dev/sdh1 /dev/disk/by-id/ata-Gigastone_SSD_GSTD02TB230102-part1
/dev/sdk /dev/disk/by-id/ata-Gigastone_SSD_GSTG02TB230206
/dev/sdk1 /dev/disk/by-id/ata-Gigastone_SSD_GSTG02TB230206-part1
/dev/sdf /dev/disk/by-id/ata-Samsung_SSD_870_EVO_1TB_S626NF0R302498T
/dev/sdf1
/dev/disk/by-id/ata-Samsung_SSD_870_EVO_1TB_S626NF0R302498T-part1
/dev/sdf2
/dev/disk/by-id/ata-Samsung_SSD_870_EVO_1TB_S626NF0R302498T-part2
/dev/sdf3
/dev/disk/by-id/ata-Samsung_SSD_870_EVO_1TB_S626NF0R302498T-part3
/dev/sde /dev/disk/by-id/ata-Samsung_SSD_870_EVO_1TB_S626NF0R302502E
/dev/sde1
/dev/disk/by-id/ata-Samsung_SSD_870_EVO_1TB_S626NF0R302502E-part1
/dev/sde2
/dev/disk/by-id/ata-Samsung_SSD_870_EVO_1TB_S626NF0R302502E-part2
/dev/sde3
/dev/disk/by-id/ata-Samsung_SSD_870_EVO_1TB_S626NF0R302502E-part3
/dev/sdd /dev/disk/by-id/ata-Samsung_SSD_870_EVO_1TB_S626NF0R302507V
/dev/sdd1
/dev/disk/by-id/ata-Samsung_SSD_870_EVO_1TB_S626NF0R302507V-part1
/dev/sdd2
/dev/disk/by-id/ata-Samsung_SSD_870_EVO_1TB_S626NF0R302507V-part2
/dev/sdd3
/dev/disk/by-id/ata-Samsung_SSD_870_EVO_1TB_S626NF0R302507V-part3
/dev/sdg /dev/disk/by-id/ata-Samsung_SSD_870_EVO_1TB_S626NF0R302509W
/dev/sdg1
/dev/disk/by-id/ata-Samsung_SSD_870_EVO_1TB_S626NF0R302509W-part1
/dev/sdg2
/dev/disk/by-id/ata-Samsung_SSD_870_EVO_1TB_S626NF0R302509W-part2
/dev/sdg3
/dev/disk/by-id/ata-Samsung_SSD_870_EVO_1TB_S626NF0R302509W-part3
/dev/sda /dev/disk/by-id/ata-Samsung_SSD_870_QVO_1TB_S5RRNF0T201730V
/dev/sda1
/dev/disk/by-id/ata-Samsung_SSD_870_QVO_1TB_S5RRNF0T201730V-part1
/dev/sda2
/dev/disk/by-id/ata-Samsung_SSD_870_QVO_1TB_S5RRNF0T201730V-part2
/dev/sda3
/dev/disk/by-id/ata-Samsung_SSD_870_QVO_1TB_S5RRNF0T201730V-part3
/dev/md0 /dev/disk/by-id/md-name-coyote:0
/dev/md0p1 /dev/disk/by-id/md-name-coyote:0-part1
/dev/md2 /dev/disk/by-id/md-name-coyote:2
/dev/md1 /dev/disk/by-id/md-name-_none_:1
/dev/md0 /dev/disk/by-id/md-uuid-3d5a3621:c0e32c8a:e3f7ebb3:318edbfb
/dev/md0p1
/dev/disk/by-id/md-uuid-3d5a3621:c0e32c8a:e3f7ebb3:318edbfb-part1
/dev/md1 /dev/disk/by-id/md-uuid-57a88605:27f5a773:5be347c1:7c5e7342
/dev/md2 /dev/disk/by-id/md-uuid-bb6e03ce:19d290c8:5171004f:0127a392
/dev/sdc /dev/disk/by-id/usb-Brother_MFC-J6920DW_BROG5F229909-0:0
/dev/sdb /dev/disk/by-id/usb-USB_Mass_Storage_Device_816820130806-0:0
/dev/sdf /dev/disk/by-id/wwn-0x5002538f413394a5
/dev/sdf1 /dev/disk/by-id/wwn-0x5002538f413394a5-part1
/dev/sdf2 /dev/disk/by-id/wwn-0x5002538f413394a5-part2
/dev/sdf3 /dev/disk/by-id/wwn-0x5002538f413394a5-part3
/dev/sde /dev/disk/by-id/wwn-0x5002538f413394a9
/dev/sde1 /dev/disk/by-id/wwn-0x5002538f413394a9-part1
/dev/sde2 /dev/disk/by-id/wwn-0x5002538f413394a9-part2
/dev/sde3 /dev/disk/by-id/wwn-0x5002538f413394a9-part3
/dev/sdd /dev/disk/by-id/wwn-0x5002538f413394ae
/dev/sdd1 /dev/disk/by-id/wwn-0x5002538f413394ae-part1
/dev/sdd2 /dev/disk/by-id/wwn-0x5002538f413394ae-part2
/dev/sdd3 /dev/disk/by-id/wwn-0x5002538f413394ae-part3
/dev/sdg /dev/disk/by-id/wwn-0x5002538f413394b0
/dev/sdg1 /dev/disk/by-id/wwn-0x5002538f413394b0-part1
/dev/sdg2 /dev/disk/by-id/wwn-0x5002538f413394b0-part2
/dev/sdg3 /dev/disk/by-id/wwn-0x5002538f413394b0-part3
/dev/sda /dev/disk/by-id/wwn-0x5002538f42205e8e
/dev/sda1 /dev/disk/by-id/wwn-0x5002538f42205e8e-part1
/dev/sda2 /dev/disk/by-id/wwn-0x5002538f42205e8e-part2
/dev/sda3 /dev/disk/by-id/wwn-0x5002538f42205e8e-part3
root@coyote:~#
but like I wrote, 2 pairs with identical "serial numbers", so the
assunption is that the last one overwrites the first on by udev, when
IMO it should be yelling about the duplicats.
I straightened out the wrapping mess, and gave each entry a line number. I see
nothing I recognize as representing serial number duplication among /dev/sdX
(physical device) names:
/dev/md0 1 /dev/disk/by-id/md-name-coyote:0
/dev/md0 2 /dev/disk/by-id/md-uuid-3d5a3621:c0e32c8a:e3f7ebb3:318edbfb
/dev/md0p1 3 /dev/disk/by-id/md-name-coyote:0-part1
/dev/md0p1 4
/dev/disk/by-id/md-uuid-3d5a3621:c0e32c8a:e3f7ebb3:318edbfb-part1
/dev/md1 5 /dev/disk/by-id/md-name-_none_:1
/dev/md1 6 /dev/disk/by-id/md-uuid-57a88605:27f5a773:5be347c1:7c5e7342
/dev/md2 7 /dev/disk/by-id/md-name-coyote:2
/dev/md2 8 /dev/disk/by-id/md-uuid-bb6e03ce:19d290c8:5171004f:0127a392
/dev/sda 9 /dev/disk/by-id/ata-Samsung_SSD_870_QVO_1TB_S5RRNF0T201730V
/dev/sda 10 /dev/disk/by-id/wwn-0x5002538f42205e8e
/dev/sda1 11
/dev/disk/by-id/ata-Samsung_SSD_870_QVO_1TB_S5RRNF0T201730V-part1
/dev/sda1 12 /dev/disk/by-id/wwn-0x5002538f42205e8e-part1
/dev/sda2 13
/dev/disk/by-id/ata-Samsung_SSD_870_QVO_1TB_S5RRNF0T201730V-part2
/dev/sda2 14 /dev/disk/by-id/wwn-0x5002538f42205e8e-part2
/dev/sda3 15
/dev/disk/by-id/ata-Samsung_SSD_870_QVO_1TB_S5RRNF0T201730V-part3
/dev/sda3 16 /dev/disk/by-id/wwn-0x5002538f42205e8e-part3
/dev/sdb 17 /dev/disk/by-id/usb-USB_Mass_Storage_Device_816820130806-0:0
/dev/sdc 18 /dev/disk/by-id/usb-Brother_MFC-J6920DW_BROG5F229909-0:0
# How does a printer get a storage device assignment???
/dev/sdd 19 /dev/disk/by-id/ata-Samsung_SSD_870_EVO_1TB_S626NF0R302507V
/dev/sdd 20 /dev/disk/by-id/wwn-0x5002538f413394ae
/dev/sdd1 21
/dev/disk/by-id/ata-Samsung_SSD_870_EVO_1TB_S626NF0R302507V-part1
/dev/sdd1 22 /dev/disk/by-id/wwn-0x5002538f413394ae-part1
/dev/sdd2 23
/dev/disk/by-id/ata-Samsung_SSD_870_EVO_1TB_S626NF0R302507V-part2
/dev/sdd2 24 /dev/disk/by-id/wwn-0x5002538f413394ae-part2
/dev/sdd3 25
/dev/disk/by-id/ata-Samsung_SSD_870_EVO_1TB_S626NF0R302507V-part3
/dev/sdd3 26 /dev/disk/by-id/wwn-0x5002538f413394ae-part3
/dev/sde 27 /dev/disk/by-id/wwn-0x5002538f413394a9
/dev/sde 28 /dev/disk/by-id/ata-Samsung_SSD_870_EVO_1TB_S626NF0R302502E
/dev/sde1 29
/dev/disk/by-id/ata-Samsung_SSD_870_EVO_1TB_S626NF0R302502E-part1
/dev/sde1 30 /dev/disk/by-id/wwn-0x5002538f413394a9-part1
/dev/sde2 31
/dev/disk/by-id/ata-Samsung_SSD_870_EVO_1TB_S626NF0R302502E-part2
/dev/sde2 32 /dev/disk/by-id/wwn-0x5002538f413394a9-part2
/dev/sde3 33
/dev/disk/by-id/ata-Samsung_SSD_870_EVO_1TB_S626NF0R302502E-part3
/dev/sde3 34 /dev/disk/by-id/wwn-0x5002538f413394a9-part3
/dev/sdf 35 /dev/disk/by-id/wwn-0x5002538f413394a5
/dev/sdf 36 /dev/disk/by-id/ata-Samsung_SSD_870_EVO_1TB_S626NF0R302498T
/dev/sdf1 37
/dev/disk/by-id/ata-Samsung_SSD_870_EVO_1TB_S626NF0R302498T-part1
/dev/sdf1 38 /dev/disk/by-id/wwn-0x5002538f413394a5-part1
/dev/sdf2 39
/dev/disk/by-id/ata-Samsung_SSD_870_EVO_1TB_S626NF0R302498T-part2
/dev/sdf2 40 /dev/disk/by-id/wwn-0x5002538f413394a5-part2
/dev/sdf3 41
/dev/disk/by-id/ata-Samsung_SSD_870_EVO_1TB_S626NF0R302498T-part3
/dev/sdf3 42 /dev/disk/by-id/wwn-0x5002538f413394a5-part3
/dev/sdg 43 /dev/disk/by-id/ata-Samsung_SSD_870_EVO_1TB_S626NF0R302509W
/dev/sdg 44 /dev/disk/by-id/wwn-0x5002538f413394b0
/dev/sdg1 45
/dev/disk/by-id/ata-Samsung_SSD_870_EVO_1TB_S626NF0R302509W-part1
/dev/sdg1 46 /dev/disk/by-id/wwn-0x5002538f413394b0-part1
/dev/sdg2 47
/dev/disk/by-id/ata-Samsung_SSD_870_EVO_1TB_S626NF0R302509W-part2
/dev/sdg2 48 /dev/disk/by-id/wwn-0x5002538f413394b0-part2
/dev/sdg3 49
/dev/disk/by-id/ata-Samsung_SSD_870_EVO_1TB_S626NF0R302509W-part3
/dev/sdg3 50 /dev/disk/by-id/wwn-0x5002538f413394b0-part3
/dev/sdh 51 /dev/disk/by-id/ata-Gigastone_SSD_GSTD02TB230102
/dev/sdh1 52 /dev/disk/by-id/ata-Gigastone_SSD_GSTD02TB230102-part1
/dev/sdi 53 /dev/disk/by-id/ata-Gigastone_SSD_GST02TBG221146
/dev/sdj1 54 /dev/disk/by-id/ata-Gigastone_SSD_GST02TBG221146-part1
/dev/sdk 55 /dev/disk/by-id/ata-Gigastone_SSD_GSTG02TB230206
/dev/sdk1 56 /dev/disk/by-id/ata-Gigastone_SSD_GSTG02TB230206-part1
/dev/sr0 57 /dev/disk/by-id/ata-ATAPI_iHAS424_B_3524253_327133504865
Exactly which line numbers represent duplication among the physical drives?
lsblk, which I've published several times, shows 5 drives. by-id listing
only shows 3. The drive I've been trying to use bounces from /dev/sdd to
sde to sdh dependin on which controller it is curently plugged into.
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.
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.
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
