At Thu, 21 Jun 2018 10:48:28 +0300,
Toomas Soome wrote:
>
>
>
> > On 21 Jun 2018, at 09:00, KIRIYAMA Kazuhiko wrote:
> >
> > At Wed, 20 Jun 2018 23:34:48 -0400,
> > Allan Jude wrote:
> >>
> >> On 2018-06-20 21:36, KIRIYAMA Kazuhiko wrote:
> >>> Hi all,
> >>>
> >>> I've been reported ZFS
[cross-posting for advice on general debugging + network-specific thoughts]
TLDR since a week or so, probably around r335381 I can reliably get my machine
to hang*** by unloading pf, while there's network traffic (e.g. video streaming
or rsync) and waiting a minute or two I still see it with
On Mon, Jun 25, 2018 at 02:04:32AM +, Rick Macklem wrote:
> Konstantin Belousov wrote:
> >On Sat, Jun 23, 2018 at 09:03:02PM +, Rick Macklem wrote:
> >> During testing of the pNFS server I have been frequently
> >> killing/restarting the nfsd.
> >> Once in a while, the "slave" nfsd
On Mon, Jun 25, 2018 at 11:40 AM, tech-lists wrote:
> On 25/06/2018 16:37, Warner Losh wrote:
>
>> While the compat stuff generally works, there are edge cases where it
>> will fail when you have a mixed environment. You're best bet is to
>> reinstall all ports. If you do just a few, you'll hit
On 6/24/2018 12:57 AM, Gary Jennejohn wrote:
> On Sat, 23 Jun 2018 17:05:16 +0200
> Dimitry Andric wrote:
>
>> On 23 Jun 2018, at 15:40, Gary Jennejohn wrote:
>>>
>>> There is a strange error building clang with this use case:
>>>
>>> cd /usr/src
>>> make -j10 makeworld
>>
>> What's the
On Sun, Jun 24, 2018 at 12:03:29PM +0200, Alexander Leidinger wrote:
>
> I don't have hard evidence, but there is enough "smell" to open up a
> discussion...
>
> Short:
> Can it be that enabling numa in the kernel is the reason why some
> people see instability with zfs and usage of swap
On 25/06/2018 16:37, Warner Losh wrote:
While the compat stuff generally works, there are edge cases where it
will fail when you have a mixed environment. You're best bet is to
reinstall all ports. If you do just a few, you'll hit the edge cases.
Hi,
What do you mean by "mixed environment"?
On Mon, Jun 25, 2018 at 6:40 AM, tech-lists wrote:
> Hello,
>
> When upgrading an old-ish 12-current (r317212), as per:
>
> 20170523:
>> The "ino64" 64-bit inode project has been committed, which extends
>> a number of types to 64 bits. In order to upgrade, carefully
>> follow
On 25.06.2018 17:03, Dimitry Andric wrote:
> Which file system is
> /data/src/sys/netgraph/bluetooth/drivers/ubtbcmfw/ubtbcmfw.c
> on? Is your obj directory on another file system?
It is two different local ZFS FSes on the same pool
zpool/usr/obj 4.83G 109G 4.83G /usr/obj
On 22 Jun 2018, at 16:18, Lev Serebryakov wrote:
>
> I tripped over very strange, but repeateable (in my conditions) bug in
> clang on 12-CURRENT. This message will be rather long, as I need to
> describe all details.
...
> /usr/bin/cc -target x86_64-unknown-freebsd12.0
>
Hello,
When upgrading an old-ish 12-current (r317212), as per:
20170523:
The "ino64" 64-bit inode project has been committed, which extends
a number of types to 64 bits. In order to upgrade, carefully follow
the full procedure documented below under the heading "To
In the last version of the top, units of memory measurements in GB.
I only have 16GB of memory. And now I do not see the dynamics of treason.
--
-
Alex.
___
freebsd-current@freebsd.org mailing list
12 matches
Mail list logo
