Teo, If you are using glusterfs--mainline--2.4, please add to the write-behind 'option flush-behind off' and if needed 'option transport-timeout <secs>' to protocol/client volumes (where <secs> is sufficiently large enough). the optoin flush-behind should most likely fix your error. Instead you could just tla update to the latest patch (patch-184) and the errors should disappear. thanks, avati
I have cleared all the binaries and libraries from previous install. > Double checked-it with updatedb and "locate glus". Only client.vol > configuration file waws kept. > > Made a fully fresh install, no problem. > Activated writebehind again, started from scratch, at first attempt to > vacuum the database, error. > >
-- Anand V. Avati
