new file hanging? -- solution

[Brandon Ooi]

Hi guys,

Great it works! thanks to Juan, Brad, Jason and Justin for all their help.

Problems I encountered.

1) Redefining $/ in a global way seems to cause problems with Perlbal 
internals. Solution is to local scope it.
2) The 'dev' directories in /var/mogdata need to be created manually.
3) Linux::AIO seems to cause problems. Building Perlbal with IO::AIO 
seems to work (or just without Linux::AIO present)
4) Also requires mogstored to be built with IO::AIO. The mogstored 
version 1.00 requres Linux::AIO. the mogstored in CVS has an abstraction 
layer built in.

If we do use this in production, i'll be sure to write some 
documentation on how to get it all to work. the current documentation 
doesn't do it justice ;)


A few side questions:

1) Juan mentioned that we should be using Perlbal 1.36 until 1.40 
arrives. In general, are there "stable" versions of this software? 
(perlbal, mogstored, mogilefsd)
2) Can the /var/mogdata/devX directories be symlinks to different 
devices and/or filesystems?


Thanks!

Brandon



Brad Fitzpatrick wrote:

>On Wed, 24 Aug 2005, Brandon Ooi wrote:
>
>  
>
>>Hi Juan,
>>
>>Interesting that you say that. I read this mailing list's archive and I
>>came across a problem with Linux::AIO here.
>>
>>http://lists.danga.com/pipermail/mogilefs/2005-March/000029.html
>>
>>The latest Linux::AIO (v1.8) does not pass "make test". I reverted to
>>using Linux::AIO 1.72. While this is Fedora Core 4, it is the 32-bit x86
>>build.
>>
>>I would like to try IO::AIO (which I believe is API compatible). How can
>>I instruct Perlbal to use IO::AIO instead of Linux::AIO?
>>    
>>
>
>Uninstall Linux::AIO.  Perlbal will prefer Linux::AIO, then IO::AIO, then
>native (blocking).
>
>You can also set it with:
>
>   server aio_mode = linux
>   server aio_mode = ioaio
>   server aio_mode = none
>
>In your perlbal config file.  (but in mogstored's case, it auto-generates
>the config file...)
>
>
>  
>
>>Brandon
>>
>>
>>Juan Ignacio Leon wrote:
>>
>>    
>>
>>>Brandon,
>>>As far as I dug, I was able to see that the problems had to do with
>>>the asynchronous IO routines.
>>>At the time I was testing (early this summer), Linux::AIO was a
>>>requirement and did not work well with 64bit kernels on RedHat (epoll
>>>problems also). Now, you can instruct perlbal to use IO::AIO which is
>>>a portable asynch IO written by the same developer - Lehmann.
>>>
>>>I ended up having to ditch the RedHat clone for the storage solution
>>>and threw mogile on Debian.  I will, however, try again on a RedHat
>>>derivative at some point in the future. Sorry I can't be of more help.
>>>This community is pretty darn good and quite active lately so best of
>>>luck.
>>>
>>>Oh one more thing:  be sure to try using CVS builds for all these
>>>sources rather than the older ones linked from the website.
>>>
>>>Juan
>>>
>>>
>>>On 8/24/05, Brandon Ooi <brandono at berkeley.edu> wrote:
>>>
>>>
>>>      
>>>
>>>>I am running on Fedora Core 4 SMP. (which is probably an RHEL somethign
>>>>clone). Did you ever figure out what caused the hangs?
>>>>
>>>>Brandon
>>>>
>>>>Juan Ignacio Leon wrote:
>>>>
>>>>
>>>>
>>>>        
>>>>
>>>>>Brandon,
>>>>>What platform are you running mogilefs on? I had similar hangs when
>>>>>using CentOS 4.1 (RHEL 4.1 Clone).
>>>>>J
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>          
>>>>>
>>    
>>
>
>  
>