Discussion:
System dump hosed my OS/2 partition: HPFS.IFS unstable ?
(too old to reply)
Lars Erdmann
2007-11-30 23:42:49 UTC
Permalink
Raw Message
Hallo,

using eCS 1.2R, all the latest patches:

I have only one OS/2 partition (as a compatibility volume) which is
formatted with HPFS. Lately, I initiated a system dump (Ctrl-Alt NumLock
NumLock) in order to examine some things.
I know that there is a risk with initiating a system dump but I have done so
a couple of times on my old Warp 4 system which always went ok (I don't
remember if I ran CACHE.EXE /LAZY:OFF every single time I did that in order
to at least keep the file cache out of the game).

But now, for the 2. time in a few months, doing so has completely hosed my
HPFS partition (I know I should have known better and since I am a lazy
person, I don't have a partition image).
CHKDSK ran (which was to be expected) and deleted a whole bunch of broken
files and recovered even more files into the FOUND0 directory (I don't know
from the top of my head but I guess it's about 500 files). At least I am now
able to get to a commandline and restore my private files (as much as
remains from them).
Info: since I have 2 GBs of memory, I have created a > 2GB dump partition at
the very disk end (disk size is 120 GB), formatted with DUMPFS (and replaced
OS2DUMP with the version that comes with DUMPFS) and let TRAPDUMP point to
that partition.

Now I wonder if the HPFS.IFS I have on my system is known to be
buggy/instable. I have this one:

bldlevel: 14.103, 141830 bytes, 2005/1/10

Is this known to be a problematic version of HPFS.IFS ?

P.S.: Guess what, I am writing this from my WinXP installation ...

Thanks for any help or hints,
Lars
Peter Brown
2007-12-01 01:40:59 UTC
Permalink
Raw Message
Hi Lars
Post by Lars Erdmann
Hallo,
I have only one OS/2 partition (as a compatibility volume) which is
formatted with HPFS. Lately, I initiated a system dump (Ctrl-Alt NumLock
NumLock) in order to examine some things.
I know that there is a risk with initiating a system dump but I have done so
a couple of times on my old Warp 4 system which always went ok (I don't
remember if I ran CACHE.EXE /LAZY:OFF every single time I did that in order
to at least keep the file cache out of the game).
But now, for the 2. time in a few months, doing so has completely hosed my
HPFS partition (I know I should have known better and since I am a lazy
person, I don't have a partition image).
You really need to perform the occasional system backup - even if it is
simply an xcopy of all files to a USB drive :-)

I can say this having learnt the hard way myself :-)
Post by Lars Erdmann
CHKDSK ran (which was to be expected) and deleted a whole bunch of broken
files and recovered even more files into the FOUND0 directory (I don't know
from the top of my head but I guess it's about 500 files). At least I am now
able to get to a commandline and restore my private files (as much as
remains from them).
Info: since I have 2 GBs of memory, I have created a > 2GB dump partition at
the very disk end (disk size is 120 GB), formatted with DUMPFS (and replaced
OS2DUMP with the version that comes with DUMPFS) and let TRAPDUMP point to
that partition.
Now I wonder if the HPFS.IFS I have on my system is known to be
bldlevel: 14.103, 141830 bytes, 2005/1/10
Is this known to be a problematic version of HPFS.IFS ?
I hope not - it seems to have been working here fine since installation
over a year ago.

However, I do not have a replacement OS2DUMP on the system and have not
even tried to perform a dump as it has not been necessary.

Maybe there is some sort of bad interaction between hpfs.ifs and the
version of OS2DUMP in use there...

Regards

Pete
Post by Lars Erdmann
P.S.: Guess what, I am writing this from my WinXP installation ...
Thanks for any help or hints,
Lars
scott
2007-12-02 19:28:18 UTC
Permalink
Raw Message
Post by Lars Erdmann
Info: since I have 2 GBs of memory, I have created a > 2GB dump partition at
the very disk end (disk size is 120 GB), formatted with DUMPFS (and replaced
OS2DUMP with the version that comes with DUMPFS) and let TRAPDUMP point to
that partition.
I would guess it to be more likely to be a problem in the dumpfs code
(that I wrote) -- either a flat-out bug or maybe just something about
your particular BIOS or something I didn't know about at the time. I'd
say your're probably SOL, unfortunately.
Post by Lars Erdmann
P.S.: Guess what, I am writing this from my WinXP installation ...
Good idea, though maybe Linux would be more fun (and cheaper).

-Scott
Lars Erdmann
2007-12-02 22:58:54 UTC
Permalink
Raw Message
Hallo Scott,

thanks for the answer. Since I screwed up my partition anyway (and need to
reinstall), I will try if I can get dumping to run without DUMPFS (2 GB is
the borderline for the old OS2DUMP in conjunction with FAT16, correct ?).
Then do a couple of system dumps to see if I end up with the same problem
(BEFORE doing a clean reinstall !).

By the way:
1.) At least with Warp 4, I never managed to make the "old" (SADUMP, FAT16)
dump partition start beyond or cross the 8 GB limit (some BIOS limitation I
vaguely remember). Has this changed with later OS/2, eCS ?
2.) can the dumpfs source code be made public or is it IBM property ? I'd
really like to have a look at it (and maybe add the stuff that is missing:
EA support to keep the WPS happy, for example)
3.) WinXP came with this PC and was "for free" (well not exactly, obviously)
and I am just too damn lazy to learn the Linux/Unix shell commands (and I
use the shell very often: under WinXP, under OS/2). I think I am just
getting too old to learn everything all over again (after all, it's only SW
and computers) ...
Post by scott
Post by Lars Erdmann
Info: since I have 2 GBs of memory, I have created a > 2GB dump partition
at the very disk end (disk size is 120 GB), formatted with DUMPFS (and
replaced OS2DUMP with the version that comes with DUMPFS) and let
TRAPDUMP point to that partition.
I would guess it to be more likely to be a problem in the dumpfs code
(that I wrote) -- either a flat-out bug or maybe just something about your
particular BIOS or something I didn't know about at the time. I'd say
your're probably SOL, unfortunately.
Post by Lars Erdmann
P.S.: Guess what, I am writing this from my WinXP installation ...
Good idea, though maybe Linux would be more fun (and cheaper).
-Scott
scott
2007-12-03 04:47:29 UTC
Permalink
Raw Message
Post by Lars Erdmann
I will try if I can get dumping to run without DUMPFS (2 GB is
the borderline for the old OS2DUMP in conjunction with FAT16, correct ?).
right
Post by Lars Erdmann
1.) At least with Warp 4, I never managed to make the "old" (SADUMP, FAT16)
dump partition start beyond or cross the 8 GB limit (some BIOS limitation I
vaguely remember). Has this changed with later OS/2, eCS ?
Maybe. Probably not. I, too, am getting "fuzzy" on that.
Post by Lars Erdmann
2.) can the dumpfs source code be made public or is it IBM property ?
No, and yes, respectively (they are two very different questions,
actually).
Post by Lars Erdmann
3.) WinXP came with this PC and was "for free" (well not exactly, obviously)
and I am just too damn lazy to learn the Linux/Unix shell commands
Perfectly reasonable. I don't blame you a bit. I happen to have Vista
(ugh!) on this particular computer.
Steven Levine
2007-12-04 02:44:43 UTC
Permalink
Raw Message
In <BTL4j.22561$***@newssvr14.news.prodigy.net>, on 12/03/2007
at 04:47 AM, scott <***@nothing.net> said:

