similar to: [PATCH] ocfs2: Prevent mount with "-o acl" if acl isn't supported.

On RHEL4 also, the service o2cb starts later than _netdev device mounts. So mount fails. Should the o2cb service start earlier to fix this? Zafar -----Original Message----- From: ocfs2-users-bounces@oss.oracle.com [mailto:ocfs2-users-bounces@oss.oracle.com] On Behalf Of ocfs2-users-request@oss.oracle.com Sent: Tuesday, June 28, 2005 12:00 PM To: ocfs2-users@oss.oracle.com Subject: Ocfs2-users

Hi I'd like to know if OCFS2 1.4 on RHEL5 with the REDHAT latest kernel supports disk quotas, the xattr and acl. I could have done something wrong but only the acl seem to work. Apparently instead on FC12, where support is enabled in the kernel itself OCFS grep / boot / config * CONFIG_OCFS2_FS = m CONFIG_OCFS2_FS_O2CB = m CONFIG_OCFS2_FS_USERSPACE_CLUSTER = m # CONFIG_OCFS2_FS_STATS is

Hi, These three patches fix the problems in the version two. And them base on the Tao's patches: ocfs2/xattr: xattr improvement The first patch fix some problem in xattr code. The second patch add security EA support. The third patch add ACL support. Best regards, tiger

Hi all, I'm testing OCFS2 as a cluster filesystem for a mail system based on maildir, so basically the filesystem must be able to deal with lots of directories, and lots of small files. The first "oddity", is that when I mount a newly formated ocfs2 fs, it already contains used space: [root@ocfs1 /]# df /cgp02 Filesystem 1K-blocks Used Available Use% Mounted on

Hi all, I stumbled over a curious thing. The Linux tools "df" and "du" aren't working correctly on an OCFS2 filesystem. "df" shows approx. twice the size as there is on the volume. Here how I found out about this issue: - same dir(a few files more in OCFS but the files are ca. 12 kB in size), first on XFS second on the OCFS volume # du -ms

Hello. I am experimenting with OCFS2 on Suse Linux Enterprise Server 11 Service Pack 1. I am performing various stress tests. My current exercise involves writing to files using a shared-writable mmap() from two nodes. (Each node mmaps and writes to different files; I am not trying to access the same file from multiple nodes.) Both nodes are logging messages like these: [94355.116255]

Hi list, today, I installed a two node Oracle 10g RAC system on SLES9 SP2 RC2 which shares (via a SAN) a database volume and a quorum (ocr and voting). This volumes are formated with ocfs2 - so far no problem. At the moment I'm stuck with the mounting of these volumes at boot time. The user-guide of ocfs2-tools mentions to add the corresponding lines to fstab - but at the time when fstab

new_inode() does not return ERR_PTR() but NULL in case of failure. Correct checking of the return value. Signed-off-by: Jan Kara <jack at suse.cz> --- fs/ocfs2/namei.c | 4 ++-- 1 files changed, 2 insertions(+), 2 deletions(-) diff --git a/fs/ocfs2/namei.c b/fs/ocfs2/namei.c index d5d808f..0372ef0 100644 --- a/fs/ocfs2/namei.c +++ b/fs/ocfs2/namei.c @@ -382,8 +382,8 @@ static int

Hi, we have recently started to use ocfs2 on some RHEL 5.5 servers (ocfs2-1.4.7) Some days ago, two servers sharing an ocfs2 filesystem, and with quite virtual services, stalled, in what it seems on ocfs2 issue. This are the lines in their messages files: =====node heraclito (0)======================================== /Dec 4 09:15:06 heraclito kernel: o2net: connection to node parmenides

I'm trying to mount a ocfs2 volume (created on sles11) on my sles10sp2 server. I created the volume with these options: "mkfs.ocfs2 -C 128k -L CLUFS -M cluster -N 16 /dev/sdc". (dev/sdc is an iscsi device). It works to mount the volume with "mount.ocfs2 /dev/sdc /ocfs2" on my boxes (with o2cb configured for both nodes). When creating files on the ocfs2 volume I cant see

Hi there I recently installed an OCFS2 filesystem on our FC-SAN. Everything seemed to work fine and I could read & write the filesystem from both servers that are mounting it. After a while though, writes coming from one node do not appear on the other node and vice versa. I am not sure what's causing this, and not very experienced at debugging filesystems. If anybody has any

Hi, In the ongoing drama surrounding this upgrade, I have encountered another issue that I am unable to currently resolve. mount.ocfs2 /dev/sdb1 /mnt mount.ocfs2: Stale NFS file handle while mounting /dev/sdb1 on /mnt. Check 'dmesg' for more information on this error. dmesg: (3701,1):ocfs2_populate_inode:240 ERROR: file entry generation does not match superblock!

checks IO error in ocfs2_get_sector(). this patch is based on 1.4 git. Signed-off-by: Wengang wang <wen.gang.wang at oracle.com> -- Index: fs/ocfs2/super.c =================================================================== --- fs/ocfs2/super.c (revision 128) +++ fs/ocfs2/super.c (working copy) @@ -1203,6 +1203,12 @@ static int ocfs2_get_sector(struct super unlock_buffer(*bh);

In commit ea455f8ab68338ba69f5d3362b342c115bea8e13, we move the dentry lock put process into ocfs2_wq. This is OK for most case, but as for umount, it lead to at least 2 bugs. See http://oss.oracle.com/bugzilla/show_bug.cgi?id=1133 and http://oss.oracle.com/bugzilla/show_bug.cgi?id=1135. And it happens easily if we have opened a lot of inodes. For 1135, the reason is that during umount will call

We need to use le32_to_cpu to test rec->e_cpos in ocfs2_dinode_insert_check. Signed-off-by: Tao Ma <tao.ma at oracle.com> --- fs/ocfs2/alloc.c | 3 ++- 1 files changed, 2 insertions(+), 1 deletions(-) diff --git a/fs/ocfs2/alloc.c b/fs/ocfs2/alloc.c index 3a9e5de..19e3a96 100644 --- a/fs/ocfs2/alloc.c +++ b/fs/ocfs2/alloc.c @@ -176,7 +176,8 @@ static int

fs/ocfs2/dir.c: In function ?ocfs2_extend_dir?: fs/ocfs2/dir.c:2700: warning: ?ret? may be used uninitialized in this function fs/ocfs2/suballoc.c: In function ?ocfs2_get_suballoc_slot_bit?: fs/ocfs2/suballoc.c:2216: warning: comparison is always true due to limited range of data type Signed-off-by: Tao Ma <tao.ma at oracle.com> --- fs/ocfs2/dir.c | 2 +- fs/ocfs2/suballoc.c |

o2dlm join and leave messages are more than informational as they are required is debugging locking issues. This patch changes them from KERN_INFO to KERN_NOTICE. Signed-off-by: Sunil Mushran <sunil.mushran at oracle.com> --- fs/ocfs2/dlm/dlmdomain.c | 6 +++--- 1 files changed, 3 insertions(+), 3 deletions(-) diff --git a/fs/ocfs2/dlm/dlmdomain.c b/fs/ocfs2/dlm/dlmdomain.c index

Currently, when listing xattrs, kernel define XATTR_LIST_MAX as 65536 in include/linux/limits.h, so it can't handle too many xattrs. But with ocfs2 xattr tree, we actually have no limit for the number. And it will pollute the message with something like this when listing. (27738,0):ocfs2_iterate_xattr_buckets:3158 ERROR: status = -34 (27738,0):ocfs2_xattr_tree_list_index_block:3264 ERROR:

Hello, i want to install ocfs2-tools-1.2.0-1 on slackware 10.2 (up-to-date) with 2.6.17.2 kernel and i got error: ./configure checking build system type... i686-pc-linux-gnu checking host system type... i686-pc-linux-gnu checking for gcc... gcc checking for C compiler default output file name... a.out checking whether the C compiler works... yes checking whether we are cross compiling... no

Hello, i want to install ocfs2-tools-1.2.0-1 on slackware 10.2 (up-to-date) with 2.6.17.2 kernel and i got error: ./configure checking build system type... i686-pc-linux-gnu checking host system type... i686-pc-linux-gnu checking for gcc... gcc checking for C compiler default output file name... a.out checking whether the C compiler works... yes checking whether we are cross compiling... no