[parisc-linux] Once more: JFS

[Peter Weilbacher]

Hi again,

I gave it a new try with JFS on PA-RISC-Linux. I got kernel
2.4.7-pa2 (linux-20010810.tar.gz) and patched it with JFS 1.0.2.
Cross-compiling the kernel went well, but I had to use the native
PA-RISC-gcc to compile the utilities.

mkfs.jfs now works ok, as opposed to kernel 2.4.0-pa49, and I can
copy files to that partition, but fsck.jfs seems to have problems.
When checking on boot the following messages are written to dmesg:

fsck.jfs(34): unaligned access to 0xfaf0050f at ip=0x0002e50b
fsck.jfs(34): unaligned access to 0xfaf0050f at ip=0x0002e517
fsck.jfs(34): unaligned access to 0xfaf0050f at ip=0x0002e533
fsck.jfs(34): unaligned access to 0xfaf0050f at ip=0x0002e443
fsck.jfs(34): unaligned access to 0xfaf0050f at ip=0x0002e50b
fsck.jfs(34): unaligned access to 0xfaf0050f at ip=0x0002e517
fsck.jfs(34): unaligned access to 0xfaf0050f at ip=0x0002e533
fsck.jfs(34): unaligned access to 0xfaf0050f at ip=0x0002e443
fsck.jfs(34): unaligned access to 0xfaf0058f at ip=0x0002e50b
fsck.jfs(34): unaligned access to 0xfaf0058f at ip=0x0002e517
fsck.jfs(34): unaligned access to 0xfaf0058f at ip=0x0002e533
fsck.jfs(34): unaligned access to 0xfaf0058f at ip=0x0002e443
fsck.jfs(34): unaligned access to 0xfaf004cf at ip=0x0002e50b
fsck.jfs(34): unaligned access to 0xfaf004cf at ip=0x0002e517
fsck.jfs(34): unaligned access to 0xfaf004cf at ip=0x0002e533
fsck.jfs(34): unaligned access to 0xfaf004cf at ip=0x0002e443
fsck.jfs(34): unaligned access to 0xfaf004cf at ip=0x0002e50b
fsck.jfs(34): unaligned access to 0xfaf004cf at ip=0x0002e517
fsck.jfs(34): unaligned access to 0xfaf004cf at ip=0x0002e533
fsck.jfs(34): unaligned access to 0xfaf004cf at ip=0x0002e443
fsck.jfs(34): unaligned access to 0xfaf004cf at ip=0x0002e50b
fsck.jfs(34): unaligned access to 0xfaf004cf at ip=0x0002e517
fsck.jfs(34): unaligned access to 0xfaf004cf at ip=0x0002e533
fsck.jfs(34): unaligned access to 0xfaf004cf at ip=0x0002e443

And hundreds more similar errors when doing a manual fsck.jfs are
written to kern.log, and this check never finishes...

This time it seems to be a PA-RISC-Linux problem, as I recall
earlier problems with "unaligned access" messages.

Greetings,
	Peter.