From Newsgroup: comp.os.os2.misc

It appears that the ArcaOS JFS driver is trapping on
my system.
Background:
=============
I have a T60, which had a 512 GB Crucial SSD (2014),
that bricked in December after some partitioning
efforts. I replaced that with a 512 GB spinning
Toshiba and (almost) identical partition setup. I
recently received a new Crucial 512 GB SSD, and when I
was transferring files, I had some write problems, and
then it continually trapped ('e' & '8' mostly in
OS2KRNL) while I was attempting to restore a 450 GB
partition. After some more errors, I determined the
SSD had write errors, and I returned and replaced it
with a Samsung 860 Pro. I partitioned that the same,
but surprisingly, it also trapped while restoring files
on the large partition.
The 454 GB partition kept trapping at 89 GB written.
I changed the partition size to different values, and
smaller partitions would allow more writing. Finally,
at a 300 GB size, I could fill the partition without
trapping. I thought it was a SSD unique problem, until
afterwards I checked the Toshiba, which I had earlier
only filled with about 50 GB onto the large partition.
That drive also trapped at about 100 GB filled.
My system is partitioned with a HPFS C: franken
OS/2 installation, which has much eCS. It ran for ten
years without issues, originally on 512 GB spinning
rust, and the last 4.5 years on a 512 GB SSD. D: Drive
is a minimal HPFS maintenance partition, and E: Drive
is JFS ArcaOS 5.0 (was eCS). roiroCroCroCroCroCroCroCroCroCroCroCroCroCroCroCroCroCroCroCroCroCroCroCroCroCroCroCroCroCroCroCroCroCroCroCroCroCroCroCroCroCroCroCroCroCroCroCroCroCroCroCroCroCroCroCroCroCroCroCroCroCroCroCroCroCroCroCroCroCroCroCroCroCroCroCroCroCroCroE
roe Logical Volume Type Status File System Size (MB)roe
roLroCroCroCroCroCroCroCroCroCroCroCroCroCroCroCroCroCroCroCroCroCroCroCroCroCroCroCroCroCroCroCroCroCroCroCroCroCroCroCroCroCroCroCroCroCroCroCroCroCroCroCroCroCroCroCroCroCroCroCroCroCroCroCroCroCroCroCroCroCroCroCroCroCroCroCroCroCroCron
roeOS2 C: Compatibility Startable HPFS 502 roe
roeMaint D: Compatibility HPFS 15 roe
roeArcaOS E: Compatibility JFS 1027 roe
roeData F: LVM JFS 32002 roe
roeFotos G: LVM JFS 454830 roe
rooroCroCroCroCroCroCroCroCroCroCroCroCroCroCroCroCroCroCroCroCroCroCroCroCroCroCroCroCroCroCroCroCroCroCroCroCroCroCroCroCroCroCroCroCroCroCroCroCroCroCroCroCroCroCroCroCroCroCroCroCroCroCroCroCroCroCroCroCroCroCroCroCroCroCroCroCroCroCroy
Determination:
=============
This trap problem only started in May after I tried
restoring a large partition using ArcaOS 5.0 on SSDs.
Both the old OS (eCS) and ArcaOS trapped, and the old
OS2 mostly predates ArcaOS. I first contemplated and
checked whether heat, 'lvm' or 'format were
responsible. I further investigated, and found that
both OS use the newer JFS files, as I had installed the
"JFS - Journaled File System for OS/2 v1.09.07"
package.
44251 0 0 2016-10-24 09:48 OS2/CACHEJFS.EXE
280192 0 0 2017-01-06 17:47 OS2/DLL/UJFS.DLL
193319 0 0 2016-10-24 09:48 OS2/JFS.IFS
6495 0 0 2016-10-24 09:48 OS2/JFSCHK32.EXE
44949 0 0 2016-10-24 09:48 OS2/jfsstats.exe
I then checked an older backup, and found that the
JFS files were different:
44268 0 0 2010-04-27 12:57 OS2/CACHEJFS.EXE
99061 0 0 2010-04-27 12:57 OS2/CHKLGJFS.EXE
281594 0 0 2010-04-27 12:58 OS2/DLL/UJFS.DLL
193291 0 0 2010-04-27 12:55 OS2/JFS.IFS
6495 0 0 2010-04-27 12:57 OS2/JFSCHK32.EXE
I restored over all the old files, and the system
ran and filled the 450 GB partitions faultlessly on
both the Toshiba and SSD.
Resolution:
=============
It appears that the new ArcaOS JFS faults writing to
large partitions. It may be from a timing issue, as
this problem originally occurred when restoring SSD
drives. It also occurred on the spinning drive, but
the Toshiba did successfully fill 400+ GB one time out
of many traps.
thanks,
Baden
--- Synchronet 3.22a-Linux NewsLink 1.2

