blocks|key|200337|text|如果目录中已存在同名的文件，则可能会导致此问题。|type|unstyled|depth|inlineStyleRanges|offset|length|style|BOLD|entityRanges|data|200338|请注意，在linux计算机上，一个目录不能同时包含同名的文件和文件夹。|200339|entityMap^0|B|2|0|0^^$0|@$1|2|3|4|5|6|7|J|8|@$9|K|A|L|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|M|8|@]|D|@]|E|$]]|$1|H|3|-4|5|6|7|N|8|@]|D|@]|E|$]]]|I|$]]

This could be caused if there is already a file by the same name located in the directory.
Note that a directory cannot contain both a file and folder by the same name on linux machines.

blocks|key|200350|text|检查是否存在与$directory同名的文件(不是目录)。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|200351|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

Check to see if there is a file (not a directory) with a name same as $directory.

blocks|key|200356|text|如果在同一目录下存在同名文件，则mkdir+-p不会创建目录。否则，它将按预期工作。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|200357|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

mkdir -p won't create directory if there is a file with the same name is existing in the same directory. Otherwise it will work as expected.

blocks|key|202666|text|您的目录是否碰巧是FUSE-based网络挂载？|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|202667|除了具有该名称的文件已经存在(其他答案)之外，当曾经在此目录中挂载某些内容的熔丝进程使崩溃(或被杀死，例如使用kill+-9或通过Linux+OOM杀手)时，可能会发生这种情况。|style|BOLD|CODE|202668|要查看正在发生的详细情况，请运行strace+-fy+mkdir+-p+$directory，它会显示所有涉及的syscall及其返回值。|202669|202670|我认为在这种情况下发出的错误消息是mkdir+-p+(特别是gnulib库)中的一个错误：|202671|当您在挂载了FUSE进程但该进程崩溃的dir上运行它时，它会说|202672|mkdir:+cannot+create+directory+‘/mymount’:+File+exists|code-block|syntax|javascript|202673|这是非常不准确的，因为the+underlying+stat()调用返回ENOTCONN+(Transport+endpoint+is+not+connected)；但是mkdir向上传播来自the+previous+mkdir()+sycall的不太具体的错误。它特别令人困惑，因为手册页上说：|202674|+++-p,+--parents
++++++++++no+error+if+existing,+make+parent+directories+as+needed|202675|因此，如果目录存在，它应该不会出错，但ls+-l+/显示：|202676|d?????????+?+?++++?+++++++?++++++++++++?+files|202677|所以根据这个(d)，它是一个目录，但它不是根据test+-d。|202678|202679|我认为更好的错误消息(本例中mkdir+-p应该发出的错误消息)应该是：|202680|mkdir:+cannot+create+directory+‘/mymount’:+Transport+endpoint+is+not+connected|202681|entityMap|0|LINK|mutability|MUTABLE|url|https://en.wikipedia.org/wiki/Filesystem_in_Userspace|1|http://git.savannah.gnu.org/cgit/gnulib.git/tree/lib/mkdir-p.c?id=a02a6f2e1dcad63999954bb72825a084800742ae#n152|2|http://git.savannah.gnu.org/cgit/gnulib.git/tree/lib/mkdir-p.c?id=a02a6f2e1dcad63999954bb72825a084800742ae#n130^0|9|4|0|0|8|6|12|5|1J|7|0|G|U|0|0|H|8|U|6|0|0|0|Q|6|10|1A|2D|5|31|7|B|L|1|2O|R|2|0|0|J|7|0|0|7|1|N|7|0|0|E|8|0|0^^$0|@$1|2|3|4|5|6|7|1L|8|@]|9|@$A|1M|B|1N|1|1O]]|C|$]]|$1|D|3|E|5|6|7|1P|8|@$A|1Q|B|1R|F|G]|$A|1S|B|1T|F|G]|$A|1U|B|1V|F|H]]|9|@]|C|$]]|$1|I|3|J|5|6|7|1W|8|@$A|1X|B|1Y|F|H]]|9|@]|C|$]]|$1|K|3|-4|5|6|7|1Z|8|@]|9|@]|C|$]]|$1|L|3|M|5|6|7|20|8|@$A|21|B|22|F|H]|$A|23|B|24|F|H]]|9|@]|C|$]]|$1|N|3|O|5|6|7|25|8|@]|9|@]|C|$]]|$1|P|3|Q|5|R|7|26|8|@]|9|@]|C|$S|T]]|$1|U|3|V|5|6|7|27|8|@$A|28|B|29|F|H]|$A|2A|B|2B|F|H]|$A|2C|B|2D|F|H]|$A|2E|B|2F|F|H]]|9|@$A|2G|B|2H|1|2I]|$A|2J|B|2K|1|2L]]|C|$]]|$1|W|3|X|5|R|7|2M|8|@]|9|@]|C|$S|T]]|$1|Y|3|Z|5|6|7|2N|8|@$A|2O|B|2P|F|H]]|9|@]|C|$]]|$1|10|3|11|5|R|7|2Q|8|@]|9|@]|C|$S|T]]|$1|12|3|13|5|6|7|2R|8|@$A|2S|B|2T|F|H]|$A|2U|B|2V|F|H]]|9|@]|C|$]]|$1|14|3|-4|5|6|7|2W|8|@]|9|@]|C|$]]|$1|15|3|16|5|6|7|2X|8|@$A|2Y|B|2Z|F|H]]|9|@]|C|$]]|$1|17|3|18|5|R|7|30|8|@]|9|@]|C|$S|T]]|$1|19|3|-4|5|6|7|31|8|@]|9|@]|C|$]]]|1A|$1B|$5|1C|1D|1E|C|$1F|1G]]|1H|$5|1C|1D|1E|C|$1F|1I]]|1J|$5|1C|1D|1E|C|$1F|1K]]]]

