On 16/01/18 07:59 PM, Dave Howorth wrote:
So I reboot and this time I unmount the two JFS partitions. I then start FF, copy the URL, start chromium, paste the URL ... and all works fine!
I suppose, ultimately, the question is not simply is it a problem with JSF, but is it a problem with the scheduler? Is it an interaction with the other FS drivers?
As advised by a page on JFS setup I have
# cat /sys/block/sda/queue/scheduler noop [deadline] cfq
Has anyone observed this? I'm not finding illumination with google but perhaps my fu is off today as well. Any ideas? Maybe version numbers for system, kernel, FF, chromium, JFS etc might help. Also what process is causing that load factor?
Kernel 4.14.13-4 of Jan 12 from the kernel Stable repository FF 52.2.0 chromium 63.0.3239.108-104.44.1 from openSUSE-Leap-42.2-Update I'm presuming the jfs driver itself is from /lib/modules/ I run strings on that and don't find any version number The jfsutil is 1.1.15-27.1 # fsck.jfs -V fsck.jfs version 1.1.15, 04-Mar-2011 when I run search it seems that's the version for tumbleweed and 42.3 as well. -- A: Yes. > Q: Are you sure? >> A: Because it reverses the logical flow of conversation. >>> Q: Why is top posting frowned upon? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org