search for: mtime_nsec

Hello, We have a 3-node cluster setup with ocfs2. Since friday one of the nodes went down and would not become clustermember after a reboot because it was unable to write to the ocfs2 filesystem. Message: no space left on device. There is plenty of diskspace though. No problem whatsoever to create a file / directory on the filesystem using one of the other nodes. Today one of the remaining

Hello, I have found, that ocfs2 is very slow when doing I/O operation without cache. See a simple test: ng-vvv1:~# dd if=/data/verejna/dd-1G bs=1k | dd of=/dev/null 1048576+0 records in 1048576+0 records out 1073741824 bytes (1.1 GB) copied, 395.183 s, 2.7 MB/s 2097152+0 records in 2097152+0 records out 1073741824 bytes (1.1 GB) copied, 395.184 s, 2.7 MB/s The underlying block device is quite

...s: 1280000 ctime: 0x4f845934 -- Tue Apr 10 11:00:52 2012 atime: 0x0 -- Wed Dec 31 18:00:00 1969 mtime: 0x4f845934 -- Tue Apr 10 11:00:52 2012 dtime: 0x0 -- Wed Dec 31 18:00:00 1969 ctime_nsec: 0x00000000 -- 0 atime_nsec: 0x00000000 -- 0 mtime_nsec: 0x00000000 -- 0 Refcount Block: 0 Last Extblk: 0 Orphan Slot: 0 Sub Alloc Slot: Global Sub Alloc Bit: 65535 fs_state: Device => Id: 254,2 Uuid: 45B8B88228BD4DFBBE91BFC85C748FB6 Gen: 0x364EAC5A Label: Volume => State: 2 Flags: 0x0 Sizes => Block...

...(root) Group: 0 (root) Size: 0 Links: 0 Clusters: 13107199 ctime: 0x48f80fe8 -- Fri Oct 17 15:09:12 2008 atime: 0x0 -- Thu Jan 1 10:00:00 1970 mtime: 0x48f80fe8 -- Fri Oct 17 15:09:12 2008 dtime: 0x0 -- Thu Jan 1 10:00:00 1970 ctime_nsec: 0x00000000 -- 0 atime_nsec: 0x00000000 -- 0 mtime_nsec: 0x00000000 -- 0 Last Extblk: 0 Sub Alloc Slot: Global Sub Alloc Bit: 65535 debugfs: echo "stat /brad/aaaaa" | debugfs.ocfs2 /dev/xvdd1 |cat debugfs.ocfs2 1.4.3 debugfs: Inode: 11539619 Mode: 0750 Generation: 3859452415 (0xe60a91ff) FS Generation: 964566170...

...: 27476584 ctime: 0x4baca081 -- Fri Mar 26 11:54:41 2010 atime: 0x0 -- Thu Jan 1 00:00:00 1970 mtime: 0x4baca081 -- Fri Mar 26 11:54:41 2010 dtime: 0x0 -- Thu Jan 1 00:00:00 1970 ctime_nsec: 0x00000000 -- 0 atime_nsec: 0x00000000 -- 0 mtime_nsec: 0x00000000 -- 0 Last Extblk: 0 Sub Alloc Slot: Global Sub Alloc Bit: 65535 /etc/init.d/o2cb status Driver for "configfs": Loaded Filesystem "configfs": Mounted Stack glue driver: Loaded Stack plugin "o2cb": Loaded Driver for "ocfs2_dlmfs&quot...

We are setting up 2 new EL5 U4 machines to replace our current database servers running our demo environment. We use 3Par SANs and their snap clone options. The current production system we snap clone from is EL4 U5 with ocfs2 1.2.9, the new servers have ocfs2 1.4.3 installed. Part of the refresh process is to run fsck.ocfs2 on the volume to recover, but right now as I am trying to run it on our

...ctime: 0x4786481b -- Thu Jan 10 16:30:19 2008 atime: 0x46a9a7dc -- Fri Jul 27 09:07:56 2007 mtime: 0x4786481b -- Thu Jan 10 16:30:19 2008 dtime: 0x0 -- Thu Jan 1 01:00:00 1970 ctime_nsec: 0x33de5143 -- 870207811 atime_nsec: 0x0ba52bb0 -- 195374000 mtime_nsec: 0x33de5143 -- 870207811 Last Extblk: 0 Sub Alloc Slot: 4 Sub Alloc Bit: 544 Tree Depth: 0 Count: 243 Next Free Rec: 1 ## Offset Clusters Block# 0 0 1 20289216 fsck.ocfs2 gives internal logic failures (or faliure...

...ctime: 0x4786481b -- Thu Jan 10 16:30:19 2008 atime: 0x46a9a7dc -- Fri Jul 27 09:07:56 2007 mtime: 0x4786481b -- Thu Jan 10 16:30:19 2008 dtime: 0x0 -- Thu Jan 1 01:00:00 1970 ctime_nsec: 0x33de5143 -- 870207811 atime_nsec: 0x0ba52bb0 -- 195374000 mtime_nsec: 0x33de5143 -- 870207811 Last Extblk: 0 Sub Alloc Slot: 4 Sub Alloc Bit: 544 Tree Depth: 0 Count: 243 Next Free Rec: 1 ## Offset Clusters Block# 0 0 1 20289216 fsck.ocfs2 gives internal logic failures (or faliure...

Hello, I'm writing from the otherside of the world from where my systems are, so details are coming in slow. We have a 6TB OCFS2 volume across 20 or so nodes all running OEL5.4 running ocfs2-1.4.4. The system has worked fairly well for the last 6-8 months. Something has happened over the last few weeks which has driven write performance nearly to a halt. I'm not sure how to proceed, and

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

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

...: 47456155 ctime: 0x4be7dd41 -- Mon May 10 12:17:37 2010 atime: 0x0 -- Thu Jan 1 01:00:00 1970 mtime: 0x4be7dd41 -- Mon May 10 12:17:37 2010 dtime: 0x0 -- Thu Jan 1 01:00:00 1970 ctime_nsec: 0x00000000 -- 0 atime_nsec: 0x00000000 -- 0 mtime_nsec: 0x00000000 -- 0 Refcount Block: 0 Last Extblk: 0 Orphan Slot: 0 Sub Alloc Slot: Global Sub Alloc Bit: 65535 But why is inline-data, indexed-dirs and so on incompatible? # debugfs.ocfs2 -V debugfs.ocfs2 1.6.0 #uname -a Linux server 2.6.32.12 Stefan