Re: tmpfs is zero bytes (no free space), maybe a zfs bug?
On Wed, Jan 19, 2011 at 05:27:38PM +0100, Ivan Voras wrote: > On 19 January 2011 16:02, Kostik Belousov wrote: > > >> http://people.freebsd.org/~ivoras/diffs/tmpfs.h.patch > >> > >> I don't think this is a complete solution but it's a start. If you can, > >> try it and see if it helps. > > This is not a start, and actually a step in the wrong direction. > > Tmpfs is wrong now, but the patch would make the wrongness even bigger. > > > > Issue is that the current tmpfs calculation should not depend on the > > length of the inactive queue or the amount of free pages. This data only > > measures the pressure on the pagedaemon, and has absolutely no relation > > to the amount of data that can be put into anonymous objects before the > > system comes out of swap. > > > > vm_lowmem handler is invoked in two situations: > > - when KVA cannot satisfy the request for the space allocation; > > - when pagedaemon have to start the scan. > > None of the situations has any direct correlation with the fact that > > tmpfs needs to check, that is "Is there enough swap to keep all my > > future anonymous memory requests ?". > > > > Might be, swap reservation numbers can be useful to the tmpfs reporting. > > Also might be, tmpfs should reserve the swap explicitely on start, instead > > of making attempts to guess how much can be allocated at random moment. > > Thank you for your explanation! I'm still not very familiar with VM > and VFS. Could you also read my report at > http://www.mail-archive.com/freebsd-current@freebsd.org/msg126491.html > ? I'm curious about the fact that there is lots of 'free' memory here > in the same situation. This is another ugliness in the dynamic calculation. Your wired is around 15GB, that is always greater then available swap + free + inactive. As result, tmpfs_mem_info() always returns 0. In this situation TMPFS_PAGES_MAX() seems to return negative value, and then TMPFS_PAGES_AVAIL() clamps at 0. > > Do you think that there is something which can be done as a band-aid > without a major modification to tmpfs? pgpZ2A2eFkpjo.pgp Description: PGP signature
Re: KERN - mfi driver for Dell raid h200 on r210 servers
On 29 January 2011 23:24, Bjoern A. Zeeb wrote:
> On Sat, 29 Jan 2011, Damien Fleuriot wrote:
>
>> Hello lists,
>>
>>
>>
>> I'm trying to get FreeBSD 8.0 or 8.1 to run on a Dell poweredge r210
>> server.
>>
>> It ships with a SATA/SAS h200 RAID controller.
>>
>>
>> Sadly, the MFI driver doesn't seem to register for this card...
>>
>>
>> Find below the pciconf -lcvb
>>
>> --
>> none6@pci0:1:0:0: class=0x010700 card=0x1f1d1028 chip=0x00721000
>> rev=0x02 hdr=0x00
>> vendor = 'LSI Logic (Was: Symbios Logic, NCR)'
>> class = mass storage
>> subclass = SAS
>> bar [10] = type I/O Port, range 32, base 0xfc00, size 256, enabled
>> bar [14] = type Memory, range 64, base 0xdf2b, size 65536, enabled
>> bar [1c] = type Memory, range 64, base 0xdf2c, size 262144,
>> enabled
>> cap 01[50] = powerspec 3 supports D0 D1 D2 D3 current D0
>> cap 10[68] = PCI-Express 2 endpoint max data 256(4096) link x8(x8)
>> cap 03[d0] = VPD
>> cap 05[a8] = MSI supports 1 message, 64 bit
>> cap 11[c0] = MSI-X supports 15 messages in map 0x14
>> --
>>
>>
>> I have added the following to /usr/src/sys/dev/mfi/mfi_pci.c at line 119:
>> --
>> {0x1000, 0x0072, 0x1028, 0x1f1e, MFI_FLAGS_GEN2, "Dell PERC H200
>> Integrated"},
>> --
>
> It's 1f1d not 1f1e. I hope it was only a paste problem into email?
>
Ok I've loaded the newly patched mfi.ko and booted a MFS image.
Here's the relevant snip from dmesg.run :
at
mfi0: port 0xfc00-0xfcff mem
0xdf2b-0xdf2b,0xdf2c-0xdf2f irq 16 at device 0.0 on
pci1
mfi0: Megaraid SAS driver Ver 3.00
mfi0: firmware stuck in state 0
mfi0: Firmware not in READY state, error 6
I'll have to try mps then, unless someone has an idea about this
"stuck in state 0" thing.
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: KERN - mfi driver for Dell raid h200 on r210 servers
I've "backported" the mps driver to 8.2 (I used cp -r :)) and I have generated an img suited to the dedibox (that's what you are targeting, right? :)) I tried to test it in vmware but I have a password issue right now. It is also a ZFSv28 image. Le 30 janv. 2011 à 01:56, Damien Fleuriot a écrit : > On 29 Jan 2011, at 20:26, Andrew Thompson wrote: > >> On 30 January 2011 06:20, Damien Fleuriot wrote: >>> Hello lists, >>> >>> >>> >>> I'm trying to get FreeBSD 8.0 or 8.1 to run on a Dell poweredge r210 server. >>> >>> It ships with a SATA/SAS h200 RAID controller. >>> >> >> This card may need the mps(4) driver which is only in HEAD at the moment. >> >> >> Andrew > > > Will give this a try if Bjoern's advice doesn't work for me, although I'll > come back for directions on how to cleanly port mps on 8.x > then.___ > freebsd-stable@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org" > ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: KERN - mfi driver for Dell raid h200 on r210 servers
On 30.1.2011 г. 13:30 ч., Damien Fleuriot wrote: Ok I've loaded the newly patched mfi.ko and booted a MFS image. Here's the relevant snip from dmesg.run : at mfi0: port 0xfc00-0xfcff mem 0xdf2b-0xdf2b,0xdf2c-0xdf2f irq 16 at device 0.0 on pci1 mfi0: Megaraid SAS driver Ver 3.00 mfi0: firmware stuck in state 0 mfi0: Firmware not in READY state, error 6 I'll have to try mps then, unless someone has an idea about this "stuck in state 0" thing. You should first try the mfi driver found in the LSI site (http://www.lsi.com). It does support few more variants than the FreeBSD driver. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: KERN - mfi driver for Dell raid h200 on r210 servers
Indeed that is, the bsd install is aimed at a r210 EG server :) Is there any place one can get your image ? --- Fleuriot Damien On 30 Jan 2011, at 13:10, Ollivier Robert wrote: > I've "backported" the mps driver to 8.2 (I used cp -r :)) and I have > generated an img suited to the dedibox (that's what you are targeting, right? > :)) > > I tried to test it in vmware but I have a password issue right now. > > It is also a ZFSv28 image. > > Le 30 janv. 2011 à 01:56, Damien Fleuriot a écrit : > >> On 29 Jan 2011, at 20:26, Andrew Thompson wrote: >> >>> On 30 January 2011 06:20, Damien Fleuriot wrote: Hello lists, I'm trying to get FreeBSD 8.0 or 8.1 to run on a Dell poweredge r210 server. It ships with a SATA/SAS h200 RAID controller. >>> >>> This card may need the mps(4) driver which is only in HEAD at the moment. >>> >>> >>> Andrew >> >> >> Will give this a try if Bjoern's advice doesn't work for me, although I'll >> come back for directions on how to cleanly port mps on 8.x >> then.___ >> freebsd-stable@freebsd.org mailing list >> http://lists.freebsd.org/mailman/listinfo/freebsd-stable >> To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org" >> ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: KERN - mfi driver for Dell raid h200 on r210 servers
On 30 Jan 2011, at 13:14, Daniel Kalchev wrote: > On 30.1.2011 г. 13:30 ч., Damien Fleuriot wrote: >> >> Ok I've loaded the newly patched mfi.ko and booted a MFS image. >> Here's the relevant snip from dmesg.run : >> at >> mfi0: port 0xfc00-0xfcff mem >> 0xdf2b-0xdf2b,0xdf2c-0xdf2f irq 16 at device 0.0 on >> pci1 >> mfi0: Megaraid SAS driver Ver 3.00 >> mfi0: firmware stuck in state 0 >> mfi0: Firmware not in READY state, error 6 >> >> >> I'll have to try mps then, unless someone has an idea about this >> "stuck in state 0" thing. > You should first try the mfi driver found in the LSI site > (http://www.lsi.com). I'll have a look cheers___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: KERN - mfi driver for Dell raid h200 on r210 servers
On Sun, 30 Jan 2011, Damien Fleuriot wrote: Ok I've loaded the newly patched mfi.ko and booted a MFS image. Here's the relevant snip from dmesg.run : at mfi0: port 0xfc00-0xfcff mem 0xdf2b-0xdf2b,0xdf2c-0xdf2f irq 16 at device 0.0 on pci1 mfi0: Megaraid SAS driver Ver 3.00 mfi0: firmware stuck in state 0 mfi0: Firmware not in READY state, error 6 I'll have to try mps then, unless someone has an idea about this "stuck in state 0" thing. it means that you should ask Dell for the information as the mfi(4) driver needs some special handling to support that exact chip. Probably needs some special initialization and a couple of if ()s, as usual. LSI/Dell are the people to talk to. /bz -- Bjoern A. Zeeb You have to have visions! Going to jail sucks -- All my daemons like it! http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/jails.html ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: KERN - mfi driver for Dell raid h200 on r210 servers
According to Garrett Cooper: > +1. PERC7 should be supported by mfi(4) (required bits may need to > be added to mfi(4) though as you've pointed out, but additional > details may need to be obtained from Dell). I've seen mention of the mps driver (in head) and of the mfi one. Which one is the right one? For the OP: I may be gaining access to a test system (Dell R210 / as in new dedibox[1]) tomorrow on which I could test my mfsboot image... -- Ollivier ROBERT -=- FreeBSD: The Power to Serve! -=- robe...@keltia.freenix.fr In memoriam to Ondine : http://ondine.keltia.net/ ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: KERN - mfi driver for Dell raid h200 on r210 servers
According to Ollivier Robert: > For the OP: I may be gaining access to a test system (Dell R210 / as in new > dedibox[1]) tomorrow on which I could test my mfsboot image... Here is the missing link (French): http://www.online.net/serveur-dedie/comparatif-serveur-dedie-start.xhtml http://www.online.net/serveur-dedie/comparatif-serveur-dedie-pro.xhtml -- Ollivier ROBERT -=- FreeBSD: The Power to Serve! -=- robe...@keltia.freenix.fr In memoriam to Ondine : http://ondine.keltia.net/ ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
RELEASE_6 -> RELEASE_8
I was trying to upgrade a machine from RELEASE_6 (latest) to RELEASE_8 (latest) via source. I was unable to get make buildworld to complete. There were two problems sets of problems. libelf and sys headers were not available to some of the solaris derived parts. include_next's failed. Adding extra -I's to the Makefiles allowed these parts to complete. The first missing header was sys/elf.h so that should help locate the correct Makefile. Linking then failed due to __stack_chk_fail_local not being found. i386 build. Sorry this report is not more complete as I blew away the tree and restarted on RELEASE_7 as a stepping stone to RELEASE_8. RELEASE_7 latest will at least compile. However it will only run in safe mode as it dies in ar5212Detach with a kernel fault. I suspect this will also be a problem for RELEASE_8. Mark -- Mark Andrews, ISC 1 Seymour St., Dundas Valley, NSW 2117, Australia PHONE: +61 2 9871 4742 INTERNET: ma...@isc.org ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: RELEASE_6 -> RELEASE_8
On 1/30/2011 6:45 PM, Mark Andrews wrote: > I was trying to upgrade a machine from RELEASE_6 (latest) > to RELEASE_8 (latest) via source. I was unable to get > make buildworld to complete. Strange, I have done a number of machines going from RELENG_6, RELENG_7 and then RELENG_8 without too much issue. The ports can be a bit problematic, but of the half dozen or so I have done, it hasnt been an issue. Were you using a custom kernel, or GENERIC as defined from each of the branches ? ---Mike ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: RELEASE_6 -> RELEASE_8
In message <4d46119f.5060...@sentex.net>, Mike Tancsa writes: > On 1/30/2011 6:45 PM, Mark Andrews wrote: > > I was trying to upgrade a machine from RELEASE_6 (latest) > > to RELEASE_8 (latest) via source. I was unable to get > > make buildworld to complete. > > Strange, I have done a number of machines going from RELENG_6, RELENG_7 > and then RELENG_8 without too much issue. The ports can be a bit > problematic, but of the half dozen or so I have done, it hasnt been an > issue. Were you using a custom kernel, or GENERIC as defined from each > of the branches ? It's the double release jump that doesn't work. Looking at 7.x the headers needed are installed in /usr/include. Similarly 7.x's gcc has the symbol but doesn't turn on the compiler flags which use it. Basically RELENG_8 is not completely building against itself. Trying to go from 6.x to 8.x is showing some of places where the new OS doesn't build against itself. This was with GENERIC for all builds and almost no ports installed. > ---Mike -- Mark Andrews, ISC 1 Seymour St., Dundas Valley, NSW 2117, Australia PHONE: +61 2 9871 4742 INTERNET: ma...@isc.org ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: RELEASE_6 -> RELEASE_8
Mark Andrews writes:
>
> In message <4d46119f.5060...@sentex.net>, Mike Tancsa writes:
> > On 1/30/2011 6:45 PM, Mark Andrews wrote:
> > > I was trying to upgrade a machine from RELEASE_6 (latest)
> > > to RELEASE_8 (latest) via source. I was unable to get
> > > make buildworld to complete.
> >
> > Strange, I have done a number of machines going from RELENG_6, RELENG_7
> > and then RELENG_8 without too much issue. The ports can be a bit
> > problematic, but of the half dozen or so I have done, it hasnt been an
> > issue. Were you using a custom kernel, or GENERIC as defined from each
> > of the branches ?
>
> It's the double release jump that doesn't work. Looking at 7.x the
> headers needed are installed in /usr/include. Similarly 7.x's gcc
> has the symbol but doesn't turn on the compiler flags which use it.
> Basically RELENG_8 is not completely building against itself. Trying
> to go from 6.x to 8.x is showing some of places where the new OS
> doesn't build against itself.
>
> This was with GENERIC for all builds and almost no ports installed.
The following Makefiles needed to be modified to add
-I${.CURDIR}/../../../lib/libelf and/or -I${.CURDIR}/../../../sys.
/usr/release8/src/cddl/usr.bin/sgsmsg/Makefile lib/libelf
/usr/release8/src/cddl/lib/libctf/Makefile lib/libelf sys
/usr/release8/src/cddl/usr.bin/ctfconvert/Makefile lib/libelf sys
/usr/release8/src/cddl/usr.bin/ctfmerge/Makefile sys
e.g.
CFLAGS+=-I${.CURDIR}/../../../sys/cddl/compat/opensolaris \
-I${.CURDIR}/../../../cddl/compat/opensolaris/include \
-I${.CURDIR}/../../../lib/libelf \
-I${.CURDIR}/../../../sys \
-I${OPENSOLARIS_USR_DISTDIR} \
-I${OPENSOLARIS_SYS_DISTDIR} \
-I${OPENSOLARIS_USR_DISTDIR}/head \
-I${OPENSOLARIS_USR_DISTDIR}/tools/ctf/common \
-I${OPENSOLARIS_USR_DISTDIR}/tools/ctf/cvt \
-I${OPENSOLARIS_SYS_DISTDIR}/uts/common
"make make" is also needed for 6.x -> 8.x so that should be
added to UPDATING.
The build will then run until stopping in libexec/atrun with
/usr/release8/usr/release8/src/tmp/usr/lib/libpam.so: undefined reference to
`__stack_chk_fail_local'
--
Mark Andrews, ISC
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742 INTERNET: ma...@isc.org
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
