Is it possible that ext4 is not allowed for my cache partition?
On 10/15/2011 12:47 AM, Jeff Blaine wrote:
This has to be something really dumb on my part, but I can't make sense of it. RHEL 5.7 x86_64 2.6.18-274.3.1.el5 SMP on a brand new box. I've tried both of the following, separately, with the same result: 1. OpenAFS 1.4.14 binaries built from source 20 days ago, copied verbatim from a working RHEL 5.7 x86_64 2.6.18-274.3.1.el5 SMP box. 2. Fresh OpenAFS 1.4.14 build from source *on* this box, then installed sh /etc/init.d/afs.rc start => kernel panic Rebooting to single user, the insmod works fine and shows: Oct 14 23:36:34 rcf-monitor kernel: libafs: module license 'http://www.openafs.org/dl/license10.html' taints kernel. Oct 14 23:36:34 rcf-monitor kernel: Found system call table at 0xffffffff8028ff40 (pattern scan) Oct 14 23:36:34 rcf-monitor kernel: Using keyrings, rather than hooking system calls Oct 14 23:36:34 rcf-monitor kernel: Found 32-bit system call table at 0xffffffff80291280 (pattern scan) Oct 14 23:36:34 rcf-monitor kernel: Using keyrings, rather than hooking system calls What I can see of the panic on the console is shown in the screenshot here: http://dl.dropbox.com/u/15519230/panic.jpg If I build 1.4.14.1 from source, it works fine on this box it seems. I cannot explain how 1.4.14 is working fine on our other similar boxes, but not this one. _______________________________________________ OpenAFS-info mailing list [email protected] https://lists.openafs.org/mailman/listinfo/openafs-info
_______________________________________________ OpenAFS-info mailing list [email protected] https://lists.openafs.org/mailman/listinfo/openafs-info
