b***@baden.nu
2019-06-02 01:11:12 UTC
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
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