You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@netbeans.apache.org by "Bradley Willcott (Jira)" <ji...@apache.org> on 2019/12/24 10:19:00 UTC
[jira] [Comment Edited] (NETBEANS-3582) Not enough space to
download and unpack index for Maven 'Central Repository'
[ https://issues.apache.org/jira/browse/NETBEANS-3582?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17002768#comment-17002768 ]
Bradley Willcott edited comment on NETBEANS-3582 at 12/24/19 10:18 AM:
-----------------------------------------------------------------------
Thank you Lazlo. That was it. The Maven Central repository WAS using /tmp to not only hold the downloaded zip file, but was also unpacking it into /tmp as it recreated the files into the final directories, else where. Total space usage was over 1.7Gb, maybe more.
"df -h" showed that the /tmp dir was being set as a "tmpfs". My laptop currently only has 4Gb RAM with which to use. After some more research I found out that the /tmp dir is setup by "systemd". Since the _tmpfs_ limit was 1.9Gb, including the other directories using this space ...
My solution is as follows:
{code:java}
$ systemctl mask tmp.mount //stops systemd from mounting /tmp as a tmpfs, leaving it using the block device
$ sudo nedit /usr/lib/tmpfiles.d/tmp.conf
{code}
This is my current "tmp.conf":
{noformat}
# This file is part of systemd.
#
# systemd is free software; you can redistribute it and/or modify it
# under the terms of the GNU Lesser General Public License as published by
# the Free Software Foundation; either version 2.1 of the License, or
# (at your option) any later version.
# See tmpfiles.d(5) for details
# Clear tmp directories separately, to make them easier to override
#q /tmp 1777 root root 10d
D! /tmp 1777 root root 0
q /var/tmp 1777 root root 30d
{noformat}
The line beginning: "#q /tmp ..." was originally "q /tmp ..." and active.
Now the line: "D! /tmp ..." has replaced it.
The difference is that as the contents of /tmp is now being stored on the HDD instead of RAM, it needs to be cleared,
ideally at boot time. This line does that.
I hope this information is of some use to others in the future.
Thanks guys.
was (Author: bwillcott):
Thank you Lazlo. That was it. The Maven Central repository WAS using /tmp to not only hold the downloaded zip file, but was also unpacking it into /tmp as it recreated the files into the final directories, else where. Total space usage was over 1.7Gb, maybe more.
"df -h" showed that the /tmp dir was being set as a "tmpfs". My laptop currently only has 4Gb RAM with which to use. After some more research I found out that the /tmp dir is setup by "systemd". Since the _tmpfs_ limit was 1.9Gb, including the other directories using this space ...
My solution is as follows:
{code:java}
$ systemctl mask tmp.mount //stops systemd from mounting /tmp as a tmpfs, leaving it using the block device
$ sudo nedit /usr/lib/tmpfiles.d/tmp.conf
{code}
This is my current "tmp.conf":
{noformat}
# This file is part of systemd.
#
# systemd is free software; you can redistribute it and/or modify it
# under the terms of the GNU Lesser General Public License as published by
# the Free Software Foundation; either version 2.1 of the License, or
# (at your option) any later version.
# See tmpfiles.d(5) for details
# Clear tmp directories separately, to make them easier to override
#q /tmp 1777 root root 10d
D! /tmp 1777 root root 0
q /var/tmp 1777 root root 30d
{noformat}
The line beginning: "#q /tmp ..." was originally "q /tmp ..." and active.
Now the line: "D! /tmp ..." has replaced it.
The difference is that as the contents of /tmp is now being stored on the HDD instead of RAM, it needs to be cleared,
ideally at boot time. This line does that.
I hope this information is of some use to other in the future.
Thanks guys.
> Not enough space to download and unpack index for Maven 'Central Repository'
> ----------------------------------------------------------------------------
>
> Key: NETBEANS-3582
> URL: https://issues.apache.org/jira/browse/NETBEANS-3582
> Project: NetBeans
> Issue Type: Bug
> Affects Versions: 11.2
> Environment: Operating System: Fedora 31
> KDE Plasma Version: 5.16.5
> KDE Frameworks Version: 5.64.0
> Qt Version: 5.12.5
> Kernel Version: 5.3.14-300.fc31.x86_64
> OS Type: 64-bit
> Processors: 4 × Intel® Core™ i7-5500U CPU @ 2.40GHz
> Memory: 3.7 GiB of RAM
> Reporter: Bradley Willcott
> Priority: Major
> Labels: Maven
> Fix For: 11.2
>
> Attachments: UI-Log.xml
>
>
> Both the automatic download process that occurs when you create a Maven project, and in the 'Services' tab for Maven, of the index completes up to the point of unpacking. Looking at the exception info I can only assume that Netbeans doesn't know that 491Gb is larger than 802Mb! Unless the zip file unpacks out to over 491Gb?!?! If this is so, then how can ANYONE develop a Maven based project. I would not expect everyone to have _this_ must free disk space.
>
> ================================================================
> [indexing] ERROR org.apache.maven.index.updater.DefaultIndexUpdater - Fallback to *.zip also failed: java.io.FileNotFoundException: Resource nexus-maven-repository-index.zip does not exist
> INFO [org.netbeans.modules.maven.indexer.NexusRepositoryIndexerImpl]: Downloaded maven index file has size 802,161,664 (zipped). The usable space in /home/bwillcott/.cache/netbeans/11.2 is 491,860,180,992.
> INFO [org.netbeans.modules.maven.indexer.NexusRepositoryIndexerImpl]
> java.io.IOException: No space left on device
> ================================================================
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@netbeans.apache.org
For additional commands, e-mail: commits-help@netbeans.apache.org
For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists