LiuLei, Using your example you can run umount -l /disk10 ( Lower case L ) on the disk and it will lazy dismount and will not wait for a disconnect.
Thanks, --- Brandon Freeman System Engineer Explorys, Inc. 8501 Carnegie Ave., Suite 200 Cleveland, OH 44106 http://www.explorys.com<http://www.explorys.com/> | 216-235-5021 From: Arpit Agarwal <aagar...@hortonworks.com<mailto:aagar...@hortonworks.com>> Reply-To: "user@hadoop.apache.org<mailto:user@hadoop.apache.org>" <user@hadoop.apache.org<mailto:user@hadoop.apache.org>> Date: Thursday, February 13, 2014 12:09 PM To: "u...@hbase.apache.org<mailto:u...@hbase.apache.org>" <u...@hbase.apache.org<mailto:u...@hbase.apache.org>> Subject: Fwd: umount bad disk bcc'ed hadoop-user Lei, perhaps hbase-user can help. ---------- Forwarded message ---------- From: lei liu <liulei...@gmail.com<mailto:liulei...@gmail.com>> Date: Thu, Feb 13, 2014 at 1:04 AM Subject: umount bad disk To: user@hadoop.apache.org<mailto:user@hadoop.apache.org> I use HBase0.96 and CDH4.3.1. I use Short-Circuit Local Read: <property> <name>dfs.client.read.shortcircuit</name> <value>true</value></property><property> <name>dfs.domain.socket.path</name> <value>/home/hadoop/cdh4-dn-socket/dn_socket</value></property> When one disk is bad, because the RegionServer open some file on the disk, so I don't run "umount", example: sudo umount -f /disk10 umount2: Device or resource busy umount: /disk10: device is busy umount2: Device or resource busy umount: /disk10: device is busy I must stop RegionServer in order to run umount command. How can don't stop RegionServer and delete the bad disk. Thanks, LiuLei CONFIDENTIALITY NOTICE NOTICE: This message is intended for the use of the individual or entity to which it is addressed and may contain information that is confidential, privileged and exempt from disclosure under applicable law. If the reader of this message is not the intended recipient, you are hereby notified that any printing, copying, dissemination, distribution, disclosure or forwarding of this communication is strictly prohibited. If you have received this communication in error, please contact the sender immediately and delete it from your system. Thank You.
