On Tue, Apr 16, 2013 at 11:08:34AM -0600, Jerry Smith
wrote:> Good Morning all,
>
>
> Have started seeing this over the last few days on a couple of hosts.
> Does anyone have any familiarity with this, and or how I can debug what
> mount/filesystem/inode is having the issues?
>
> Apr 16 02:49:36 host1 kernel:
> (dtocatalogbr,5864,3):ocfs2_prepare_dir_for_insert:4391 ERROR: status = -17
> Apr 16 02:49:36 host1 kernel:
> (dtocatalogbr,5864,3):__ocfs2_prepare_orphan_dir:1932 ERROR: status = -17
> Apr 16 02:49:36 host1 kernel:
> (dtocatalogbr,5864,3):ocfs2_prepare_orphan_dir:1973 ERROR: status = -17
> Apr 16 02:49:36 host1 kernel: (dtocatalogbr,5864,3):ocfs2_unlink:887
> ERROR: status = -17
Somehow you are trying to unlink a file whose inode is already in the
orphan dir. You can use debugfs.ocfs2 to determine what inodes are in
the orphan dir, but it isn't easy to see which one triggered the error.
You might try checking multiple times over the course of an hour. If
the same inode number remains while all of the others clear out, that
might be your culprit.
Joel
>
>
> #uname -a
> Linux host1 2.6.32-300.27.1.el6uek.x86_64 #1 SMP Tue Jun 19 14:21:30 EDT
> 2012 x86_64 x86_64 x86_64 GNU/Linux
>
> #cat /etc/redhat-release
> Red Hat Enterprise Linux Server release 6.2 (Santiago)
>
> #rpm -qa | grep ocfs
> ocfs2console-1.6.4-1.el6.x86_64
> ocfs2-tools-devel-1.6.4-1.el6.x86_64
> ocfs2-tools-1.6.4-1.el6.x86_64
>
>
> I have a few boxes a bit further along at OEL 6.3 and newer ocfs2 bits,
> where I am not seeing these errors arise.
>
> ocfs2 versions of:
>
> $ rpm -qa |grep
> ocfs
>
> ocfs2-tools-1.8.0-10.el6.x86_64
> ocfs2-tools-devel-1.8.0-10.el6.x86_64
>
> Are there known issues/fixes between these kernels/ocfs2-tools that fix
> the ERROR -17 I am seeing?
>
> Thanks,
>
> --Jerry
>
>
> _______________________________________________
> Ocfs2-users mailing list
> Ocfs2-users at oss.oracle.com
> https://oss.oracle.com/mailman/listinfo/ocfs2-users
--
You can use a screwdriver to screw in screws or to clean your ears,
however, the latter needs real skill, determination and a lack of fear
of injuring yourself. It is much the same with JavaScript.
- Chris Heilmann
http://www.jlbec.org/
jlbec at evilplan.org