From Newsgroup: comp.os.os2.misc

On 06/03/19 03:27 PM, baden@baden.nu wrote:

On Monday, 3 June 2019 10:23:09 UTC-5, Dave Yeo wrote:

On 06/01/19 06:11 PM, baden@baden.nu wrote:

It appears that the ArcaOS JFS driver is trapping on
my system.

You should probably file an issue at the ArcaOS bug tracker, assuming
you still have an active subscription and the latest JFS.
Dave

Hi Dave:

Thanks, ArcaOS does not make it easy to address deficiencies. After purchasing 5.0 & 5.01, and a further subscription, I do not think it should be necessary for me to pay them more money to log issues that caused me considerable inconvenience, time, effort, and money to resolve.

I am hoping that usenet might be monitored by them.

Unluckily, they've stated they don't have time to monitor various places
such as usenet, though you might get lucky.
You don't have the cache maxed out do you?
Dave
--- Synchronet 3.22a-Linux NewsLink 1.2

From Newsgroup: comp.os.os2.misc

On Tuesday, 18 June 2019 at 18:30:59 UTC-5, becky.ku...@gmail.com wrote:

El lunes, 17 de junio de 2019, 23:32:15 (UTC-5), Lars Erdmann escribi||:

On 12.06.19 07.39, Dave Yeo wrote:

On 06/10/19 07:55 PM, becky.ku...@gmail.com wrote:

El martes, 4 de junio de 2019, 1:37:09 (UTC-5), Dave Yeo escribi||:

On 06/03/19 03:27 PM, ba...@baden.nu wrote:

On Monday, 3 June 2019 10:23:09 UTC-5, Dave Yeo wrote:

On 06/01/19 06:11 PM, ba...@baden.nu wrote:

It appears that the ArcaOS JFS driver is trapping on
my system.

Interestingly, the other day, I was downloading files off my camera's >> CF Card onto my SSD, and ... TRAP!

Hi Lars:

So how did you access the CF Card ? Via a USB card reader ?

No, through the PCMCIA slot and drivers.

BASEDEV=PCMCIA.SYS
BASEDEV=SS2TICB.SYS
BASEDEV=AUTODRV2.SYS
DEVICE=C:\OS2\BOOT\PCMSSDIF.SYS
BASEDEV=PCM2ATA.ADD /S:1 /!DM
BASEDEV=OS2PCARD.DMD

After it trapped using the PCMCIA card, I also
'rem'ed those out, tried using SSD to SSD xfer, and it
also trapped with that.

thanks,
Baden

If yes, it's also possible that USBMSD.ADD fails on you.
Given its overall quality, I would not be surprised.
You can give it a try and use the one from my package after you have backed up the existing one (you can keep the rest of the AN USB stack): http://hobbes.nmsu.edu/download/pub/os2/system/drivers/misc/usbdrv227.zip

Make sure you reinstate everything else.

--- Synchronet 3.22a-Linux NewsLink 1.2

From Newsgroup: comp.os.os2.misc

Okay, I *finally* found what caused the traps. I was just reading on os2world how OS2AHCI.ADD is a replacement for the *506* drivers, which I never knew. I looked in my CONFIG.SYS, which had:
BASEDEV=OS2AHCI.ADD
BASEDEV=DANIS506.ADD /!BIOS
BASEDEV=DANIATAP.FLT
I subsequently removed the AHCI driver, and all worked well. I then reinstated it, and removed the DANI drivers, and all worked well. So, with a large (JFS) partition, and both drivers active, the system can trap.
Can someone let Arca know about this?
thanks, Baden
On Saturday, 1 June 2019 at 20:11:12 UTC-5, ba...@baden.nu wrote:

It appears that the ArcaOS JFS driver is trapping on
my system.

Background:
=============

