|
From: | Vijay Bellur |
Subject: | Re: [Gluster-devel] Specific volume name causing read-only? |
Date: | Mon, 26 Mar 2012 20:45:50 +0530 |
User-agent: | Mozilla/5.0 (X11; Linux x86_64; rv:7.0) Gecko/20110927 Thunderbird/7.0 |
On 03/26/2012 08:03 PM, Yang Ye wrote:
Hi, Will the volume name causing read-only volume? When I create a volume named as korolev with following gluster> volume create korolev replica 2 transport tcp ... and mount with192.168.2.103:/korolev /home/korolev glusterfs defaults,_netdev,loglevel=WARNING,log-file=/var/log/gluster-korolev.log 0 0The mounted volume is a read-only volume.
This is a bug. The 'ro' in the log-file name should be causing this. Can you please open a bug report? A workaround for now would be to use a log-file name that doesn't contain 'ro'.
Thanks, Vijay
[Prev in Thread] | Current Thread | [Next in Thread] |