Comment 13 for bug 1103047

Bruno, could you please attach the boot.log in question? I need to see the entirety of what mountall is doing to understand what's really going wrong. It's normal that mountall will attempt to mount all filesystems ASAP after boot, which means sometimes it tries to mount them before the network is up; then it will retry the mount for each network interface that's brought up. So seeing the full log will show which part isn't working correctly.

One possibility is that glusterfs is taking so long to fail to mount, that between the time the mount fails and it actually notifies mountall that it /has/ failed, all the network interface events have already gone past. But

> The only thing is that actually my /var/log is a dedicated partition
> like often on servers.

I don't think this is a very common configuration at all. I don't see any reason to have /var/log separate from the rest of /var. On the other hand, I'm not aware of any services that would currently have problems with this except for glusterfs.