Bug 154623 - ocfs2 volume mounting fails
Summary: ocfs2 volume mounting fails
Status: RESOLVED DUPLICATE of bug 154618
Alias: None
Product: SUSE Linux 10.1
Classification: openSUSE
Component: Kernel (show other bugs)
Version: Beta 5
Hardware: x86-64 Other
: P5 - None : Critical (vote)
Target Milestone: ---
Assignee: E-mail List
QA Contact: E-mail List
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-03-02 07:29 UTC by Nohez Poonawala
Modified: 2006-03-02 08:55 UTC (History)
0 users

See Also:
Found By: Beta-Customer
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Nohez Poonawala 2006-03-02 07:29:31 UTC
Mounting ocfs2 volume fails with the following error message in /var/log/messages

klogd: OCFS2 Node Manager 1.2.0-SLES Tue Feb 21 14:36:13 PST 2006 (build sles)
klogd: o2cb heartbeat: registered disk mode
klogd: OCFS2 DLM 1.2.0-SLES Tue Feb 21 14:36:13 PST 2006 (build sles)
klogd: OCFS2 DLMFS 1.2.0-SLES Tue Feb 21 14:36:13 PST 2006 (build sles)
klogd: OCFS2 User DLM kernel interface loaded
klogd: (4632,3):__dlm_print_nodes:384 Nodes in my domain ("3C66554CA6BD4D3E8882009C1D093CEF"):
klogd: (4632,3):__dlm_print_nodes:388  node 2
klogd: jbd: no version for "struct_module" found: kernel tainted.
klogd: jbd: module not supported by Novell, setting U taint flag.
klogd: ocfs2: disagrees about version of symbol journal_force_commit
klogd: ocfs2: Unknown symbol journal_force_commit
klogd: ocfs2: disagrees about version of symbol journal_dirty_metadata
klogd: ocfs2: Unknown symbol journal_dirty_metadata
klogd: ocfs2: disagrees about version of symbol journal_wipe
klogd: ocfs2: Unknown symbol journal_wipe
klogd: ocfs2: disagrees about version of symbol journal_errno
klogd: ocfs2: Unknown symbol journal_errno
klogd: ocfs2: disagrees about version of symbol journal_extend
klogd: ocfs2: Unknown symbol journal_extend
klogd: ocfs2: disagrees about version of symbol journal_unlock_updates
modprobe: FATAL: Error inserting ocfs2 (/lib/modules/2.6.16-rc5-git2-2-smp/kernel/fs/ocfs2/ocfs2.ko): Unknown symbol in module, or unknown pa
rameter (see dmesg)
klogd: ocfs2: Unknown symbol journal_unlock_updates
klogd: ocfs2: disagrees about version of symbol journal_ack_err
klogd: ocfs2: Unknown symbol journal_ack_err
klogd: ocfs2: disagrees about version of symbol journal_lock_updates
klogd: ocfs2: Unknown symbol journal_lock_updates
klogd: ocfs2: disagrees about version of symbol journal_start_commit
klogd: ocfs2: Unknown symbol journal_start_commit
klogd: ocfs2: disagrees about version of symbol journal_flush
klogd: ocfs2: Unknown symbol journal_flush
klogd: ocfs2: disagrees about version of symbol journal_load
klogd: ocfs2: Unknown symbol journal_load
klogd: ocfs2: disagrees about version of symbol journal_get_write_access
klogd: ocfs2: Unknown symbol journal_get_write_access
klogd: ocfs2: disagrees about version of symbol journal_get_undo_access
klogd: ocfs2: Unknown symbol journal_get_undo_access
klogd: ocfs2: disagrees about version of symbol journal_destroy
klogd: ocfs2: Unknown symbol journal_destroy
klogd: ocfs2: disagrees about version of symbol journal_clear_err
klogd: ocfs2: Unknown symbol journal_clear_err
klogd: ocfs2: disagrees about version of symbol journal_stop
klogd: ocfs2: Unknown symbol journal_stop
klogd: ocfs2: disagrees about version of symbol journal_init_inode
klogd: ocfs2: Unknown symbol journal_init_inode
klogd: ocfs2: disagrees about version of symbol journal_start
klogd: ocfs2: Unknown symbol journal_start
klogd: ocfs2: disagrees about version of symbol log_wait_commit
klogd: ocfs2: Unknown symbol log_wait_commit
klogd: ocfs2: disagrees about version of symbol journal_restart
klogd: ocfs2: Unknown symbol journal_restart

Kernel      : kernel-smp-2.6.16_rc5_git2-2
Ocfs2-tools : ocfs2-tools-1.1.3svn1105-6
Ocfs2console: ocfs2console-1.1.3svn1105-6

It used to work upto kernel-smp-2.6.16_rc3_git3-2.x86_64

Thanks
Comment 1 Olaf Kirch 2006-03-02 08:55:09 UTC

*** This bug has been marked as a duplicate of 154618 ***