Fsck linux how long does it take
Logout Register. How long should fsck run? It has been working fine for a long time. Just for fun I know, I know I decided to try running fsck. I created a file named forcefsck in the root directory and rebooted. That was about 16 hours ago. The Pi is showing a burst of SSD activity about once per second. That's all.
It's headless, so I don't know if there are any progress messages from fsck if indeed it provides any. That's not really a long-term scaleable solution and would end up costing you more than a decent RAID. But it might be a quick fix if you have drives lying around.
For any solution involving hard disk drives, make sure they have a fast rotation speed and low seek latency. Your File Server disk should be doing a lot of seek as the other guys said. Smart will give you some results. If you're sending a hdparm to HDD that is mounted with concurrent access, that could be the answer why your results are a lot less than before.
Sign up to join this community. The best answers are voted up and rise to the top. Stack Overflow for Teams — Collaborate and share knowledge with a private group.
Create a free Team What is Teams? Learn more. How long does it take to fsck a volume? Ask Question. Asked 9 years, 8 months ago. Active 5 years, 11 months ago. Viewed 57k times. So now we want to run fsck to fix the disk problem. Will fsck will solve this issue? The manual fsck on each drive and manual database rebuild fixed everything. Previous Topic Index Next Topic. Print Topic Switch to Threaded Mode. Generated in 0. Zlib compression enabled.
Powered by UBB. You are not logged in. Topic Options. Moved from Off Topic. Toggle navigation. Sorry, you are not logged in. Your login session has expired. Please click on the link below to re-login to support.
Summary This article discusses the factors that play into how long fsck can take to run on an LMI appliance but there is no exact way to calculate it. The duration is more of an unknown for EVAs because Tibco does not provide the hardware for those so disk performance will differ for everyone.
Details Details. If you have rebooted or just powered on your system and the system has booted up but has not yet reached the login stage after the normal amount of time it takes to reach that point then an fsck may have been triggered.
This occurs because either the of mounts for a given filesystem exceeded the max mount count or because more than 6 months has elapsed since the last fsck for a mount point.
0コメント