0

today we notice about very strange issue

the following partition ( from /etc/fstab) defined with "2" in the end of the line

that means that fsck will be activate during boot

since the data on that partition is 24T

that means that reboot should be take around couple hours or more

but reboot actually takes 4 min !!!

from /etc/fstab

“UUID=7eab43c-41ba-1331-8ab7-a538326a5b8e /BD_APP    xfs     rw,noatime,inode64,allocsize=16m 1 2”

how we explian this strange thing?

why fsck was not "on" during boot ?

  • Will this answer help? It is for ext4 file system, but may have useful info. – jc__ May 2 '18 at 13:25
2

according to man fsck.xfs

XFS is a journaling filesystem and performs recovery at mount(8) time if necessary, so fsck.xfs simply exits with a zero exit status.

as man suggest try xfs_repair

There is no need to fsck as recovery is performed at mount time.

  • so let me summary what you said , what is configured in my fstab will not do nothing ( its mean fsck will not performed ) , second in order to do real fsck to /dev/sdb we need to do xfs_repair , am I correct ? – yael May 2 '18 at 11:53
  • +1 for your answer , – yael May 2 '18 at 11:57
  • second question , if this is the case then what we need to change in the fstab to perform fsck during boot ? – yael May 2 '18 at 12:01
  • another note we have redhat version 6.x – yael May 2 '18 at 12:01

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.