Bug 421801

Summary:	Disk partitioning tool does not properly recognize bootable OS/2 JFS (type 07)
Product:	[openSUSE] openSUSE 11.0	Reporter:	Lewis Rosenthal <lgrosenthal>
Component:	YaST2	Assignee:	E-mail List <yast2-maintainers>
Status:	RESOLVED FIXED	QA Contact:	Jiri Srain <jsrain>
Severity:	Enhancement
Priority:	P4 - Low	CC:	ancor, aschnell, mrmazda
Version:	Final
Target Milestone:	Future/Later
Hardware:	PC
OS:	openSUSE 11.0
Whiteboard:
Found By:	Customer	Services Priority:
Business Priority:		Blocker:	---
Marketing QA Status:	---	IT Deployment:	---
Attachments:	YaST2 installation log from openSUSE 11.0

Description Lewis Rosenthal 2008-08-31 03:59:11 UTC

OS/2 (now eComStation) has had support for bootable JFS volumes for some time. Unfortunately, the partition type for bootable JFS is the same as for HPFS and NTFS, specifically, 07. The partitioner sees a type 07 partition and assumes it to be HPFS/NTFS, and inserts the incorrect fs data into /etc/fstab.

Manually editing fstab to change the type to jfs results in the partition being properly mountable, however, many OS/2 users are not Linux experts, and expect the installer to handle this properly.

Suggest partitioner be modified to examine the filesystem type (as it does for type 83) to determine whether it is indeed an OS/2 bootable JFS partition, and label it accordingly.

Comment 1 Felix Miata 2008-09-15 22:50:03 UTC

It does the wrong thing with type 0x07 formatted as HPFS as well, even though it predates NTFS by several years. This is the fstab entry I typically create for HPFS partitions:

/dev/hda1 /hpfs/C hpfs noauto,users,noexec,umask=0,case=asis 0 0

Comment 2 Lewis Rosenthal 2008-09-16 02:34:59 UTC

Thanks for the clarification, Felix. I did indeed confirm your data (by looking again to refresh my recollection). For some reason, it just lumps 07 as "HPFS/NTFS" in the partitioner gui.

Comment 3 Arvin Schnell 2008-09-22 14:01:02 UTC

Please provide logs of an installation where this problem occurs.

Comment 4 Felix Miata 2008-09-25 13:45:42 UTC

I never use JFS, but can probably find a log set for HPFS if that will help. I have probably 8-10 11.0 & Factory installs coexisting with HPFS. It's been a while since a fresh install, and I won't be doing one before the dust settles on the Factory mirror restructuring.

Comment 5 Lewis Rosenthal 2008-09-27 05:47:37 UTC

Created attachment 242097 [details]
YaST2 installation log from openSUSE 11.0

Note that /dev/hda6 is the OS/2 bootable JFS partition (type 07) and /dev/hda14 is the openSUSE JFS partition.

Comment 6 Arvin Schnell 2009-01-20 19:53:56 UTC

This is a non-trivial feature request. So far I didn't have time to look
at it and since OS/2 is not a major OS anymore I consider the request as
not important. If you disagree with that please open a entry in openFATE,
see:

http://news.opensuse.org/2009/01/16/opensuse-project-opens-feature-tracking-with-openfate/

Comment 7 Lewis Rosenthal 2019-09-16 18:33:50 UTC

In 15.x, type 07 partitions are shown as NTFS and the filesystem is properly identified (which is absurd: partition type NTFS, formatted JFS or HPFS).

ArcaOS is a current, shipping OS/2 distribution, and this issue persists, misidentifying bootable partitions.

Comment 8 Ancor Gonzalez Sosa 2019-09-17 09:27:56 UTC

(In reply to Lewis Rosenthal from comment #7)
> In 15.x, type 07 partitions are shown as NTFS and the filesystem is properly
> identified (which is absurd: partition type NTFS, formatted JFS or HPFS).

Why is that absurd? If I got your comments, the partitioner tells you the partition id is NTFS (which is how most tools call the id 07) and the filesystem inside the partition is JFS. That's exactly the situation you described, isn't it?

Anyway, we recently changed how the type column is displayed (already available in Tumbleweed and coming in Leap 15.2). See https://lizards.opensuse.org/2019/06/25/yast-sprints-77-79/

If I'm not wrong, in your case that new version will omit the partition id and simply display "JFS Partition".

Comment 9 Lewis Rosenthal 2019-09-17 20:09:32 UTC

If it simply says JFS Partition, then that's fine.

The absurdity is the nomenclature. A type 07 partition is not an NTFS partition, any more than a type 83 is an EXT partition. There simply is no good name for a type 07 other tha, well, "type 07" (unfortunately, as we don't have anything as descriptive as "Linux Native").

Thanks for the pointer to the upcoming Tumbleweed change (I haven't booted my Tumbleweed in some time; now I can see just how long that's been, apparently).

While I'm not altogether sold on removing the partition type column, it's less distracting than having it show me an incorrect partition type name with a conflicting filesystem next to it.