Re: ZFS secondarycache on SSD problem on r255173

2013-10-18 Thread Vitalij Satanivskij
Hello. Yesterday system was rebooted with vfs.zfs.trim.enabled=0 System version 10.0-BETA1 FreeBSD 10.0-BETA1 #6 r256669, without any changes in code Uptime 10:51 up 16:41 sysctl vfs.zfs.trim.enabled vfs.zfs.trim.enabled: 0 Around 2 hours ago errors counter's

gcc kernel build fail @ SVN r256730

2013-10-18 Thread Michael Butler
-current kernel compiled with gcc fails with: cc1: warnings being treated as errors /usr/src/sys/geom/label/g_label.c: In function 'g_label_resize': /usr/src/sys/geom/label/g_label.c:135: warning: null format string [-Wformat] *** [g_label.o] Error code 1

Re: ZFS secondarycache on SSD problem on r255173

2013-10-18 Thread Steven Hartland
Hmm so that rules out a TRIM related issue. I wonder if the increase in ashift has triggered a problem in compression. What are all the values reported by: sysctl -a kstat.zfs.misc.arcstats Regards Steve - Original Message - From: Vitalij Satanivskij sa...@ukr.net To: Steven

Re: ZFS secondarycache on SSD problem on r255173

2013-10-18 Thread Vitalij Satanivskij
Just right now stats not to actual because of some another test. Test is simply all gpart information destroyed from ssd and They used as raw cache devices. Just 2013-10-18.11:30:49 zpool add disk1 cache /dev/ada1 /dev/ada2 /dev/ada3 So sizes at last l2_size and l2_asize in not actual.

Re: ZFS secondarycache on SSD problem on r255173

2013-10-18 Thread Steven Hartland
Looking at the l2arc compression code I believe that metadata is always compressed with lz4, even if compression is off on all datasets. This is backed up by what I'm seeing on my system here as it shows a non-zero l2_compress_successes value even though I'm not using compression at all. I

[rfc] removing the NDISulator

2013-10-18 Thread Adrian Chadd
Hi all, I'd like to remove the NDISulator. I've had many requests to update it to the latest NDIS version and support more of the 64 bit wifi drivers. But, to be perfectly honest, I have no desire to keep hacking at this. The world has changed quite a bit - we can port/reimplement drivers from

Re: BE Loader Menu (was Re: rcs)

2013-10-18 Thread Teske, Devin
On Oct 10, 2013, at 9:42 AM, Julian Elischer wrote: On 10/11/13 12:39 AM, Teske, Devin wrote: On Oct 10, 2013, at 9:06 AM, Julian Elischer wrote: On 10/10/13 1:05 AM, Teske, Devin wrote: I'm late to the party again ;D (didn't realize the rcs thread had turned BE) Both problems can be

Re: [rfc] removing the NDISulator

2013-10-18 Thread Steve Wills
I would love to have a native driver for this: none2@pci0:2:0:0: class=0x028000 card=0x00101028 chip=0x472714e4 rev=0x01 hdr=0x00 vendor = 'Broadcom Corporation' device = 'BCM4313 802.11b/g/n Wireless LAN Controller' class = network Are there docs or other drivers

Re: [rfc] removing the NDISulator

2013-10-18 Thread Steve Kargl
On Fri, Oct 18, 2013 at 08:53:54PM +, Steve Wills wrote: I would love to have a native driver for this: none2@pci0:2:0:0: class=0x028000 card=0x00101028 chip=0x472714e4 rev=0x01 hdr=0x00 vendor = 'Broadcom Corporation' device = 'BCM4313 802.11b/g/n Wireless LAN

Re: [rfc] removing the NDISulator

2013-10-18 Thread Adrian Chadd
Hi, On 18 October 2013 13:53, Steve Wills swi...@freebsd.org wrote: I would love to have a native driver for this: none2@pci0:2:0:0: class=0x028000 card=0x00101028 chip=0x472714e4 rev=0x01 hdr=0x00 vendor = 'Broadcom Corporation' device = 'BCM4313 802.11b/g/n

Re: [rfc] removing the NDISulator

2013-10-18 Thread Nathan Whitehorn
On 10/18/13 16:01, Steve Kargl wrote: On Fri, Oct 18, 2013 at 08:53:54PM +, Steve Wills wrote: I would love to have a native driver for this: none2@pci0:2:0:0: class=0x028000 card=0x00101028 chip=0x472714e4 rev=0x01 hdr=0x00 vendor = 'Broadcom Corporation' device =

Re: [rfc] removing the NDISulator

2013-10-18 Thread Adrian Chadd
bwn(4) requires a lot more than just an additional PCI ID. The driver is somewhat architected for all the different RF and PHY modules that plug into the internal bus (the whole SIBA thing) but it does sorely need updating. Thanks, -adrian On 18 October 2013 14:04, Nathan Whitehorn

Re: [rfc] removing the NDISulator

2013-10-18 Thread Alfred Perlstein
On 10/18/13 2:04 PM, Nathan Whitehorn wrote: On 10/18/13 16:01, Steve Kargl wrote: On Fri, Oct 18, 2013 at 08:53:54PM +, Steve Wills wrote: I would love to have a native driver for this: none2@pci0:2:0:0: class=0x028000 card=0x00101028 chip=0x472714e4 rev=0x01 hdr=0x00 vendor

Re: [rfc] removing the NDISulator

2013-10-18 Thread Adrian Chadd
I don't know how many times i can say it needs a maintainer and it needs updating. So yeah, it needs (a) a maintainer, (b) updating. -adrian On 18 October 2013 15:47, Alfred Perlstein bri...@mu.org wrote: On 10/18/13 2:04 PM, Nathan Whitehorn wrote: On 10/18/13 16:01, Steve Kargl wrote:

[head tinderbox] failure on ia64/ia64

2013-10-18 Thread FreeBSD Tinderbox
TB --- 2013-10-19 01:35:56 - tinderbox 2.20 running on freebsd-current.sentex.ca TB --- 2013-10-19 01:35:56 - FreeBSD freebsd-current.sentex.ca 8.3-PRERELEASE FreeBSD 8.3-PRERELEASE #0: Mon Mar 26 13:54:12 EDT 2012 d...@freebsd-current.sentex.ca:/usr/obj/usr/src/sys/GENERIC amd64 TB ---

[head tinderbox] failure on mips64/mips

2013-10-18 Thread FreeBSD Tinderbox
TB --- 2013-10-19 03:31:17 - tinderbox 2.20 running on freebsd-current.sentex.ca TB --- 2013-10-19 03:31:17 - FreeBSD freebsd-current.sentex.ca 8.3-PRERELEASE FreeBSD 8.3-PRERELEASE #0: Mon Mar 26 13:54:12 EDT 2012 d...@freebsd-current.sentex.ca:/usr/obj/usr/src/sys/GENERIC amd64 TB ---