This is probably a directory. debugs.ocfs2 -R 'stat <52663>' /dev/ will
dump the inode.
Are you sure fsck is fixing it? Does the output show this block getting
fixed?
If not, you may want to run fsck.ocfs2 v1.8. I think a fix code was added
for it.
On Wed, Feb 20, 2013 at 1:01 AM, Fiorenza Meini wrote:
> Hi there,
> I have a partition formatted with ocfs2 (1.6.3) on a 2.6.37 Linux Kernel
> system. This partition is managed by a cluster (corosync/pacemaker).
> The backend of this ocfs2 partition is drbd on Lvm.
>
> I see this line in the messages log file:
> ocfs2_read_virt_blocks:871 ERROR: Inode #52663 contains a hole at offset
> 69632
>
> The error is reported more than once and the offset is the same..
>
> When I do a check on this partition, errors are found and resolved, but
> in a short time the problems appears again.
> I can't understand at what level is the problem:
> * kernel ?
> * hardware ?
> * lvm + drbd ?
>
> There are tools that can be used to understand ?
> Any suggestion?
>
> Thanks and regards.
>
> Fiorenza
> --
>
> Fiorenza Meini
> Spazio Web S.r.l.
>
> V. Dante Alighieri, 10 - 13900 Biella
> Tel.: 015.2431982 - 015.9526066
> Fax: 015.2522600
> Reg. Imprese, CF e P.I.: 02414430021
> Iscr. REA: BI - 188936
> Iscr. CCIAA: Biella - 188936
> Cap. Soc.: 30.000,00 Euro i.v.
>
> ___
> Ocfs2-users mailing list
> Ocfs2-users@oss.oracle.com
> https://oss.oracle.com/mailman/listinfo/ocfs2-users
>
___
Ocfs2-users mailing list
Ocfs2-users@oss.oracle.com
https://oss.oracle.com/mailman/listinfo/ocfs2-users
