2011/12/1 Chris Dunlop <chris@xxxxxxxxxxxx>: [!snip] >> I'm also not sure about the printk in the NFS case. Instead of littering >> the logs, we should probably just disallow the stacked filesystem (are >> we talking about eCryptfs here?) from mounting on top of NFS in the >> first place. > > See other reply: it wasn't a stacked file system. I've actually hit the same think with NFS on vanilla 2.6.39.4. There was no stacked fs on top as this host is only running Jenkins master instance where few jar are on NFS homedir mounted by autofs. As there's no way I could actually wait for Al patches what is then the best way to limit this issue (BTW: I was not able to reproduce this anywhere yet)? The gentle msg info and -EIO sound like good idea until we will be suck up by black hole. -Jacek -- To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
