> Ok. Problem solved. > We were mounting the file system with: > > mount -t glusterfs -o volume-name=cache /etc/glusterfs/replicatedb.vol > /mnt/replicate > > So I dropped the db and the tablespace and remounted the gluster share as: > > mount -t glusterfs -o volume-name=replicate /etc/glusterfs/replicatedb.vol > /mnt/replicate > > After that our full database restore completed with no errors. > This is a great thing! > As you can see the volume-name=cache references write-behind, which seemed > to be causing the problems. > volume-name=cache references io-cache and write-behind. Can you try with volume-name=write-behind and see if things work? That way we can corner the issue to be in io-cache specifically. Avati
