, Raghavendra Gowdappa
<rgowd...@redhat.com> wrote:
>
>
> On Tue, Mar 6, 2018 at 10:58 PM, Raghavendra Gowdappa <rgowd...@redhat.com>
> wrote:
>>
>>
>>
>> On Tue, Mar 6, 2018 at 10:22 PM, Paul Anderson <p...@umich.edu> wrote:
>>>
>>>
ile, but on
debian, it appears to have to be a real file.
Paul
On Tue, Mar 6, 2018 at 10:28 PM, Kaleb S. KEITHLEY <kkeit...@redhat.com> wrote:
> On 03/06/2018 05:50 PM, Paul Anderson wrote:
>> When I follow the directions at
>> http://docs.gluster.org/en/latest/Install-G
When I follow the directions at
http://docs.gluster.org/en/latest/Install-Guide/Install/ to install
the latest gluster on a debian 9 docker container, I get the following
error:
Step 6/15 : RUN echo deb [arch=amd64]
, Raghavendra Gowdappa
<rgowd...@redhat.com> wrote:
> +Csaba.
>
> On Tue, Mar 6, 2018 at 2:52 AM, Paul Anderson <p...@umich.edu> wrote:
>>
>> Raghavendra,
>>
>> Thanks very much for your reply.
>>
>> I fixed our data corruption problem by dis
gt; On Mon, Mar 5, 2018 at 8:21 PM, Paul Anderson <p...@umich.edu> wrote:
>>
>> Hi,
>>
>> tl;dr summary of below: flock() works, but what does it take to make
>> sync()/fsync() work in a 3 node GFS cluster?
>>
>> I am under the impression that POSIX f
Hi,
tl;dr summary of below: flock() works, but what does it take to make
sync()/fsync() work in a 3 node GFS cluster?
I am under the impression that POSIX flock, POSIX
fcntl(F_SETLK/F_GETLK,...), and POSIX read/write/sync/fsync are all
supported in cluster operations, such that in theory,
Hello,
I have a gluster 3.7 setup that I recently created. I can cd into
directories that should be there and then do an ls, but if I do an ls from
the parent directory the directory that I know is there does not show up. I
should also mention that I create the gluster bricks with preexisting
