fs_generation is randomly generated during mkfs and is added to each inode.
fsck uses it to identify current inodes (and not confuse with inodes
existing
from before the mkfs).
The error suggests that the root inode has a different fs_generation
that what
the superblock suggests. Unsure how that could happen.... unless you used a
really old version of mkfs that did not clear the two ends of the volume
at the
start of format.
See if running fsck helps.
# fsck.ocfs2 -f /dev/sdX.
Sunil
Randy Ramsdell wrote:
Hi,
In the ongoing drama surrounding this upgrade, I have encountered
another issue that I am unable to currently resolve.
mount.ocfs2 /dev/sdb1 /mnt
mount.ocfs2: Stale NFS file handle while mounting /dev/sdb1 on /mnt.
Check 'dmesg' for more information on this error.
dmesg:
(3701,1):ocfs2_populate_inode:240 ERROR: file entry generation does not
match superblock! osb->fs_generation=261a17ad, fe->i_fs_generation=794e6467
(3701,1):ocfs2_init_global_system_inodes:227 ERROR: status = -116
(3701,1):ocfs2_initialize_super:1492 ERROR: status = -116
(3701,1):ocfs2_fill_super:544 ERROR: status = -116
ocfs2: Unmounting device (8,17) on (node 255)
Any ideas?
Thanks,
RCR
_______________________________________________
Ocfs2-users mailing list
[email protected]
http://oss.oracle.com/mailman/listinfo/ocfs2-users
_______________________________________________
Ocfs2-users mailing list
[email protected]
http://oss.oracle.com/mailman/listinfo/ocfs2-users
