From mboxrd@z Thu Jan 1 00:00:00 1970 Message-ID: <140e7ec30808060837k54754430p6a4b8cab06627799@mail.gmail.com> Date: Wed, 6 Aug 2008 23:37:48 +0800 From: sqweek To: "Fans of the OS Plan 9 from Bell Labs" <9fans@9fans.net> In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: Subject: Re: [9fans] 9pfuse on mac os x Topicbox-Message-UUID: fc1f7934-ead3-11e9-9d60-3106f5b1d025 On Wed, Aug 6, 2008 at 10:57 PM, Jeff Sickel wrote: > > On Aug 6, 2008, at 9:31 AM, Skip Tavakkolian wrote: > > More depressing that sqweek's change works for OS X 10.4.x but not with the > MacFUSE build for 10.5.x. All I get is: > > % ls ... > FUSE <- unique 0x3 (Getattr) attr_valid 1 ino 0x8000000000000000 size 0 > blocks 0 atime 1218033034 mtime 1218033034 ctime 1218033034 mode 040500 > nlink 1 uid 501 gid 501 rdev 0 > ls: .: Input/output error Is this a 32-bit machine? That's a big frigging inode. I don't have a clue how mac works, but I recently hit a bug with v9fs where a certain qid path got mapped to an inode of zero and subsequently disappeared in the linux vfs layer. Though there was no i/o error there. -sqweek