I'm seeing same interesting errors running against a server from a big NAS vendor that shall remain unnamed: p224160.955651] CIFS VFS: Unexpected lookup error -5 [224161.298853] CIFS VFS: Unexpected lookup error -5 [224161.643559] CIFS VFS: Unexpected lookup error -5 [224161.992309] CIFS VFS: Unexpected lookup error -5 [224162.333310] CIFS VFS: Unexpected lookup error -5 [224162.677982] CIFS VFS: Unexpected lookup error -5 Unfortunately it seems like a EIO is the catchall for unknown SMB errors, so trying to debug this seems a bit hard. Should we maybe look into propagating the SMB error codes further up the chain inside the cifs driver instead of converting them at a fairly low level? -- To unsubscribe from this list: send the line "unsubscribe linux-cifs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
