Re: File Corruption when adding bricks to live replica volumes

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Assuming you're using FUSE protocol to mount your volume, then it would be /var/log/glusterfs/hiphenated-mount-point-path.log
For example if your volume is mounted at /mnt/glusterfs, the corresponding log file would be named "/var/log/glusterfs/mnt-glusterfs.log".
The shd logs are named "/var/log/glusterfs/glustershd.log".

-Krutika

From: "Lindsay Mathieson" <lindsay.mathieson@xxxxxxxxx>
To: "Krutika Dhananjay" <kdhananj@xxxxxxxxxx>
Cc: "gluster-users" <Gluster-users@xxxxxxxxxxx>
Sent: Friday, January 22, 2016 11:34:04 AM
Subject: Re: File Corruption when adding bricks to live replica volumes

On 21/01/16 20:03, Krutika Dhananjay wrote:
Also could you please attach glustershd.log files and the client logs?




Which client logs are those?

Regards how I cleared the brick - idid a "rm -rf" from the root dir, i.e for vng.proxmox.softlog:/vmdata/datastore1:

vng$ cd /vmdata
vng$ rm -rf datastore1


Also, all the bricks are hosted on zfs datastest.
-- 
Lindsay Mathieson

_______________________________________________
Gluster-users mailing list
Gluster-users@xxxxxxxxxxx
http://www.gluster.org/mailman/listinfo/gluster-users

[Index of Archives]     [Gluster Development]     [Linux Filesytems Development]     [Linux ARM Kernel]     [Linux ARM]     [Linux Omap]     [Fedora ARM]     [IETF Annouce]     [Bugtraq]     [Linux OMAP]     [Linux MIPS]     [eCos]     [Asterisk Internet PBX]     [Linux API]

  Powered by Linux