[Gluster-devel] Cascading different translator doesn't work as expectation

[yaomin @ gmail]

Krishna,

    Thank you first.

    I will follow your suggestions to modify the vol files.

Thanks,
Yaomin

--------------------------------------------------
From: "Krishna Srinivas" <krishna at zresearch.com>
Sent: Tuesday, January 06, 2009 1:09 PM
To: "yaomin @ gmail" <yangyaomin at gmail.com>
Cc: <gluster-devel at nongnu.org>
Subject: Re: [Gluster-devel] Cascading different translator doesn't work as 
expectation

> Alfred,
> Your vol files are wrong. you need to remove all the volume
> definitions below "writeback" in the client vol file. For server vol
> file the definition of performance translators is not having any
> effect. Also you need to use "features/locks" translator above
> "storage/posix"
> Krishna
>
> On Tue, Jan 6, 2009 at 8:51 AM, yaomin @ gmail <yangyaomin at gmail.com> 
> wrote:
>> All,
>>
>>     It seems difficult for you.
>>
>>     There is a new problem when I tested.
>>
>>     When I kill all the storage nodes, the client still try to send data,
>> and doesn't quit.
>>
>> Thanks,
>> Alfred
>> From: yaomin @ gmail
>> Sent: Monday, January 05, 2009 10:52 PM
>> To: Krishna Srinivas
>> Cc: gluster-devel at nongnu.org
>> Subject: Re: [Gluster-devel] Cascading different translator doesn't work 
>> as
>> expectation
>> Krishna,
>>     Thank you for your quick response.
>>     There are two log information in the client's log file when setting 
>> up
>> the client.
>>     2009-01-05 18:44:59 W [fuse-bridge.c:389:fuse_entry_cbk] 
>> glusterfs-fuse:
>> 2: (34) / => 1 Rehashing 0/0
>>     2009-01-05 18:48:04 W [fuse-bridge.c:389:fuse_entry_cbk] 
>> glusterfs-fuse:
>> 2: (34) / => 1 Rehashing 0/0
>>
>>   There is no any information in the storage node's log file.
>>
>>   Although I changed the scheduler from ALU to RR, there only the
>> No.3(192.168.13.5) and No.4(192.168.13.7) storage nodes on working.
>>
>>   Each machine has 2GB memory.
>>
>> Thanks,
>> Alfred
>>