[Ocfs2-users] How to fsck.ocfs2
Werner Flamme
werner.flamme at ufz.de
Tue Feb 22 06:36:46 PST 2011
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Werner Flamme [22.02.2011 13:55]:
> Sunil Mushran [22.02.2011 03:40]:
>> If fsck completed successfully, then o2image is not required.
>
> ---snip---
> # fsck.ocfs2 -fy /dev/sdf 2>&1 | tee /ocfs2/sap02/fsck_sap01_hot.txt
> fsck.ocfs2 1.4.3
> Checking OCFS2 filesystem in /dev/sdf:
> Label: SAP01
> UUID: 5969C8CABB854F8EA9C17B5B8DE48EC6
> Number of blocks: 183500800
> Block size: 4096
> Number of clusters: 183500800
> Cluster size: 4096
> Number of slots: 15
>
> fsck.ocfs2: extent_tree.c:435: ocfs2_new_path: Assertion
> `root_el->l_tree_depth < 5' failed.
> ---pins---
>
> So, the error disappears not because of the "-f", but because of "-n"?
>
> fsck does not start, even when I use "-f -y" and when I leave "-y" away.
> But it does start when I add "-n", but since I want to repair the fs,
> this is not a useful option :-(
>
> Regards,
> Werner
>
Given the expected file size, I can't provide an o2image:
- ---snip---
# o2image /dev/sdf /ocfs2/sap02/o2image_sap01.dat
o2image: Bad magic number in inode while reading global bitmap inode
14034875
o2image: Bad magic number in inode while reading global bitmap inode
14034876
o2image: Bad magic number in inode while reading global bitmap inode
14034877
o2image: Bad magic number in inode while reading global bitmap inode
14034878
o2image: Bad magic number in inode while reading global bitmap inode
14034879
Image file expected to be 80031676K, Available free space 155338816K.
Continue ? (y/N): n
Aborting image creation.
- ---pins---
How can I repair the volume? mkfs.ocfs2?
Regards,
Werner
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.15 (GNU/Linux)
Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org/
iEYEARECAAYFAk1jyf4ACgkQk33Krq8b42OaCwCaAmYORFkrwU0NhMf0ruAoAO/F
SZ8An1Xk8WcWEtD9z6WjOZRl0EjbfTJ2
=Ralf
-----END PGP SIGNATURE-----
More information about the Ocfs2-users
mailing list