thanks Harsh but you didn't answer on this before, I will try to move old
directory name to new location and restart services . Hope it will not
loose any data .
old Location
$ sudo ls -l /var/lib/hadoop-hdfs/cache/hdfs/dfs/
total 12
drwx--. 3 hdfs hdfs 4096 Dec 19 02:37 data
drwxr-xr-x. 3
Hi,
The exact error is displayed on your log and should be somewhat self
explanatory:
org.apache.hadoop.hdfs.server.common.InconsistentFSStateException:
Directory /mnt/san1/hdfs/cache/hdfs/dfs/name is in an inconsistent
state: storage directory does not exist or is not accessible.
Please check
Even i created the file /mnt/san1/hdfs/cache/hdfs/dfs/name/in_use.lock and
set permission . when i restart hadoop services. It removes and I find
below logs.
Do I need to format the NN?
Below is the command to format the NN ?
Any kind of loss while formatting ?
Is there any way to avoid
After creating the directory and setting permission I tried to restart the
services and i get error /mnt/san1/hdfs/cache/hdfs/dfs/name/in_use.lock
acquired by nodename 7...@opera-mast1.ny.os.local and services are not
being started.
Need to check few logs from below logs.
Thanks Harsh, /mnt/san1/hdfs/cache/hdfs/dfs/name is not being created . If
I do compare with the older path the permissions are same on the parent
directories.
Do I need to create this this directory manually and set the permission ?
Older Path
# ll /var/lib/hadoop-hdfs/cache/hdfs/
total 4
Hi,
May i know the answer plz ?
Thanks,
On Thu, Feb 28, 2013 at 4:28 PM, Mohit Vadhera project.linux.p...@gmail.com
wrote:
Even i created the
file /mnt/san1/hdfs/cache/hdfs/dfs/name/in_use.lock and set permission .
when i restart hadoop services. It removes and I find below logs.
Do I
I believe I already responded to another one of your multiple threads
on this problem, that you have to move contents of the old dir to the
new dir and not format. Thats how one changes the dfs.name.dir
properly.
On Fri, Mar 1, 2013 at 12:11 PM, Mohit Vadhera
project.linux.p...@gmail.com wrote:
Actually, I did: http://search-hadoop.com/m/qvn7EhQQHm1. Perhaps you aren't
subscribed to the lists and wouldn't have received anything sent back.
On Fri, Mar 1, 2013 at 1:21 PM, Mohit Vadhera
project.linux.p...@gmail.comwrote:
thanks Harsh but you didn't answer on this before, I will try to
org.apache.hadoop.hdfs.server.namenode.FSNamesystem: NameNode low on
available disk space. Entering safe mode.
2013-01-21 01:22:52,218 INFO org.apache.hadoop.hdfs.StateChange: STATE*
Safe mode is ON.
On Wed, Jan 23, 2013 at 2:50 AM, Steve Loughran
steve.lough...@gmail.com wrote:
ser
104857600
2013-01-21 01:22:52,218 WARN
org.apache.hadoop.hdfs.server.namenode.FSNamesystem: NameNode low on
available disk space. Entering safe mode.
2013-01-21 01:22:52,218 INFO org.apache.hadoop.hdfs.StateChange:
STATE* Safe mode is ON.
On Wed, Jan 23, 2013 at 2:50 AM, Steve Loughran
:52,218 WARN
org.apache.hadoop.hdfs.server.namenode.FSNamesystem: NameNode low on
available disk space. Entering safe mode.
2013-01-21 01:22:52,218 INFO org.apache.hadoop.hdfs.StateChange:
STATE* Safe mode is ON.
On Wed, Jan 23, 2013 at 2:50 AM, Steve Loughran
steve.lough...@gmail.com wrote
org.apache.hadoop.hdfs.server.namenode.FSNamesystem: NameNode low on
available disk space. Entering safe mode.
2013-01-21 01:22:52,218 INFO org.apache.hadoop.hdfs.StateChange:
STATE* Safe mode is ON.
On Wed, Jan 23, 2013 at 2:50 AM, Steve Loughran
steve.lough...@gmail.com wrote:
ser
org.apache.hadoop.hdfs.server.namenode.NameNodeResourceChecker: Space
available on volume '/dev/mapper/vg_lv_root' is 10653696, which is
below
the configured reserved amount 104857600
2013-01-21 01:22:52,218 WARN
org.apache.hadoop.hdfs.server.namenode.FSNamesystem: NameNode low on
available disk space. Entering safe mode.
2013-01-21 01
on
available disk space. Entering safe mode.
2013-01-21 01:22:52,218 INFO org.apache.hadoop.hdfs.StateChange:
STATE* Safe mode is ON.
On Wed, Jan 23, 2013 at 2:50 AM, Steve Loughran
steve.lough...@gmail.com wrote:
ser@hadoop.apache.orglist
--
Harsh J
--
Harsh J
--
Harsh J
On Wed, Jan 23, 2013 at 10:37 PM, Mohit Vadhera
project.linux.p...@gmail.com wrote:
51200
51200 *bytes* is 50 KB. 50 MB is 50*1024*1024, which is 52428800. You can
verify changes to config by visiting the http://NNHOST:50070/conf page and
searching for the config key name to see if the NN has
' is 10653696, which is below
the configured reserved amount 104857600
2013-01-21 01:22:52,218 WARN
org.apache.hadoop.hdfs.server.namenode.FSNamesystem: NameNode low on
available disk space. Entering safe mode.
2013-01-21 01:22:52,218 INFO org.apache.hadoop.hdfs.StateChange: STATE*
Safe mode
org.apache.hadoop.hdfs.server.namenode.FSNamesystem: NameNode low on
available disk space. Entering safe mode.
2013-01-21 01:22:52,218 INFO org.apache.hadoop.hdfs.StateChange: STATE*
Safe mode is ON.
On Wed, Jan 23, 2013 at 2:50 AM, Steve Loughran steve.lough...@gmail.comwrote:
ser@hadoop.apache.orglist
the configured reserved amount 104857600
2013-01-21 01:22:52,218 WARN
org.apache.hadoop.hdfs.server.namenode.FSNamesystem: NameNode low on
available disk space. Entering safe mode.
2013-01-21 01:22:52,218 INFO org.apache.hadoop.hdfs.StateChange: STATE*
Safe mode is ON.
On Wed, Jan 23, 2013 at 2
org.apache.hadoop.hdfs.server.namenode.NameNodeResourceChecker: Space
available on volume '/dev/mapper/vg_lv_root' is 10653696, which is below
the configured reserved amount 104857600
2013-01-21 01:22:52,218 WARN
org.apache.hadoop.hdfs.server.namenode.FSNamesystem: NameNode low on
available disk space
org.apache.hadoop.hdfs.server.namenode.NameNodeResourceChecker: Space
available on volume '/dev/mapper/vg_lv_root' is 10653696, which is below
the configured reserved amount 104857600
2013-01-21 01:22:52,218 WARN
org.apache.hadoop.hdfs.server.namenode.FSNamesystem: NameNode low on
available disk space. Entering safe mode.
2013-01-21 01:22:52,218 INFO
20 matches
Mail list logo
