[Ocfs2-users] OCFS2 and berkeley database files

Tue Dec 5 16:14:18 PST 2006

It really try to create a shared writable MMAP. And it already cause
numerous problems with another file systems.

----- Original Message ----- 
From: "Sunil Mushran" <Sunil.Mushran at oracle.com>
To: <hartmut.woehrle at mail.pcom.de>
Cc: <Ocfs2-users at oss.oracle.com>
Sent: Tuesday, December 05, 2006 3:45 PM
Subject: Re: [Ocfs2-users] OCFS2 and berkeley database files

You are on a very old release of OCFS2. The OCFS2 homepage and FAQ both
list a SLES9 kernel version newer than the one you are using.

But that may not be the reason for the error. My bet is that bdb is
attempting to create
a shared writeable mmap that ocfs2 1.2 does not support.

hartmut.woehrle at mail.pcom.de wrote:
> Hello Forum,
>
> when trying to install a mailserver on a shared SAN Device with ocfs2, I
> realized some strange problems with Berkeley .db files:
>
> Trying to install OpenLDAP:
> Dec  1 16:16:56 server_1 slapd[18497]: bdb_db_init: Initializing BDB
database
> Dec  1 16:16:56 server_1 slapd[18498]: bdb(ou=users,dc=mycomp,dc=de):
mmap:
> Invalid argument
> Dec  1 16:16:56 server_1 slapd[18498]: bdb_db_open: dbenv_open failed:
> Invalid
> argument (22)
> Dec  1 16:16:56 server_1 slapd[18498]: backend_startup: bi_db_open failed!
> (22)
> Dec  1 16:16:56 server_1 slapd[18498]: bdb(ou=users,dc=mycomp,dc=de):
> DB_ENV->lock_id_free interface requires an environment configured for th
> e locking subsystem
> Dec  1 16:16:56 server_1 slapd[18498]: bdb(ou=users,dc=mycomp,dc=de):
> txn_checkpoint interface requires an environment configured for the tran
> saction subsystem
> Dec  1 16:16:56 server_1 slapd[18498]: bdb_db_destroy: txn_checkpoint
failed:
> Invalid argument (22)
> Dec  1 16:17:50 server_1 slapd[18525]: bdb_db_init: Initializing BDB
database
> Dec  1 16:17:50 server_1 slapd[18526]: bdb(ou=users,dc=mycomp,dc=de):
mmap:
> Invalid argument
> Dec  1 16:17:50 server_1 slapd[18526]: bdb_db_open: dbenv_open failed:
> Invalid
> argument (22)
> Dec  1 16:17:50 server_1 slapd[18526]: backend_startup: bi_db_open failed!
> (22)
> Dec  1 16:17:50 server_1 slapd[18526]: bdb(ou=users,dc=mycomp,dc=de):
> DB_ENV->lock_id_free interface requires an environment configured for th
> e locking subsystem
> Dec  1 16:17:50 server_1 slapd[18526]: bdb(ou=users,dc=mycomp,dc=de):
> txn_checkpoint interface requires an environment configured for the tran
> saction subsystem
>
>
>
> .....
>
> When installing on a standard ext3 - no problems.
>
> When installing cyrus (initial start after creation of cyrus admin
account):
>
> Dec  5 04:15:01 server_1 ctl_mboxlist[29435]: IOERROR:
> mapping /var/lib/imap/mailboxes.db file: Invalid argument
> Dec  5 14:14:43 server_1 ctl_cyrusdb[32679]: IOERROR:
> mapping /communication/var/lib/imap/mailboxes.db file: Invalid argument
> Dec  5 14:14:43 server_1 idled[32680]: IOERROR:
> mapping /communication/var/lib/imap/mailboxes.db file: Invalid argument
> Dec  5 14:14:43 server_1 idled[32680]: failed to
> mmap /communication/var/lib/imap/mailboxes.db file
> Dec  5 14:14:43 server_1 pop3[32684]: IOERROR:
> mapping /communication/var/lib/imap/mailboxes.db file: Invalid argument
> Dec  5 14:14:43 server_1 pop3[32684]: Fatal error: failed to
> mmap /communication/var/lib/imap/mailboxes.db file
> Dec  5 14:14:43 server_1 pop3s[32685]: IOERROR:
> mapping /communication/var/lib/imap/mailboxes.db file: Invalid argument
> Dec  5 14:14:43 server_1 pop3s[32685]: Fatal error: failed to
> mmap /communication/var/lib/imap/mailboxes.db file
> Dec  5 14:14:43 server_1 pop3s[32691]: IOERROR:
> mapping /communication/var/lib/imap/mailboxes.db file: Invalid argument
> Dec  5 14:14:43 server_1 pop3s[32691]: Fatal error: failed to
> mmap /communication/var/lib/imap/mailboxes.db file
> Dec  5 14:14:43 server_1 pop3[32690]: IOERROR:
> mapping /communication/var/lib/imap/mailboxes.db file: Invalid argument
> Dec  5 14:14:43 server_1 pop3[32690]: Fatal error: failed to
> mmap /communication/var/lib/imap/mailboxes.db file
> Dec  5 14:14:43 server_1 pop3[32693]: IOERROR:
> mapping /communication/var/lib/imap/mailboxes.db file: Invalid argument
> Dec  5 14:14:43 server_1 pop3[32693]: Fatal error: failed to
> mmap /communication/var/lib/imap/mailboxes.db file
> Dec  5 14:14:43 server_1 pop3s[32694]: IOERROR:
> mapping /communication/var/lib/imap/mailboxes.db file: Invalid argument
> Dec  5 14:14:43 server_1 pop3s[32694]: Fatal error: failed to
> mmap /communication/var/lib/imap/mailboxes.db file
> Dec  5 14:14:43 server_1 pop3s[32695]: IOERROR:
> mapping /communication/var/lib/imap/mailboxes.db file: Invalid argument
> Dec  5 14:14:43 server_1 pop3s[32695]: Fatal error: failed to
> mmap /communication/var/lib/imap/mailboxes.db file
> Dec  5 14:14:43 server_1 pop3[32697]: IOERROR:
> mapping /communication/var/lib/imap/mailboxes.db file: Invalid argument
> Dec  5 14:14:43 server_1 pop3[32697]: Fatal error: failed to
> mmap /communication/var/lib/imap/mailboxes.db file
> Dec  5 14:14:43 server_1 pop3s[32698]: IOERROR:
> mapping /communication/var/lib/imap/mailboxes.db file: Invalid argument
> Dec  5 14:14:43 server_1 pop3s[32698]: Fatal error: failed to
> mmap /communication/var/lib/imap/mailboxes.db file
> Dec  5 14:14:43 server_1 pop3s[32701]: IOERROR:
> mapping /communication/var/lib/imap/mailboxes.db file: Invalid argument
> Dec  5 14:14:43 server_1 pop3s[32701]: Fatal error: failed to
> mmap /communication/var/lib/imap/mailboxes.db file
> Dec  5 14:14:43 server_1 sieve[32686]: IOERROR:
> mapping /communication/var/lib/imap/mailboxes.db file: Invalid argument
> Dec  5 14:14:43 server_1 sieve[32692]: IOERROR:
> mapping /communication/var/lib/imap/mailboxes.db file: Invalid argument
> Dec  5 14:14:43 server_1 pop3[32696]: IOERROR:
> mapping /communication/var/lib/imap/mailboxes.db file: Invalid argument
> Dec  5 14:14:43 server_1 pop3[32696]: Fatal error: failed to
> mmap /communication/var/lib/imap/mailboxes.db file
>
> ....
> and so on.
>
> With google I didn´t find that anything about this problem. Is it unknown,
> already solved or something concerned with my setup??
>
> Server is a DELL Poweredge with EMC CLARiiON SAN
> System SuSE SLES9 SP3+
> ->  2.6.5-7.244-smp Kernel with (...> modinfo ocfs2):
> license:        GPL
> author:         Oracle
> version:        1.1.7-SLES 5AF01E6455FC04917FE52FB
> description:    OCFS2 1.1.7-SLES Tue Nov  1 14:45:27 PST 2005 (build sles)
> depends:        ocfs2_nodemanager,ocfs2_dlm,jbd
> supported:      yes
> vermagic:       2.6.5-7.244-smp SMP gcc-3.3
>
> and in addition
> DELL/EMC PowerPath 4.5.1 for Linux
> to use the multiple path environment (not GPL multipath)
>
> Thanks
> Hartmut Woehrle
>
>
>
>

_______________________________________________
Ocfs2-users mailing list
Ocfs2-users at oss.oracle.com
http://oss.oracle.com/mailman/listinfo/ocfs2-users