pinxi/inxi beta testers? 3.2.0 -L / -R LVM, RAID rewrite, etc

Forum Forums General Software pinxi/inxi beta testers? 3.2.0 -L / -R LVM, RAID rewrite, etc

Tagged: , , , ,

  • This topic has 5 replies, 3 voices, and was last updated Dec 11-12:51 am by Anonymous.
Viewing 6 posts - 1 through 6 (of 6 total)
  • Author
    Posts
  • #46816
    Member
    h2

      Hi antiX’ers, you have new forums!! I did not know that until tonight, nice.

      Note that besides the new features and redone raid, everything internally in pinxi has been altered pretty much, so if you can find any bugs or things that seem wrong, that would be great too!! Thanks.

      pinxi is at an advanced stage now, the oldest issues and glitches are now being taken care of, a large internal refactor, many new small features and fixes.

      If you have pinxi already, then just do: pinxi -U

      to install it: cd /usr/local/bin && sudo wget -O pinxi smxi.org/pinxi && chmod +x pinxi

      The new option is -L, for –logical, it was going to be –lvm but then I realized there were other types of logical block devices.

      To get -L able to function, I had to rewrite RAID -R, which now also supports LVM RAID. -D Local Storage totals now take RAID into account, and will modify the reported totals and uses, with raw: …. usable: used and also for LVM, an lvm-free: item with -x which shows how much unassigned LVM space there is.

      Note that the test vm has a bunch of disks, many volume groups, logical volumes, lvm raid, mdraid.. and of course, lvm on mdraid.

      It does not have all the variants possible since there are too many, which is why feedback would be appreciated.

      Note that I have on my todo list bcache support, but I am getting a bit burned on this, so figured, let’s see if the basic stuff is working for most people before it gets extended.

      Let me know if there is anything you think is missing or should be added, LVM uses lvs to get the data, which a specially constructed option list, so it it can be added that way, I can extend stuff, but not a lot more.

      This is in pinxi current, not in inxi, inxi and pinxi right now are about as far apart from eachother as they have been since pinxi perl was born, I’d say 10-15% of the internal logic has been refactored or optimized or enhanced or restructured.

      # pinxi -LRDy
      Logical:
        VG-1: vg0 type: lvm2 size: 49.99 GiB free: 23.99 GiB 
        LV-1: flac type: linear size: 15 GiB devices: 1: sdb 2: sdc 
        LV-2: mp3 type: linear size: 6 GiB devices: 1: sdb 
        LV-3: opus type: linear size: 5 GiB devices: 1: sdb 
        VG-2: vg1 type: lvm2 size: 24.41 GiB free: 14.64 GiB 
        LV-1: lvm_raid1 type: raid1 size: 4.88 GiB components: c-1: dm-10 c-2: dm-11 
        c-3: dm-13 c-4: dm-15 
        VG-3: vg2 type: lvm2 size: 24.98 GiB free: 4.98 GiB 
        LV-1: data1 type: linear size: 5 GiB devices: 1: md0 
        LV-2: data2 type: linear size: 5 GiB devices: 1: md0 
        LV-3: data3 type: linear size: 5 GiB devices: 1: md0 
        LV-4: data4 type: linear size: 5 GiB devices: 1: md0 
        VG-4: vg3 type: lvm2 size: 38.37 GiB free: 26.36 GiB 
        LV-1: lvm_raid5 type: raid5 size: 8 GiB components: c-1: dm-12 c-2: dm-5 
        c-3: dm-6 c-4: dm-7 c-5: dm-8 c-6: dm-9 
        VG-5: vg4 type: lvm2 size: 24.41 GiB free: 14.64 GiB 
        LV-1: thin_mirror0 type: raid1 size: 4.88 GiB components: c-1: dm-21 
        c-2: dm-22 c-3: dm-23 c-4: dm-24 
        Crypto-1: LUKS id: luks-a00baac5-44ff-4b48-b303-3bedb1f623ce size: 4.26 GiB 
        devices: 1: sda2 
        Crypto-2: LUKS id: luks-3342c0fb-1868-4ee4-84bd-4f77278cdb61 size: 35.91 GiB 
        devices: 1: sda1 
      RAID:
        Device-1: lvm_raid1 type: lvm2 level: mirror size: 4.88 GiB sync: idle 
        Components: Online: 1: dm-11 2: dm-15 Meta: 1: dm-10 2: dm-13 
        Device-2: lvm_raid5 type: lvm2 level: raid-5 size: 8 GiB sync: idle 
        Components: Online: 1: dm-12 2: dm-6 3: dm-8 Meta: 1: dm-5 2: dm-7 3: dm-9 
        Device-3: thin_mirror0 type: lvm2 level: mirror size: 4.88 GiB sync: idle 
        Components: Online: 1: dm-22 2: dm-24 Meta: 1: dm-21 2: dm-23 
        Device-4: md0 type: mdraid level: mirror status: active size: 24.98 GiB 
        report: 2/2 UU 
        Components: Online: 0: sdf 1: sdg Spare: 2: sdi 
      Drives:
        Local Storage: total: raw: 340.19 GiB usable: 276.38 GiB 
        used: 8.49 GiB (3.1%) 
        ID-1: /dev/sda vendor: VirtualBox model: VBOX HARDDISK size: 40.19 GiB 
        ID-2: /dev/sdb vendor: VirtualBox model: VBOX HARDDISK size: 25 GiB 
        ID-3: /dev/sdc vendor: VirtualBox model: VBOX HARDDISK size: 25 GiB 
        ID-4: /dev/sdd vendor: VirtualBox model: VBOX HARDDISK size: 25 GiB 
        ID-5: /dev/sde vendor: VirtualBox model: VBOX HARDDISK size: 25 GiB 
        ID-6: /dev/sdf vendor: VirtualBox model: VBOX HARDDISK size: 25 GiB 
        ID-7: /dev/sdg vendor: VirtualBox model: VBOX HARDDISK size: 25 GiB 
        ID-8: /dev/sdh vendor: VirtualBox model: VBOX HARDDISK size: 25 GiB 
        ID-9: /dev/sdi vendor: VirtualBox model: VBOX HARDDISK size: 25 GiB 
        ID-10: /dev/sdj vendor: VirtualBox model: VBOX HARDDISK size: 25 GiB 
        ID-11: /dev/sdk vendor: VirtualBox model: VBOX HARDDISK size: 25 GiB 
        ID-12: /dev/sdl vendor: VirtualBox model: VBOX HARDDISK size: 25 GiB 
        ID-13: /dev/sdm vendor: VirtualBox model: VBOX HARDDISK size: 25 GiB 
      ## And the full, --admin level RAID and Logical report.
      # pinxi -LRDay
      Logical:
        VG-1: vg0 type: lvm2 size: 49.99 GiB free: 23.99 GiB 
        LV-1: flac type: linear maj-min: 254:2 dm: dm-2 size: 15 GiB 
        devices: 1: sdb maj-min: 8:16 size: 25 GiB 2: sdc maj-min: 8:32 size: 25 GiB 
        LV-2: mp3 type: linear maj-min: 254:4 dm: dm-4 size: 6 GiB 
        devices: 1: sdb maj-min: 8:16 size: 25 GiB 
        LV-3: opus type: linear maj-min: 254:3 dm: dm-3 size: 5 GiB 
        devices: 1: sdb maj-min: 8:16 size: 25 GiB 
        VG-2: vg1 type: lvm2 size: 24.41 GiB free: 14.64 GiB 
        LV-1: [lvm_raid1_rimage_0] type: linear maj-min: 254:11 dm: dm-11 
        size: 4.88 GiB 
        devices: 1: sdd1 maj-min: 8:49 size: 12.21 GiB 
        LV-2: [lvm_raid1_rimage_1] type: linear maj-min: 254:15 dm: dm-15 
        size: 4.88 GiB 
        devices: 1: sde1 maj-min: 8:65 size: 12.21 GiB 
        LV-3: [lvm_raid1_rmeta_0] type: linear maj-min: 254:10 dm: dm-10 size: 4 MiB 
        devices: 1: sdd1 maj-min: 8:49 size: 12.21 GiB 
        LV-4: [lvm_raid1_rmeta_1] type: linear maj-min: 254:13 dm: dm-13 size: 4 MiB 
        devices: 1: sde1 maj-min: 8:65 size: 12.21 GiB 
        LV-5: lvm_raid1 type: raid1 maj-min: 254:16 dm: dm-16 size: 4.88 GiB 
        components: 
        c-1: dm-10 maj-min: 254:10 size: 4 MiB dev: d-1: sdd1 maj-min: 8:49 
        size: 12.21 GiB 
        c-2: dm-11 maj-min: 254:11 size: 4.88 GiB dev: d-1: sdd1 maj-min: 8:49 
        size: 12.21 GiB 
        c-3: dm-13 maj-min: 254:13 size: 4 MiB dev: d-1: sde1 maj-min: 8:65 
        size: 12.21 GiB 
        c-4: dm-15 maj-min: 254:15 size: 4.88 GiB dev: d-1: sde1 maj-min: 8:65 
        size: 12.21 GiB 
        VG-3: vg2 type: lvm2 size: 24.98 GiB free: 4.98 GiB 
        LV-1: data1 type: linear maj-min: 254:17 dm: dm-17 size: 5 GiB 
        devices: 1: md0 maj-min: 9:0 size: 24.98 GiB 
        LV-2: data2 type: linear maj-min: 254:18 dm: dm-18 size: 5 GiB 
        devices: 1: md0 maj-min: 9:0 size: 24.98 GiB 
        LV-3: data3 type: linear maj-min: 254:19 dm: dm-19 size: 5 GiB 
        devices: 1: md0 maj-min: 9:0 size: 24.98 GiB 
        LV-4: data4 type: linear maj-min: 254:20 dm: dm-20 size: 5 GiB 
        devices: 1: md0 maj-min: 9:0 size: 24.98 GiB 
        VG-4: vg3 type: lvm2 size: 38.37 GiB free: 26.36 GiB 
        LV-1: [lvm_raid5_rimage_0] type: linear maj-min: 254:6 dm: dm-6 size: 4 GiB 
        devices: 1: sdd2 maj-min: 8:50 size: 12.79 GiB 
        LV-2: [lvm_raid5_rimage_1] type: linear maj-min: 254:8 dm: dm-8 size: 4 GiB 
        devices: 1: sde2 maj-min: 8:66 size: 12.79 GiB 
        LV-3: [lvm_raid5_rimage_2] type: linear maj-min: 254:12 dm: dm-12 
        size: 4 GiB 
        devices: 1: sdh2 maj-min: 8:114 size: 12.79 GiB 
        LV-4: [lvm_raid5_rmeta_0] type: linear maj-min: 254:5 dm: dm-5 size: 4 MiB 
        devices: 1: sdd2 maj-min: 8:50 size: 12.79 GiB 
        LV-5: [lvm_raid5_rmeta_1] type: linear maj-min: 254:7 dm: dm-7 size: 4 MiB 
        devices: 1: sde2 maj-min: 8:66 size: 12.79 GiB 
        LV-6: [lvm_raid5_rmeta_2] type: linear maj-min: 254:9 dm: dm-9 size: 4 MiB 
        devices: 1: sdh2 maj-min: 8:114 size: 12.79 GiB 
        LV-7: lvm_raid5 type: raid5 maj-min: 254:14 dm: dm-14 size: 8 GiB 
        components: 
        c-1: dm-12 maj-min: 254:12 size: 4 GiB dev: d-1: sdh2 maj-min: 8:114 
        size: 12.79 GiB 
        c-2: dm-5 maj-min: 254:5 size: 4 MiB dev: d-1: sdd2 maj-min: 8:50 
        size: 12.79 GiB 
        c-3: dm-6 maj-min: 254:6 size: 4 GiB dev: d-1: sdd2 maj-min: 8:50 
        size: 12.79 GiB 
        c-4: dm-7 maj-min: 254:7 size: 4 MiB dev: d-1: sde2 maj-min: 8:66 
        size: 12.79 GiB 
        c-5: dm-8 maj-min: 254:8 size: 4 GiB dev: d-1: sde2 maj-min: 8:66 
        size: 12.79 GiB 
        c-6: dm-9 maj-min: 254:9 size: 4 MiB dev: d-1: sdh2 maj-min: 8:114 
        size: 12.79 GiB 
        VG-5: vg4 type: lvm2 size: 24.41 GiB free: 14.64 GiB 
        LV-1: [thin_mirror0_rimage_0] type: linear maj-min: 254:22 dm: dm-22 
        size: 4.88 GiB 
        devices: 1: sdh1 maj-min: 8:113 size: 12.21 GiB 
        LV-2: [thin_mirror0_rimage_1] type: linear maj-min: 254:24 dm: dm-24 
        size: 4.88 GiB 
        devices: 1: sdj1 maj-min: 8:145 size: 12.21 GiB 
        LV-3: [thin_mirror0_rmeta_0] type: linear maj-min: 254:21 dm: dm-21 
        size: 4 MiB 
        devices: 1: sdh1 maj-min: 8:113 size: 12.21 GiB 
        LV-4: [thin_mirror0_rmeta_1] type: linear maj-min: 254:23 dm: dm-23 
        size: 4 MiB 
        devices: 1: sdj1 maj-min: 8:145 size: 12.21 GiB 
        LV-5: thin_mirror0 type: raid1 maj-min: 254:25 dm: dm-25 size: 4.88 GiB 
        components: 
        c-1: dm-21 maj-min: 254:21 size: 4 MiB dev: d-1: sdh1 maj-min: 8:113 
        size: 12.21 GiB 
        c-2: dm-22 maj-min: 254:22 size: 4.88 GiB dev: d-1: sdh1 maj-min: 8:113 
        size: 12.21 GiB 
        c-3: dm-23 maj-min: 254:23 size: 4 MiB dev: d-1: sdj1 maj-min: 8:145 
        size: 12.21 GiB 
        c-4: dm-24 maj-min: 254:24 size: 4.88 GiB dev: d-1: sdj1 maj-min: 8:145 
        size: 12.21 GiB 
        Crypto-1: LUKS id: luks-a00baac5-44ff-4b48-b303-3bedb1f623ce maj-min: 254:1 
        dm: dm-1 size: 4.26 GiB 
        devices: 1: sda2 maj-min: 8:2 size: 4.26 GiB 
        Crypto-2: LUKS id: luks-3342c0fb-1868-4ee4-84bd-4f77278cdb61 maj-min: 254:0 
        dm: dm-0 size: 35.91 GiB 
        devices: 1: sda1 maj-min: 8:1 size: 35.92 GiB 
      RAID:
        Device-1: lvm_raid1 maj-min: 254:16 type: lvm2 level: mirror size: 4.88 GiB 
        sync: idle 
        Info: stripes: 2 mismatches: 0 copied: 100% v-group: vg1 vg-size: 24.41 GiB 
        vg-free: 14.64 GiB 
        Components: Online: 
        1: dm-11 maj-min: 254:11 size: 4.88 GiB mapped: vg1-lvm_raid1_rimage_0 
        dev: sdd1 
        2: dm-15 maj-min: 254:15 size: 4.88 GiB mapped: vg1-lvm_raid1_rimage_1 
        dev: sde1 
        Meta: 
        1: dm-10 maj-min: 254:10 size: 4 MiB mapped: vg1-lvm_raid1_rmeta_0 dev: sdd1 
        2: dm-13 maj-min: 254:13 size: 4 MiB mapped: vg1-lvm_raid1_rmeta_1 dev: sde1 
        Device-2: lvm_raid5 maj-min: 254:14 type: lvm2 level: raid-5 size: 8 GiB 
        sync: idle 
        Info: stripes: 3 mismatches: 0 copied: 100% v-group: vg3 vg-size: 38.37 GiB 
        vg-free: 26.36 GiB 
        Components: Online: 
        1: dm-12 maj-min: 254:12 size: 4 GiB mapped: vg3-lvm_raid5_rimage_2 
        dev: sdh2 
        2: dm-6 maj-min: 254:6 size: 4 GiB mapped: vg3-lvm_raid5_rimage_0 dev: sdd2 
        3: dm-8 maj-min: 254:8 size: 4 GiB mapped: vg3-lvm_raid5_rimage_1 dev: sde2 
        Meta: 
        1: dm-5 maj-min: 254:5 size: 4 MiB mapped: vg3-lvm_raid5_rmeta_0 dev: sdd2 
        2: dm-7 maj-min: 254:7 size: 4 MiB mapped: vg3-lvm_raid5_rmeta_1 dev: sde2 
        3: dm-9 maj-min: 254:9 size: 4 MiB mapped: vg3-lvm_raid5_rmeta_2 dev: sdh2 
        Device-3: thin_mirror0 maj-min: 254:25 type: lvm2 level: mirror 
        size: 4.88 GiB sync: idle 
        Info: stripes: 2 mismatches: 0 copied: 100% v-group: vg4 vg-size: 24.41 GiB 
        vg-free: 14.64 GiB 
        Components: Online: 
        1: dm-22 maj-min: 254:22 size: 4.88 GiB mapped: vg4-thin_mirror0_rimage_0 
        dev: sdh1 
        2: dm-24 maj-min: 254:24 size: 4.88 GiB mapped: vg4-thin_mirror0_rimage_1 
        dev: sdj1 
        Meta: 
        1: dm-21 maj-min: 254:21 size: 4 MiB mapped: vg4-thin_mirror0_rmeta_0 
        dev: sdh1 
        2: dm-23 maj-min: 254:23 size: 4 MiB mapped: vg4-thin_mirror0_rmeta_1 
        dev: sdj1 
        System supports mdraid: raid1 raid6 raid5 raid4 
        Device-4: md0 maj-min: 9:0 type: mdraid level: mirror status: active 
        state: clean size: 24.98 GiB 
        Info: report: 2/2 UU blocks: 26196992 chunk size: N/A super blocks: 1.2 
        Components: Online: 
        0: sdf maj-min: 8:80 size: 25 GiB state: active sync 
        1: sdg maj-min: 8:96 size: 25 GiB state: active sync 
        Spare: 
        2: sdi maj-min: 8:128 size: 25 GiB state: spare 
      Drives:
        Local Storage: total: raw: 340.19 GiB usable: 276.38 GiB lvm-free: 84.61 GiB 
        used: 8.49 GiB (3.1%) 
        ID-1: /dev/sda maj-min: 8:0 vendor: VirtualBox model: VBOX HARDDISK 
        size: 40.19 GiB block size: physical: 512 B logical: 512 B speed: 3.0 Gb/s 
        serial: VBd3607451-41a541bd rev: 1.0 
        SMART: no 
        ID-2: /dev/sdb maj-min: 8:16 vendor: VirtualBox model: VBOX HARDDISK 
        size: 25 GiB block size: physical: 512 B logical: 512 B speed: 3.0 Gb/s 
        serial: VBb5407051-c69764d7 rev: 1.0 
        SMART: no 
        ID-3: /dev/sdc maj-min: 8:32 vendor: VirtualBox model: VBOX HARDDISK 
        size: 25 GiB block size: physical: 512 B logical: 512 B speed: 3.0 Gb/s 
        serial: VBc4b6b2f6-4eb40f0f rev: 1.0 
        SMART: no 
        ID-4: /dev/sdd maj-min: 8:48 vendor: VirtualBox model: VBOX HARDDISK 
        size: 25 GiB block size: physical: 512 B logical: 512 B speed: 3.0 Gb/s 
        serial: VB8d5f7ac2-dfdff49c rev: 1.0 
        SMART: no 
        ID-5: /dev/sde maj-min: 8:64 vendor: VirtualBox model: VBOX HARDDISK 
        size: 25 GiB block size: physical: 512 B logical: 512 B speed: 3.0 Gb/s 
        serial: VBde128404-98e24d6f rev: 1.0 
        SMART: no 
        ID-6: /dev/sdf maj-min: 8:80 vendor: VirtualBox model: VBOX HARDDISK 
        size: 25 GiB block size: physical: 512 B logical: 512 B speed: 3.0 Gb/s 
        serial: VBbeae7bc0-99a26ed8 rev: 1.0 
        SMART: no 
        ID-7: /dev/sdg maj-min: 8:96 vendor: VirtualBox model: VBOX HARDDISK 
        size: 25 GiB block size: physical: 512 B logical: 512 B speed: 3.0 Gb/s 
        serial: VBbd6c1deb-58016f41 rev: 1.0 
        SMART: no 
        ID-8: /dev/sdh maj-min: 8:112 vendor: VirtualBox model: VBOX HARDDISK 
        size: 25 GiB block size: physical: 512 B logical: 512 B speed: 3.0 Gb/s 
        serial: VBb4535226-dd865fc8 rev: 1.0 
        SMART: no 
        ID-9: /dev/sdi maj-min: 8:128 vendor: VirtualBox model: VBOX HARDDISK 
        size: 25 GiB block size: physical: 512 B logical: 512 B speed: 3.0 Gb/s 
        serial: VBf19cf218-38c5f705 rev: 1.0 
        SMART: no 
        ID-10: /dev/sdj maj-min: 8:144 vendor: VirtualBox model: VBOX HARDDISK 
        size: 25 GiB block size: physical: 512 B logical: 512 B speed: 3.0 Gb/s 
        serial: VB6ba6751b-ab1b1795 rev: 1.0 
        SMART: no 
        ID-11: /dev/sdk maj-min: 8:160 vendor: VirtualBox model: VBOX HARDDISK 
        size: 25 GiB block size: physical: 512 B logical: 512 B speed: 3.0 Gb/s 
        serial: VB864d77ae-b60876e6 rev: 1.0 
        SMART: no 
        ID-12: /dev/sdl maj-min: 8:176 vendor: VirtualBox model: VBOX HARDDISK 
        size: 25 GiB block size: physical: 512 B logical: 512 B speed: 3.0 Gb/s 
        serial: VBbdcf5f67-52d5d0eb rev: 1.0 
        SMART: no 
        ID-13: /dev/sdm maj-min: 8:192 vendor: VirtualBox model: VBOX HARDDISK 
        size: 25 GiB block size: physical: 512 B logical: 512 B speed: 3.0 Gb/s 
        serial: VBef5e7de6-368cd338 rev: 1.0 
        SMART: no
      • This topic was modified 3 years, 5 months ago by anticapitalista. Reason: fixed code tags
      • This topic was modified 3 years, 5 months ago by h2.
      #46876
      Moderator
      Brian Masinick

        h2, great to hear from you again!

        Not long ago I mentioned you and your excellent work.

        Glad to see there are more developments and I look forward to using them!
        —Brian

        --
        Brian Masinick

        #46930
        Member
        h2

          If you can test pinxi that helps, with this big of a rewrite, even though I’ve tested on all my available systems, those are just the ones that I have access too, and it’s possible undefined data alerts occur, though they are now less likely than before.

          Errors look mostly like this: a perl warning that on a specific line undefined value was used, or, a field is empty of its value, that one is harder to spot since there is no error, it means a test for null or empty data did not happen when it needed to happen, then show N/A.

          Best tests are: pinxi; pinxi -b, pinxi -F, pinxi -v8, with and without sudo for each one. There’s a lot of internal interlinking of data, and it’s hard to get it all working consistently, easy to overlook possible situations.

          Right now I’m debating whether or not to make a truly recursive, that is, go in as many levels as exist, component -> device generator for these things, I have max 2 levels coded in, but in weird cases, there can be more, like physical > lvm > mdraid > luks > lvm, or various bcache options, it’s all lunacy, but it’s technically possible to do it, but hard to code it.

          • This reply was modified 3 years, 5 months ago by h2.
          • This reply was modified 3 years, 5 months ago by h2.
          #46975
          Anonymous

            hi h2,

            On sid/bullseye pinxi worked great on my tower with no errors.
            and sudo shows serial numbers where regular user doesn’t.
            great program to get a lot of system info quickly.

            #47048
            Member
            h2

              Good to hear. Found a few more subtle bugs when I made my logical volume test setup even more absurd, that exposed some issues that have been around for a long time, subtle, for unmounted drives for example.

              I’ve changed Logical to use the same syntax and layout as RAID, since they are really closely related cousins, both use Device-xx: for primary row id, then use type to define what type of logical or raid it is.

              I’ve also expanded possible logical device types to include some fallbacks and generic categories.

              If you aren’t clear, I wasn’t really, a logical block device is one that is made up out of either a physical or a logical device. The numbers of daisy chained logical devices can get kind of crazy/insane, that’s how I found some more subtle bugs in pinxi, these are also in inxi.

              The last step which I don’t know if I will do because it’s hard and confusing is to use recursive data structures, dynamic, for logical components, the goal being to always end up on physical devices at the end, but in particular the output part of that is really difficult given how pinxi wants its output indentations to work, so I may or may not expand and rewrite those parts, right now it only goes back max 2 levels, which covers many to most user logical volume situations, but it fails to cover things like a luks on a logical volume that contains logical volumes in the luks top layer, and other complicated scenarios. It will currently let you track down these elements in the logical report since all the logical devices are listed, but it’s not as elegant as it could be per device.

              #47052
              Anonymous

                ok to clarify …. this was on physical drives not logical running
                the
                Best tests are: pinxi; pinxi -b, pinxi -F, pinxi -v8, with and without sudo for each one.
                tests and all is good.

              Viewing 6 posts - 1 through 6 (of 6 total)
              • You must be logged in to reply to this topic.