Results 1 to 7 of 7

Thread: Yast not displaying volume label - LVM data created by OS/2

  1. #1
    Join Date
    Jan 2018
    Location
    Annandale, VA
    Posts
    234

    Default Yast not displaying volume label - LVM data created by OS/2

    I have a desktop with LVM partition information and multiple FAT and JFS partitions. I installed openSUSE LEAP 42.3 and the Yast partitioner displayed ^A instead of the volume labels for the JFS logical drives. It correctly displayed the FAT logical drives. The Linux system is currently inaccessible due to other reasons, but I noticed that the volume labels all contain space, period or underscore - could that be the source of the problem? If not, do you have any other suggestions?

    Code:
    Creating new log  : 'F:\TOOLS\DFSEE\log\partitions.log' (7-bit ASCII)
    Working directory : F:\TOOLS\DFSEE\BIN
         Registration : DFSee 12.x reg-nr for 'neil@blondeguy.com': 3780563177
         RgKey status : This is a permanent key for 12.x, it will not expire.
    ReadWrite Store A : PhysDisk : 1 PartId 00 = --    mode=FDISK     140118-194400
    RC:0      <Enter> : 00000000 u=00000000 x=00000000 this=00000000  Base=00000000
    ____________________________________________________________________________________ 2
    ____________________________________________________________________________________ 1
    DFSee  invocation : F:\TOOLS\DFSEE\BIN\DFSOS2.EXE
    Working directory : F:\TOOLS\DFSEE\BIN
         Registration : DFSee 12.x reg-nr for 'neil@blondeguy.com': 3780563177
         RgKey status : This is a permanent key for 12.x, it will not expire.
         UI TxWindows : 2.71 03-04-2015 (c) 1995-2015: Fsys Software
         OS   version : OS/2       4.50     Internal : 20.45 on drive F:
    ____________________________________________________________________________________ 1
    DFSee OS/2   12.4 : Executing: map -M -m
    Command timestamp : Sunday 2018-01-14 19:44:01
    Disk  DFSee  Disk   Image filename or
     id   type    nr    (Unix) device, and optional partitionable media description
    ====  =====  ====   ===========================================================
      1   Phys     1    /dev/hda          Physical disk  1 
      2   Phys     2    /dev/hdb          Physical disk  2 
      3   Phys     3    /dev/hdc          Physical disk  3 
      4   Phys     4    /dev/hdd          Physical disk  4 
      5   Phys     5    /dev/hde          Physical disk  5 
      6   Phys     6    /dev/hdf          Physical disk  6 
      7   Phys     7    /dev/hdg          Physical disk  7 
      8   Phys     8    /dev/hdh          Physical disk  8 
      9   Phys     9    /dev/hdi          Physical disk  9 
    Number of disks   : 9
    
     P-Geo Disk 1 Cyl :     0 H:  0 S:0   Bps:512   Size : 0x111F83A0 =  140272 MiB
     Disk 1 L-Geo from: LVM info at PSN 0x0000003e ACCEPTED as matching DLAT sector
     L-Geo Disk 1 Cyl : 17882 H:255 S:63  Bps:512   Size : 0x111F755A =  140270 MiB
     BIOS Int13 limit : 1024, I13X support needed beyond : 8032.5 MiB
     MBR crc 6794972f : 0x56647a5d = Martin Kiewitz AirBoot bootmanager, I13X
     L-Geo Disk 2 Cyl :   512 H: 12 S:32  Bps:512   Size : 0x00030000 =    96.0 MiB
    DUMMY, disk 2 seems reserved with no media present (USB/PCCARD etc)
     L-Geo Disk 3 Cyl :   512 H: 12 S:32  Bps:512   Size : 0x00030000 =    96.0 MiB
    DUMMY, disk 3 seems reserved with no media present (USB/PCCARD etc)
     L-Geo Disk 4 Cyl :   512 H: 12 S:32  Bps:512   Size : 0x00030000 =    96.0 MiB
    DUMMY, disk 4 seems reserved with no media present (USB/PCCARD etc)
     L-Geo Disk 5 Cyl :   512 H: 12 S:32  Bps:512   Size : 0x00030000 =    96.0 MiB
    DUMMY, disk 5 seems reserved with no media present (USB/PCCARD etc)
     L-Geo Disk 6 Cyl :   512 H: 12 S:32  Bps:512   Size : 0x00030000 =    96.0 MiB
    DUMMY, disk 6 seems reserved with no media present (USB/PCCARD etc)
     L-Geo Disk 7 Cyl :   512 H: 12 S:32  Bps:512   Size : 0x00030000 =    96.0 MiB
    DUMMY, disk 7 seems reserved with no media present (USB/PCCARD etc)
     L-Geo Disk 8 Cyl :   512 H: 12 S:32  Bps:512   Size : 0x00030000 =    96.0 MiB
    DUMMY, disk 8 seems reserved with no media present (USB/PCCARD etc)
     L-Geo Disk 9 Cyl :   512 H: 12 S:32  Bps:512   Size : 0x00030000 =    96.0 MiB
    DUMMY, disk 9 seems reserved with no media present (USB/PCCARD etc)
    +-<MBR disk  1>--</dev/hda>--<[ D1 ]>--------------------------------------------------------------+
    | |+==++==++==+===============================================================================|   ||
    | ||  ||  ||  |+--++--++--++--++--+|   |+--++--++--++--++--+|   |+--++--+|   |+--++--++--++--+|   ||
    |m||1 ||2 ||3 ||4 ||5 ||6 ||7 ||8 ||9  ||9 ||10||11||12||13||14 ||14||15||16 ||16||17||18||19||20 ||
    |b||  ||  ||C:||D:||E:||F:||G:||Ho||   ||Q:||U:||  ||HO||N:||   ||W:||P:||   ||I:||  ||  ||  ||   ||
    |r||BM||EX||FA||FA||JF||JF||JF||JF||Fre||HP||HP||JF||JF||JF||Fre||JF||FA||Fre||HP||HP||EX||EX||Par||
    | ||  ||  ||  |+--++--++--++--++--+|ace|+--++--++--++--++--+|ace|+--++--+|ace|+--++--++--++--+|l C||
    | |+==++==++==+===============================================================================|lin||
    +--------------------------------------------------------------------------------------------------+
    ____________________________________________________________________________________ 1
    DFSee OS/2   12.4 : Executing: fdisk -r-
    Command timestamp : Sunday 2018-01-14 19:44:02
    %20.20sOr recreate it completely with DFSee (CR in recovery mode).
    Partition is of LVM type 0x35, has LVM-information  (DLAT),
     Pid08=Ho warning : but lacks the LVM-signature sector with LVM-features (BBR).
                        Volume needs to be recreated using the regular LVM program!
                        Use the 'create from existing partition' selection there,
     Pid08=Ho WARNING : Partition bootsector is a match to MULTIPLE driveletters! This
                        could be caused by imaging or cloning. You can make it unique
                        by opening the partition and updating the volume serial-number:
                        Mode=xxx ->Boot area fixes/updates ->Set Volume Serial Number
                        where 'xxx' is the filesystem on the partition (FAT, HPFS etc).
     Pid12=HO WARNING : Partition bootsector is a match to MULTIPLE driveletters!
    +---+--+-----------------+--+--------+--------+-----------+--------------+---------+
    |ID |Dr|Type, description|ux|Format  |Related |VolumeLabel|LVM Vol,Part /| Size MiB|
    +--<MBR disk  1></dev/hda    >-------+--------+----------<[ D1 ]          >--------+
    |01 |  |Prim 0a IBM-BMGR | 3|BMGR    |LVM     |I13Xneeded |, [ BOOT MANAG|      7.8|
    |02*|  |Prim 83 LinuxNatv| 2|EXT3    |GRUB    |SUSEboot   |Linux  /boot, |     23.5|
    |03>|C:|Prim 06 FAT16    | 1|FAT16   |FRDOS4.1|DOSBOOT    |DOS boot, DOS |     54.9|
    |04 |D:|Log  06 FAT16    | 5|FAT     |IBM 4.50|DOSDATA    |DOS Data, DOS |    101.9|
    |05*|E:|Log  07 Inst-FSys| 6|JFS     |IBM 4.50|ECS 2_1 BOO|eCS 2.1 boot, |   4102.5|
    |06 |F:|Log  07 Inst-FSys| 7|JFS     |IBM 4.50|ECS 2_2 BET|eCS 2.2 beta, |   4110.4|
    |07 |G:|Log  07 Inst-FSys| 8|JFS     |IBM 4.50|Arca 5.0.1 |ArcaOS 5.0.1, |   4102.5|
    |08 |Ho|Log  35 Warp-LVM | 9|JFS     |IBM 4.50|USER DATA 1|User Data 01, |   4102.5|
    |09 |  |FreeSpace Logical|  |-- -- --|-- -- --|- - - - - -|              |   2157.2|
    |09*|Q:|Log  07 Inst-FSys|10|HPFS    |IBM 4.50|ECS 2_0 GA |eCS 2.0 GA, eC|   2055.2|
    |10 |U:|Log  35 Warp-LVM |11|HPFS    |IBM 4.50|SMEDLEY    |Man,  Smedley |   5145.8|
    |11 |  |Log  35 Warp-LVM |12|JFS     |IBM 4.50|Manuals    |Manuals, Manua|   8197.2|
    |12 |HO|Log  35 Warp-LVM |13|JFS     |IBM 4.50|USER DATA 1|userdata01, us|   4102.5|
    |13 |N:|Log  35 Warp-LVM |14|JFS     |IBM 4.50|MANUALS    |Manuals 16gB, |  16386.6|
    |14 |  |FreeSpace Logical|  |-- -- --|-- -- --|- - - - - -|              |  36436.5|
    |14 |W:|Log  35 Warp-LVM |15|JFS     |IBM 4.50|Work Space |Work space, [P|  16386.6|
    |15 |P:|Log  06 FAT16    |16|FAT     |IBM 4.50|SADUMP     |post mortem, p|   2047.3|
    |16 |  |FreeSpace Logical|  |-- -- --|-- -- --|- - - - - -|              |   2055.2|
    |16 |I:|Log  35 Warp-LVM |17|HPFS    |IBM 4.50|COMM       |eCS data for C|   4102.5|
    |17 |  |Log  07 Inst-FSys|18|HPFS    |IBM 4.50|SMEDLEY    |Old Smedley Bu|   2055.2|
    |18 |  |Log  83 LinuxNatv|19|EXT3    |Linux   |SUSE10.3   |OpenSUSE 10.3 |  20481.3|
    |19 |  |Log  83 LinuxNatv|20|EXT3    |Linux   |SUSEhome   |/home, OpenSUS|   2055.2|
    |20 |  |Partial Cylinder |  |-- -- --|-- -- --|- - - - - -|              |      1.8|
    +---+--+-----------------+--+--------+--------+-----------+--------------+---------+
       > = Active/Startable * = Bootable r = Removable R = Removable+Active/Bootable (possibly)
    ____________________________________________________________________________________ 1
    DFSee OS/2   12.4 : Executing: disk 1
    Command timestamp : Sunday 2018-01-14 19:44:12
     L-Geo Disk 1 Cyl : 17882 H:255 S:63  Bps:512   Size : 0x111F755A =  140270 MiB
    CRC=50adf076; LSN : 0x00000000 = Master   Boot Rec Cyl    0 H:  0 S: 1 00000000
    MBR crc  6794972f : 0x56647a5d = Martin Kiewitz AirBoot bootmanager, I13X
    Offset   Fl|BeginCHS|Tp| EndCHS | BR-offset  |sectors     [Partition Table ]
            +==+--------+==+--------+------------+-----------+
    -001BE-  80 00 01 04 06 fe 3f 0a  04 fb 00 00 47 b7 01 00 [......?.....G...]
    -001CE-  00 00 01 01 83 fe 3f 03  c1 3e 00 00 43 bc 00 00 [......?..>..C...]
    -001DE-  00 01 01 00 0a fe 3f 00  3f 00 00 00 82 3e 00 00 [......?.?....>..]
    -001EE-  00 00 01 0b 0f fe ff ff  4b b2 02 00 0f c3 1c 11 [........K.......]
            +==+--------+==+--------+------------+-----------+
    Partition index 0 : Type 0x06  = FAT16     <--------- Active/Startable PID : 03
     LBA offset value : 0x0000FB04   Sectors : 0x0001B747 =    54.9 MiB
     Begin sector PSN : 0x0000FB04 = Cyl:    4 H:  0 S: 1
     End sector   PSN : 0x0002B24A = Cyl:   10 H:254 S:63
    Partition index 1 : Type 0x83  = LinuxNatv                             PID : 02
     LBA offset value : 0x00003EC1   Sectors : 0x0000BC43 =    23.5 MiB
     Begin sector PSN : 0x00003EC1 = Cyl:    1 H:  0 S: 1
     End sector   PSN : 0x0000FB03 = Cyl:    3 H:254 S:63
    Partition index 2 : Type 0x0a  = IBM-BMGR                              PID : 01
     LBA offset value : 0x0000003F   Sectors : 0x00003E82 =     7.8 MiB
     Begin sector PSN : 0x0000003F = Cyl:    0 H:  1 S: 1
     End sector   PSN : 0x00003EC0 = Cyl:    0 H:254 S:63
    Partition index 3 : Type 0x0f  = ExtendBig                             PID : 04
     LBA offset value : 0x0002B24B   Sectors : 0x111CC30F =  140184 MiB
     Begin sector PSN : 0x0002B24B = Cyl:   11 H:  0 S: 1
     End sector   PSN : 0x111F7559 = Cyl:17881 H:254 S:63 CHS C:1023 H:254 S:63 
    ReadWrite Store A : PhysDisk : 1 PartId 00 = --    mode=FDISK     140118-194412
    RC:0      <Enter> : 0002B24B u=0000003F x=0000003E this=00000000  Base=00000000
    ____________________________________________________________________________________ 1
    DFSee OS/2   12.4 : Executing: dfsdisk 1 -!
    Command timestamp : Sunday 2018-01-14 19:45:06
    DFSee OS/2   12.4 : Executing: dfsdisk 1 -b:"F:\TOOLS\DFSEE\log\DFSDISKo" -s:ANY BOTH 
    Command timestamp : Sunday 2018-01-14 19:45:18
    Closing logfile   : 'F:\TOOLS\DFSEE\log\partitions.log'
    Appending to log  : 'F:\TOOLS\DFSEE\log\partitions.log' (7-bit ASCII)
    DFSDISK procedure : finished for disk: 1

  2. #2
    Join Date
    Jun 2008
    Location
    Netherlands
    Posts
    29,740

    Default Re: Yast not displaying volume label - LVM data created by OS/2

    Volume labels are a feature of file systems. Every type of file system has it's own way to implement it (or not). It may be that YaST hasn't enough knowledge of JFS find the label.

    BTW I do not understand much of your listing.
    Last edited by hcvv; 02-Mar-2018 at 01:46.
    Henk van Velden

  3. #3
    Join Date
    Sep 2012
    Posts
    7,094

    Default Re: Yast not displaying volume label - LVM data created by OS/2

    Quote Originally Posted by shmuelmetz View Post
    If not, do you have any other suggestions?
    It is not clear what your question is. Do you have any actual problems accessing JFS partitions? Or is it just cosmetic display issue?

    If you are really concerned, you will need to debug where the problem comes from - is it YaST or more low level issue. Do JFS tools on Linux show correct label (like "jfs_tune -l"? Does "blkid" show correct label? Does udev database contain correct label? Once you found what tool makes mistake you can consider reporting it as appropriate.

  4. #4
    Join Date
    Jan 2018
    Location
    Annandale, VA
    Posts
    234

    Default Re: Yast not displaying volume label - LVM data created by OS/2

    Quote Originally Posted by arvidjaar View Post
    It is not clear what your question is. Do you have any actual problems accessing JFS partitions? Or is it just cosmetic display issue?

    If you are really concerned, you will need to debug where the problem comes from - is it YaST or more low level issue. Do JFS tools on Linux show correct label (like "jfs_tune -l"? Does "blkid" show correct label? Does udev database contain correct label? Once you found what tool makes mistake you can consider reporting it as appropriate.
    I wouldn't consider it cosmetic, since the volume display in dolphin doesn't identify which is which, but I can access the volumes. I believe that the problem is that dolphin only looks at the file system label and not at the partition label. If I add a file system label, dolphin displays it.

    Note: All of my OS/2 volumes are JFS; I assume that the issue actually applies to other file systems as well.

  5. #5
    Join Date
    Jun 2008
    Location
    Netherlands
    Posts
    29,740

    Default Re: Yast not displaying volume label - LVM data created by OS/2

    Did this ever work for you?

    I ask because normal MS-DOS partitions do not have labels. Thus I am not sure that other containers (like the LVs you talk about) which (according to you) have them, are implemented in Dolphin (which is about file system, the contents, and not about partitions/volumes)
    Henk van Velden

  6. #6
    Join Date
    Sep 2012
    Posts
    7,094

    Default Re: Yast not displaying volume label - LVM data created by OS/2

    Quote Originally Posted by shmuelmetz View Post
    I believe that the problem is that dolphin only looks at the file system label and not at the partition label.
    There is no such thing as "partition label" in MBR style partitions. What you mean is likely OS/2 LVM volume name. This information is located outside of partitions in (E)MBR gap space which is normally unused. The only Linux tool that made use of it was EVMS but this project is dead long ago. In Linux today "label" always refers to filesystem label on this partition. I do not think any program expects anything else. Dolphin itself does not do anything - it simply gets information from lower level tools. It may be possible to write a program that scans disk for LVM DLAT and overrides filesystem label with LVM volume name during device detection. But providing support for both filesystem label and volume name would require changing every program that works with and presents disk information; not something that is likely to happen for rather niche use case.

  7. #7
    Join Date
    Jun 2008
    Location
    Netherlands
    Posts
    29,740

    Default Re: Yast not displaying volume label - LVM data created by OS/2

    Quote Originally Posted by arvidjaar View Post
    There is no such thing as "partition label" in MBR style partitions. What you mean is likely OS/2 LVM volume name. This information is located outside of partitions in (E)MBR gap space which is normally unused. The only Linux tool that made use of it was EVMS but this project is dead long ago. In Linux today "label" always refers to filesystem label on this partition. I do not think any program expects anything else. Dolphin itself does not do anything - it simply gets information from lower level tools. It may be possible to write a program that scans disk for LVM DLAT and overrides filesystem label with LVM volume name during device detection. But providing support for both filesystem label and volume name would require changing every program that works with and presents disk information; not something that is likely to happen for rather niche use case.
    Thanks for confirming very clear what I was thinking.
    Henk van Velden

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •