similar to: Odd INFO "120 seconds" in logs for 2.6.18-194.3.1

Hi All, When a couple of EXT4 filesystems are mounted in a server I get the message Oct 1 18:49:42 sraid3 kernel: EXT4-fs (sdb): mounted filesystem without journal Oct 1 18:49:42 sraid3 kernel: EXT4-fs (sdc): mounted filesystem without journal in the system logs. My confusion is why are they mounted without a journal? They were both created with mkfs -t ext4 /dev/sdb mkfs -t ext4

Currently, default behavior of O_DIRECT writes was allowing concurrent writing among nodes, no cluster coherency guaranteed (no EX locks was taken), it hurts buffered reads on other nodes by reading stale data from cache. The new mount option introduce a chance to choose two different behaviors for O_DIRECT writes: * coherency=full, as the default value, will disallow concurrent

Hello, I've hit a bug in OCFS2 delete code which results in inodes being left on disk without any links to them. The workload triggering this creates directories on one node and deletes them on another node in the cluster. The inode is not deleted because both nodes bail out from ocfs2_delete_inode() with: Skipping delete of 100405 because it is in use on other nodes The scenario which I

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

writeback_inodes_sb(_nr)_if_idle() is re-implemented by replacing down_read() with down_read_trylock() because - If ->s_umount is write locked, then the sb is not idle. That is writeback_inodes_sb(_nr)_if_idle() needn''t wait for the lock. - writeback_inodes_sb(_nr)_if_idle() grabs s_umount lock when it want to start writeback, it may bring us deadlock problem when doing umount.

We are running kernel 2.6.18-164.6.1.el5 with exporting 3 aoe provided ext4 directories. For a couple of weeks we had a small number of users using the system with no issues, today we added 7 users and the system crashed and did not perform correctly since. Nov 23 10:20:03 sulphur rpc.idmapd[5199]: nfsdcb: id '-2' too big! Nov 23 10:42:25 sulphur nfsd[27306]: nfssvc: Setting version

Hi Linus, Nick found a bad rb tree corruption problem in btrfs with fsx. It would be nice to have this in 2.6.31, so please pull. Thanks! git://git.kernel.dk/linux-2.6-block.git btrfs From: Nick Piggin (1): btrfs: fix inode rbtree corruption fs/btrfs/inode.c | 21 ++++++++++++++------- 1 files changed, 14 insertions(+), 7 deletions(-) diff --git a/fs/btrfs/inode.c

After running ceph on XFS for some time, I decided to try btrfs again. Performance with the current "for-linux-min" branch and big metadata is much better. The only problem (?) I''m still seeing is a warning that seems to occur from time to time: [87703.784552] ------------[ cut here ]------------ [87703.789759] WARNING: at fs/btrfs/inode.c:2103

Hello. I found bugs on error handlings in the functions arround the ext3 file system, which cause inadequate completions of synchronous write I/O operations when disk I/O failures occur. Both 2.4 and 2.6 have this problem. I carried out following experiment: 1. Mount a ext3 file system on a SCSI disk with ordered mode. 2. Open a file on the file system with O_SYNC|O_RDWR|O_TRUNC|O_CREAT

I do not mean to be argumentative, but I have to admit a little frustration with Gluster. I know an enormous emount of effort has gone into this product, and I just can't believe that with all the effort behind it and so many people using it, it could be so fragile. So here goes. Perhaps someone here can point to the error of my ways. I really want this to work because it would be ideal

Hi, while doing work, my luks encrypted btrfs home got a nice stacktrace i run a Debian testing and a kernel 3.4 vanilla % uname -a Linux Klappe2 3.4.0 #2 SMP Thu Jun 14 03:02:37 CEST 2012 x86_64 GNU/Linux the box is a dell xps m 1330 with about 4gb ram % btrfs fi show Label: ''home'' uuid: 9c1a77c9-3767-43aa-908d-0bae1ef4e534 Total devices 1 FS bytes used 198.25GB devid

Hi, System description : RedHat EL 5.3 Previous version of samba : 3.2.11. The problem : ... Linking bin/smbd /usr/bin/ld: warning: libssl.so.6, needed by /usr/local/lib/libcups.so, may conflict with libssl.so.0.9.8 /usr/bin/ld: warning: libcrypto.so.6, needed by /usr/local/lib/libcups.so, may conflict with libcrypto.so.0.9.8 smbd/ipc.o: In function `api_dcerpc_cmd_write_done':

From: Andi Kleen <ak@linux.intel.com> 240f62c8756 replaced the node_lock with rcu_read_lock, but forgot to remove the actual lock in the data structure. Remove it here. Signed-off-by: Andi Kleen <ak@linux.intel.com> --- fs/btrfs/ctree.h | 3 --- fs/btrfs/disk-io.c | 1 - 2 files changed, 0 insertions(+), 4 deletions(-) diff --git a/fs/btrfs/ctree.h b/fs/btrfs/ctree.h index

use i_size_read() instead of accessing inode->i_size directly. Signed-off-by: Wengang Wang <wen.gang.wang at oracle.com> -- diff --git a/fs/ocfs2/aops.c b/fs/ocfs2/aops.c index b2c52b3..4491851 100644 --- a/fs/ocfs2/aops.c +++ b/fs/ocfs2/aops.c @@ -1920,7 +1920,7 @@ int ocfs2_write_end_nolock(struct address_space *mapping, out_write_size: pos += copied; - if (pos >

Folks, I tried using full_audit on Samba 3.0.28 by putting the following lines on smb.conf (global section): vfs objects = full_audit full_audit:facility = LOCAL2 full_audit:priority = WARN full_audit:prefix = %u|%m|%S full_audit:success = rename rmdir unlink write full_audit:failure = none My log says: Dec 29 13:57:07 lua smbd_audit: [2008/12/29 13:57:07, 0] lib/fault.c:fault_report(45) Dec

Hi posted this on the forum but then found the mailing list :-) so hope it's ok to post to the list aswell. we have a centos 4.3 server running samba, winbind and squid authenticating by winbind to our NT domain. Once in a while in the early hours it has the below error in /var/log/messages this causes the machine to fail and we carn't connect to it. It's double dutch to me,

CENTOS 5.5 dahdi 1.4.3.0.1 uname -r 2.6.18-194.3.1.el5PAE [root at localhost dahdi-linux-2.3.0.1]# service dahdi start Loading DAHDI hardware modules: FATAL: Module dahdi not found. wct4xxp: FATAL: Module wct4xxp not found. [FAILED] wctc4xxp: FATAL: Module wctc4xxp not found.

CentOS Errata and Security Advisory 2010:0398 Important Upstream details at : https://rhn.redhat.com/errata/RHSA-2010-0398.html The following updated files have been uploaded and are currently syncing to the mirrors: ( md5sum Filename ) i386: 48350c45095dbcb07f21e49e38ec0cd2 kernel-2.6.18-194.3.1.el5.i686.rpm 2c506236d9b99c221ff414f4647a3964 kernel-debug-2.6.18-194.3.1.el5.i686.rpm

CentOS Errata and Security Advisory 2010:0398 Important Upstream details at : https://rhn.redhat.com/errata/RHSA-2010-0398.html The following updated files have been uploaded and are currently syncing to the mirrors: ( md5sum Filename ) x86_64: 2a0042c6c3ab52e2868ac1b51daeb51a kernel-2.6.18-194.3.1.el5.x86_64.rpm 15bcb343225cc941e8aea6f9d5a2ca6b kernel-debug-2.6.18-194.3.1.el5.x86_64.rpm

I have a box running CentOS 5.x 32 bit. I noticed these kernels are installed. [root at ns1 log]# rpm -qa |grep kern |sort kernel-2.6.18-194.11.1.el5 kernel-2.6.18-194.3.1.el5 kernel-2.6.18-194.8.1.el5 kernel-PAE-devel-2.6.18-194.11.1.el5 kernel-PAE-devel-2.6.18-194.3.1.el5 kernel-PAE-devel-2.6.18-194.8.1.el5 [root at ns1 log]# uname -a Linux ns1.xx.net 2.6.18-194.11.1.el5 #1 SMP Tue Aug 10