Local storage will not repair after XenServer is rebooted.

1. To verify if a file system check is in progress, use the Linux command ps –ef | grep fsck.
   • If you only see the last line in the image below (grep fsck), then there is no file system check in progress. Proceed to the next step.
   • If you do see something with “fsck –a /dev/…”, then there is a file system check in progress and you should not attempt a repair of the storage. You should periodically run the same command, until you see no “fsck –a …” running as shown in the following screenshot.

2. With the last command, you can now perform a “repair” on storage repository (SR) called “Local Storage 2”:

1. Another way to verify if a file system check is in progress, is to examine the XenServer Storage Management log file (/var/log/SMlog) as shown in the following screenshot:

In the above image, you will see the “cat SMlog | grep fsck”, which confirms what you saw with Linux “ps –ef” command earlier.

Problem Cause

On hosts with high uptime (over 90 days), a file system check is forced by Linux control VM (domain 0) on file system. This is by design with open-source Linux and is not specific to XenServer.