I have a T60, which had a 512 GB Crucial SSD (2014),
that bricked in December after some partitioning
efforts. I replaced that with a 512 GB spinning
Toshiba and (almost) identical partition setup. I
recently received a new Crucial 512 GB SSD, and when I
was transferring files, I had some write problems, and
then it continually trapped ('e' & '8' mostly in
OS2KRNL) while I was attempting to restore a 450 GB
partition. After some more errors, I determined the
SSD had write errors, and I returned and replaced it
with a Samsung 860 Pro. I partitioned that the same,
but surprisingly, it also trapped while restoring files
on the large partition.

The 454 GB partition kept trapping at 89 GB written.
I changed the partition size to different values, and
smaller partitions would allow more writing. Finally,
at a 300 GB size, I could fill the partition without
trapping. I thought it was a SSD unique problem, until
afterwards I checked the Toshiba, which I had earlier
only filled with about 50 GB onto the large partition.
That drive also trapped at about 100 GB filled.

My system is partitioned with a HPFS C: franken
OS/2 installation, which has much eCS. It ran for ten
years without issues, originally on 512 GB spinning
rust, and the last 4.5 years on a 512 GB SSD. D: Drive
is a minimal HPFS maintenance partition, and E: Drive
is JFS ArcaOS 5.0 (was eCS).

roiroCroCroCroCroCroCroCroCroCroCroCroCroCroCroCroCroCroCroCroCroCroCroCroCroCroCroCroCroCroCroCroCroCroCroCroCroCroCroCroCroCroCroCroCroCroCroCroCroCroCroCroCroCroCroCroCroCroCroCroCroCroCroCroCroCroCroCroCroCroCroCroCroCroCroCroCroCroCroE
roe Logical Volume Type Status File System Size (MB)roe roLroCroCroCroCroCroCroCroCroCroCroCroCroCroCroCroCroCroCroCroCroCroCroCroCroCroCroCroCroCroCroCroCroCroCroCroCroCroCroCroCroCroCroCroCroCroCroCroCroCroCroCroCroCroCroCroCroCroCroCroCroCroCroCroCroCroCroCroCroCroCroCroCroCroCroCroCroCroCron
roeOS2 C: Compatibility Startable HPFS 502 roe
roeMaint D: Compatibility HPFS 15 roe
roeArcaOS E: Compatibility JFS 1027 roe
roeData F: LVM JFS 32002 roe
roeFotos G: LVM JFS 454830 roe rooroCroCroCroCroCroCroCroCroCroCroCroCroCroCroCroCroCroCroCroCroCroCroCroCroCroCroCroCroCroCroCroCroCroCroCroCroCroCroCroCroCroCroCroCroCroCroCroCroCroCroCroCroCroCroCroCroCroCroCroCroCroCroCroCroCroCroCroCroCroCroCroCroCroCroCroCroCroCroy

Determination:
=============

This trap problem only started in May after I tried
restoring a large partition using ArcaOS 5.0 on SSDs.
Both the old OS (eCS) and ArcaOS trapped, and the old
OS2 mostly predates ArcaOS. I first contemplated and
checked whether heat, 'lvm' or 'format were
responsible. I further investigated, and found that
both OS use the newer JFS files, as I had installed the
"JFS - Journaled File System for OS/2 v1.09.07"
package.

44251 0 0 2016-10-24 09:48 OS2/CACHEJFS.EXE
280192 0 0 2017-01-06 17:47 OS2/DLL/UJFS.DLL
193319 0 0 2016-10-24 09:48 OS2/JFS.IFS
6495 0 0 2016-10-24 09:48 OS2/JFSCHK32.EXE
44949 0 0 2016-10-24 09:48 OS2/jfsstats.exe

I then checked an older backup, and found that the
JFS files were different:

44268 0 0 2010-04-27 12:57 OS2/CACHEJFS.EXE
99061 0 0 2010-04-27 12:57 OS2/CHKLGJFS.EXE
281594 0 0 2010-04-27 12:58 OS2/DLL/UJFS.DLL
193291 0 0 2010-04-27 12:55 OS2/JFS.IFS
6495 0 0 2010-04-27 12:57 OS2/JFSCHK32.EXE

I restored over all the old files, and the system
ran and filled the 450 GB partitions faultlessly on
both the Toshiba and SSD.

