[jboss-jira] [JBoss JIRA] (WFCORE-1309) Applying patch - "no space available" not specific enough
Tomas Hofman (JIRA)
issues at jboss.org
Tue Jan 19 08:45:01 EST 2016
[ https://issues.jboss.org/browse/WFCORE-1309?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Tomas Hofman moved JBEAP-2882 to WFCORE-1309:
---------------------------------------------
Project: WildFly Core (was: JBoss Enterprise Application Platform)
Key: WFCORE-1309 (was: JBEAP-2882)
Workflow: GIT Pull Request workflow (was: CDW v1)
Component/s: Patching
(was: Patching)
Target Release: (was: 7.0.0.GA)
Affects Version/s: 2.0.7.Final
(was: 7.0.0.ER3)
> Applying patch - "no space available" not specific enough
> ---------------------------------------------------------
>
> Key: WFCORE-1309
> URL: https://issues.jboss.org/browse/WFCORE-1309
> Project: WildFly Core
> Issue Type: Bug
> Components: Patching
> Affects Versions: 2.0.7.Final
> Reporter: Tomas Hofman
> Assignee: Tomas Hofman
>
> Copy of https://bugzilla.redhat.com/show_bug.cgi?id=1299160:
> Patch apply can fail if there is not enough free space, however the message does not indicate what device does not have any free space. Users assume there is not enough free space on the drive where the JBoss install they are applying the patch to, however it appears this may or may not be the case.
> Patch apply uses tmp space and if there is not enough tmp space it will fail with this message as well. The message should be more explicit as to where there is no space so that the user knows which drive to check.
> [disconnected /] patch apply /path/to/jboss-eap-6.2.4-patch.zip
> java.io.IOException: No space left on device
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
More information about the jboss-jira
mailing list