EC2: How dangerous is it to turn off fsck for EBS volumes?
- by Janine
I have been tearing my hair out trying to figure out why my EC2 instances (made from my own custom AMIs) were taking many tries to come up properly. They would fail with the following error:
fsck.ext3: No such file or directory while trying to open /dev/sdf
For both of the EBS volumes I was attaching during startup.
Finally, I figured out the problem. I had put this in /etc/fstab:
/dev/sdf /export ext3 defaults 1 2
/dev/sdi /export2 ext3 defaults 1 2
The 2 tells the system to fsck the drives on the way up. Changing this to
/dev/sdf /export ext3 defaults 1 0
/dev/sdi /export2 ext3 defaults 1 0
Avoids the problem completely, but now the volumes are never going to be fsck'd. How much does this matter? Once the instance goes into production it's going to be running pretty much 24/7, so not many fscks would be happening anyway, but still... this just feels like a bad idea.
I have not been able to find anyone else even reporting this problem (there are people with the same error message, but different causes). It seems unbelievable that I could be the only person to ever make this mistake, but perhaps I'm just talented that way. :) If there is another solution to the problem I would love to hear it; I have not been able to find one.
