kern/146528: [zfs] Severe memory leak in ZFS on i386
peter.maloney at brockmann-consult.de
Wed Jan 25 11:44:05 UTC 2012
When I built mine, my goal was to be able to rebuild the same thing I
tested later on a different machine, so I used a specific date in my
But you can also do:
# uname -a
FreeBSD bcnas1.bc.local 8.2-STABLE FreeBSD 8.2-STABLE #0: Thu Sep 29
15:06:03 CEST 2011
root at bcnas1.bc.local:/usr/obj/usr/src/sys/GENERIC amd64
Which as you can see, tells you a time somewhere around the csup'd
version (Sept 27), but it is actually the build time (probably 'make
I am not sure what it would say for something you get from an iso (would
it be a week after the release tag the day it was built, or the tag
date, etc.). But if you install a snapshot, such as the
8.2-STABLE-201105 iso you can find on ftp, it says 8.2-STABLE-201105
instead of 8.2-STABLE.
On 01/25/2012 11:48 AM, Damien Fleuriot wrote:
> Hijacking thread quickly.
> How do you guys usually check your build/csup date on -stable and such ?
> I guess I'd go with the latest kernel build date, but there may be
> better ways.
> On 1/25/12 10:58 AM, Peter Maloney wrote:
>> When was your 8.2-STABLE built / csup'd?
>> On 01/25/2012 09:40 AM, Michel Le Cocq wrote:
>>> Hi every body, I upgrade my Freebsd 8.2-STABLE i386 to 9.0 i386.
>>> Intel(R) Atom(TM) CPU D510 @ 1.66GHz
>>> real memory = 4294967296 (4096 MB)
>>> avail memory = 3127390208 (2982 MB)
>>> I'm on a ZFS Root file systeme on 2 USB drive and 6 sata drive for
>>> # zpool list
>>> NAME SIZE ALLOC FREE CAP DEDUP HEALTH ALTROOT
>>> data 931G 254G 677G 27% 1.00x ONLINE -
>>> stock 74.5G 12.4G 62.1G 16% 1.00x ONLINE -
>>> tank 696G 574G 122G 82% 1.00x ONLINE -
>>> zroot 3.66G 2.49G 1.17G 67% 1.00x ONLINE -
>>> Before upgrade, I must use some mana things in my /boot/loader.conf
>>> With this config my server was not so stable.
>>> Some days it work perfectly, some others it freeze with kmem_malloc
>>> kmem_map too small.
>>> Without this mana it freeze really often.
>>> The thing which make me upgrade is that after one of this crash after
>>> reboot it won't mount my data pool which was at 99% of his CAP. The
>>> only way I find to boot is to disconnect the pools drive and export
>>> Now I'm on exactly the same host after upgrade to 9.0 and it seems to
>>> work really really better (3 days up with out any trouble).
>>> Garrett Cooper a écrit:
>>>> The following reply was made to PR kern/146528; it has been noted by GNATS.
>>>> From: Garrett Cooper <yanegomi at gmail.com>
>>>> To: bug-followup at FreeBSD.org, EdwinGuy at GMail.com
>>>> Subject: Re: kern/146528: [zfs] Severe memory leak in ZFS on i386
>>>> Date: Sun, 9 Oct 2011 12:34:00 -0700
>>>> Could you please try upgrading to 8.2-STABLE or 9.0 and see if the
>>>> issue persists with ZFS v28?
>>>> freebsd-fs at freebsd.org mailing list
>>>> To unsubscribe, send any mail to "freebsd-fs-unsubscribe at freebsd.org"
> freebsd-fs at freebsd.org mailing list
> To unsubscribe, send any mail to "freebsd-fs-unsubscribe at freebsd.org"
Tel: +49 4152 889 300
Fax: +49 4152 889 333
E-mail: peter.maloney at brockmann-consult.de
More information about the freebsd-fs