On Wed, Apr 23, 2014 at 03:30:51AM -0500, Shawn K. Quinn wrote:
> On Tue, Apr 22, 2014, at 11:24 PM, Chris Cappuccio wrote:
> > there are some interesting patches in bitrig that you could try to
> > apply in the openbsd tree, recompile your kernel and see if
> > any of them help.
> >
> > https:/
On Wed, Apr 23, 2014 at 9:06 AM, Marc Espie wrote:
> On Tue, Apr 22, 2014 at 05:11:35PM -0500, Shawn K. Quinn wrote:
> > Also, it should be noted tmpfs allocates the entire amount of memory
> > available by default.
>
> Nope. Your wording is incorrect. mfs *reserves* memory. tmpfs doesn't.
> If y
On Tue, Apr 22, 2014, at 11:24 PM, Chris Cappuccio wrote:
> there are some interesting patches in bitrig that you could try to
> apply in the openbsd tree, recompile your kernel and see if
> any of them help.
>
> https://github.com/bitrig/bitrig/commit/c2ce175
> "Fix integer overflows handling o
On Tue, Apr 22, 2014 at 05:11:35PM -0500, Shawn K. Quinn wrote:
> Also, it should be noted tmpfs allocates the entire amount of memory
> available by default.
Nope. Your wording is incorrect. mfs *reserves* memory. tmpfs doesn't.
If you want to put limits on it, you can use parameters to mount to
On Mon, Apr 21, 2014, at 12:26 AM, Shawn K. Quinn wrote:
> With a tmpfs mounted on /tmp:
>
> $ cd /tmp
> $ dd if=/dev/zero of=0 bs=1M ; sync ; sleep 5 ; rm 0
>
> results in dmesg getting spammed with:
>
> uao_flush: strange, got an out of range flush (fixed)
Forgot to mention, this is on amd64
With a tmpfs mounted on /tmp:
$ cd /tmp
$ dd if=/dev/zero of=0 bs=1M ; sync ; sleep 5 ; rm 0
results in dmesg getting spammed with:
uao_flush: strange, got an out of range flush (fixed)
If the tmpfs is large enough (larger than physical RAM, maybe?) another
error happens (I don't have it handy
6 matches
Mail list logo
