On Wednesday 31 March 2010 14:41:53 David Howells wrote: > Romain DEGEZ <romain.degez@xxxxxxxxxxxx> wrote: > > [ 4868.465413] CacheFiles: I/O Error: Unlink failed > > I'm at a bit of a loss to explain why Ext4 returned EIO. > > Sticking an extra call to vfs_unlink() to try and delete the file twice > results in ENOENT on the second call, not EIO. > > The only path out of ext4_unlink() that results in EIO without some sort of > error message is: > > retval = -EIO; > if (le32_to_cpu(de->inode) != inode->i_ino) > goto end_unlink; > > The good news is that I've found a way to reproduce it. > > David Hi, So you think this is related to ext4 ? I switched 2 of the 4 servers to use an ext3 back-end for the cache. Will see if it is still happening. Regards, -- RD -- Linux-cachefs mailing list Linux-cachefs@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/linux-cachefs