Hi,
Post by scott
Post by Lars Erdmann
1.) At least with Warp 4, I never managed to make the "old" (SADUMP, FAT16)
dump partition start beyond or cross the 8 GB limit (some BIOS limitation I
vaguely remember). Has this changed with later OS/2, eCS ?
Maybe. Probably not. I, too, am getting "fuzzy" on that.
FWIW, you fixed all this up around the time of MCP, along with some LVM
drive letter translation issues. I can't speak to dumpfs, although the
folks I know that are using it haven't complained. However, we are
talking about a small number of users, so who knows.

Steven
--
--------------------------------------------------------------------------------------------
Steven Levine <***@earthlink.bogus.net> MR2/ICE 3.00 beta 09 #10183
eCS/Warp/DIY/14.103a_W4 www.scoug.com irc.ca.webbnet.info #scoug (Wed 7pm PST)
--------------------------------------------------------------------------------------------
PJ
2007-12-05 17:39:40 UTC
Permalink
Raw Message
Do you also have OS/2 on the same disk and manage to boot both OS's from
the BM ? (I've tried but no success so far.)
Peter
Post by scott
Perfectly reasonable. I don't blame you a bit. I happen to have Vista
(ugh!) on this particular computer.
Lars Erdmann
2007-12-06 00:34:15 UTC
Permalink
Raw Message
Post by PJ
Do you also have OS/2 on the same disk and manage to boot both OS's from
the BM ? (I've tried but no success so far.)
Peter
Post by scott
Perfectly reasonable. I don't blame you a bit. I happen to have Vista
(ugh!) on this particular computer.
Yes, no problem. Are you using LVM or the old fdisk ? There were some
issues with the old fdkisk. As far as I remember, you had to delete and
recreate bootmanager after installation of FP15 for Warp 4.

Lars
PJ
2007-12-06 02:50:26 UTC
Permalink
Raw Message
Post by Lars Erdmann
Yes, no problem. Are you using LVM or the old fdisk ? There were some
issues with the old fdkisk. As far as I remember, you had to delete and
recreate bootmanager after installation of FP15 for Warp 4.
Lars
Actually I tried eCS2RC3 and LVM. Vista was preinstalled and I couldn't
boot it after installing eCS and BM.
Peter
Franz Bakan
2007-12-03 20:45:41 UTC
Permalink
Raw Message
On 2007-12-02, Lars Erdmann <***@arcor.de> wrote:
...
Post by Lars Erdmann
1.) At least with Warp 4, I never managed to make the "old" (SADUMP, FAT16)
dump partition start beyond or cross the 8 GB limit (some BIOS limitation I
vaguely remember). Has this changed with later OS/2, eCS ?
here it lives somwhere near the end of a 80GB disk (in a T23)

Franz
Lars Erdmann
2007-12-06 00:36:41 UTC
Permalink
Raw Message
Post by Franz Bakan
...
Post by Lars Erdmann
1.) At least with Warp 4, I never managed to make the "old" (SADUMP, FAT16)
dump partition start beyond or cross the 8 GB limit (some BIOS limitation I
vaguely remember). Has this changed with later OS/2, eCS ?
here it lives somwhere near the end of a 80GB disk (in a T23)
Franz
Yes, but are you running old Warp 4 or eCS ?

Lars
Franz Bakan
2007-12-06 11:21:58 UTC
Permalink
Raw Message
Post by Lars Erdmann
Post by Franz Bakan
Post by Lars Erdmann
1.) At least with Warp 4, I never managed to make the "old" (SADUMP, FAT16)
dump partition start beyond or cross the 8 GB limit (some BIOS limitation I
vaguely remember). Has this changed with later OS/2, eCS ?
here it lives somwhere near the end of a 80GB disk (in a T23)
Franz
Yes, but are you running old Warp 4 or eCS ?
I'm running eCS 1.x

Franz

Loading...