[CentOS] unattended fsck on reboot
R P Herrold
herrold at owlriver.comThu Feb 18 15:42:00 UTC 2010
- Previous message: [CentOS] unattended fsck on reboot
- Next message: [CentOS] unattended fsck on reboot
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On Thu, 18 Feb 2010, Kai Schaetzl wrote: > Rudi Ahlers wrote on Thu, 18 Feb 2010 10:54:11 +0200: > >> The server booted up, ran fsck, then each VM, as it booted up ran fsck as >> well - which just slowed down the whole process since there's a 5 minute >> delay in starting each VM. > > Why would you autostart a VM only every 5 minutes? Or did you mean the next > one only started once the earlier one had finished fsck? As mine aren't doing > this I haven't ever seen that. We found (suffered) a 'thundering herd' effect in autostarting all domU's at once where 20 or more were present, and so added control logic to stagger such starts after a reboot (and also track running/stopped state outside of dropping links in the /etc/xen/ directory hierarchy) -- Russ herrold
- Previous message: [CentOS] unattended fsck on reboot
- Next message: [CentOS] unattended fsck on reboot
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the CentOS mailing list