Re: Mounting HPFS partition with SuSE 9.3

PaulRS wrote:
>>>-- I know this is a Linux question, BUT it is also directlly connected
>>>with OS/2 and you OS/2ers may be better equipped to answer . . . .
>>>
>>>-- I have a new install of SuSE 9.3 on a box with OS/2 4.52 also
>>>installed. The OS/2 system uses HPFS (high performance file system).
>>>This is a new system with SATA drives that are approached as SCSI
>>>(sda, sdb).
>>>
>>>(1) I modified FSTAB to see the HPFS partitions
>>> /dev/sda6 /drives/os2 hpfs ro,user,noauto 00
>>>
>>>(2) When I try to mount them I get:
>>> (a) wrong fs type, bad option, bad superblock, missing code page
>>>or other error
>>
>> It looks like you're mounting the wrong partition. The super block is
>>at a fixed offset from a partitions' start. If you're mounting the
>>proper partition, it should find the super block, and then the other
>>file system structures.
>>
>>
>>> (b) dmesg | tail READS
>>> hpfs: unsupported module tainting kernel
>>> HPFS: filesystem error: dir band size mismatch:
>>>dir_band_start==00177ff4, dir_band_end==00000000,
>>>n_dir_band==0017be83; already mounted read-only
>>>
>>>Booting to OS2 works fine. Also, other HPFS partition on this box get
>>>the same messages
>>
>> If booting OS/2 works, then the file system is ok, so all you need is
>>make sure the driver finds the superblock.
>
>
> The same thing happens with every HPFS partition including a SCSI -
> Zip100. A FAT-16 disk is seen fine, but not a HPFS disk. Under the
> OS/2 boot all partitions are seen and written to just fine.

As I stated earlier, it looks like all the errors you are getting
come from it not being able to locate the superblock (which is a trivial
thing to do). As far as I can tell, either you are specifying the wrong
partition (unlikely, since you have tried with multiple devices, and
since FAT works), or there's a problem with the driver (more likely).

Do you happen to know where the source to the hpfs driver is located?
(a CVS online browser would be great).

My theories:
1) The driver is simply broken:
- due to some special configuration you have (oddball geometry which
the driver dislikes?)
- due to recent changes in the kernel
2) Dark Magic (have you annoyed any evil wizards lately?)

Though it could be as simple as some mount piculiarity I don't know
about. For my *nix needs, I mostly use NetBSD myself, so I know little
about Linux quirks.
.

Relevant Pages

  • Installation Woes
    ... have an os/2 system with 3 os/2 operating system partitions, ... my SCSI driver to ... other SCSI drivers, I got past the trap E, ... the existing working partition, while some faster 64 bit processor ...
    (comp.os.os2.setup.misc)
  • Re: Install XP on blank partition on Vista machine
    ... What I have is Vista Home Premium and I'll ... there such a thing as a generic SATA driver and where would I go for it? ... I did notice the initial setup loading various SCSI things but do not ... I have created a blank partition using Paragon Hard Disk Manager, ...
    (microsoft.public.windowsxp.general)
  • Re: Mounting HPFS partition with SuSE 9.3
    ... >> This is a new system with SATA drives that are approached as SCSI ... > It looks like you're mounting the wrong partition. ... The same thing happens with every HPFS partition including a SCSI - ... A FAT-16 disk is seen fine, ...
    (comp.os.os2.misc)
  • FIle corruption on HPFS partition
    ... I have an HPFS partition containing numerous small files (java source files). ... These files are frequently edited and compiled, so there is a lot of file activity on this partition. ... I can manually repair the damaged files and carry on from there successfully... ...
    (comp.os.os2.misc)
  • Re: Boot problem
    ... Unable to Log on if the Boot Partition Drive Letter Has Changed ... How to restore the system/boot drive letter in Windows ... is a small FAT partition and an HPFS partition. ...
    (microsoft.public.win2000.general)