Hi Allen, Thanks for the pointer! You are dead on!
This is what I got: [j...@alextest ~]$ du /storage/hadoop-jill/dfs/data/ 3 /storage/hadoop-jill/dfs/data/detach 6 /storage/hadoop-jill/dfs/data/current 3 /storage/hadoop-jill/dfs/data/tmp 18 /storage/hadoop-jill/dfs/data [j...@alextest ~]$ [j...@alextest ~]$ which du /usr/xpg4/bin/du [j...@alextest ~]$ which gdu /opt/local/bin/gdu [j...@alextest ~]$ It turns out what I got isn't the GNU du. I got it to run by doing this under /opt/local/bin: ln -s du gdu alias didn't work. hadoop must be looking for 'whch du' and use whichever if found first in the PATH. Thanks so much! My data node is now up! -alex On Sat, May 15, 2010 at 12:14 AM, Allen Wittenauer <[email protected] > wrote: > > On May 14, 2010, at 3:27 AM, Alex Li wrote: > > I'm running it as user 'jill' and I don't even know where that > > > > "24 /tmp/hadoop-jill/dfs/data" > > > > is coming from. > > > > What am I missing? I'm very baffled :( > > It is likely coming from the output of du, which the datanode uses to > determine space. We run Hadoop on Solaris, but not in a zone so there > shouldn't be any issues there, unless Joyent is doing odd things. > > What version of Solaris and what does your output of du > /tmp/hadoop-jill/dfs/data give? [tabs vs. spaces, etc, counts!] > > > >
