An administrator is attempting to recover a filesystem that fails to manually unmount. The fsck command produces the following output:<br /> The current volume is: /dev/fslv02<br /> File system is currently mounted.  <br /> Invalid file system size in the primary superblock.<br /> Invalid file system size in the secondary superblock. <br /> Primary superblock is corrupt. Secondary superblock is corrupt.  <br /> fsck: 0507-018 Superblock is corrupt and cannot be repaired.<br /> Both primary and secondary copies are corrupt.Cannot continue<br /> tried to mount <br /> Which steps will resolve the problem?()<p> An&en
A、A.Reboot the server into maintenance mode and run ‘fsck’ with the ‘-p’ parameter while the filesystem is mounted.
B、B.Reboot the server into maintenance mode and run ‘fsck’ with the ‘-y’ parameter while the filesystem is unmounted.
C、C.Force a umount of the filesystem with ‘umount -F /dev/fslv02’, and then run ‘fsck -p /dev/fslv02’ while the filesystem is unmounted.
D、D.Force a umount of the filesystem by varying off the hosting volume group and then varyon the volume group. This will permit ‘fsck -y’ to be run against the failing filesystem.