On Tue, Jul 05, 2016 at 02:46:26PM +0530, Prasanna Kumar Kalever wrote:
> currently all the libgfapi logs defaults to '/dev/stderr' as it was hardcoded
> in a call to glfs logging api, in case if debug level is chosen to DEBUG/TRACE
> gfapi logs will be huge and fill/overflow the console view.
>
>
Just to pick up on how the block device is defined. I think sharding is the
best option - it's already the 'standard' for virtual disks, and the images
files for iSCSI are no different in my mind. They have pretty much the same
requirements around sizing, fault tolerance and recovery.
Let's keep i
On 07/01/2016 01:45 AM, B.K.Raghuram wrote:
I have not gone through this implementation nor the new iscsi
implementation being worked on for 3.9 but I thought I'd share the
design behind a distributed iscsi implementation that we'd worked on
some time back based on the istgt code with a libgfapi
Hi,
I tried to go through the patch and find the reason behind the question
posted. But could'nt get any concrete details about the same.
When going through the mail chain, there were mentions of generic
snapshot interface. I'd be interested in doing the changes if you guys
could fill me with s
Hi,
Thanks all who joined!
Next week at the same time (Tuesday 12:00 UTC) we will have an other bug
triage meeting to catch the bugs that were not handled by developers and
maintainers yet. We'll stay repeating this meeting as safety net so that
bugs get the initial attention and developers can
Hi all,
The Gluster Bug Triage Meeting will start in approx. 1 hour 30 minutes from now.
Please join if you are interested in getting a decent status of bugs
that have recently been filed, and maintainers/developers did not pickup
yet.
The meeting also includes a little bit about testing and oth
currently all the libgfapi logs defaults to '/dev/stderr' as it was hardcoded
in a call to glfs logging api, in case if debug level is chosen to DEBUG/TRACE
gfapi logs will be huge and fill/overflow the console view.
this patch provides a commandline option to mention log file path which helps
in
Just for the record...
In the meantime i also filed a bug at the apparmor bugtracker:
https://bugs.launchpad.net/apparmor/+bug/1595451
Unfortunately they also could not help until now :-(
Regards
André
Am 22.06.2016 um 12:42 schrieb André Bauer:
> Hi Vijay,
>
> i just used "tail -f /var/log/g
1279747 (mainline) MODIFIED: spec: add CFLAGS=-DUSE_INSECURE_OPENSSL to
configure command-line for RHEL-5 only
** mchan...@redhat.com: No change posted, but bug 1279747 is in MODIFIED **
1338593 (mainline) ASSIGNED: clean posix locks based on client-id as part of
server_connection_cleanup
[m