On Thu, 24 May 2018, Xen wrote:
- loop device "gone" = 0
- loop device "gone" after multiple hours = EIO.
I don't know if anyone is on this list, but I guess the issue must come
from (inode) caching; I was using a FUSE filesystem I mean,
but I can't figure out why the cache would be so long, however I'm not
kernel compiling currently, so I can't check much.
In any case FUSE has a dentry and inode timeout and it seems possible that
that would cause a delayed error,
it's just a tad weird that cache would be longer than 6 hours.
loop.c merely queries the VFS, the VFS in this case queries FUSE, which
queries the underlying,
FUSE has some code that can create a fake inode and return -EIO
which is probably then the source of this phenomenon.
--
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs
