[
https://issues.apache.org/jira/browse/HADOOP-6284?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tsz Wo (Nicholas), SZE resolved HADOOP-6284.
--------------------------------------------
Resolution: Fixed
I have committed this. Thanks, Koji!
> Any hadoop commands crashing jvm (SIGBUS) when /tmp (tmpfs) is full
> --------------------------------------------------------------------
>
> Key: HADOOP-6284
> URL: https://issues.apache.org/jira/browse/HADOOP-6284
> Project: Hadoop Common
> Issue Type: Improvement
> Components: scripts
> Reporter: Koji Noguchi
> Assignee: Koji Noguchi
> Priority: Minor
> Attachments: hadoop-6284-patch-v1.txt
>
>
> {noformat}
> [knoguchi@ ~]$ df /tmp
> Filesystem 1K-blocks Used Available Use% Mounted on
> tmpfs 524288 524288 0 100% /tmp
> [knoguchi@ ~]$ hadoop dfs -ls
> #
> # An unexpected error has been detected by Java Runtime Environment:
> #
> # SIGBUS (0x7) at pc=0x00824077, pid=19185, tid=4160617360
> #
> # Java VM: Java HotSpot(TM) Server VM (10.0-b22 mixed mode linux-x86)
> # Problematic frame:
> # C [libc.so.6+0x6e077] memset+0x37
> #
> # An error report file with more information is saved as:
> # /homes/knoguchi/hs_err_pid19185.log
> #
> # If you would like to submit a bug report, please visit:
> # http://java.sun.com/webapps/bugreport/crash.jsp
> #
> Aborted
> [knoguchi@ ~]$
> {noformat}
> This does not happen when /tmp is not in tmpfs.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
