On Fri, Apr 21, 2017 at 9:44 PM, J. R. Okajima <hooanon05g@xxxxxxxxx> wrote: > Miklos Szeredi: >> OTOH lost+found is just a plain old directory that is handled by >> userspace tools only. No kernel fs driver treats /lost+found >> specially. So putting this in upperdir would be a namespace pollution >> issue and generally we'd like to avoid that. Aufs has lived with that >> sort of thing, and probably it wouldn't be a problem in practice. But > > ?? > As far as I know, aufs doesn't handle lost+found specially, but the > layer fs handles. What is the "namespace pollution" you call? > That would be names of files reserved for use by fs that user cannot use (i.e. .wh. files). Miklos did not mean that aufs handles lost+found, but that it lives without a problem with reserved filenames. Anyway, I do agree that avoiding namespace pollution should be avoided if possible. Cheers, Amir. -- To unsubscribe from this list: send the line "unsubscribe linux-unionfs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
