An administrator is attempting to recover a filesystem that fails to manually unmount. The fsck command produces the following output： The current volume is： /dev/fslv02 File system is currently mounted. Invalid file system size in the primary superblock. Invalid file system size in the secondary superblock. Primary superblock is corrupt. Secondary superblock is corrupt. fsck： 0507-018 Superblock is corrupt and cannot be repaired. Both primary and secondary copies are corrupt.Cannot continue tried to mount Which steps will resolve the problem？（）A.Reboot the server into maintenance mode and run ‘fsck’ with the ‘-p’ parameter while the filesystem is mounted.B.Reboot the server into maintenance mode and run ‘fsck’ with the ‘-y’ parameter while the filesystem is unmounted.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.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.

单项选择题

An administrator is attempting to recover a filesystem that fails to manually unmount. The fsck command produces the following output：
The current volume is： /dev/fslv02
File system is currently mounted.
Invalid file system size in the primary superblock.
Invalid file system size in the secondary superblock.
Primary superblock is corrupt. Secondary superblock is corrupt.
fsck： 0507-018 Superblock is corrupt and cannot be repaired.
Both primary and secondary copies are corrupt.Cannot continue
tried to mount
Which steps will resolve the problem？（）

A.Reboot the server into maintenance mode and run ‘fsck’ with the ‘-p’ parameter while the filesystem is mounted.
B.Reboot the server into maintenance mode and run ‘fsck’ with the ‘-y’ parameter while the filesystem is unmounted.
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.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.

IBM(000-104)