blocks|key|266816|text|您的默认临时目录似乎具有错误的权限。这是我的|type|unstyled|depth|inlineStyleRanges|entityRanges|data|266817|$+ls+-ld+/tmp
drwxrwxrwt+22+root+root+4096+2011-06-10+09:17+/tmp|code-block|syntax|javascript|266818|关键部分是“每个人”都可以读或写。你也需要这样做。它当然可以包含子目录。|266819|您运行的是AppArmor或SE+Linux之类的操作系统吗？|266820|编辑2011-07-21:因为有人认为有必要否决这个答案--+help(tempfile)非常清楚tmpdir+(临时文件或目录的默认目录)尝试的值：|offset|length|style|CODE|266821|266822|默认情况下，'tmpdir'将是'tempdir()'提供的目录。这将是通过以下规则找到的临时目录的子目录。依次检查环境变量'TMPDIR'、'TMP'和'TEMP'，并使用第一个找到的指向可写目录的变量:如果都没有成功，则使用'/tmp'。|blockquote|266823|266824|266825|所以我把钱花在检查这三个环境变量上。但在一些发行版上，AppArmor和SELinux也是一个问题。|266826|entityMap^0|0|0|0|0|V|E|1D|6|0|0|6|8|G|B|1Q|8|1Z|5|25|6|36|6|0|0|0|0^^$0|@$1|2|3|4|5|6|7|10|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|11|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|12|8|@]|9|@]|A|$]]|$1|I|3|J|5|6|7|13|8|@]|9|@]|A|$]]|$1|K|3|L|5|6|7|14|8|@$M|15|N|16|O|P]|$M|17|N|18|O|P]]|9|@]|A|$]]|$1|Q|3|-4|5|6|7|19|8|@]|9|@]|A|$]]|$1|R|3|S|5|T|7|1A|8|@$M|1B|N|1C|O|P]|$M|1D|N|1E|O|P]|$M|1F|N|1G|O|P]|$M|1H|N|1I|O|P]|$M|1J|N|1K|O|P]|$M|1L|N|1M|O|P]]|9|@]|A|$]]|$1|U|3|-4|5|6|7|1N|8|@]|9|@]|A|$]]|$1|V|3|-4|5|6|7|1O|8|@]|9|@]|A|$]]|$1|W|3|X|5|6|7|1P|8|@]|9|@]|A|$]]|$1|Y|3|-4|5|6|7|1Q|8|@]|9|@]|A|$]]]|Z|$]]

Your default temporary directory appears to have the wrong permissions. Here I have

<pre><code>$ ls -ld /tmp
drwxrwxrwt 22 root root 4096 2011-06-10 09:17 /tmp
</code></pre>

The key part is 'everybody' can read or write. You need that too. It certainly can contain subdirectories.

Are you running something like AppArmor or SE Linux?

Edit 2011-07-21: As someone just deemed it necessary to downvote this answer -- <code>help(tempfile)</code> is very clear on what values <code>tmpdir</code> (the default directory for temporary files or directories) tries:

<blockquote>
 By default, <code>'tmpdir'</code> will be the directory given by <code>'tempdir()'</code>. This
 will be a subdirectory of the temporary directory found by the
 following rule. The environment variables <code>'TMPDIR'</code>, <code>'TMP'</code> and <code>'TEMP'</code>
 are checked in turn and the first found which points to a writable
 directory is used: if none succeeds <code>'/tmp'</code> is used.
</blockquote>

So my money is on checking those three environment variables. But AppArmor and SELinux have shown to be an issue too on some distributions.

blocks|key|265391|text|Dirk是对的，但忽略了一点:如果/tmp已满，则不能在其中创建子目录。试一试|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|265392|df+/tmp|code-block|syntax|javascript|265393|我刚刚在一个共享服务器上遇到了这个问题，在这个服务器上，/tmp挂载在它自己的分区上，并且由许多用户共享。在这种情况下，您不能真正看到是谁的错，因为权限限制了您查看谁在填充tmp分区。基本上必须让sys管理员来解决这个问题。|265394|entityMap^0|H|4|0|0|S|4|0^^$0|@$1|2|3|4|5|6|7|O|8|@$9|P|A|Q|B|C]]|D|@]|E|$]]|$1|F|3|G|5|H|7|R|8|@]|D|@]|E|$I|J]]|$1|K|3|L|5|6|7|S|8|@$9|T|A|U|B|C]]|D|@]|E|$]]|$1|M|3|-4|5|6|7|V|8|@]|D|@]|E|$]]]|N|$]]