Resolution:
=============

It appears that the new ArcaOS JFS faults writing to
large partitions. It may be from a timing issue, as
this problem originally occurred when restoring SSD
drives. It also occurred on the spinning drive, but
the Toshiba did successfully fill 400+ GB one time out
of many traps.

thanks,
Baden

--- Synchronet 3.22a-Linux NewsLink 1.2

From Newsgroup: comp.os.os2.misc

On Thu, 25 Mar 2021 05:30:34 UTC, "baden.kudrenecky@gmail.com" <baden.kudrenecky@gmail.com> wrote:

Okay, I *finally* found what caused the traps. I was just reading on os2world how OS2AHCI.ADD is a replacement for the *506* drivers, which I never knew.

Not exactly. OS2AHCI.ADD is support for the AHCI feature of SATA. The
Dani drivers are really for IDE drives, but SATA has a feature to
operate in IDE mode. You really do need to READ the documentation.

I looked in my CONFIG.SYS, which had:

BASEDEV=OS2AHCI.ADD
BASEDEV=DANIS506.ADD /!BIOS
BASEDEV=DANIATAP.FLT

I subsequently removed the AHCI driver, and all worked well. I then reinstated it, and removed the DANI drivers, and all worked well. So, with a large (JFS) partition, and both drivers active, the system can trap.

Can someone let Arca know about this?

Why? You are obviously using some ancient version of OS2AHCI, or you
have an invalid configuration. The first driver to load, runs the
device. Any other driver that loads, cannot operate the device, and
doesn't even try (unless you also have some ancient version of the
Dani driver).

IF you can make the latest OS2AHCI driver fail, then YOU need to
report it, along with all of the required support documentation. Look
in the Wiki for instructions on how to properly report a problem.
Nobody else can do it, because we don't have your machine to be able
to produce the supporting documentation.

If you don't have a current subscription, you don't have support.
Bitching about that here isn't going to do anybody any good.

thanks, Baden

On Saturday, 1 June 2019 at 20:11:12 UTC-5, ba...@baden.nu wrote:

It appears that the ArcaOS JFS driver is trapping on
my system.

Background:
=============

I have a T60, which had a 512 GB Crucial SSD (2014),
that bricked in December after some partitioning
efforts. I replaced that with a 512 GB spinning
Toshiba and (almost) identical partition setup. I
recently received a new Crucial 512 GB SSD, and when I
was transferring files, I had some write problems, and
then it continually trapped ('e' & '8' mostly in
OS2KRNL) while I was attempting to restore a 450 GB
partition. After some more errors, I determined the
SSD had write errors, and I returned and replaced it
with a Samsung 860 Pro. I partitioned that the same,
but surprisingly, it also trapped while restoring files
on the large partition.

The 454 GB partition kept trapping at 89 GB written.
I changed the partition size to different values, and
smaller partitions would allow more writing. Finally,
at a 300 GB size, I could fill the partition without
trapping. I thought it was a SSD unique problem, until
afterwards I checked the Toshiba, which I had earlier
only filled with about 50 GB onto the large partition.
That drive also trapped at about 100 GB filled.

My system is partitioned with a HPFS C: franken
OS/2 installation, which has much eCS. It ran for ten
years without issues, originally on 512 GB spinning
rust, and the last 4.5 years on a 512 GB SSD. D: Drive
is a minimal HPFS maintenance partition, and E: Drive
is JFS ArcaOS 5.0 (was eCS).

+------------------------------------------------------------------------------+
| Logical Volume Type Status File System Size (MB)| |------------------------------------------------------------------------------|
|OS2 C: Compatibility Startable HPFS 502 |
|Maint D: Compatibility HPFS 15 |
|ArcaOS E: Compatibility JFS 1027 |
|Data F: LVM JFS 32002 |
|Fotos G: LVM JFS 454830 | +------------------------------------------------------------------------------+

Determination:
=============

This trap problem only started in May after I tried
restoring a large partition using ArcaOS 5.0 on SSDs.
Both the old OS (eCS) and ArcaOS trapped, and the old
OS2 mostly predates ArcaOS. I first contemplated and
checked whether heat, 'lvm' or 'format were
responsible. I further investigated, and found that
both OS use the newer JFS files, as I had installed the
"JFS - Journaled File System for OS/2 v1.09.07"
package.

