Hi,
A client had some issues with their glusterfs cluster and botched an
update. Currently they have loads of broken symlinks in their bricks
.glusterfs subfolders
Like the second symlink one below
lrwxrwxrwx 1 root root 55 Jul 14 2017
591c33db-e88b-4544-9372-bea4ec362360 ->
Were you able to set new limits after seeing this error?
On Tue, Feb 13, 2018 at 4:19 PM, Hari Gowtham wrote:
> Yes, I need the log files in that duration, the log rotated file after
> hitting the
> issue aren't necessary, but the ones before hitting the issues are needed
>
I'm using gluster for a virt-store with 3x2 distributed/replicated
servers for 16 qemu/kvm/libvirt virtual machines using image files
stored in gluster and accessed via libgfapi. Eight of these disk images
are standalone, while the other eight are qcow2 images which all share a
single backing
Yes, I need the log files in that duration, the log rotated file after
hitting the
issue aren't necessary, but the ones before hitting the issues are needed
(not just when you hit it, the ones even before you hit it).
Yes, you have to do a stat from the client through fuse mount.
On Tue, Feb 13,
Hi Hari,
Sure no problem, I will send you in a minute another mail where you can
download all the relevant log files including the quota.conf binary file. Let
me know if you need anything else. In the mean time here below is the output of
a volume status.
Best regards,
M.
Status of volume:
Hi Hari,
Sorry for not providing you more details from the start. Here below you will
find all the relevant log entries and info. Regarding the quota.conf file I
have found one for my volume but it is a binary file. Is it supposed to be
binary or text?
Regards,
M.
*** gluster volume info
Hi,
A part of the log won't be enough to debug the issue.
Need the whole log messages till date.
You can send it as attachments.
Yes the quota.conf is a binary file.
And I need the volume status output too.
On Tue, Feb 13, 2018 at 1:56 PM, mabi wrote:
> Hi Hari,
> Sorry
Thank you for your answer. This problem seem to have started since last week,
so should I also send you the same log files but for last week? I think
logrotate rotates them on a weekly basis.
The only two quota commands we use are the following:
gluster volume quota myvolume limit-usage
Hi,
A client had some issues with their glusterfs cluster and botched an
update. Currently they have loads of broken symlinks in their bricks
.glusterfs folder Like the second one below
lrwxrwxrwx 1 root root 55 Jul 14 2017
591c33db-e88b-4544-9372-bea4ec362360 ->
I tried to set the limits as you suggest by running the following command.
$ sudo gluster volume quota myvolume limit-usage /directory 200GB
volume quota : success
but then when I list the quotas there is still nothing, so nothing really
happened.
I also tried to run stat on all directories
10 matches
Mail list logo