[Ocfs-users] Upgraded to 1.0.12, formatted archive vol andnow
fsck.ocfs errors
Sunil Mushran
Sunil.Mushran at oracle.com
Tue Jun 29 13:22:36 CDT 2004
Yes. known issue. Harmless though. Will be fixed in the new release.
Ignore it.
On Tue, 2004-06-29 at 07:19, Gathman, Donald wrote:
> Thanks for your reply! The mount cleaned up the error. However, after I
> go to OCFSTOOL, select Preferences, Advanced, Edit: set User:oracle
> Group:dba and Protection 0775, and then run fsck.ocfs I get the
> following warning:
>
> fsck.ocfs /dev/sdc9
> fsck.ocfs 1.0.10-PROD1 Fri Mar 5 14:35:41 PST 2004 (build
> b5602eb387c7409e9f814faf1d363b5b)
> Checking Volume Header...
> WARNING: nonzero bytes after the disk header structure
> /dev/sdc9: clean, 256 objects, 105/114681 blocks
>
> Is this OK? Why is fsck complaining?
>
> Thanks!!
>
>
> -----Original Message-----
> From: Sunil Mushran [mailto:Sunil.Mushran at oracle.com]
> Sent: Monday, June 28, 2004 4:38 PM
> To: Gathman, Donald
> Cc: ocfs-users at oss.oracle.com
> Subject: Re: [Ocfs-users] Upgraded to 1.0.12, formatted archive vol
> andnow fsck.ocfs errors
>
> The current released mkfs does not fully format the volume. For e.g., it
> does not create the root dir (root_off = 0). That is done on the first
> mount.
>
> The next release of mkfs will do the full format.
>
> So, go ahead, mount the volume on any node. The next fsck should report
> a clean run.
>
> On Mon, 2004-06-28 at 15:24, Gathman, Donald wrote:
> > 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
> >
> >
> >
> > ______________________________________________________________________
> > _______________________________________________
> > Ocfs-users mailing list
> > Ocfs-users at oss.oracle.com
> > http://oss.oracle.com/mailman/listinfo/ocfs-users
>
>
>
More information about the Ocfs-users
mailing list