Dirk is right, but misses a point: If <code>/tmp</code> is full, you can't create subdirectories there. Try

<pre><code>df /tmp
</code></pre>

I just hit this on a shared server, where <code>/tmp</code> is mounted on it's own partition, and is shared by many users. In this particular case, you can't really see who's fault it is, because permissions restrict you seeing who is filling up the tmp partition. Basically have to ask the sys admins to figure it out.

blocks|key|2959991|text|才有了这个问题，终于解决了。简单地说是一个windows权限问题。转到环境变量并查找临时文件夹的位置。然后右键单击文件夹>属性>安全性>高级>将每个人更改为完全控制>勾选“用来自此对象的可继承权限项替换所有子对象权限项”>确定>确定。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2959992|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|$]]

Just had this issue and finally solved it. Simply a windows permission issue. Go to environment variables and find the location of the temp folders. Then right click on the folder > properties > security > advanced > change everyone to full control > tick "replace all child object permission entries with inheritable permission entries from this object" > Ok > ok.

blocks|key|265437|text|转到您的用户目录，创建一个名为.Renviron的文件，添加以下行，保存它并重新打开RStudio或Rgui或Rterm|type|unstyled|depth|inlineStyleRanges|entityRanges|data|265438|TMP+=+'<path+to+folder+where+Everyone+has+full+control>'|code-block|syntax|javascript|265439|这对我在Windows+7上很有效|265440|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|K|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|L|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|M|8|@]|9|@]|A|$]]|$1|I|3|-4|5|6|7|N|8|@]|9|@]|A|$]]]|J|$]]

Go to your user directory and create a file called .Renviron and add the following line, save it and reopen RStudio or Rgui or Rterm

<pre><code>TMP = '&lt;path to folder where Everyone has full control&gt;'
</code></pre>

This worked with me on Windows 7

blocks|key|265442|text|当你的计算机完全，完全没有空间时，也会发生这种情况。目前，我的Mac有0+kb的空闲空间，它导致了这个错误。释放一些空间解决了这个问题。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|265443|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|$]]

This will also happen when your computer is completely, utterly out of space. Currently, my Mac has 0 kb free and it's causing this error. Freeing up some space solved the problem.

blocks|key|3173904|text|检查用于启动RStudio的用户帐户。现在，您可以检查TMP(系统环境变量)中它的位置。如果启动RStudio的用户对这些目录具有Write访问权限，则不会遇到此问题。也就是说，您正面临着这个问题，您所要做的就是更改该用户的权限，以便拥有对这些目录的write访问权限。|type|unstyled|depth|inlineStyleRanges|offset|length|style|BOLD|entityRanges|data|3173905|entityMap^0|R|3|1T|5|31|2|3H|5|0^^$0|@$1|2|3|4|5|6|7|H|8|@$9|I|A|J|B|C]|$9|K|A|L|B|C]|$9|M|A|N|B|C]|$9|O|A|P|B|C]]|D|@]|E|$]]|$1|F|3|-4|5|6|7|Q|8|@]|D|@]|E|$]]]|G|$]]

Check for the user account with which you are launching the RStudio with. Now u check the TMP(System Environment variable) for its location. If the user who is launching RStudio has Write access for those directories you will not face this issue. Being said that you are facing this issue, all you have to do is to change the permissions for that user to have write access on those directories.

