search for: marowski

Support for SLES9 seems to be pretty much lacking at the moment. The OCFS2 site [1] states OCFS2 is supported with SP2+. There actually does not exist a SP2+ for SLES9 (or should this rather read "will be supported in SP3" instead?). Latest RPMs that come with SLES9 SP2 are 0.99.14 which has critical known bugs and is unusable. Anybody got to compile current source on SLES9 x86_64?

Is it possible to create a highly-available OCFS2 cluster (i.e., A storage cluster that mitigates the single point of failure [SPoF] created by storing an OCFS2 volume on a single LUN)? The OCFS2 Project Page makes this claim... > OCFS2 is a general-purpose shared-disk cluster file system for Linux capable of providing both high performance and high availability. ...but without backing-up

Hi all, what do you think of a half-day / day long miniconference on clustering along LPC? (http://lwn.net/Articles/319215/) It's a bit late, but if noone objects, I'll submit a proposal tomorrow. What topics would you like to see discussed? We probably don't have enough mass to justify our completely own summit, but on-going integration, (lack of) progress since the meeting in

hi! when will OCFS be available on RedHat AS/ES 4 or any 2.6 kernel distro ? Thanks Miguel -------------- next part -------------- An HTML attachment was scrubbed... URL: http://oss.oracle.com/pipermail/ocfs2-users/attachments/20050516/52aa4375/attachment.html

Hello all, I am running SLES9 with the latest kernel patches (2.6.5-7.282-bigsmp) and ocfs2 version (1.2.1-SLES), I was wondering if anyone had any info on if the latest ocfs2 will be included in SLES anytime soon. Or how to get the patches from Novell. Thanks in advance! - Andy Andy Kipp Network Administrator Velcro USA Inc. 406 Brown Ave. Manchester, NH 03103 Phone: (603) 222-4844 Email:

Hi all, tracing a couple of reports here (on a somewhat older version of OCFS2, with a user-space/pacemaker/dlm_controld.pcmk stack) where we see fnctl(F_SETLK) return ENOSYS. This happens after a node has failed/been fenced and recovered. It affects only individual mounts, not the whole system. The only code path that I can see so far that could lead to ENOSYS being returned here is from within