Sunil;
Just wanted to say thanks. We disabled the emtaecc feature on one of the
volumes (a backup volume) to test and the issue went away.
What we had:
> # tunefs.ocfs2 -q -Q "All Features: %M %H %O\n" /dev/mapper/backup-part1
> All Features: backup-super strict-journal-super sparse extended-s
Forgot to add that this issue is limited to metaecc. So you could avoid the
issue in your
same setup by not enabling metaecc on the volume. And last I checked mkfs
did not
enable it by default.
On Mon, Aug 27, 2012 at 10:35 AM, Sunil Mushran wrote:
> So you are running into a bug that has been fi
So you are running into a bug that has been fixed in 2.6.36. Upgrade to
that version,
if not something more current.
$ git describe --tags 13ceef09
v2.6.35-rc3-14-g13ceef0
commit 13ceef099edd2b70c5a6f3a9ef5d6d97cda2e096
Author: Jan Kara
Date: Wed Jul 14 07:56:33 2010 +0200
jbd2/ocfs2: Fix
# uname -a
Linux FILEt1 2.6.34.7-0.7-desktop #1 SMP PREEMPT 2010-12-13 11:13:53 +0100
x86_64 x86_64 x86_64 GNU/Linux
# modinfo ocfs2
filename: /lib/modules/2.6.34.7-0.7-desktop/kernel/fs/ocfs2/ocfs2.ko
license:GPL
author: Oracle
version:1.5.0
description:OCFS2 1.5
What is the version of the kernel, ocfs2 and ocfs2 tools?
uname -a
modinfo ocfs2
mkfs.ocfs2 --version
On Fri, Aug 24, 2012 at 1:09 PM, Rory Kilkenny wrote:
> We have an HP P2000 G3 Storage array, fiber connected. The storage
> array has a RAID5 array broken into 2 physical OCFS2 volumes (A & B
We have an HP P2000 G3 Storage array, fiber connected. The storage array
has a RAID5 array broken into 2 physical OCFS2 volumes (A & B).
A & B are both mounted and formatted as NTFS.
One of the volumes is NFS mounted.
Every couple of months or so we start getting tons of errors on the NFS
mount
