Date: Thu, 5 Nov 2009 18:29:43 GMT From: jh@FreeBSD.org To: tt@kyon.de, jh@FreeBSD.org, jh@FreeBSD.org, freebsd-bugs@FreeBSD.org Subject: Re: bin/127932: [unionfs] mkdir -p PATH fails if a directory in PATH is on a read-only unionfs Message-ID: <200911051829.nA5IThLj068103@freefall.freebsd.org>
next in thread | raw e-mail | index | archive | help
Old Synopsis: [patch] mkdir(1): mkdir -p PATH fails if a directory in PATH is on a read-only fs New Synopsis: [unionfs] mkdir -p PATH fails if a directory in PATH is on a read-only unionfs State-Changed-From-To: feedback->analyzed State-Changed-By: jh State-Changed-When: Thu Nov 5 18:20:45 UTC 2009 State-Changed-Why: Now I see how this can happen with unionfs: unionfs_lookup() returns EROFS for CREATE namei operation when unionfs is mounted as read-only even if the file exists. I consider this a kernel (unionfs) problem and I don't think it's sensible to patch mkdir(1). Responsible-Changed-From-To: jh->freebsd-bugs Responsible-Changed-By: jh Responsible-Changed-When: Thu Nov 5 18:20:45 UTC 2009 Responsible-Changed-Why: Back to pool. http://www.freebsd.org/cgi/query-pr.cgi?pr=127932
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200911051829.nA5IThLj068103>