[Ocfs-users] Regarding debugocfs

[Sunil Mushran]

This is an unused system file. When the file is used,
the fs adds an extent in the inode.

Takahiro Yoshimura wrote:
> Hi experts,
>
> My customer issued debugocfs to check for file_size and extent info
> but values such as file_size, alloc_size, next_free_ext were 0.
> (/dev/sdi1 contains datafiles and arc files)
>
> # debugocfs -a 0 /dev/sdi1
> debugocfs 1.0.10-PROD1 Fri Mar 5 14:35:29 PST 2004
> (build fcb0206676afe0fcac47a99c90de0e7b)
> file_extent_0:
> file_number = 128
> disk_offset = 1433600
> curr_master = 0
> file_lock = OCFS_DLM_NO_LOCK
> oin_node_map = 00000000000000000000000000000000
> seq_num = 0
> local_ext = true
> granularity = -1
> filename = ExtentFile128
> filename_len = 0
> file_size = 0
> alloc_size = 0
>
> next_free_ext = 0
> extent[0].file_off = 0
> extent[0].num_bytes = 0
> extent[0].disk_off = 0
>
> We don't have a clue why these values are 0.
> Does anybody have any idea or any possibilities
> why these values became 0?
>
> Customer env:
>
> OS：Red Hat AS 2.1　
> DB：Oracle9i Database Enterprise Edition 9.2.0.5
> OCFS:
> ocfs-2.4.9-e-enterprise-1.0.14-1
> ocfs-tools-1.0.10-1
> ocfs-support-1.0.10-1
>
> Regards,
> Takahiro
>
>