I have sent a rfc patch [1] for review.
https://review.gluster.org/#/c/glusterfs/+/23011/
On Thu, Jul 4, 2019 at 1:13 AM Pranith Kumar Karampuri
wrote:
>
>
> On Wed, Jul 3, 2019 at 10:59 PM FNU Raghavendra Manjunath <
> rab...@redhat.com> wrote:
>
>>
>>
>> On Wed, Jul 3, 2019 at 3:28 AM
On Wed, Jul 3, 2019 at 10:59 PM FNU Raghavendra Manjunath
wrote:
>
>
> On Wed, Jul 3, 2019 at 3:28 AM Pranith Kumar Karampuri <
> pkara...@redhat.com> wrote:
>
>>
>>
>> On Wed, Jul 3, 2019 at 10:14 AM Ravishankar N
>> wrote:
>>
>>>
>>> On 02/07/19 8:52 PM, FNU Raghavendra Manjunath wrote:
>>>
On Wed, Jul 3, 2019 at 3:28 AM Pranith Kumar Karampuri
wrote:
>
>
> On Wed, Jul 3, 2019 at 10:14 AM Ravishankar N
> wrote:
>
>>
>> On 02/07/19 8:52 PM, FNU Raghavendra Manjunath wrote:
>>
>>
>> Hi All,
>>
>> In glusterfs, there is an issue regarding the fallocate behavior. In
>> short, if
On Wed, Jul 3, 2019 at 10:14 AM Ravishankar N
wrote:
>
> On 02/07/19 8:52 PM, FNU Raghavendra Manjunath wrote:
>
>
> Hi All,
>
> In glusterfs, there is an issue regarding the fallocate behavior. In
> short, if someone does fallocate from the mount point with some size that
> is greater than the
On 02/07/19 8:52 PM, FNU Raghavendra Manjunath wrote:
Hi All,
In glusterfs, there is an issue regarding the fallocate behavior. In
short, if someone does fallocate from the mount point with some size
that is greater than the available size in the backend filesystem
where the file is
Hi All,
In glusterfs, there is an issue regarding the fallocate behavior. In short,
if someone does fallocate from the mount point with some size that is
greater than the available size in the backend filesystem where the file is
present, then fallocate can fail with a subset of the required
