[Ocfs-users] Upgraded to 1.0.12, formatted archive vol and now fsck.ocfs errors

[Bryan, Shane A]

The email I just forwarded to you has an explanation and solution

 

Shane...

 

-----Original Message-----
From: ocfs-users-bounces at oss.oracle.com
[mailto:ocfs-users-bounces at oss.oracle.com] On Behalf Of Gathman, Donald
Sent: Monday, June 28, 2004 3:24 PM
To: ocfs-users at oss.oracle.com
Subject: [Ocfs-users] Upgraded to 1.0.12, formatted archive vol and now
fsck.ocfs errors

 

After upgrading to ocfs 1.0.12 I formatted an archive volume per the
recommendation in the readme, and now fsck.ocfs  generates the following
error:

 

Any ideas on how to fix this???

 

Thanks...

 

 

Fsck.ocfs /dev/sdc9

fsck.ocfs 1.0.10-PROD1 Fri Mar  5 14:35:41 PST 2004 (build
b5602eb387c7409e9f814faf1d363b5b)

Checking Volume Header...                       

ERROR: structure failed verification, fsck.c, 384

ocfs_vol_disk_hdr

=================================

minor_version: 2

major_version: 1

signature: OracleCFS

mount_point: /ocfs-arch1a

serial_num: 0

device_size: 15033417728

start_off: 0

bitmap_off: 56320

publ_off: 23552

vote_off: 39936

root_bitmap_off: 0

data_start_off: 1368064

root_bitmap_size: 0

root_off: <INVALID VALUE> 0

root_size: 0

cluster_size: 131072

num_nodes: 32

num_clusters: 114681

dir_node_size: 0

file_node_size: 0

internal_off: <INVALID VALUE> 0

node_cfg_off: 4096

node_cfg_size: 17408

new_cfg_off: 21504

prot_bits: ----------

uid: 0 (root)

gid: 0 (root)

excl_mount: OCFS_INVALID_NODE_NUM

 

ERROR: Volume header bad. Exiting, fsck.c, 669

/dev/sdc9: 2 errors, 0 objects, 0/114681 blocks

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://oss.oracle.com/pipermail/ocfs-users/attachments/20040628/c20bb4cc/attachment.htm