On Tue, Sep 22, 2015, at 15:57, Michael Butler wrote:
> On 09/22/15 16:20, Adam Vande More wrote:
> > On Tue, Sep 22, 2015 at 2:26 PM, Martin Birgmeier wrote:
>
> >> I am quite sure that the
> >> cause is to be found there
> >>
> >
> > I don't see any cause for surety in the info you have give
On 09/22/15 16:20, Adam Vande More wrote:
> On Tue, Sep 22, 2015 at 2:26 PM, Martin Birgmeier wrote:
>> I am quite sure that the
>> cause is to be found there
>>
>
> I don't see any cause for surety in the info you have given us. Have you
> tried any basic steps like monitoring usage during the
On Tue, Sep 22, 2015 at 2:26 PM, Martin Birgmeier wrote:
> I don't think it is related to zfs. The 8GB machine did not even have
> zfs loaded or a zfs file system when I first reported the problem. (The
> problem with 'zfs send' only happened recently on the 16GB machine.)
>
> I'd like to know wh
I don't think it is related to zfs. The 8GB machine did not even have
zfs loaded or a zfs file system when I first reported the problem. (The
problem with 'zfs send' only happened recently on the 16GB machine.)
I'd like to know what has changed between FBSD 9 and 10 regarding memory
management and
To me this sounds a lot like vbox and zfs arc are fighting for resources.
What does the memory line in top look like when this problem happens?
A simple workaround would be to limit zfs arc in loader.conf if that is the
problem.
Am 22.09.2015 5:13 nachm. schrieb "Martin Birgmeier" :
>
> This did
This did not happen when the machine was running FreeBSD 9.2 with
virtualbox-ose-4.3.20 installed. So I would not qualify this as "known
behavior".
One server has 16G main memory, a VM gets 3G. The other has 8G main mem and
again 3G allocated to the VM.
This is definitely a bug in how VirtualB
