• SSD, LVM, and USB

    From tholen@antispam.ham@21:1/5 to All on Sat Mar 23 00:01:15 2019
    It's been a while since I've used LVM, so maybe I've forgotten how
    something was done previously.

    I've got a 2 TB SSD that I want to connect to my OS/2 system via
    a USB port. I created a single 2 TB LVM volume and then tried to
    format it with JFS, but the formatting program refused to do so,
    claiming that it had to be an LVM volume, which seemed odd because
    I had created an LVM volume. So I went back into LVM, and it
    reported it as a compatibility volume. Deleted that volume and
    started over, making absolutely certain that I selected an LVM
    volume. Same problem. Format refused because it had to be an LVM
    volume, and going back into LVM, it was reported as a compatibility
    volume.

    Turns out the only way I could coax LVM into creating an LVM volume
    was to create a logical partition rather than a primary partition.
    Of course, that left about 31 MB of the capacity unused, a small
    annoyance considering the size of the drive.

    Now, I have other 2 TB spinning disks that I've connected to my
    OS/2 system via a USB port, and LVM reports them as having a
    primary partition and JFS, so it must be possible to create an LVM
    volume on a 2 TB primary partition. But I couldn't do it with
    this particular SSD. Is there something about an SSD that gives
    LVM problems with primary partitions?

    Issue #2

    All the above was done on one OS/2 system, which happily recognized
    the SSD whenever I plugged it into the USB port. When I tried to
    use the same SSD on a different OS/2 system, the machine totally
    ignored it. My first thought was that I didn't have the
    REMOVABLES option set high enough in the CONFIG.SYS BASEDEV=USBMSD.ADD
    option, but I checked it, and it was indeed high enough. I verified
    that I could plug in a memory key and it was recognized by the system.
    Removed the memory key, plugged in the SSD, but it was ignored. So
    I tried ejecting one of the spinning disks and then reattaching it,
    which worked fine. Tried the SSD again, but it was ignored. I did
    this over a dozen times, and the SSD was ignored every time. I even
    tried closing some programs, thinking that maybe there wasn't enough
    free memory to deal with the SSD, but no joy.

    Some days later, I was ready to reboot the computer and try plugging
    in the SSD on a freshly booted system, but I decided to try one last
    time before rebooting. Plugged in the SSD, and it was recognized, at
    last!

    Any ideas why the behavior would be so inconsistent?

    Issue #3

    The spinning USB drive has data transfer rates about 6 times FASTER
    than the SSD. I know that OS/2's USB drivers aren't the greatest
    when it comes to speed, but one might expect an SSD to perform at
    least as fast as a spinning disk. I tried a much smaller 120 GB SSD
    on the first OS/2 system and got transfer rates as fast as a spinning
    disk, so an SSD is at least capable of performing decently with OS/2's
    USB drivers.

    Specifics: Warp 4.52 system, problematic SSD is a Samsung T5, which
    came preformatted with the exFAT file system (and not NTFS, which
    surprised me).

    Anybody know enough about the low-level characteristics to explain
    what is happening with LVM, drive recognition, and transfer speeds?

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Herbert Rosenau@21:1/5 to All on Sat Mar 23 16:08:38 2019
    Am 23.03.19 um 01:01 schrieb tholen@antispam.ham:
    It's been a while since I've used LVM, so maybe I've forgotten how
    something was done previously.

    I've got a 2 TB SSD that I want to connect to my OS/2 system via
    a USB port. I created a single 2 TB LVM volume and then tried to
    format it with JFS, but the formatting program refused to do so,
    claiming that it had to be an LVM volume, which seemed odd because
    I had created an LVM volume. So I went back into LVM, and it
    reported it as a compatibility volume. Deleted that volume and
    started over, making absolutely certain that I selected an LVM
    volume. Same problem. Format refused because it had to be an LVM
    volume, and going back into LVM, it was reported as a compatibility
    volume.


    create at lest 1 partition on that drive. You can do that in physical
    vie. You gives each partrition a drive name like C: or D: ....

    When you have created any psrtition (logical drive you goes back to
    logical view. There you can compound multiple drives together (it's an
    option!) together to a logical LVM drive. A LVM drive is 1 single OR
    componded partitions.You MUST split a physical drive into one or more
    physical partition(s). You can't use the plain physical drive. The
    compunded logical drives can spawned over partitions on multiple
    physical drives together to a single logical drive.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Grant Taylor@21:1/5 to tholen@antispam.ham on Sat Mar 23 10:42:28 2019
    On 3/23/19 at 01:01 AM, tholen@antispam.ham wrote:
    I've got a 2 TB SSD that I want to connect to my OS/2 system via a
    USB port.

    How does OS/2 handle partitions that are too big for MBR partition
    schemes? (I thought that was the 2 TB mark.)



    --
    Grant. . . .
    unix || die

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Marcel Mueller@21:1/5 to All on Sat Mar 23 18:54:20 2019
    Am 23.03.19 um 17:42 schrieb Grant Taylor:
    On 3/23/19 at 01:01 AM, tholen@antispam.ham wrote:
    I've got a 2 TB SSD that I want to connect to my OS/2 system via a USB
    port.

    How does OS/2 handle partitions that are too big for MBR partition
    schemes?  (I thought that was the 2 TB mark.)

    Probably not at all. The maximum partition size is 2TB.


    Marcel

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Dave Yeo@21:1/5 to Grant Taylor on Sat Mar 23 12:18:19 2019
    Grant Taylor wrote:
    On 3/23/19 at 01:01 AM, tholen@antispam.ham wrote:
    I've got a 2 TB SSD that I want to connect to my OS/2 system via a USB
    port.

    How does OS/2 handle partitions that are too big for MBR partition
    schemes? (I thought that was the 2 TB mark.)

    2TBs or so is the current limit for OS/2 and that takes some
    non-standard CHS values. I think you have to basically delete the MBR
    and start anew. Also due to having to align the partitions on cylinder boundaries, there's almost always going to be a small amount of wastage. Another important thing with many modern drives and all SSDs is to set
    things up so the JFS blocks of 4kb line up with the internal 4kb
    sectors. This is important both for speed and wear, when writing (or
    reading) a block, should only write (read) one sector.
    I forget the math.

    Dave

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Dave Yeo@21:1/5 to Marcel Mueller on Sat Mar 23 12:20:46 2019
    Marcel Mueller wrote:
    Am 23.03.19 um 17:42 schrieb Grant Taylor:
    On 3/23/19 at 01:01 AM, tholen@antispam.ham wrote:
    I've got a 2 TB SSD that I want to connect to my OS/2 system via a
    USB port.

    How does OS/2 handle partitions that are too big for MBR partition
    schemes? (I thought that was the 2 TB mark.)

    Probably not at all. The maximum partition size is 2TB.

    There are plans to add a filter driver to split large drives into 2TB
    units, so a 4TB drive would show as 2 drives. Still have the 2TB
    partition limit but I guess you could combine the partitions into one
    large volume.
    Dave

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Grant Taylor@21:1/5 to Dave Yeo on Sat Mar 23 15:51:15 2019
    On 3/23/19 1:18 PM, Dave Yeo wrote:
    2TBs or so is the current limit for OS/2 and that takes some
    non-standard CHS values. I think you have to basically delete the MBR
    and start anew. Also due to having to align the partitions on cylinder boundaries, there's almost always going to be a small amount of wastage. Another important thing with many modern drives and all SSDs is to set
    things up so the JFS blocks of 4kb line up with the internal 4kb
    sectors. This is important both for speed and wear, when writing (or
    reading) a block, should only write (read) one sector.
    I forget the math.

    ACK

    This all makes sense and jives with what I'm aware of for other more
    modern partitioning schemes and file systems on SSDs.

    Thank you Dave for the confirmation that it is possible to do such with
    OS/2 JFS.



    --
    Grant. . . .
    unix || die

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)