marking super-block as CLEAN??

[mark.M]

Is it important log?
How must you handle?

/sbin/bcheckrc:
Checking for LVM volume groups and Activating (if any exist)
Volume group "/dev/vg00" has been successfully changed.
Activated volume group
Volume group "/dev/vg01" has been successfully changed.
Resynchronized volume group /dev/vg00
vxfs fsck: sanity check: root file system OK (mounted read/write)
Resynchronized volume group /dev/vg01
Checking hfs file systems
/sbin/fsclean: /dev/vg00/lvol1 (mounted) ok
HFS file systems are OK, not running fsck
Checking vxfs file systems
/dev/vg00/lvol8 :
vxfs fsck: sanity check: /dev/vg00/lvol8 needs checking
log replay in progress
replay complete - marking super-block as CLEAN
/dev/vg00/lvol9 :
vxfs fsck: sanity check: /dev/vg00/lvol9 needs checking
log replay in progress
replay complete - marking super-block as CLEAN
/dev/vg01/lvol1 :
vxfs fsck: sanity check: /dev/vg01/lvol1 needs checking
log replay in progress
replay complete - marking super-block as CLEAN
/dev/vg01/lvol2 :
vxfs fsck: sanity check: /dev/vg01/lvol2 needs checking
log replay in progress
replay complete - marking super-block as CLEAN
/dev/vg01/lvol3 :
vxfs fsck: sanity check: /dev/vg01/lvol3 needs checking
log replay in progress
replay complete - marking super-block as CLEAN
/dev/vg00/lvol3 :
vxfs fsck: sanity check: root file system OK (mounted read/write)
/dev/vg00/lvol4 :
vxfs fsck: sanity check: /dev/vg00/lvol4 needs checking
log replay in progress
replay complete - marking super-block as CLEAN
/dev/vg00/lvol5 :
vxfs fsck: sanity check: /dev/vg00/lvol5 needs checking
log replay in progress
replay complete - marking super-block as CLEAN
/dev/vg00/lvol6 :
vxfs fsck: sanity check: /dev/vg00/lvol6 needs checking
log replay in progress
replay complete - marking super-block as CLEAN
/dev/vg00/lvol7 :
vxfs fsck: sanity check: /dev/vg00/lvol7 needs checking
log replay in progress
replay complete - marking super-block as CLEAN

[Derek Whigham_1 · Accepted solution]

fsck_vxfs command use

The following command line shows fsck being entered to check a filesystem that was active when the system failed. The system response is the messages generated by a successful intent log replay, as in this example:

$ fsck -F vxfs /dev/rdsk/c1b0t0d0s2
log replay in progress
replay complete - marking superblock as CLEAN

In other words you filesystem is GOOD.

[Pedro Cirne]

Hi,

This is a normal cenario when a system was not shutdown gracefully or crashed. Filesystems are checked and super-bock is marked CLEAN, so they can be mounted.

Enjoy :)

[mirco_1]

hy,

is OK.

but the system have a crash and reboot ?

DM.

[Sudeesh]

Looks like your system was not shutdown properly. From the message, your filesystems are fine. If you still want to do a detailed fsck run:

fsck -o full,nolog /dev/vg00/rlvol7


Sudeesh

[Simon Hargrave]

Your filesystems are okay as the message says, however it implies that your system didn't get shutdown properly. When a filesystem is mounted, the superblock is marked as not clean. When it is unmounted cleanly, it's marked as clean. When the server boots up it runs fsck, which checks for this clean flag to know whether it is clean or not. In your case it was not clean and forced a scan.

It is also possible that your systems have been configured to force a full scan of all filesystems on reboot.

Some environments will manually edit the bcheckrc file (the script that runs bootup filesystem checks)

/sbin/fs/vxfs/bcheckrc

This can force a check every boot and could give the symptoms you see.

[Mahesh Kumar Malik]

Hi

This is the situation where graceful shutdown has not happened. In such case, hp-ux has a feature to perform file system consistency check at power on. All configured file systems are checked and repaired for inconsistency. VXFS file system is considered to be quite reliable from above aspect.

Check syslog.OLD and rc.log files for errors if any and accordingly place a support call to local HP support provider.

Regards
Mahesh

[Bill Hassell]

Yes, your system either crashed or someone disconnected power to the computer and it rebooted. Just like Windows, it is not recommended to turn off power without a proper shutdown.

To see what happened, look in /etc/shutdownlog which is the only place unexpected reboots are logged.