Was your directory a <a href="https://en.wikipedia.org/wiki/Filesystem_in_Userspace" rel="nofollow noreferrer">FUSE</a>-based network mount by any chance?

In addition to a file with that name already existing (other answer), this can happen when a FUSE process that once mounted something at this directory crashed (or was killed, e.g. with <code>kill -9</code> or via the Linux OOM killer).

To see what is happening in detail, run <code>strace -fy mkdir -p $directory</code>, which shows all syscalls involved and their return values.

<hr>

I consider the error messages emitted in this case a bug in <code>mkdir -p</code> (in particular the <code>gnulib</code> library):

When you run it on a dir that had a FUSE process mounted but that process crashed, it says

<pre><code>mkdir: cannot create directory ‘/mymount’: File exists
</code></pre>

which is rather highly inaccurate, because <a href="http://git.savannah.gnu.org/cgit/gnulib.git/tree/lib/mkdir-p.c?id=a02a6f2e1dcad63999954bb72825a084800742ae#n152" rel="nofollow noreferrer">the underlying <code>stat()</code></a> call returns <code>ENOTCONN (Transport endpoint is not connected)</code>; but <code>mkdir</code> propagates up the less-specific error from <a href="http://git.savannah.gnu.org/cgit/gnulib.git/tree/lib/mkdir-p.c?id=a02a6f2e1dcad63999954bb72825a084800742ae#n130" rel="nofollow noreferrer">the previous <code>mkdir()</code> sycall</a>.
It's extra confusing because the man page says:

<pre><code> -p, --parents
 no error if existing, make parent directories as needed
</code></pre>

so it shouldn't error if the dir exists, yet <code>ls -l /</code> shows:

<pre><code>d????????? ? ? ? ? ? files
</code></pre>

so according to this (<code>d</code>), it is a directory, but it isn't according to <code>test -d</code>.

<hr>

I believe a better error message (which <code>mkdir -p</code> should emit in this case) would be:

<pre><code>mkdir: cannot create directory ‘/mymount’: Transport endpoint is not connected
</code></pre>

On one of our remote systems <code>mkdir -p $directory</code> fails when the directory exists. which means it shows 

<blockquote>
 mkdir: cannot create directory '$directory' : file exists
</blockquote>

This is really puzzling, as I believed the contract of <code>-p</code> was that is always succeed when the directory already exists. And it works on the other systems I tried.

there is a user <code>test</code> on all of these systems, and <code>directory=/home/test/tmp</code>.

mkdir -p fails when directory exists

Linux

在我们的一个远程系统上，当目录存在时，mkdir -p $directory会失败。这意味着它显示了 mkdir:无法创建目录'$directory‘：文件已存在这真的很令人费解，因为我相信当目录已经存在时，-p的契约总是成功的。它在我尝试过的其他系统上也能正常工作。所有这些系统上都有一个用户test和directory=/home/test/tmp。

问目录存在时mkdir -p失败
EN

回答 4

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问目录存在时mkdir -p失败EN

回答 4

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问目录存在时mkdir -p失败
EN