44251 0 0 2016-10-24 09:48 OS2/CACHEJFS.EXE
280192 0 0 2017-01-06 17:47 OS2/DLL/UJFS.DLL
193319 0 0 2016-10-24 09:48 OS2/JFS.IFS
6495 0 0 2016-10-24 09:48 OS2/JFSCHK32.EXE
44949 0 0 2016-10-24 09:48 OS2/jfsstats.exe

I then checked an older backup, and found that the
JFS files were different:

44268 0 0 2010-04-27 12:57 OS2/CACHEJFS.EXE
99061 0 0 2010-04-27 12:57 OS2/CHKLGJFS.EXE
281594 0 0 2010-04-27 12:58 OS2/DLL/UJFS.DLL
193291 0 0 2010-04-27 12:55 OS2/JFS.IFS
6495 0 0 2010-04-27 12:57 OS2/JFSCHK32.EXE

I restored over all the old files, and the system
ran and filled the 450 GB partitions faultlessly on
both the Toshiba and SSD.

Resolution:
=============

It appears that the new ArcaOS JFS faults writing to
large partitions. It may be from a timing issue, as
this problem originally occurred when restoring SSD
drives. It also occurred on the spinning drive, but
the Toshiba did successfully fill 400+ GB one time out
of many traps.

thanks,
Baden

--
From Doug Bissett's ArcaOS
dougb007 at telus dot net
(Please make the obvious changes, to e-mail me)

--- Synchronet 3.22a-Linux NewsLink 1.2

From Newsgroup: comp.os.os2.misc

On 03/27/21 09:45 PM, baden.kudrenecky@gmail.com wrote:

Hi Doug:

Thank-you very much for your prompt and informative response. I appreciate that someone with strong connections and unfaltering support for ArcaOS still monitors the usenet. Evidently, your technical knowledge, diplomacy, and business acumen might only be surpassed by Lewis Rosenthal in your endless quest for excellence.

There's a couple of us volunteers who monitor the newsgroups. Doug
basically said what I meant to. Note that neither Doug or I can speak
for Arca Noae, just that we have _slightly_ more access to how things go
with Arca Noae.

On Saturday, 27 March 2021 at 11:17:23 UTC-6, Doug Bissett wrote:

On Thu, 25 Mar 2021 05:30:34 UTC, "baden.ku...@gmail.com"
<baden.ku...@gmail.com> wrote:

Okay, I *finally* found what caused the traps. I was just reading on os2world how OS2AHCI.ADD is a replacement for the *506* drivers, which I never knew.

Not exactly. OS2AHCI.ADD is support for the AHCI feature of SATA. The
Dani drivers are really for IDE drives, but SATA has a feature to
operate in IDE mode. You really do need to READ the documentation.

If this is the case, how do both drivers function independently and identically? Would not there be a huge performance difference?

Think of systems that used to be common, a AHCI hard drive plugged into
a SATA port and a IDE DVD drive plugged into a IDE port. My current
computer is the first I've had with no IDE port.
Ideally the AHCI driver loads first and claims the hard drive and then
the S506 driver loads and claims the left overs, namely anything plugged
into the IDE interface, usually a DVD writer, but there has been times I plugged in an old HD.
They should co-operate.

I looked in my CONFIG.SYS, which had:

BASEDEV=OS2AHCI.ADD
BASEDEV=DANIS506.ADD /!BIOS
BASEDEV=DANIATAP.FLT

I subsequently removed the AHCI driver, and all worked well. I then reinstated it, and removed the DANI drivers, and all worked well. So, with a large (JFS) partition, and both drivers active, the system can trap.

Can someone let Arca know about this?

Why? You are obviously using some ancient version of OS2AHCI, or you
have an invalid configuration. The first driver to load, runs the
device. Any other driver that loads, cannot operate the device, and
doesn't even try (unless you also have some ancient version of the
Dani driver).

I wish I knew about this more than I do, but the best obvious information I can provide is:

