On 06/08/2011 03:36 PM, Herman wrote: > Hi all, > > Using: RHEL 6 / DRBD 8.3.10-2 kmod from ElRepo / OCFS2 compiled from > Redhat's kernel source 2.6.32-71.18.2.el6.x86_64 > > I have a system running DRBD with OCFS2. The OCFS2 filesystem is not > being used for databases. I had a split-brain due to > RHEL6's /etc/init.d/iptables script. Immediately after the split-brain > the OCFS2 filesystem started giving errors and they came in pretty fast. > I recovered from the split-brain manually, but that didn't stop the > messages. Rebooting, switching primary nodes, fsck.ocfs2, all didn't > work... the messages still came in fast. I finally had to find out what > that inode was pointing to and remove it before the messages stopped. > > > From looking through the archives, I guess it's due to there being a > hole in the inode from the sparse filesystem? But I don't know why it's > complaining about it, and I don't know why fsck.ocfs2 couldn't fix it. > > Here's the errors I got: > Apr 18 07:53:07 server-2 kernel: (8163,0):ocfs2_read_virt_blocks:853 > ERROR: Inode #5377026 contains a hole at offset 466944 > Apr 18 07:53:07 server-2 kernel: (8163,0):ocfs2_read_dir_block:533 > ERROR: status = -5 > Apr 18 07:53:08 server-2 kernel: (8163,12):ocfs2_read_virt_blocks:853 > ERROR: Inode #5377026 contains a hole at offset 466944 > Apr 18 07:53:08 server-2 kernel: (8163,12):ocfs2_read_dir_block:533 > ERROR: status = -5 > Apr 18 07:53:08 server-2 kernel: (8508,0):ocfs2_read_virt_blocks:853 > ERROR: Inode #5377026 contains a hole at offset 466944 > Apr 18 07:53:08 server-2 kernel: (8508,0):
The directory cannot have holes. That's the error. I am assuming that triggered due to the network/drbd. If so, atleast one should be ok. fsck should detect the problem. Don't know offhand whether we have a fix code for it or not. First time seeing this issue. File a bug on oss.oracle.com/bugzilla. _______________________________________________ Ocfs2-users mailing list Ocfs2-users@oss.oracle.com http://oss.oracle.com/mailman/listinfo/ocfs2-users
