Dev1 Galaxy Forum / Devuan jfs boot warnings and errors

Re: Devuan jfs boot warnings and errors

dummy@example.com (Dutch_Master) — Sun, 11 Dec 2022 13:07:14 +0000

CPU and RAM are not particularly connected to JFS, but being a journaling file system the required checks take time if you have low RAM and/or a low capacity CPU. Make sure you have the jfsutils package installed, but given you can boot eventually I think it already is.

Re: Devuan jfs boot warnings and errors

dummy@example.com (amaro) — Sun, 11 Dec 2022 11:05:08 +0000

I had used 'jfs' on this laptop in the past with 'Slackware' so there is no reason to doubt the CPU or the RAM capacity
But if you have some information that connects the CPU or the RAM capacity with 'jfs' I would like to read it if don't mind sharing the link to it

# cat /etc/fstab
UUID=1190ddee-8f83-40a9-8688-0eaeb317d634	/	jfs	defaults,noatime	0	1
/swapfile	none	swap	sw	0	0

Re: Devuan jfs boot warnings and errors

dummy@example.com (Dutch_Master) — Tue, 06 Dec 2022 16:14:11 +0000

No. I'm using JFS on all my partitions/disks and it boots pretty quickly. Having said that, I had some issues with one drive (with a JFS partition) but that turned out to be a hardware failure. Fortunately I already had anticipated said failure coming so I had saved my data to a different drive and after a last sync between them the failed drive is now out of my desktop.

In any case, I don't see the JFS warnings/issues you mentioned in your posted dmesg abstract.
For starters, post the contents of the /etc/fstab file. I'm also interested in your CPU make/model and installed RAM capacity.

Devuan jfs boot warnings and errors

dummy@example.com (amaro) — Tue, 06 Dec 2022 07:54:02 +0000

Hello everybody,

I installed Devuan on 'jfs' partition
As a result I get lots of warnings and errors which are not there on Devuan on 'ext4' partition
And on every boot there is a significance delay due to the system's necessity to automatically perform 'jfs.fsck' after the first 5 or 6 warnings
Is this the case (i.e. to be expected) when using 'jfs'?

# dmesg -T --color=always --level=err,warn  | more
[Tue Dec  6 08:25:59 2022] APIC calibration not consistent with PM-Timer: 1269ms instead of 100ms
[Tue Dec  6 08:25:59 2022] pmd_set_huge: Cannot satisfy [mem 0xe0000000-0xe0200000] with a huge-page mapping
 due to MTRR override.
[Tue Dec  6 08:26:01 2022] ACPI Warning: SystemIO range 0x0000000000000428-0x000000000000042F conflicts with
 OpRegion 0x0000000000000400-0x000000000000047F (\PMIO) (20200925/utaddress-204)
[Tue Dec  6 08:26:01 2022] ACPI Warning: SystemIO range 0x00000000000011B0-0x00000000000011BF conflicts with
 OpRegion 0x0000000000001180-0x00000000000011FF (\GPIO) (20200925/utaddress-204)
[Tue Dec  6 08:26:01 2022] ACPI Warning: SystemIO range 0x0000000000001180-0x00000000000011AF conflicts with
 OpRegion 0x0000000000001180-0x00000000000011FF (\GPIO) (20200925/utaddress-204)
[Tue Dec  6 08:26:01 2022] lpc_ich: Resource conflict(s) found affecting gpio_ich
[Tue Dec  6 08:26:01 2022] r8169 0000:07:00.0: can't disable ASPM; OS doesn't have ASPM control
[Tue Dec  6 08:26:01 2022] ACPI BIOS Error (bug): AE_AML_BUFFER_LIMIT, Index (0x00000000F) is beyond end of
 object (length 0x8) (20200925/exoparg2-393)
[Tue Dec  6 08:26:01 2022] ACPI Error: Aborting method \_SB.PCI0.IBCM due to previous error (AE_AML_BUFFER_
LIMIT) (20200925/psparse-529)
[Tue Dec  6 08:26:01 2022] ACPI Error: Aborting method \_SB.PCI0.GFX0.DD02._BCM due to previous error (AE_A
ML_BUFFER_LIMIT) (20200925/psparse-529)
[Tue Dec  6 08:26:01 2022] ACPI Error: Evaluating _BCM failed (20200925/video-357)
[Tue Dec  6 08:26:01 2022] clocksource: timekeeping watchdog on CPU0: Marking clocksource 'tsc-early' as uns
table because the skew is too large:
[Tue Dec  6 08:26:01 2022] clocksource:                       'hpet' wd_now: 36be22b wd_last: 2f07d56 mask: 
ffffffff
[Tue Dec  6 08:26:01 2022] clocksource:                       'tsc-early' cs_now: 154b698d94 cs_last: 150f7a
a72a mask: ffffffffffffffff
[Tue Dec  6 08:26:01 2022] TSC found unstable after boot, most likely due to broken BIOS. Use 'tsc=unstable'.
[Tue Dec  6 08:26:01 2022] ata1.00: unexpected _GTF length (8)
[Tue Dec  6 08:26:01 2022] ata1.00: unexpected _GTF length (8)
[Tue Dec  6 08:26:02 2022] sd 6:0:0:0: [sdb] No Caching mode page found
[Tue Dec  6 08:26:02 2022] sd 6:0:0:0: [sdb] Assuming drive cache: write through
[Tue Dec  6 08:26:02 2022] ata2.00: unexpected _GTF length (8)
[Tue Dec  6 08:26:02 2022] ata2.00: unexpected _GTF length (8)
[Tue Dec  6 08:26:08 2022] at24 0-0050: supply vcc not found, using dummy regulator
[Tue Dec  6 08:26:10 2022] ath5k 0000:06:00.0: can't disable ASPM; OS doesn't have ASPM control
[Tue Dec  6 08:30:12 2022] xfs filesystem being mounted at /media/vb/xfs supports timestamps until 2038 (0x7fffffff)