BldLevel: @#Arca Noae LLC:2.04#@##1## 12 Dec 2017 17:09:14 DAZAR1 ::::::@@AHCI Driver (c) 2017 Arca Noae LLC
CmdLine: OS2AHCI.ADD /N
port #0 interrupt error status: 0x40000001; restarting port
port #0 interrupt error status: 0x40000001; restarting port
Adapter 0: PCI=0:31:2 ID=8086:27c5 Intel ICH7M irq=16 addr=0xee444400 version=10100
Port 0:
Drive 0: 62260 cylinders, 255 heads, 63 sectors per track (488382MB) (LVM)
Model: Samsung SSD 860 PRO 512GB

R1.08.15 /!BIOS
Daniela's Bus Master IDE Driver for OS/2 Version 1.08.15 Controller:0 Port:01F0 IRQ:0E Status:OK BusMaster Scatter/Gather
Intel ICH7 PATA host (8086:27DF rev:02) on PCI 0:31.1#0
Unit:0 Status:OK ATAPI BusMaster UltraDMA2/PIO4
Model:DVD/CDRW UJDA775 CB03
Controller:1 Port:18D0 IRQ:10 Status:OK BusMaster Scatter/Gather
Intel ICH7 SATA host (8086:27C5 rev:02) on PCI 0:31.2#0
Unit:0 Status:OK LBA BusMaster 1.5GBit/s BPB
Model:Samsung SSD 860 PRO 512GB RVM01B6Q
OS2:log phys BPB/BIOS IDE:log phys Total Sectors
C 62260 65535 65535 16383 Avail 1000215216
H 255 16 255 16 16 OS2 1000206900
S 63 63 63 63 63 % Used 99.99

As Doug says, it is old drivers which have likely been fixed. Have to reproduce with the latest.

IF you can make the latest OS2AHCI driver fail, then YOU need to
report it, along with all of the required support documentation. Look
in the Wiki for instructions on how to properly report a problem.
Nobody else can do it, because we don't have your machine to be able
to produce the supporting documentation.

I am amazed that a purported OS vendor does not have test machines, especially a T60 or equivalent, which is one of the few laptops that might operate ArcaOS.

Of course they do. From what I pick up they have quite a few. Lewis
seems to have mostly T42 or T43, Andy (not sure of his involvement) has
a T60, David, who maintains the AHCI driver, seems to have lots of
changing devices, but they seem to be mostly newer as that is the focus.
Us testers can spot problems with older hardware, hopefully.

If you don't have a current subscription, you don't have support.
Bitching about that here isn't going to do anybody any good.

Arca should be enthusiastically receptive to receiving critical bug reports. We (customers) are doing them (vendor) a huge favour. How many customers just dropped the platform altogether after going through a fraction of the grief, time, and expense I did? Having closed subscription based fora (ostrich emulation mode) just exacerbates their hardware compatibility problems.

They have to be bug reports on current drivers, otherwise it is just
wasting developers time to tell you that your bug has been fixed. As
Doug said, make a bug report with current drivers and you will get a
positive response, including a fix most of the time and otherwise a description of why a fix is not possible. I have access to all bug
reports and follow interesting ones, Arca Noae is very good at dealing
with bug reports but they do demand that you run the most recent,
including the debugging tools such as the script to learn about your
system.

As soon as ArcaOS has a viable browser and supports my external 1920 monitor, I will be the first to throw some more money their way.

The proof of concept Simple Browser works surprisingly well, even
gracefully recovering from crashes, with a "this tab crashed, reload?"
type of thing. It is a proof of concept and very simple with no copy and
paste support or even figuring out the URL you are going to without the
whole thing typed in, but looks good remembering it is just a test
program. Bitwise is not doing the port for free and needs money to pay
for their developer, if you can afford to shoot 20+ euros their way, it
would help. Bitwise is not Arca Noae. Use OS2VOICE for donations.
And what is the problem with your 1920 monitor? ArcaOS should support
it. I know my T42 works well when plugging in an external monitor.
Dave
--- Synchronet 3.22a-Linux NewsLink 1.2

From Newsgroup: comp.os.os2.misc

On 03/28/21 09:13 pm, baden.kudrenecky@gmail.com wrote:

I assume that Linux also uses a Panorama base, so the OS/2
functionality shortfall is confusing.

Hardly... Panorama is just a generic VESA driver. The (now ancient)
SNAP Graphics may still work better for you. http://os2news.warpstock.org/ArcaOS.html#VideoCards

--- Synchronet 3.22a-Linux NewsLink 1.2