Re: SOLVED: 8.1 xl + dual-speed Netgear hub = yoyo
Out of pure interest, I'd love to see whether xl on an earlier kernel (say 4.x, if the hardware can even run it) or even 6.x would work. Adrian ___ 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
Questions about using gvirstor as a RAID0 solution
Hi all,
I would like to use gvirstor as a thin provisioning solution for a
mysql server, but I have some doubts about using it:
a) Do I need to put geom_virstor_load=YES on loader.conf or this
kernel module is loaded automatically at boot If I create gvirstor
volume using the label option??
b) Does gvirstor supports UFS journaling?? For example:
gjournal label /dev/virstor/mydata
newfs -O 2 -J /dev/virstor/mydata
c) Can i use growfs utility If I need to expand a virstor volume at
filesystem level??
Thanks
P.D: I am using FreeBSD9-RC1 in this server
--
CL Martinez
carlopmart {at} gmail {d0t} com
___
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: Questions about using gvirstor as a RAID0 solution
On 24/10/2011 11:21, carlopmart wrote: Hi all, I would like to use gvirstor as a thin provisioning solution for a mysql server, but I have some doubts about using it: Yes, it's kind of what it was created for... a) Do I need to put geom_virstor_load=YES on loader.conf or this kernel module is loaded automatically at boot If I create gvirstor volume using the label option?? You need to load the module yourself, the same as with other GEOM modules. b) Does gvirstor supports UFS journaling?? For example: gjournal label /dev/virstor/mydata newfs -O 2 -J /dev/virstor/mydata You can do that. It will be very inefficient (i.e. you will only avoid fscks, there will probably be no performance gains at all) but nothing should break. Both virstor and gjournal add their overheads (specifically, they can be seek-intensive in different ways), so you wouldn't want to use either if sustained random IO performance is important. On the other hand, since you are using 9-stable, you can also use the journaled soft-updates instead of gjournal, for much better efficiency. c) Can i use growfs utility If I need to expand a virstor volume at filesystem level?? Not exactly; virstor will immediately create a volume with large virtual size (whatever you specify at the volume creation) ragardless of how many physical devices you have. If you add more physical devices to the virstor later, you do not have to do anything with the file system itself, it will still see the original large virtual size. If you are talking about expanding the virtual volume size, that's not implemented yet (and in that case you would need to use growfs). signature.asc Description: OpenPGP digital signature
Re: Questions about using gvirstor as a RAID0 solution
On 10/24/2011 12:12 PM, Ivan Voras wrote:
On 24/10/2011 11:21, carlopmart wrote:
Hi all,
I would like to use gvirstor as a thin provisioning solution for a
mysql server, but I have some doubts about using it:
Yes, it's kind of what it was created for...
a) Do I need to put geom_virstor_load=YES on loader.conf or this
kernel module is loaded automatically at boot If I create gvirstor
volume using the label option??
You need to load the module yourself, the same as with other GEOM modules.
b) Does gvirstor supports UFS journaling?? For example:
gjournal label /dev/virstor/mydata
newfs -O 2 -J /dev/virstor/mydata
You can do that. It will be very inefficient (i.e. you will only avoid
fscks, there will probably be no performance gains at all) but nothing
should break. Both virstor and gjournal add their overheads
(specifically, they can be seek-intensive in different ways), so you
wouldn't want to use either if sustained random IO performance is important.
On the other hand, since you are using 9-stable, you can also use the
journaled soft-updates instead of gjournal, for much better efficiency.
c) Can i use growfs utility If I need to expand a virstor volume at
filesystem level??
Not exactly; virstor will immediately create a volume with large virtual
size (whatever you specify at the volume creation) ragardless of how
many physical devices you have. If you add more physical devices to the
virstor later, you do not have to do anything with the file system
itself, it will still see the original large virtual size.
If you are talking about expanding the virtual volume size, that's not
implemented yet (and in that case you would need to use growfs).
Solved. Many thanks Ivan.
--
CL Martinez
carlopmart {at} gmail {d0t} com
___
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: Call for testers : ALi/ULi M5261/M5263 ethernet controller
On Sun, Oct 16, 2011 at 05:22:13PM -0700, YongHyeon PYUN wrote: Hi, If you have ALi/ULi M5261/M5263 ethernet controller please try the patch at the following URL and let me know how it works. http://people.freebsd.org/~yongari/dc/dc.uli562x.diff The patch was generated against latest HEAD and it should be cleanly applied to latest stable/8 and stable/7. I committed revised version to HEAD(r226699, r226701). Thanks. ___ 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: 8.1 xl + dual-speed Netgear hub = yoyo
On 23-10-2011 17:09, per...@pluto.rain.com wrote: but there was no forwarding table and all packets were forwarded to all ports. I always figured that's normal for a hub as opposed to a switch. I also remember that SOME hubs of that era had series problems if the cable was too short. How come I feel old. Well I think that that was the reason why thick-Ethernet used to have repeaters and bridges. Repeaters just did what they said, on the most basic electrical level. Nothing more that a 2 port HUB, but then with MUI connectors. They where just part of the collision domain. Bridges actually learned which hosts where on the left and the right side. And only bridged when they really needed to. Otherwise they'd leave the traffic on the segment where it originated. It did segment the collision domain into two parts. And they used to be horrendously expensive and only run 10Mbit. --WjW ___ 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: 8.1 xl + dual-speed Netgear hub = yoyo
On Fri, Oct 21, 2011 at 1:28 AM, Damien Fleuriot m...@my.gd wrote: On 10/21/11 5:00 PM, per...@pluto.rain.com wrote: I have an 8.1-RELEASE system with an xl on the mainboard: xl0: 3Com 3c905C-TX Fast Etherlink XL port 0xdc80-0xdcff mem 0xf8fffc00-0xf8fffc7f irq 16 at device 4.0 on pci2 miibus0: MII bus on xl0 xlphy0: 3c905C 10/100 internal PHY PHY 24 on miibus0 xlphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto xl0: Ethernet address: 00:b0:d0:22:5a:14 xl0: [ITHREAD] It has been working properly while connected to an old 10-BaseT hub, but when I moved it to a (not as old) Netgear 10/100 dual-speed hub the link started to yo-yo: Pray tell, what's a dual-speed hub , marketing mumbo-jumbo ? If that's a hub that supports negotiation of different speeds (10 vs 100), then yes, I call that marketing mumbo-jumbo ;) Go back to the days of hubs, and the first 10/100 Mbps hubs from just about every manufacturer was labelled dual-speed. Meaning, it supported 10 Mbps connections and 100 Mbps connection (dual meaning two). ;) 3Com OfficeConnect hubs are all labelled dual-speed. With the advent of switches, the dual-speed moniker was pretty much universally dropped in favour of just listing the speeds it supported (10/100, 10/100/1000, etc). Maybe it's marketing mumbo jumbo, but it was pretty universal for the time. -- Freddie Cash fjwc...@gmail.com ___ 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
ntpd couldn't resolve host name on system boot
Hi all, I have a problem with ntpd on many of our servers running 8.2-RELEASE or newer. Some of them are newly installed, most of them are 7.x upgraded to 8.2 or 8-STABLE amd64 with GENERIC. Ntpd can't resolve host names on boot. This error did not existed on 7.x Oct 24 12:45:22 vcela kernel: Trying to mount root from ufs:/dev/mirror/gm0s1a Oct 24 12:45:23 vcela named[757]: starting BIND 9.6.-ESV-R3 -t /var/named -u bind Oct 24 12:45:23 vcela named[757]: built with '--prefix=/usr' '--infodir=/usr/share/info' '--mandir=/usr/share/man' '--enable-threads' '--enable-getifaddrs' '--disable-linux-caps' '--with-openssl=/usr' '--with-randomdev=/dev/random' '--without-idn' '--without-libxml2' Oct 24 12:45:23 vcela named[757]: command channel listening on 127.0.0.1#953 Oct 24 12:45:23 vcela named[757]: command channel listening on ::1#953 Oct 24 12:45:23 vcela named[757]: running Oct 24 12:45:24 vcela ntpd[960]: ntpd 4.2.4p5-a (1) Oct 24 12:45:24 vcela kernel: nfe0: link state changed to UP Oct 24 12:45:24 vcela kernel: acd0: FAILURE - ATA_IDENTIFY status=51READY,DSC,ERROR error=4ABORTED LBA=0 Oct 24 12:45:31 vcela snmpd[1333]: send: Connection refused Oct 24 12:45:43 vcela ntpd_initres[986]: host name not found: 0.freebsd.pool.ntp.org Oct 24 12:45:43 vcela ntpd_initres[986]: couldn't resolve `0.freebsd.pool.ntp.org', giving up on it Oct 24 12:45:43 vcela ntpd_initres[986]: host name not found: 1.freebsd.pool.ntp.org Oct 24 12:45:43 vcela ntpd_initres[986]: couldn't resolve `1.freebsd.pool.ntp.org', giving up on it Oct 24 12:45:43 vcela ntpd_initres[986]: host name not found: 2.freebsd.pool.ntp.org Oct 24 12:45:43 vcela ntpd_initres[986]: couldn't resolve `2.freebsd.pool.ntp.org', giving up on it Is there any know changes in network drivers (nfe or bge) or in order of rc scripts? It seems that nfe interface is bringed up too late. I know there is rc.d/netwait in 8-STABLE, but it is not available on 8.2-RELEASE and I think that there is some regression as this error was not there in the time of FreeBSD 7.x. Miroslav Lachman ___ 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: ntpd couldn't resolve host name on system boot
On Tue, Oct 25, 2011 at 12:50:29AM +0200, Miroslav Lachman wrote: I have a problem with ntpd on many of our servers running 8.2-RELEASE or newer. Some of them are newly installed, most of them are 7.x upgraded to 8.2 or 8-STABLE amd64 with GENERIC. Ntpd can't resolve host names on boot. This error did not existed on 7.x Oct 24 12:45:22 vcela kernel: Trying to mount root from ufs:/dev/mirror/gm0s1a Oct 24 12:45:23 vcela named[757]: starting BIND 9.6.-ESV-R3 -t /var/named -u bind Oct 24 12:45:23 vcela named[757]: built with '--prefix=/usr' '--infodir=/usr/share/info' '--mandir=/usr/share/man' '--enable-threads' '--enable-getifaddrs' '--disable-linux-caps' '--with-openssl=/usr' '--with-randomdev=/dev/random' '--without-idn' '--without-libxml2' Oct 24 12:45:23 vcela named[757]: command channel listening on 127.0.0.1#953 Oct 24 12:45:23 vcela named[757]: command channel listening on ::1#953 Oct 24 12:45:23 vcela named[757]: running Oct 24 12:45:24 vcela ntpd[960]: ntpd 4.2.4p5-a (1) Oct 24 12:45:24 vcela kernel: nfe0: link state changed to UP Oct 24 12:45:24 vcela kernel: acd0: FAILURE - ATA_IDENTIFY status=51READY,DSC,ERROR error=4ABORTED LBA=0 Oct 24 12:45:31 vcela snmpd[1333]: send: Connection refused Oct 24 12:45:43 vcela ntpd_initres[986]: host name not found: 0.freebsd.pool.ntp.org Oct 24 12:45:43 vcela ntpd_initres[986]: couldn't resolve `0.freebsd.pool.ntp.org', giving up on it Oct 24 12:45:43 vcela ntpd_initres[986]: host name not found: 1.freebsd.pool.ntp.org Oct 24 12:45:43 vcela ntpd_initres[986]: couldn't resolve `1.freebsd.pool.ntp.org', giving up on it Oct 24 12:45:43 vcela ntpd_initres[986]: host name not found: 2.freebsd.pool.ntp.org Oct 24 12:45:43 vcela ntpd_initres[986]: couldn't resolve `2.freebsd.pool.ntp.org', giving up on it Is there any know changes in network drivers (nfe or bge) or in order of rc scripts? It seems that nfe interface is bringed up too late. I know there is rc.d/netwait in 8-STABLE, but it is not available on 8.2-RELEASE and I think that there is some regression as this error was not there in the time of FreeBSD 7.x. The problem is that the networking layer is not TRULY available by the time ntpd starts. This does have to do with NIC drivers, but the same behaviour can be seen on all NICs, including excellent ones like em(4). You can use the rc.conf netwait_* variables to solve this problem. I'm the author of the script that got committed so that's how I know. :-) An example: netwait_enable=yes netwait_ip=4.2.2.1 4.2.2.2 netwait_if=em0 If you need help setting this up, let me know. -- | Jeremy Chadwickjdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, US | | Making life hard for others since 1977. PGP 4BD6C0CB | ___ 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: ntpd couldn't resolve host name on system boot
- Original Message - From: Jeremy Chadwick free...@jdc.parodius.com The problem is that the networking layer is not TRULY available by the time ntpd starts. This does have to do with NIC drivers, but the same behaviour can be seen on all NICs, including excellent ones like em(4). This is generally caused by links to high end switches e.g. cisco which havent had their server ports configured with portfast or similar settings. This creates quite a delay once link establishes before traffic is passed and hence the issue. netwait is an excellent script which fixes this and other network dependency issues, something we use as standard on all our machines now :) Regards Steve This e.mail is private and confidential between Multiplay (UK) Ltd. and the person or entity to whom it is addressed. In the event of misdirection, the recipient is prohibited from using, copying, printing or otherwise disseminating it or any information contained in it. In the event of misdirection, illegible or incomplete transmission please telephone +44 845 868 1337 or return the E.mail to postmas...@multiplay.co.uk. ___ 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: SOLVED: 8.1 xl + dual-speed Netgear hub = yoyo
Adrian Chadd adr...@freebsd.org wrote: Out of pure interest, I'd love to see whether xl on an earlier kernel (say 4.x, if the hardware can even run it) or even 6.x would work. I'll put that on the list for the next time I need to reboot it. I'm sure I have a 6.1 CD somewhere, and probably a 4.x CD also. (The box is old enough -- a Dell Precision 420 -- that it quite likely will run 4.x.) I've also got another old Dell with an xl on the mainboard -- an OptiPlex GX1 running 6.1 -- which will need to get moved to a 100Mb port one of these days. That will provide another data point. ___ 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: ntpd couldn't resolve host name on system boot
On Tue, Oct 25, 2011 at 12:36:56AM +0100, Steven Hartland wrote: - Original Message - From: Jeremy Chadwick free...@jdc.parodius.com The problem is that the networking layer is not TRULY available by the time ntpd starts. This does have to do with NIC drivers, but the same behaviour can be seen on all NICs, including excellent ones like em(4). This is generally caused by links to high end switches e.g. cisco which havent had their server ports configured with portfast or similar settings. This creates quite a delay once link establishes before traffic is passed and hence the issue. Correct. Folks using STP, RSTP, or LLDP are most likely to see this. However, in our environment we have all of these turned off on our ProCurve switches yet we still see a ~1 second period of time between when the kernel says em0 is up vs. when actual packets flow. My point is that even in bare-bones environments (consumer switches, etc.) it's likely that there will be a small period of time where layer 3 packets aren't actually working yet, despite layer 1 and (a portion of) layer 2 being done. netwait is an excellent script which fixes this and other network dependency issues, something we use as standard on all our machines now :) It's a hackish workaround for something that should be solved elsewhere, but solving it elsewhere has already been discussed at length in the past so I won't get into it here. (Simple version: we really need something like svcs for Solaris, or one of those service-wrapper daemons that Linux and other OSes use. But let's not discuss that here please) netwait's design model is very specific given people's needs; the original design worked fine on some machines (all of ours) but I started getting reports of problems from people using vlan(4) and bge(4), etc... so the way it works now is actually reliable for all current NICs and weirder environments. The one shortcoming of netwait is that it doesn't support waiting for multiple NICs. Some people have dual-homed environments where they really would like to wait for both, say, em0 and em1, to come up and be functional before any more scripts are started. I left that as a project for someone else, but it's something that should be added given its importance. -- | Jeremy Chadwickjdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, US | | Making life hard for others since 1977. PGP 4BD6C0CB | ___ 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
