quot;
>
> 2017-01-28 15:51 GMT+01:00 Tim Boundy <gigap...@gmail.com>:
> > Why was this bug closed? The original reported issue hasn't been
> addressed
> > at all.
>
> I thought it was, as you said "That patch seems to have resolved the
> System error issue&qu
Why was this bug closed? The original reported issue hasn't been addressed
at all.
That patch seems to have resolved the System error issue.
On 14 November 2016 at 07:24, Mathieu Parent <math.par...@gmail.com> wrote:
> Hi TIm,
>
> Can you try the proposed patch:
> https://bugzilla.samba.org/attachment.cgi?id=12657=edit
>
> Regards
>
> 2016-1
Yes, I have 2:4.4.7+dfsg-1 of libnss-winbind installed
I've attached the 'strace ping google.com' output when using wins in
nsswitch.conf
On 13 November 2016 at 08:44, Mathieu Parent <math.par...@gmail.com> wrote:
> is.Hello,
>
> 2016-11-09 10:14 GMT+01:00 Tim Boundy <
I've just updated to 2:4.4.7+dfsg-1 to see if there's any improvement.
Massive regression. Now I can't ping via dns.
ping: google.com: System error
If I remove wins from nsswitch.conf, dns starts working again.
I've noticed that my Windows client is advertising multiple entries:
root@fusion:~# nmblookup prodigy
192.168.0.55 prodigy<00>
192.168.56.1 prodigy<00>
It is doing this because there is a virtual network switch (VirtualBox) and
it's accessible through either IP address. If I disable the virtual
Package: winbind
Version: 2:4.4.3+dfsg-4
Severity: important
Dear Maintainer,
I have my debian stretch system set to use wins in nsswitch.conf. This has
worked fine until recently, where I
can no longer resolve Windows clients on the network. Using nmblookup and
wbinfo manually works fine,
is that after a clean restart of the array and then
running dumpe2fs, the only drive in the array that was read was /dev/sdd. I
find it strange that all the relevant filesystem metadata would sit
entirely on one drive in a multi drive array over a large range of LBAs.
On 24 August 2014 15:31, Tim Boundy
I have a stride value of 128 and a stripe_width value of 384. When I
created the filesystem with 4 drives (3 + 1), these were suggested values
to encourage rotation. Is this not correct?
Package: mdadm
Version: 3.3-2
Severity: normal
Tags: upstream
I have a RAID5 array using 4x 3TB WD Red drives. On occasion while writing to
the array, the write operation will stall. Using iostat, I can see that one
of the member disks shows 95% utilisation performing reads at approximately
10 matches
Mail list logo
