Return-Path: Delivered-To: apmail-hadoop-hdfs-user-archive@minotaur.apache.org Received: (qmail 71505 invoked from network); 6 May 2010 15:44:59 -0000 Received: from unknown (HELO mail.apache.org) (140.211.11.3) by 140.211.11.9 with SMTP; 6 May 2010 15:44:59 -0000 Received: (qmail 66050 invoked by uid 500); 6 May 2010 15:44:59 -0000 Delivered-To: apmail-hadoop-hdfs-user-archive@hadoop.apache.org Received: (qmail 65977 invoked by uid 500); 6 May 2010 15:44:58 -0000 Mailing-List: contact hdfs-user-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: hdfs-user@hadoop.apache.org Delivered-To: mailing list hdfs-user@hadoop.apache.org Received: (qmail 65969 invoked by uid 99); 6 May 2010 15:44:58 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 06 May 2010 15:44:58 +0000 X-ASF-Spam-Status: No, hits=0.7 required=10.0 tests=SPF_NEUTRAL X-Spam-Check-By: apache.org Received-SPF: neutral (nike.apache.org: local policy) Received: from [74.125.83.176] (HELO mail-pv0-f176.google.com) (74.125.83.176) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 06 May 2010 15:44:52 +0000 Received: by pvg12 with SMTP id 12so44211pvg.35 for ; Thu, 06 May 2010 08:44:23 -0700 (PDT) MIME-Version: 1.0 Received: by 10.143.21.14 with SMTP id y14mr3755754wfi.43.1273160663126; Thu, 06 May 2010 08:44:23 -0700 (PDT) Received: by 10.142.88.2 with HTTP; Thu, 6 May 2010 08:44:23 -0700 (PDT) In-Reply-To: <88F0FB6E-AD8C-47F2-B013-ECB4D45D765B@eisp.co.za> References: <84A04582-D963-4EC6-9134-5C42337E5C3B@eisp.co.za> <35F6C10C-77D7-4EA2-9D96-CACD395084B5@eisp.co.za> <9A20330A-FA57-442A-8DE2-0127BF7CF7BA@eisp.co.za> <88F0FB6E-AD8C-47F2-B013-ECB4D45D765B@eisp.co.za> Date: Thu, 6 May 2010 08:44:23 -0700 Message-ID: Subject: Re: Fuse-DFS From: Eli Collins To: hdfs-user@hadoop.apache.org Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable X-Virus-Checked: Checked by ClamAV on apache.org Hey Seraph, The -d is just a debug option, to print output to the terminal, shouldn't change the execution. I suspect something else is going on, perhaps you have an old fuse process running? Thanks, Eli On Thu, May 6, 2010 at 4:55 AM, Seraph Imalia wrote: > Hi, > > I am experiencing an annoying problem... > > When I run this "./fuse_dfs_wrapper.sh dfs://dynobuntu10:8020 /Volumes/hd= fs > -obig_writes -d" then everything works fine. > > When I run this "./fuse_dfs_wrapper.sh dfs://dynobuntu10:8020 /Volumes/hd= fs > -obig_writes" (i.e. remove the daemonize option) I get issues connecting = to > hadoop... > > Here is what is in /var/log/syslog after running "ls /Volumes/hdfs" > > May =A06 12:57:16 dynobuntu17 fuse_dfs: ERROR: could not connect to > dynobuntu10:8020 fuse_impls_getattr.c:37 > May =A06 12:57:23 dynobuntu17 fuse_dfs: ERROR: could not connect to > dynobuntu10:8020 fuse_impls_getattr.c:37 > > No errors appear in the syslog when the -d option is specified. > > I also tried port 9000 with exactly the same results. =A0There is no fire= wall > software installed on any of the servers. > > It almost appears as something is stopping the connection to a the > nameserver when fuse_dfs runs as a daemon. =A0Please help. > We are running OS: =A0Ubuntu 9.04 x64 (2.6.28-11-server #42-Ubuntu SMP Fr= i Apr > 17 02:45:36 UTC 2009 GNU/Linux) > > Seraph > > > > On 06 May 2010, at 11:31 AM, Seraph Imalia wrote: > >> Hi Eli, >> >> Thank you very much - applying patch HDFS-961-2.patch and re-building >> resolved the problem. >> >> Regards, >> Seraph >> >> On 05 May 2010, at 11:20 PM, Eli Collins wrote: >> >>> Try using a port besides 8020 or applying the patch for HDFS-961. >>> >>> Thanks, >>> Eli >>> >>> On Wed, May 5, 2010 at 9:02 AM, Seraph Imalia wrote= : >>>> >>>> I have successfully managed to mount a dfs - but here is what I am >>>> experiencing... >>>> I mounted to /Volumes/hdfs =A0when I run "ls /Volumes/hdfs" it works f= ine >>>> and >>>> returns no results. >>>> so I ran "mkdir /Volumes/hdfs/test" and it was successful and I could >>>> see >>>> the new directory exists using the web interface to browse hadoop. >>>> but now when I run "ls /Volumes/hdfs" it does this... >>>> ls: cannot access /Volumes/hdfs/p-site.x0: No such file or directory >>>> p-site.x0 >>>> >>>> and on the terminal window where I mounted it, it dumps this... >>>> LOOKUP /p-site.x0 >>>> =A0unique: 13, error: -2 (No such file or directory), outsize: 16 >>>> unique: 14, opcode: READDIR (28), nodeid: 1, insize: 80 >>>> =A0unique: 14, error: 0 (Success), outsize: 16 >>>> unique: 15, opcode: RELEASEDIR (29), nodeid: 1, insize: 64 >>>> =A0unique: 15, error: 0 (Success), outsize: 16 >>>> unique: 16, opcode: GETATTR (3), nodeid: 1, insize: 56 >>>> =A0unique: 16, error: 0 (Success), outsize: 112 >>>> unique: 17, opcode: OPENDIR (27), nodeid: 1, insize: 48 >>>> =A0unique: 17, error: 0 (Success), outsize: 32 >>>> unique: 18, opcode: READDIR (28), nodeid: 1, insize: 80 >>>> =A0unique: 18, error: 0 (Success), outsize: 112 >>>> unique: 19, opcode: GETATTR (3), nodeid: 1, insize: 56 >>>> =A0unique: 19, error: 0 (Success), outsize: 112 >>>> unique: 20, opcode: LOOKUP (1), nodeid: 1, insize: 42 >>>> >>>> I am not sure what this debug info means? >>>> Here is everything that happened on terminal 1 and 2... >>>> terminal 1 >>>> root@dynobuntu17:/opt/hadoop-0.20.2# >>>> contrib/fuse-dfs/fuse_dfs_wrapper.sh >>>> dfs://dynobuntu10:8020 /Volumes/hdfs -d >>>> port=3D8020,server=3Ddynobuntu10 >>>> fuse-dfs didn't recognize /Volumes/hdfs,-2 >>>> fuse-dfs ignoring option -d >>>> unique: 1, opcode: INIT (26), nodeid: 0, insize: 56 >>>> INIT: 7.10 >>>> flags=3D0x0000003b >>>> max_readahead=3D0x00020000 >>>> =A0INIT: 7.8 >>>> =A0flags=3D0x00000001 >>>> =A0max_readahead=3D0x00020000 >>>> =A0max_write=3D0x00020000 >>>> =A0unique: 1, error: 0 (Success), outsize: 40 >>>> unique: 2, opcode: GETATTR (3), nodeid: 1, insize: 56 >>>> =A0unique: 2, error: 0 (Success), outsize: 112 >>>> unique: 3, opcode: OPENDIR (27), nodeid: 1, insize: 48 >>>> =A0unique: 3, error: 0 (Success), outsize: 32 >>>> unique: 4, opcode: READDIR (28), nodeid: 1, insize: 80 >>>> =A0unique: 4, error: -2 (No such file or directory), outsize: 16 >>>> unique: 5, opcode: RELEASEDIR (29), nodeid: 1, insize: 64 >>>> =A0unique: 5, error: 0 (Success), outsize: 16 >>>> unique: 6, opcode: GETATTR (3), nodeid: 1, insize: 56 >>>> =A0unique: 6, error: 0 (Success), outsize: 112 >>>> unique: 7, opcode: LOOKUP (1), nodeid: 1, insize: 45 >>>> LOOKUP /test >>>> =A0unique: 7, error: -2 (No such file or directory), outsize: 16 >>>> unique: 8, opcode: MKDIR (9), nodeid: 1, insize: 53 >>>> MKDIR /test >>>> =A0NODEID: 2 >>>> =A0unique: 8, error: 0 (Success), outsize: 136 >>>> unique: 9, opcode: GETATTR (3), nodeid: 1, insize: 56 >>>> =A0unique: 9, error: 0 (Success), outsize: 112 >>>> unique: 10, opcode: OPENDIR (27), nodeid: 1, insize: 48 >>>> =A0unique: 10, error: 0 (Success), outsize: 32 >>>> unique: 11, opcode: READDIR (28), nodeid: 1, insize: 80 >>>> =A0unique: 11, error: 0 (Success), outsize: 120 >>>> unique: 12, opcode: GETATTR (3), nodeid: 1, insize: 56 >>>> =A0unique: 12, error: 0 (Success), outsize: 112 >>>> unique: 13, opcode: LOOKUP (1), nodeid: 1, insize: 50 >>>> LOOKUP /p-site.x0 >>>> =A0unique: 13, error: -2 (No such file or directory), outsize: 16 >>>> unique: 14, opcode: READDIR (28), nodeid: 1, insize: 80 >>>> =A0unique: 14, error: 0 (Success), outsize: 16 >>>> unique: 15, opcode: RELEASEDIR (29), nodeid: 1, insize: 64 >>>> =A0unique: 15, error: 0 (Success), outsize: 16 >>>> unique: 16, opcode: GETATTR (3), nodeid: 1, insize: 56 >>>> =A0unique: 16, error: 0 (Success), outsize: 112 >>>> unique: 17, opcode: OPENDIR (27), nodeid: 1, insize: 48 >>>> =A0unique: 17, error: 0 (Success), outsize: 32 >>>> unique: 18, opcode: READDIR (28), nodeid: 1, insize: 80 >>>> =A0unique: 18, error: 0 (Success), outsize: 112 >>>> unique: 19, opcode: GETATTR (3), nodeid: 1, insize: 56 >>>> =A0unique: 19, error: 0 (Success), outsize: 112 >>>> unique: 20, opcode: LOOKUP (1), nodeid: 1, insize: 42 >>>> LOOKUP /% >>>> =A0unique: 20, error: -2 (No such file or directory), outsize: 16 >>>> unique: 21, opcode: READDIR (28), nodeid: 1, insize: 80 >>>> =A0unique: 21, error: 0 (Success), outsize: 16 >>>> unique: 22, opcode: RELEASEDIR (29), nodeid: 1, insize: 64 >>>> =A0unique: 22, error: 0 (Success), outsize: 16 >>>> unique: 23, opcode: GETATTR (3), nodeid: 1, insize: 56 >>>> =A0unique: 23, error: 0 (Success), outsize: 112 >>>> unique: 24, opcode: OPENDIR (27), nodeid: 1, insize: 48 >>>> =A0unique: 24, error: 0 (Success), outsize: 32 >>>> unique: 25, opcode: READDIR (28), nodeid: 1, insize: 80 >>>> =A0unique: 25, error: 0 (Success), outsize: 112 >>>> unique: 26, opcode: GETATTR (3), nodeid: 1, insize: 56 >>>> =A0unique: 26, error: 0 (Success), outsize: 112 >>>> unique: 27, opcode: LOOKUP (1), nodeid: 1, insize: 42 >>>> LOOKUP /1 >>>> =A0unique: 27, error: -2 (No such file or directory), outsize: 16 >>>> unique: 28, opcode: READDIR (28), nodeid: 1, insize: 80 >>>> =A0unique: 28, error: 0 (Success), outsize: 16 >>>> unique: 29, opcode: RELEASEDIR (29), nodeid: 1, insize: 64 >>>> =A0unique: 29, error: 0 (Success), outsize: 16 >>>> unique: 30, opcode: GETATTR (3), nodeid: 1, insize: 56 >>>> =A0unique: 30, error: 0 (Success), outsize: 112 >>>> unique: 31, opcode: OPENDIR (27), nodeid: 2, insize: 48 >>>> =A0unique: 31, error: 0 (Success), outsize: 32 >>>> unique: 32, opcode: READDIR (28), nodeid: 2, insize: 80 >>>> =A0unique: 32, error: -2 (No such file or directory), outsize: 16 >>>> unique: 33, opcode: RELEASEDIR (29), nodeid: 2, insize: 64 >>>> =A0unique: 33, error: 0 (Success), outsize: 16 >>>> unique: 34, opcode: OPENDIR (27), nodeid: 1, insize: 48 >>>> =A0unique: 34, error: 0 (Success), outsize: 32 >>>> unique: 35, opcode: READDIR (28), nodeid: 1, insize: 80 >>>> =A0unique: 35, error: 0 (Success), outsize: 120 >>>> unique: 36, opcode: GETATTR (3), nodeid: 1, insize: 56 >>>> =A0unique: 36, error: 0 (Success), outsize: 112 >>>> unique: 37, opcode: LOOKUP (1), nodeid: 1, insize: 50 >>>> LOOKUP /d-site.x0 >>>> =A0unique: 37, error: -2 (No such file or directory), outsize: 16 >>>> unique: 38, opcode: READDIR (28), nodeid: 1, insize: 80 >>>> =A0unique: 38, error: 0 (Success), outsize: 16 >>>> unique: 39, opcode: RELEASEDIR (29), nodeid: 1, insize: 64 >>>> =A0unique: 39, error: 0 (Success), outsize: 16 >>>> unique: 40, opcode: GETATTR (3), nodeid: 1, insize: 56 >>>> =A0unique: 40, error: 0 (Success), outsize: 112 >>>> unique: 41, opcode: LOOKUP (1), nodeid: 1, insize: 45 >>>> LOOKUP /test >>>> =A0NODEID: 2 >>>> =A0unique: 41, error: 0 (Success), outsize: 136 >>>> unique: 42, opcode: LOOKUP (1), nodeid: 2, insize: 47 >>>> LOOKUP /test/inside >>>> =A0unique: 42, error: -2 (No such file or directory), outsize: 16 >>>> unique: 43, opcode: MKDIR (9), nodeid: 2, insize: 55 >>>> MKDIR /test/inside >>>> =A0NODEID: 3 >>>> =A0unique: 43, error: 0 (Success), outsize: 136 >>>> unique: 44, opcode: GETATTR (3), nodeid: 2, insize: 56 >>>> =A0unique: 44, error: 0 (Success), outsize: 112 >>>> unique: 45, opcode: OPENDIR (27), nodeid: 2, insize: 48 >>>> =A0unique: 45, error: 0 (Success), outsize: 32 >>>> unique: 46, opcode: READDIR (28), nodeid: 2, insize: 80 >>>> =A0unique: 46, error: 0 (Success), outsize: 112 >>>> unique: 47, opcode: GETATTR (3), nodeid: 2, insize: 56 >>>> =A0unique: 47, error: 0 (Success), outsize: 112 >>>> unique: 48, opcode: LOOKUP (1), nodeid: 2, insize: 42 >>>> LOOKUP /test/e >>>> =A0unique: 48, error: -2 (No such file or directory), outsize: 16 >>>> unique: 49, opcode: READDIR (28), nodeid: 2, insize: 80 >>>> =A0unique: 49, error: 0 (Success), outsize: 16 >>>> unique: 50, opcode: RELEASEDIR (29), nodeid: 2, insize: 64 >>>> =A0unique: 50, error: 0 (Success), outsize: 16 >>>> unique: 51, opcode: GETATTR (3), nodeid: 2, insize: 56 >>>> =A0unique: 51, error: 0 (Success), outsize: 112 >>>> unique: 52, opcode: OPENDIR (27), nodeid: 2, insize: 48 >>>> =A0unique: 52, error: 0 (Success), outsize: 32 >>>> unique: 53, opcode: READDIR (28), nodeid: 2, insize: 80 >>>> =A0unique: 53, error: 0 (Success), outsize: 112 >>>> unique: 54, opcode: GETATTR (3), nodeid: 2, insize: 56 >>>> =A0unique: 54, error: 0 (Success), outsize: 112 >>>> unique: 55, opcode: LOOKUP (1), nodeid: 2, insize: 42 >>>> LOOKUP /test/e >>>> =A0unique: 55, error: -2 (No such file or directory), outsize: 16 >>>> unique: 56, opcode: READDIR (28), nodeid: 2, insize: 80 >>>> =A0unique: 56, error: 0 (Success), outsize: 16 >>>> unique: 57, opcode: RELEASEDIR (29), nodeid: 2, insize: 64 >>>> =A0unique: 57, error: 0 (Success), outsize: 16 >>>> unique: 58, opcode: GETATTR (3), nodeid: 2, insize: 56 >>>> =A0unique: 58, error: 0 (Success), outsize: 112 >>>> unique: 59, opcode: OPENDIR (27), nodeid: 2, insize: 48 >>>> =A0unique: 59, error: 0 (Success), outsize: 32 >>>> unique: 60, opcode: READDIR (28), nodeid: 2, insize: 80 >>>> =A0unique: 60, error: 0 (Success), outsize: 112 >>>> unique: 61, opcode: GETATTR (3), nodeid: 2, insize: 56 >>>> =A0unique: 61, error: 0 (Success), outsize: 112 >>>> unique: 62, opcode: LOOKUP (1), nodeid: 2, insize: 42 >>>> LOOKUP /test/e >>>> =A0unique: 62, error: -2 (No such file or directory), outsize: 16 >>>> unique: 63, opcode: READDIR (28), nodeid: 2, insize: 80 >>>> =A0unique: 63, error: 0 (Success), outsize: 16 >>>> unique: 64, opcode: RELEASEDIR (29), nodeid: 2, insize: 64 >>>> =A0unique: 64, error: 0 (Success), outsize: 16 >>>> unique: 65, opcode: GETATTR (3), nodeid: 2, insize: 56 >>>> =A0unique: 65, error: 0 (Success), outsize: 112 >>>> unique: 66, opcode: OPENDIR (27), nodeid: 2, insize: 48 >>>> =A0unique: 66, error: 0 (Success), outsize: 32 >>>> unique: 67, opcode: READDIR (28), nodeid: 2, insize: 80 >>>> =A0unique: 67, error: 0 (Success), outsize: 112 >>>> unique: 68, opcode: GETATTR (3), nodeid: 2, insize: 56 >>>> =A0unique: 68, error: 0 (Success), outsize: 112 >>>> unique: 69, opcode: LOOKUP (1), nodeid: 2, insize: 42 >>>> LOOKUP /test/e >>>> =A0unique: 69, error: -2 (No such file or directory), outsize: 16 >>>> unique: 70, opcode: READDIR (28), nodeid: 2, insize: 80 >>>> =A0unique: 70, error: 0 (Success), outsize: 16 >>>> unique: 71, opcode: RELEASEDIR (29), nodeid: 2, insize: 64 >>>> =A0unique: 71, error: 0 (Success), outsize: 16 >>>> unique: 72, opcode: GETATTR (3), nodeid: 2, insize: 56 >>>> =A0unique: 72, error: 0 (Success), outsize: 112 >>>> unique: 73, opcode: OPENDIR (27), nodeid: 2, insize: 48 >>>> =A0unique: 73, error: 0 (Success), outsize: 32 >>>> unique: 74, opcode: READDIR (28), nodeid: 2, insize: 80 >>>> =A0unique: 74, error: 0 (Success), outsize: 112 >>>> unique: 75, opcode: GETATTR (3), nodeid: 2, insize: 56 >>>> =A0unique: 75, error: 0 (Success), outsize: 112 >>>> unique: 76, opcode: LOOKUP (1), nodeid: 2, insize: 42 >>>> LOOKUP /test/e >>>> =A0unique: 76, error: -2 (No such file or directory), outsize: 16 >>>> unique: 77, opcode: READDIR (28), nodeid: 2, insize: 80 >>>> =A0unique: 77, error: 0 (Success), outsize: 16 >>>> unique: 78, opcode: RELEASEDIR (29), nodeid: 2, insize: 64 >>>> =A0unique: 78, error: 0 (Success), outsize: 16 >>>> terminal 2 >>>> root@dynobuntu17:~# ls /Volumes/hdfs/ >>>> root@dynobuntu17:~# mkdir /Volumes/hdfs/test >>>> root@dynobuntu17:~# ls /Volumes/hdfs/ >>>> ls: cannot access /Volumes/hdfs/p-site.x0: No such file or directory >>>> p-site.x0 >>>> root@dynobuntu17:~# ls /Volumes/hdfs/ >>>> ls: cannot access /Volumes/hdfs/%: No such file or directory >>>> % >>>> root@dynobuntu17:~# ls /Volumes/hdfs >>>> ls: cannot access /Volumes/hdfs/1: No such file or directory >>>> 1 >>>> root@dynobuntu17:~# ls /Volumes/hdfs/test >>>> root@dynobuntu17:~# ls /Volumes/hdfs/ >>>> ls: cannot access /Volumes/hdfs/d-site.x0: No such file or directory >>>> d-site.x0 >>>> root@dynobuntu17:~# mkdir /Volumes/hdfs/test/inside >>>> root@dynobuntu17:~# ls /Volumes/hdfs/test >>>> ls: cannot access /Volumes/hdfs/test/e: No such file or directory >>>> e >>>> root@dynobuntu17:~# ls /Volumes/hdfs/test >>>> ls: cannot access /Volumes/hdfs/test/e: No such file or directory >>>> e >>>> root@dynobuntu17:~# ls /Volumes/hdfs/\test >>>> ls: cannot access /Volumes/hdfs/test/e: No such file or directory >>>> e >>>> root@dynobuntu17:~# ls /Volumes/hdfs/\te\s\t >>>> ls: cannot access /Volumes/hdfs/test/e: No such file or directory >>>> e >>>> root@dynobuntu17:~# ls /Volumes/hdfs/\t\e\s\t >>>> ls: cannot access /Volumes/hdfs/test/e: No such file or directory >>>> e >>>> >>>> On 05 May 2010, at 4:57 PM, Seraph Imalia wrote: >>>> >>>> Awesome! - thank you =A0after running apt-get install libfuse-dev I go= t a >>>> successful build. >>>> >>>> Thanks for your help :) >>>> >>>> >>>> On 05 May 2010, at 4:19 PM, Jason Venner wrote: >>>> >>>> It does not look like you have the fuse-devel package installed on you= r >>>> system. >>>> >>>> On Wed, May 5, 2010 at 7:14 AM, Seraph Imalia wrot= e: >>>> >>>> Hi Jason, >>>> >>>> Thank you, =A0I had autoconf installed but not automake - after instal= ling >>>> >>>> automake, the build went further, but this time failed with... >>>> >>>> BUILD FAILED >>>> >>>> /opt/hadoop-0.20.2/build.xml:497: The following error occurred while >>>> >>>> executing this line: >>>> >>>> /opt/hadoop-0.20.2/src/contrib/build.xml:30: The following error >>>> occurred >>>> >>>> while executing this line: >>>> >>>> /opt/hadoop-0.20.2/src/contrib/fuse-dfs/build.xml:57: exec returned: 2 >>>> >>>> The output from the build is attached. >>>> >>>> >>>> >>>> We are running OS: =A0Ubuntu 9.04 x64 (2.6.28-11-server #42-Ubuntu SMP= Fri >>>> Apr >>>> >>>> 17 02:45:36 UTC 2009 GNU/Linux) >>>> >>>> Regards, >>>> >>>> Seraph >>>> >>>> >>>> On 05 May 2010, at 3:47 PM, Jason Venner wrote: >>>> >>>> You will need to install the gnu development tool chain for your >>>> >>>> platform, a quick check on an older redhat system I have suggests the >>>> >>>> automake and autoconf rpm's will provide aclocal, automake and >>>> >>>> autoconf. >>>> >>>> The ./configure: not found error is an artifact of the earlier failure= s. >>>> >>>> >>>> On Wed, May 5, 2010 at 5:37 AM, Seraph Imalia wrot= e: >>>> >>>> Hi, >>>> >>>> I have been following the following URL to mount an HDFS using >>>> >>>> fuse-dfs: http://wiki.apache.org/hadoop/MountableHDFS >>>> >>>> I have had many problems trying to build it but have managed to get >>>> >>>> through >>>> >>>> the first two build commands without build errors. =A0Running the last >>>> >>>> build >>>> >>>> command "ant compile-contrib -Dlibhdfs=3D1 -Dfusedfs=3D1" results in t= he >>>> >>>> following error: >>>> >>>> compile: >>>> >>>> =A0[echo] contrib: fuse-dfs >>>> >>>> =A0[exec] /opt/hadoop-0.20.1/src/contrib/fuse-dfs/bootstrap.sh: 18: >>>> >>>> aclocal: not found >>>> >>>> =A0[exec] /opt/hadoop-0.20.1/src/contrib/fuse-dfs/bootstrap.sh: 19: >>>> >>>> automake: not found >>>> >>>> =A0[exec] /opt/hadoop-0.20.1/src/contrib/fuse-dfs/bootstrap.sh: 20: >>>> >>>> autoconf: not found >>>> >>>> =A0[exec] /opt/hadoop-0.20.1/src/contrib/fuse-dfs/bootstrap.sh: 21: >>>> >>>> ./configure: not found >>>> >>>> BUILD FAILED >>>> >>>> /opt/hadoop-0.20.1/build.xml:497: The following error occurred while >>>> >>>> executing this line: >>>> >>>> /opt/hadoop-0.20.1/src/contrib/build.xml:30: The following error >>>> occurred >>>> >>>> while executing this line: >>>> >>>> /opt/hadoop-0.20.1/src/contrib/fuse-dfs/build.xml:54: exec returned: 1= 27 >>>> >>>> I found this link on >>>> >>>> google: http://issues.apache.org/jira/browse/HADOOP-4 which does not >>>> seem >>>> >>>> to >>>> >>>> help me. >>>> >>>> Please can you assist? >>>> >>>> Regards, >>>> >>>> Seraph >>>> >>>> >>>> >>>> -- >>>> >>>> Pro Hadoop, a book to guide you from beginner to hadoop mastery, >>>> >>>> http://www.amazon.com/dp/1430219424?tag=3Djewlerymall >>>> >>>> www.prohadoopbook.com a community for Hadoop Professionals >>>> >>>> >>>> >>>> >>>> >>>> >>>> -- >>>> >>>> Pro Hadoop, a book to guide you from beginner to hadoop mastery, >>>> >>>> http://www.amazon.com/dp/1430219424?tag=3Djewlerymall >>>> >>>> www.prohadoopbook.com a community for Hadoop Professionals >>>> >>>> >>>> >>>> >> >> > > >