after a machine crash on v249 before closing it but saving the vfs v249.
with a kernel check error alert on a first reboot.
it opened again on the vfs v248, it need to load the vfs v249, close HFS to take and write the change. (as usual)
i reverted to 248 because it was giving a better response time than 249 (before the first close).
from this page:
http://audio-planet-deluxe.eu (a 1&1 domain hosting normally not too far)
about 5mn using 249
30s using 248
Updating to 249, save the vfs, close hfs and open it again seems to work better now.
Maybe a few bot sensible on start,
65.36.241.76 internetseer.com is not cool for HFS
china telecom use also a lot of slots on many ports at the same time and it freeze HFS during few minutes.
cut the internet connection need a few time to reset HFS when it freeze, but it is faster than close and load again the vfs.