blocks|key|2960121|text|如果您正在运行其中一个/tmp+docker镜像(例如rocker/verse)，则需要将本地目录映射到容器中的rocker目录。例如,|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|2960122|docker+run+--rm+-v+${PWD}/tmp:/tmp+-p+8787:8787+-e+PASSWORD=password+rocker/verse:4.0.4|code-block|syntax|javascript|2960123|对于我来说，${PWD}是~/devProjs/r，我在其中创建了一个/tmp目录，以便容器的/tmp映射到我的~/devProjs/r/tmp目录。|2960124|entityMap^0|B|4|R|C|0|0|6|6|D|C|Z|4|1B|4|1K|G|0^^$0|@$1|2|3|4|5|6|7|O|8|@$9|P|A|Q|B|C]|$9|R|A|S|B|C]]|D|@]|E|$]]|$1|F|3|G|5|H|7|T|8|@]|D|@]|E|$I|J]]|$1|K|3|L|5|6|7|U|8|@$9|V|A|W|B|C]|$9|X|A|Y|B|C]|$9|Z|A|10|B|C]|$9|11|A|12|B|C]|$9|13|A|14|B|C]]|D|@]|E|$]]|$1|M|3|-4|5|6|7|15|8|@]|D|@]|E|$]]]|N|$]]

If you are running one of the rocker docker images (e.g., <code>rocker/verse</code>), you need to map a local directory to the <code>/tmp</code> directory in the container. For example,
<pre><code>docker run --rm -v ${PWD}/tmp:/tmp -p 8787:8787 -e PASSWORD=password rocker/verse:4.0.4
</code></pre>
where <code>${PWD}</code> for me is <code>~/devProjs/r</code>, and I created a <code>/tmp</code> directory inside it, so that the container's <code>/tmp</code> is mapped to my <code>~/devProjs/r/tmp</code> directory.

blocks|key|2960145|text|在CentOS系统上运行R，并有相同的问题。我必须从tmp目录中删除所有R文件夹。通常，所有R文件夹的格式都是/tmp+/Rtmp*，所以我尝试通过运行以下命令从/tmp中删除这些文件夹。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2960146|CD进入/tmp目录并运行rm+-rf+Rtmp*|offset|length|style|CODE|2960147|R+shell后来为我工作|2960148|entityMap^0|0|D|C|0|0^^$0|@$1|2|3|4|5|6|7|L|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|M|8|@$D|N|E|O|F|G]]|9|@]|A|$]]|$1|H|3|I|5|6|7|P|8|@]|9|@]|A|$]]|$1|J|3|-4|5|6|7|Q|8|@]|9|@]|A|$]]]|K|$]]

Running R on CentOS system and had the same issue. I had to remove all R folders from the tmp directory. Usually all R folders will be in the form of /tmp/Rtmp*****
so i tried to delete the folders from /tmp by running the below.
CD into /tmp directory and run <code>rm -rf Rtmp*</code>
R shell Worked for me afterwards

When attempting to run R, I get this error: 

<blockquote>
 Fatal error: cannot mkdir R_TempDir
</blockquote>

I found two possible fixes for this problem by googling around. The first was to ensure my tmp directory didn't contain a load of subdirectories - it doesn't and it's virtually empty. The second fix was to ensure that TMP, TMPDIR, and R_USER in my environment weren't set to non-existent paths - I didn't even have these set. Therefore, I created a tmp directory in my home directory and added it's path to TMP in my environment. I was able to run R once and then I got the fatal error again. Nothing was in the TMP directory that I set in my environment. Does anyone know what else I can try? Thanks.

Fatal error: cannot mkdir R_TempDir

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

涵盖代码开发、场景应用、自动测试全流程，助你从零构建专属AI助手

一站式MCP教程库，解锁AI应用新玩法

当尝试运行R时，我得到这个错误：致命错误:无法mkdir R_TempDir我通过谷歌搜索找到了这个问题的两个可能的修复方法。第一个是确保我的tmp目录不包含太多的子目录--它不包含，而且实际上是空的。第二个修复是确保我的环境中的TMP、TMPDIR和R_USER没有设置为不存在的路径-我甚至没有设置这些路径。因此，我...

问致命错误:无法mkdir R_TempDir
EN

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问致命错误:无法mkdir R_TempDirEN