Re: Management interface for cards powered by the "mfi" driver?
On Jun 18, 2008, at 12:15 AM, Karl Denninger wrote: No management tool = el-sucko, because you can't rebuild a failed disk or even shut the alarm on the board off! This is precisely the reason I have dropped using Adaptec controllers. The most recent ones cannot be managed with the FreeBSD tools. What I've ended up using is LSI Fibre Channel 4Gb cards (PCI-e for newer servers, but I have two with PCI-x) attached to an external RAID box. My external RAIDs are custom built by Partners Data Systems and use an Areca controller. All configuration and monitoring is done via web interface over ethernet so no proprietary software is needed. They fully support FreeBSD too. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: challenge: end of life for 6.2 is premature with buggy 6.3
On Jun 4, 2008, at 9:03 PM, Adrian Chadd wrote: If this is so important to you - contribute to the project and/or hire a FreeBSD developer. I've got a strange problem with jails and I've been trying to hire a freebsd developer, but I can't seem to get anyone to a) call me back. I got one response on "try doing xxx" which involved kernel hacking and such, which is beyond what I am in a position to do. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: challenge: end of life for 6.2 is premature with buggy 6.3
On Jun 4, 2008, at 8:22 PM, Jo Rhett wrote: If you're asking why I don't turn a production environment over to being a freebsd-unstable-testbed, I can't really answer that question in a way you'd understand (if you were asking that question) If you don't have an identical setup to test new software, then you're pretty much not able to ever upgrade anything, IMO, and your "production" environment *is* a testbed for new software. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: challenge: end of life for 6.2 is premature with buggy 6.3
On Jun 4, 2008, at 4:43 PM, Clifton Royston wrote: Speaking just for myself, I'd love to get a general response from people who have run servers on both as to whether 6.3 is on average more stable than 6.2. I really haven't gotten any clear impression as I'll throw in my "+1" for running 6.3. I have it on many boxes, some of which run gmirror and some of which have bge devices (some with both). Never any problems. They operate things varying from Postgres servers to DNS servers to mail servers (postfix) under pretty consistent load pushing lots and lots of data both network and to disk. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
jail process limits
While we're on the topic of jail resource limits, I think I'll ask my question again... I asked last month but got no response... I've got a jail server (FreeBSD 6.3/amd64) which runs a bunch of web site development environments. There is an apache or lighttpd running in each jail as user httpd (same UID on base system and each jail). On the jail host, I counted 231 processes owned by httpd. If I try to start an application server (or any process) as user httpd in one of the jails, it exits immediately with "Cannot fork: Resource temporarily unavailable". Even if I "su httpd" I get the same error on any command I try to run such as "ls". If I run the same on the jail host, it has no problems. The jail itself only has 34 processes running. On the jail host, the following is logged: Apr 22 16:34:38 staging kernel: maxproc limit exceeded by uid 80, please see tuning(7) and login.conf(5). tuning(7) and login.conf(5) have pretty much nothing to say about "maxproc". The sysctl settings are all default on this box. kern.maxproc: 6164 kern.maxprocperuid: 5547 The user httpd is of login class "daemon". My login.conf is unchanged from the distributed version, which states "unlimited" for max processes. Why am I getting the resource unavailable when I barely have 230 processes, not even close to the limits. Apache seems unaffected since the parent is run as root, so it can fork children willy-nilly and not be blocked by any limits. Can anyone tell me where to look to find out what is limiting user httpd from creating new processes inside the jail, and what exactly that limit is? More importantly, how to increase it. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Is it possible to create a directory under /dev?
On May 21, 2008, at 11:18 PM, Carlos A. M. dos Santos wrote: Assuming you're using a modern FreeBSD (version number would be useful), /dev does not live on a file system. It exists as its own file system, controlled by devfs. Check the man page for devfs for details. I'm using 7.0-STABLE. I've read devfs(8), devfs(5) and did not find an answer there. perhaps if you state your goal rather than the difficulty you encounter using the mechanism you chose to reach that goal, we could help you better. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Is it possible to create a directory under /dev?
On May 21, 2008, at 8:44 AM, Carlos A. M. dos Santos wrote: I attempted this: # mkdir /dev/foo mkdir: /dev/foo: Operation not supported Any suggestions (besides creating it elsewhere, of course)? Assuming you're using a modern FreeBSD (version number would be useful), /dev does not live on a file system. It exists as its own file system, controlled by devfs. Check the man page for devfs for details. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Instant reboot with FreeBSD 6.3 and > 2GB RAM
On May 21, 2008, at 4:01 AM, [EMAIL PROTECTED] wrote: some users of FreeNAS which is based on FreeBSD 6.3 reported instant reboots on systems with > 2GB RAM (most of them use 4GB). The reboot occurs right after displaying the FreeBSD loader menu. Most of them told me that they can boot if they reduce RAM to <= 2GB. For what it's worth, I have run several systems with 4GB RAM on FreeBSD/i386 6.3. The only i386 I have left with this much RAM was recently upgraded to 7.0; the rest of my large RAM systems run FreeBSD/ amd64. I didn't see anything obviously bad in your kernel config. By the way, thanks for making FreeNAS... I use it on my home NFS/AFP server to great success... the only thing I wish it included was the amrstat binary to test my LSI RAID controller status (I just copy it from another 6.3 system I have and it works). ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: how much memory does increasing max rules for IPFW take up?
On May 18, 2008, at 3:26 AM, Ian Smith wrote: Hashed per flow, (srcip^destip^srcport^dstport) mod curr_dyn_buckets, so packets for both directions of a given flow hash to the same bucket. In the case you mention, you could likely expect reasonable distribution by src_ip/src_port. Thanks for the detailed info. This really helps. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: how much memory does increasing max rules for IPFW take up?
How are the buckets used? Are they hashed per rule number or some other mechanism? Nearly all of my states are from the same rule (eg, on a mail server for the SMTP port rule). How should I scale the buckets with the max rules? The default seems to be 4096 rules and 256 buckets. Should I maintain that ratio? ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: how much memory does increasing max rules for IPFW take up?
On May 15, 2008, at 6:03 AM, Bruce M. Simpson wrote: Having said that the default tunable of 256 state entries is probably quite low for use cases other than "home/small office NAT gateway". The deafult on my systems seems to be 4096. My steady state on a pretty popular web server is about 400, on a busy inbound mail server, around 800 states. I need to account for peaks much higher, though. Luckily most of my connections are short-lived. Thanks for the answers! ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
how much memory does increasing max rules for IPFW take up?
I had a box run out of dynamic state space yesterday. I found I can increase the number of dynamic rules by increasing the sysctl parameter net.inet.ip.fw.dyn_max. I can't find, however, how this affects memory usage on the system. Is it dyanamically allocated and de-allocated, or is it a static memory buffer? Thanks! ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
maxproc reached inside jail, can't tell why
I've got a jail server (FreeBSD 6.3/amd64) which runs a bunch of web site development environments. There is an apache or lighttpd running in each jail as user httpd (same UID on base system and each jail). On the jail host, I counted 231 processes owned by httpd. If I try to start an application server (or any process) as user httpd in one of the jails, it exits immediately with "Cannot fork: Resource temporarily unavailable". Even if I "su httpd" I get the same error on any command I try to run such as "ls". If I run the same on the jail host, it has no problems. The jail itself only has 34 processes running. On the jail host, the following is logged: Apr 22 16:34:38 staging kernel: maxproc limit exceeded by uid 80, please see tuning(7) and login.conf(5). tuning(7) and login.conf(5) have pretty much nothing to say about "maxproc". The sysctl settings are all default on this box. kern.maxproc: 6164 kern.maxprocperuid: 5547 The user httpd is of login class "daemon". My login.conf is unchanged from the distributed version, which states "unlimited" for max processes. Why am I getting the resource unavailable when I barely have 230 processes, not even close to the limits. Apache seems unaffected since the parent is run as root, so it can fork children willy-nilly and not be blocked by any limits. Can anyone tell me where to look to find out what is limiting user httpd from creating new processes inside the jail, and what exactly that limit is? More importantly, how to increase it. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: File descriptor passing broken in FreeBSD 7?
On Apr 16, 2008, at 10:14 AM, Heiko Wundram wrote: http://www.gnome.org/~markmc/code/test-descriptor-passing.c Again it works in FreeBSD 6, but not in FreeBSD 7 (albeit with ECONNREFUSED not EBADF). Any ideas? Works fine on 7.0-STABLE from end of last week (i.e., doesn't core- dump, and outputs the contents of test-descriptor-passing.c, to which I adapted the filename). I did same on FreeBSD 7.0-RELEASE i386 as normal user. I got the same result of the contents of the file being printed to the screen. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: aaccli on recent conrollers?
On Apr 8, 2008, at 10:31 AM, Ed Maste wrote: On Fri, Nov 10, 2006 at 11:42:40AM -0500, Vivek Khera wrote: I have just built a new SunFire X4100 server with an Adaptec 2230SLP RAID card using FreeBSD 6.2-PRE kernel (from September 20). Everything is working extremely well except I cannot run the aaccli utility on this controller. Have a look at arcconf (sysutils/arcconf) -- it's Adaptec's newer tool and should support both older and newer firmware; aaccli stopped working as of a certain version and I think Adaptec has no plans to work on it any longer. If you really want to use aaccli, you can downgrade the firmware on the new card -- of course, you'll have to use arcconf to do that step. Wow... what a blast from the past. I've since decided that the Adaptec + Dell array solution was completely sub-standard performance and stability and management wise. It has been replaced with an external RAID array from Partners Data systems and connected to the same Sun box via an LSI fibre channel card. It is faster and much easier to manage. I will not be buying Adaptec parts any more since they obviously don't give a hoot about freebsd, where as LSI goes out of their way to provide engineers to help out with freebsd issues. It is important for us as a community to show support where support is due. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Upgrading to 7.0 - stupid requirements
On Mar 19, 2008, at 8:46 AM, Michael Grant wrote: My server is live and serving customers. I can't afford to take the box down for a whole day while I upgrade ports. Is there any intelligent way to do this? Here's what you do: 1) take one server at a time down from the load balancer/worker pool 2) upgrade it 3) put it back in service 4) go to step 1 until all servers are updated. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: hifn(4) causing system lockup
On Mar 17, 2008, at 4:05 PM, Sascha Klauder wrote: I've recently upgraded my 6.2-STABLE workstation to RELENG_7, and I'm now experiencing system lockups that seem to be caused by the hifn(4) driver. I've got a Soekris vpn1401 card to help with GELI disk en- cryption. Reading from a GELI volume is causing the system to freeze completely, which does not happen if software crypto is used (i.e. hifn.ko not loaded). I can't enter kernel debugger (ctrl+alt+esc doesn't work anymore) and my (remote) kgdb-fu isn't up to par anyway. I've had the exact same kind of issue with the vpn1401 PCI card in a Dell box for my firewall running pfSense (at the tie it was based on FreeBSD 6.1 I believe). It would lock up the firewall within 2 hours to 4 days of uptime. Once we removed the card, no lockups. Soekris never responded to my questions about such behavior. In contrast, their mini-PCI cards I have installed on some WRAP boards never lockup using the same software. I blame the card. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: RELEASE discs & ISO images (for future)
On Mar 7, 2008, at 4:05 AM, Vadim Goncharov wrote: But now release announcement says that for LiveFS I need TWO disks - both disc1 and livefs disk. WHY? Why not to pack they both to a single disc1, this was very comfortable. I discovered that the livefs disk is bootable and can do a full install of freebsd as well. there just are no packages on it, which suits me just fine. this is the disk i will keep handy for new installs + emergency repairs. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: BTX on USB pen drive
On Mar 6, 2008, at 11:42 AM, Vincent Mialon wrote: I want to use nanobsd to generate optimized FreeBSD-7.0-release images on USB pen drive. I generated images with nanobsd. It works on a standard pc with an old Celeron 2.4Ghz but on a brand new supermicro X7SBi with a Core 2 Quad it doesn't boot. Take a look at pfSense, a freebsd-based firewall/router with a nice GUI. I believe it can boot from USB stick. It will run as a live CD as well, which seems more secure than USB since you can't corrupt it. It is open source and free of cost. See http://www.pfsense.com/ If you *really* want to roll your own with nanobsd, see if you can make it use grub as the boot loader instead. I hear it has an easier time with some hardware. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: mpt driver: check raid status
On Mar 3, 2008, at 10:49 AM, Cristiano Deana wrote: I'm using a 7-RELEASE on a Dell PowerEdge 1955, using a mpt driver to manage a hardware raid1. Is there any way to check the status of the raid? I've been wondering this as well. My Sun X4100's have LSI SAS mirror controllers in them and I have no way to know their status short of rebooting them (well, i guess i could probe the ILOM but that's not easy to automate) I really suspect the answer is "no" given that the mpt interface is very generic on the OS side. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: FreeBSD 7.0 Questions
On Feb 28, 2008, at 9:39 AM, Chris wrote: Ahh thats useful, on the occasions I have remotely installed freebsd over linux I have always failed due to incorrectly guessing the hd id and as such a wrong fstab, if I know it will always be ad0 and ad1 and so on it makes this much easier. I much prefer to use glabel for this purpose, when the hardware might change. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Dual Core Xeon / i386 install w/ more than 4gb of RAM
On Feb 20, 2008, at 1:56 AM, Tom Samplonius wrote: And is there some really stability fear about FreeBSD on x86-64? Seems just the same as i386. Some poorly written software fails to run properly in 64-bit environment. I have one such package, and my solution was to compile it on a 32-bit box, and copy the binaries over. Works just fine with 32-bit compat enabled on the amd64 kernel. Other than that, the FreeBSD/amd64 has been 100% rock solid for me since 6.0 when I started getting 64-bit boxes. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Latest Stable FreeBSD release and is it supported on dell 2950
On Jan 23, 2008, at 12:30 AM, navneet Upadhyay wrote: Hi , I have following questions. 1. Which is the latest release of FreeBSD. 2. When was it released? 3. What is the patch level? 4.What is the stability See http://www.freebsd.org/ for above. Short answer: 6.3 released last week. 5. Which compiler to use: cc or gcc and which version . cc == gcc on freebsd. Unless your app requires a specific gcc version, just use the one the system installs for you. 6. Which platform/machine which BSD supports. Is Dell 2950 ok I've only ever had one compatibility issue with a Dell, and that was easily fixed by teaching the bge ethernet driver the name of the chipset used on that particular box. I have a PE1900 here we just got and it runs 7.0-RC1 quite nicely. In general, unless you're running some obscure devices, FreeBSD works just fine with most systems. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: NO_ knobs in /etc/make.conf
On Jan 23, 2008, at 9:24 AM, John Baldwin wrote: What was broken that required this to be "fixed"? Inconsistent use of what NO_FOO= meant. Some places only checked if it was set, other places required it to be set to "yes", so NO_FOO=no might disable FOO or it might not. The WITHOUT_* / WITH_* scheme was I guess I wasn't clear about my confusion. What was broken about putting all this in make.conf that necessitated a src.conf file too? Having the names consistent is great, though. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: NO_ knobs in /etc/make.conf
On Jan 21, 2008, at 3:34 PM, Doug Barton wrote: There is a cross-reference to src.conf(5) at the end of make.conf(5), but IMO the connection needs to be made more explicit. Anyone want to take that on? This should also go in the release notes if it's not already. So do I need to move my settings from make.conf to src.conf, or can I just leave it as-is and not worry about it. Reading the make.conf man page implies it will just continue to work without change. What was broken that required this to be "fixed"? ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: What current Dell Systems are supported/work
On Jan 15, 2008, at 1:40 PM, John Baldwin wrote: Where can one go to read up on what MSI is and how it helps us? Is enabling it just setting a sysctl? Does that have to be done in loader.conf or can it happen later? loader.conf (though it is now default on in RELENG_6). hw.pci.msi_enable=1 hw.pci.msix_enable=1 Thanks for the info. But can anyone point me to some documentation on why MSI is good for me? ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: What current Dell Systems are supported/work
On Jan 10, 2008, at 11:09 AM, John Baldwin wrote: *: This is the default behavior for 7.0, I have not encountered the problem mentioned above on any 1950/2950 boxes so far I have tested. I will enable MSI by default on 6.x now (so will take affect for 6.4). We've also enabled it by default on 6.x at work. Where can one go to read up on what MSI is and how it helps us? Is enabling it just setting a sysctl? Does that have to be done in loader.conf or can it happen later? ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: aac tool regressions on 7.0-RC1
On Jan 3, 2008, at 2:07 PM, Mike Andrews wrote: arcconf seems to be reliable (and a native amd64 binary), except for the aforementioned hanging-on-exit issue with -RC1. On -BETA4 it's fine. Google for "check_icp" if you need a Nagios plugin written around arcconf (it needs only minor edits to work on /bin/sh instead of bash). It's looking like aaccli is a lost cause though, yes. Thanks. The performance was also not cutting it for me, so with the combination of those to problems I decided to retire them from service. I now use fibre channel cards (LSI) and external RAID units from Partners Data Systems, which have been very good to me the last 6 months. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Nagios + 6.3-RELEASE == Hung Process
On Jan 2, 2008, at 8:26 PM, Marc G. Fournier wrote: My gut feeling is that it's not an architecture issue but more an interoperability issue between the Nagios threading code and the libpthread() threading library. As noted in my original report, this isn't a nagios issue per se ... my first experience with this issue was with Azureus/java ... so its a 'threading issue in general' ... For years now I've been running with libthr as the default threading library as set in libmap.conf. The *only* issue I've run into is with Java, and that requires libpthread. So my libmap.conf looks like this, and everything works really well (including Nagios, mysql, etc.) --cut here-- # use libthr instead of pthread lib libpthread.so.2 libthr.so.2 libpthread.so libthr.so # JDK HotSpot compiler fails randomly with libthr. [java] libpthread.so libpthread.so libpthread.so.2 libpthread.so.2 --cut here-- ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: aac tool regressions on 7.0-RC1
On Jan 2, 2008, at 1:06 PM, Mike Andrews wrote: In my experience, this was caused by the firmware rev of the adaptec card. Basically, the combination of FreeBSD, amd64, and Adaptec RAID cards is a bad thing for production systems, and IMO should be avoided. Well, yeah, the error message would seem to point that way, but this is the newest available firmware (v8208) for this particular card. For me, it was the latest firmware on the 2230SLP cards that "broke" the aaccli program. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: aac tool regressions on 7.0-RC1
On Jan 2, 2008, at 12:45 PM, Ed Maste wrote: I'm not aware of any reason to avoid Adaptec RAID cards specifically on amd64 now; there were a number of problems in the past but they should be addressed now. My main concern is that there is no *reliable* way to monitor the status of an Adaptec RAID system on FreeBSD/amd64. Like I said before, if anyone wants 3 2230SLP RAID cards cheap, give me a holler. :-) I've retired them (one of them is still new in box). ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: building system's libmilter with poll() support?
On Jan 2, 2008, at 11:08 AM, Gregory Shapiro wrote: SENDMAIL_CFLAGS+=-D_FFR_WORKERS_POOL Do I want this one or just -DSM_CONF_POLL ? I'm running into issues with postfix failing to connect to the milter because it is too busy (specifically the dkim milter) and one theory was to use poll to increase the number of connections that the milter can handle. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: building system's libmilter with poll() support?
On Jan 2, 2008, at 11:08 AM, Gregory Shapiro wrote: What's the procedure to configure buildworld to get sendmail to build libmilter using poll() instead of select()? Add this to /etc/make.conf: SENDMAIL_CFLAGS+=-D_FFR_WORKERS_POOL [ ... ] Note that bug 118824 has already asked for this to be part of the base. I will likely make that the case for the HEAD and then give it some testing time before MFC'ing. Sweet! Thanks a lot for your help. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
building system's libmilter with poll() support?
What's the procedure to configure buildworld to get sendmail to build libmilter using poll() instead of select()? There is discussion on the postfix mailing list that some high-load performance issues could be solved by switching this, but the "fix" was to hack the libmilter header file to force the appropriate define to be set, rather than using the sendmail configuration system. This would of course be difficult to preserve across updates and buildworlds... Thanks! ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: aac tool regressions on 7.0-RC1
On Jan 2, 2008, at 3:54 AM, Mike Andrews wrote: Command Error: the current AFAAPI.DLL.> In my experience, this was caused by the firmware rev of the adaptec card. Basically, the combination of FreeBSD, amd64, and Adaptec RAID cards is a bad thing for production systems, and IMO should be avoided. Anyone looking to buy two or three "slightly used" Adaptec 2230SLP RAID cards? :-) ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Trying to initialize padlock support on Via C7 Eden CPU
On Dec 22, 2007, at 1:38 PM, Michael Proto wrote: I purchased a Jetway J7F4K1G2E w/VIA Eden 1.2GHz cpu/motherboard combo (http://e-itx.com/jetway-j7f4k1g2e-mini-itx-motherboard.html) that I'm trying to get working with the FreeBSD padlock driver. Based on what I see from the manufacturer's CPU support list , http://www.jetwaycomputer.com/VIA3.html, I have a C7 Esther processer. It looks like the CPUID for this processor isn't recognized by FreeBSD 6.3-RC1 or 7.0-BETA3. GENERIC on 7.0-BETA3 detects the CPU as follows: FWIW, I have the exact same motherboard from E-ITX as well. I run FreeNAS on mine. FreeNAS is running the FreeBSD 6.2-REL-p8 kernel and detects the CPU just fine: CPU: VIA C7 Esther+RNG+AES+AES-CTR+SHA1+SHA256+RSA (1200.01-MHz 686- class CPU) Origin = "CentaurHauls" Id = 0x6a9 Stepping = 9 Features = 0xa7c9baff < FPU ,VME ,DE ,PSE ,TSC ,MSR ,PAE ,MCE,APIC,SEP,MTRR,PGE,CMOV,PAT,CLFLUSH,ACPI,MMX,FXSR,SSE,SSE2,TM,PBE> Features2=0x181 [[ snip ]] PadLock: HW support loaded for AES-CBC,SHA1,SHA256. It seems you have a newer ID and different Stepping than mine. I have no way to boot 6.3 on this box until FreeNAS is using 6.3. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: reboot after panic: vm_page_unwire: invalid wire count: 0
On Nov 14, 2007, at 10:13 AM, Vivek Khera wrote: I'm running 6.2-REL. The old kernel was -p5, now without the zero copy sockets, i'm running -p8. I'll know in a couple of days if this is our solution. For the archives: Removing zero copy sockets seems to have fixed the issue. Not a single panic on that box since, and it used to panic within 3-4 days under the load it has. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: FreeBSD on Dell T105? ($350 dual-core Opteron)
On Dec 7, 2007, at 10:11 AM, Chris Shenton wrote: Dell's got a decent deal on their PowerEdge T105 box with an 1.8GHz AMD dual-core Opteron, 512MB RAM, 80GB disk, and Gigabit ether: $350. Dell's got a great return policy. If it doesn't work, report here and send it back. If it does work, report here and keep it! :-) ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: IPSEC + Via Padlock + racoon + Windows
On Dec 3, 2007, at 9:39 AM, Michael Proto wrote: Not that this solves your problem, but doesn't the padlock crypto engine only provide acceleration for AES symmetric encryption? From the man page: The boot messages on my C7 based system shows this: PadLock: HW support loaded for AES-CBC,SHA1,SHA256. the CPU is identified like this, so I'm not sure what exactly is supported: CPU: VIA C7 Esther+RNG+AES+AES-CTR+SHA1+SHA256+RSA ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Software for distribution of configuration files and changes
On Nov 21, 2007, at 12:45 AM, Quan Qiu wrote: "ChallengeResponseAuthentication no" is also required to avoid sshd accepting keyboard-interactive/pam. I don't think this setting matters for PermitRootLogin without- password. At least the default on FreeBSD 6 works as expected when setting the root login limit. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: reboot after panic: vm_page_unwire: invalid wire count: 0
On Nov 13, 2007, at 7:49 PM, Kris Kennaway wrote: notification. In the meantime, your best bet is to disable ZERO_COPY_SOCKETS. There is a chance this was a recent regression, previously in 7.0 they were believed to work. I'm running 6.2-REL. The old kernel was -p5, now without the zero copy sockets, i'm running -p8. I'll know in a couple of days if this is our solution. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: reboot after panic: vm_page_unwire: invalid wire count: 0
On Nov 13, 2007, at 5:13 PM, Kip Macy wrote: In the meantime, your best bet is to disable ZERO_COPY_SOCKETS. Thanks for the info. I'm putting the new kernel in place and will see what happens and report back. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: reboot after panic: vm_page_unwire: invalid wire count: 0
On Nov 13, 2007, at 4:50 PM, Vlad GALU wrote: vmio = 1 offset = Unhandled dwarf expression opcode 0x93 (kgdb) Do you happen to have ZERO_COPY_SOCKETS in your kernel config? Yes, I do. Are they known to be bad under certain loads or just in general. I don't have this issue with any other web server running the same kernel config but those are amd64 boxes mostly. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
reboot after panic: vm_page_unwire: invalid wire count: 0
I've got a Dell 1750 box that was rock-solid stable running 4.11 for a couple of years now operating a pretty busy website backend. A month or so ago we wiped it clean and repurposed it to run a different website running Drupal with a Varnish front-end cache using FreeBSD 6.2-RELEASE-p5. The system is i386 and has 1Gb of RAM. Uname output: FreeBSD mb.kcilink.com 6.2-RELEASE-p5 FreeBSD 6.2- RELEASE-p5 #0: Wed Jun 27 10:47:15 EDT 2007 [EMAIL PROTECTED]:/n/lorax1/usr6/obj.i386/n/lorax1/usr6/src/sys/ KCI32SMP i386 The last week or so, it has been crashing regularly. Sometimes twice per day, and sometimes it runs for two days without a problem. I finally managed to make it dump a crashlog and core, and discovered that the panic was: reboot after panic: vm_page_unwire: invalid wire count: 0 I google around and found one old PR #33637 which had a patch but that was for FreeBSD 4.5. I have also found two other mentions of this panic, one on the mailing lists with no responses, and another for a PR from 6.1-PRERELEASE, PR #94578, which has no comments on it. According to the http and varnish logs, we're not being particularly hit very hard when the panic happens, but I don't know if we lose some log data during the panic. I have the core and the kernel.debug. I'm not sure what info to extract from it beyond the backtrace. The watchdog timer fired and dropped me to DDB, so I just typed "watchdog" and "c" and let it finish dumping. Here's the backtrace, and "bt full" output. # kgdb kernel.debug /var/crash/vmcore.0 [GDB will not be able to debug user-mode threads: /usr/lib/ libthread_db.so: Undefined symbol "ps_pglobal_lookup"] GNU gdb 6.1.1 [FreeBSD] Copyright 2004 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type "show copying" to see the conditions. There is absolutely no warranty for GDB. Type "show warranty" for details. This GDB was configured as "i386-marcel-freebsd". Unread portion of the kernel message buffer: panic: vm_page_unwire: invalid wire count: 0 cpuid = 1 KDB: stack backtrace: kdb_backtrace(100,c5a76000,c0e88ab0,0,d90d82c8,...) at kdb_backtrace +0x29 panic(c06b011f,0,c0e88ab0,efe80900,c057b96a,...) at panic+0x114 vm_page_unwire(c0e88ab0,0) at vm_page_unwire+0x68 vfs_vmio_release(d90d82c8) at vfs_vmio_release+0xa2 getnewbuf(0,0,4000,4000) at getnewbuf+0x2bc getblk(c6f81550,4f5,0,4000,0,...) at getblk+0x360 ffs_balloc_ufs2(c6f81550,13d4000,0,fa,c4f32780,...) at ffs_balloc_ufs2+0x1606 ffs_write(efe80bec) at ffs_write+0x2ec VOP_WRITE_APV(c06e06a0,efe80bec) at VOP_WRITE_APV+0xce vn_write(c59c8000,efe80cbc,c51cf400,0,c5a76000) at vn_write+0x1ee dofilewrite(c5a76000,c,c59c8000,efe80cbc,,...) at dofilewrite +0x77 kern_writev(c5a76000,c,efe80cbc,821bba3,fa,...) at kern_writev+0x3b write(c5a76000,efe80d04) at write+0x45 syscall(3b,809003b,bfbf003b,0,bfbfeaa4,...) at syscall+0x2bf Xint0x80_syscall() at Xint0x80_syscall+0x1f --- syscall (4, FreeBSD ELF32, write), eip = 0x483d732f, esp = 0xbfbfe9dc, ebp = 0xbfbfea08 --- Uptime: 1d20h51m58s Dumping 1023 MB (2 chunks) chunk 0: 1MB (159 pages) ... ok chunk 1: 1023MB (261872 pages) 1007 991 975 959 943 927 911 895 879 863 847 831 815 799 783 767 751 735 719 703 687 671 655 639 623 607 591 575 559 543 527 511 495 479 463 447 431 415 399 383 367 351 335 319 303 287 271 255 239 223 207 191 175 159 143 127 111 95interrupt total irq4: sio0 21758 irq15: ata11 irq16: bge0 4544565 irq17: bge1 17684238 irq18: amr0 588223 cpu0: timer323148326 cpu2: timer323148294 cpu1: timer323148331 cpu3: timer323148344 Total 1315432158 KDB: stack backtrace: kdb_backtrace(c069ec5d,4e67e6de,0,c06ea170,c06e9818,...) at kdb_backtrace+0x29 watchdog_fire(c07120e0,c8,efe80634,c065c821,efe8063c,...) at watchdog_fire+0x9d hardclock(efe8063c) at hardclock+0x115 lapic_handle_timer(0) at lapic_handle_timer+0x51 Xtimerint(c4fe6000,1,efe806a8,c066d57b,c4fe6000,...) at Xtimerint+0x30 getit(c4fe6000,c4fe6000,4,efe806c0,c0496f97,...) at getit+0x88 DELAY(1) at DELAY+0x3b amr_quartz_poll_command1(c4fe6000,c51fbff0,0,0,1000,...) at amr_quartz_poll_command1+0x1af amr_setup_polled_dmamap(c51fbff0,c4fef800,1,0) at amr_setup_polled_dmamap+0x94 bus_dmamap_load(c4ffe380,0,c0c22000,1,c0496cd4,c51fbff0,1) at bus_dmamap_load+0x4b5 amr_quartz_poll_command(c51fbff0) at amr_quartz_poll_command+0x51 amr_dump_blocks(c4fe6000,0,4cb25e,c0c22000,80) at amr_dump_blocks+0x5f amrd_dump(c515b700,c0c22000,0,9964bc00,0,1) at amrd_dump+0x7c cb_dumpdata(c0711a48,1,c06f44a0) at cb_dumpdata+0x100 foreach_chunk(c0655a78,c06f44a0,c06f44a0) at foreach_c
Re: Bringing up new Intel non-legacy system
On Nov 7, 2007, at 7:17 PM, Jack Vogel wrote: And, is the ACPI subsystem likely to be the source of the problem? I've had several systems in which I've needed to disable the ACPI timer component and then the system worked fine. in /boot/loader.conf: debug.acpi.disabled="timer" When installing, break to boot loader and type: set debug.acpi.disabled="timer" You can try the various acpi components to isolate which one is the culprit and leave the rest working. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: date/time trouble - PST came too early
On Nov 7, 2007, at 6:16 PM, Kevin Oberman wrote: In any case, since it was not in effect last year, it would be very unlikely that most FreeBSD users would have noticed it then. s/last year/last spring/g :-( ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: FreeBSD based bandwidth manager, traffic shaper
On Nov 7, 2007, at 9:51 AM, Balgansuren Batsukh wrote: I am looking high performance bandwidth manager, traffic shaper for IP core network to configure leased line, xDSL, Ethernet, GPON/EPON, wireless subscribers. You might be able to do it with pfSense (www.pfsense.com) ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: date/time trouble - PST came too early
On Nov 5, 2007, at 8:58 PM, Chris H. wrote: Ahh... I'm guessing that you missed the following post in this thread titled "date/time trouble - PST came too early [fixed]" posted 11-02. LI Xin offered the following solution, which solved my dilemma: No, I saw that... but like I said, most of us did this last year when the new DST rules went into effect. Did you not notice it last year? ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: date/time trouble - PST came too early
On Nov 2, 2007, at 3:30 AM, Chris H. wrote: FWIW The system already knows what timezone it lives in. It simply chose to change to PST according to the /normal/ standards. What happened here in the USA, is that president Bush decided that we'd be better served here if we waited an additional week to set our clocks back one hour. So. It seems this particular server decided to ignore our president (not that I blame it) Most of us went through this *last* year when the rules took effect. Did it not affect your system last year? Basically you need to get a corrected /etc/localtime and restart any long running programs that depend on time, notably cron. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Progress with usability of AMD64
On Sep 27, 2007, at 8:22 PM, Greg Black wrote: Since we're close to a new release, I'm wondering what experience people have had recently with running in 64-bit mode. Are most of those broken ports now fixed? Or is there some magic that allows building of just the broken ones in 32-bit mode such that they'll run on a 64-bit box? In practice, I have exactly one port I need in 64-bit that is not functional, and that is because it is a binary-only distribution of the Adaptec command line utility. No other software I've tried has failed to build or run on 6.2/amd64. My list of software is purely server stuff; I don't use any FreeBSD desktops. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: large RAID volume partition strategy
On Aug 29, 2007, at 2:43 PM, Kirill Ponomarew wrote: What type I/O did you test, random read/writes, sequential writes ? The performance of RAID group always depends on what software you run on your RAID group. If it's database, be prepared for many random read/writes, hence dd(1) tests would be useless. I ran my database on it with a sample workload based on our live workload. Anything else would be a waste of time. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: large RAID volume partition strategy
On Aug 17, 2007, at 10:44 PM, Ivan Voras wrote: fdisk and bsdlabels both have a limit: because of the way they store the data about the disk space they span, they can't store values that reference space > 2 TB. In particular, every partition must start at an offset <= 2 TB, and cannot be larger than 2 TB. Oh... one more note: if I don't use fdisk or paritions, I *can* newfs the raw drive much bigger than 2Tb. I just don't want to do that for a production box. :-) ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: large RAID volume partition strategy
On Aug 17, 2007, at 10:44 PM, Ivan Voras wrote: fdisk and bsdlabels both have a limit: because of the way they store the data about the disk space they span, they can't store values that reference space > 2 TB. In particular, every partition must start at an offset <= 2 TB, and cannot be larger than 2 TB. Thanks. This is good advice (along with your other note about doing it in the RAID volume manager). Nearly everyone else decided to jump on the raid level instead and spew forth the "RAID10 is better for database" party line. Well to you folks: once you have 1Gb cache and a lot of disks, there is not much difference between RAID10 and RAID5 or RAID6 in my testing. I ended up making 6 RAID volumes across all the disks to maximize spindle counts and strip the data at 16kB. This seems to work well, and I can assign the other partition as I need later on. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: large RAID volume partition strategy
On Aug 18, 2007, at 4:09 AM, Thomas Hurst wrote: Best temper your fear with some thorough testing then. If you are going to use ZFS in such a situation, though, I might be strongly tempted to use Solaris instead. Why the long gaps between maintenance? This is a DB server for a 24x7 service. Maintenance involves moving the DB master server to one of the replicas, and this involves downtime, so we like to do it as infrequently as possible. Also, it is not exposed to the internet at large, and runs on a closed private network, so remote and local attacks are not a major concern. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: large RAID volume partition strategy
On Aug 17, 2007, at 7:31 PM, Ivan Voras wrote: Depending on your allowable downtime after a crash, fscking even a 1 TB UFS file system can be a long time. For large file systems there's really no alternative to using -CURRENT / 7.0, and either gjournal or ZFS. I'll investigate this option. Does anyone know the stability reliability of the mpt(4) driver on CURRENT? Is it out of GIANT lock yet? It was hard to tell from the TODO list if it is entirely free of GIANT or not. My only fear of this is that once this system is in production, that's pretty much it. Maintenance windows are about 1 year apart, usually longer. When you get there, you'll need to create 1 small RAID volume (<= 1 GB) from which to boot (and probably use it for root) and use the rest for whatever your choice is (doesn't really matter at this point). This is because you can't have fdisk or bsdlabel partitions larger than 2 TB and you can't boot from GPT. So what your saying here is that I can't do either my option 1 or 2, but have to create smaller volumes exported as individual drives? Or just that I can't do 1, because my case 2 I could make three 2Tb fdisk slices which bsdlabel can then partition? ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: large RAID volume partition strategy
On Aug 17, 2007, at 6:10 PM, Claus Guttesen wrote: If you want to avoid the long fsck-times your remaining options are a journaling filesystem or zfs, either requires an upgrade from freebsd 6.2. I have used zfs and had a serverstop due to powerutage in out area. Our zfs-samba-server came up fine with no data corruption. So I will suggest freebsd 7.0 with zfs. Interesting idea... But, if I don't go with zfs, which would be a better way to slice the space up: RAID volumes exported as individual disks to freebsd, or one RAID volume divided into multiple logical partitions with disklabel? ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: large RAID volume partition strategy
On Aug 17, 2007, at 6:26 PM, Boris Samorodov wrote: I have 6 SATA-II 300MB/s disks at 3WARE adapter. My (very!) simple tests gave about 170MB/s for dd. BTW, I tested (OK, very fast) RAID5, RAID6, gmirror+gstripe and noone get close to RAID10. (Well, as expected, I suppose). Whichever RAID level I choose, I still need to decide how to split the 6.5Tb into smaller hunks. In any case, my testing with RAID10, RAID5, and RAID6 showed marginal differences with my workload. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
large RAID volume partition strategy
I have a shiny new big RAID array. 16x500GB SATA 300+NCQ drives connected to the host via 4Gb fibre channel. This gives me 6.5Tb of raw disk. I've come up with three possibilities on organizing this disk. My needs are really for a single 1Tb file system on which I will run postgres. However, in the future I'm not sure what I'll really need. I don't plan to ever connect any other servers to this RAID unit. The three choices I've come with so far are: 1) Make one RAID volume of 6.5Tb (in a RAID6 + hot spare configuration), and make one FreeBSD file system on the whole partition. 2) Make one RAID volume of 6.5Tb (in a RAID6 + hot spare configuration), and make 6 FreeBSD partitions with one file system each. 3) Make 6 RAID volumes and expose them to FreeBSD as multiple drives, then make one partition + file system on each "disk". Each RAID volume would span across all 16 drives, and I could make the volumes of differing RAID levels, if needed, but I'd probably stick with RAID6 +spare. I'm not keen on option 1 because of the potentially long fsck times after a crash. What advantage/disadvantage would I have between 2 and 3? The only thing I can come up with is that the disk scheduling algorithm in FreeBSD might not be optimal if the drives really are not truly independent as they are really backed by the same 16 drives, so option 2 might be better. However, with option 3, if I do ever end up connecting another host to the array, I can assign some of the volumes to the other host(s). My goal is speed, speed, speed. I'm running FreeBSD 6.2/amd64 and using an LSI fibre card. Thanks for any opinions and recommendations. =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= Vivek Khera, Ph.D.Khera Communications, Inc. Internet: [EMAIL PROTECTED] Rockville, MD +1-301-869-4449 x806 ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
How do I interpret mpt "evtlog" messages
How does one interpret these messages? I'm running 6.2-RELEASE-p5 amd64. This machine has 20Gb RAM. The mpt0 device is an LSI fibre channel card attached to an external RAID system. mpt0: port 0xc800-0xc8ff mem 0xfe2fc000-0xfe2f,0xfe2e-0xfe2e irq 16 at device 0.0 on pci5 mpt0: [GIANT-LOCKED] mpt0: MPI Version=1.5.10.0 mpt0: Port 0: LinkState: Failed mpt0: External Bus Reset Detected mpt0: Port 0x0: FC LinkEvent: LIP(f7,f7) (Loop Initialization) mpt0: Device needs AL_PA mpt0: Port 0: LinkState: Active mpt0: Rescan Port: 0 These are the messages that cropped up in the syslog over the last few days: d04.m1e.net kernel log messages: +++ /tmp/security.BlS1Kaey Tue Aug 7 03:01:04 2007 +mpt0: mpt_cam_event: 0x1 +mpt0: EvtLogData: IOCLogInfo: 0x2404 +mpt0: EvtLogData: Event Data: 01ef 0001 0888 c801 023a0082 0800 +mpt0: mpt_cam_event: 0x1 +mpt0: EvtLogData: IOCLogInfo: 0x2404 +mpt0: EvtLogData: Event Data: 01ef 0001 0888 1206 01a10105 3000 +mpt0: mpt_cam_event: 0x1 +mpt0: EvtLogData: IOCLogInfo: 0x2404 +mpt0: EvtLogData: Event Data: 01ef 0001 0888 bc17 066f008f b800 +mpt0: mpt_cam_event: 0x1 +mpt0: EvtLogData: IOCLogInfo: 0x2404 +mpt0: EvtLogData: Event Data: 01ef 0001 0888 bc12 07a10084 9000 ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: ntpd just sits there and does nothing
On Jul 20, 2007, at 3:37 AM, Stefan Lambrev wrote: Other problem that I see is if you are behind NAT/firewall. Because ntpd make a request and wait for response on different port, so check your firewall configuration and blocked packets. we have zero problems with ntpd behind a NAT firewall. The firewall has no special rules for ntp, but does 1:1 map the NTP server. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Unable to install FreeBSD from external USB cdrom
On May 31, 2007, at 1:49 AM, Daniel O'Connor wrote: Thanks so much, now I can have an automated install on a USB stick :) please, please, please share the recipes to make this. I would love to omit CD rom drives on my future systems as the only thing i ever use them for is install. also, can you run "fixit" mode from your USB stick, too? ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Some local rc scripts running twice
On May 27, 2007, at 8:11 AM, Pascal Hofstee wrote: If the above assumption holds true ... did you run the mergebase.sh script as suggested in /usr/ports/UPDATING ? Most significantly .. this script adds the following entry to your /etc/rc.conf local_startup="/usr/local/etc/rc.d" Hrm... seems this needs to be done for local_periodic in periodic.conf also! ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Some local rc scripts running twice
On May 27, 2007, at 2:48 AM, Duane Whitty wrote: Has anyone else encountered local rc scripts running twice? I thought I saw something about this on one of the @freebsd.org lists but my search efforts haven't located it yet. No, but I have noticed local periodic/daily scripts running twice on 6.2. Particularly, the postgres nightly vacuum. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: can I change probe order of mpt controllers?
On May 25, 2007, at 11:20 PM, Matthew Jacob wrote: FWIW, IMO- don't wire- use glabel instead. Hmmm... minor question: how does one deal with swap partitions? I tried as a test "glabel label -v swap1 /dev/aacd0s2b" but it doesn't show up as a label with "glabel list", and trying to stop it says it is an invalid label, and nothing showed up in /dev/label. Is that because I have to do this in single user mode with the swap partition not in use? It is the case for tunefs to label the ufs2 partitions because it can't write to a mounted file system. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: can I change probe order of mpt controllers?
On May 25, 2007, at 11:20 PM, Matthew Jacob wrote: FWIW, IMO- don't wire- use glabel instead. That's pretty neat, too! I think I like this one better since I won't have to make a special case in my system config file generator for this one host. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: can I change probe order of mpt controllers?
On May 25, 2007, at 11:23 AM, Michael Proto wrote: I believe you can use the following in your kernel config: options ROOTDEVNAME=\"ufs:da2s1" Or whatever the appropriate device/slice for your mpt2 controller. That doesn't seem like it will be of much use since the device unit name changes. Scott's solution of wiring the probe order seems like the right way to go. I'll try that after the weekend. Thanks for answering. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: can I change probe order of mpt controllers?
On May 25, 2007, at 11:22 AM, Scott Long wrote: Look in /sys/conf/NOTES for a long discussion on wiring SCSI device order. Thanks! That looks like it should do the trick. I'm assuming those go into /boot/loader.conf or do they go into the kernel config file itself? They look like loader.conf entries, but I'm not 100% sure on that. Also, any word on the adaptec monitoring program? I'm still interested in that, but my new solution is just to push the raid external and use a fibre card... which brought up this issue :-) ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
can I change probe order of mpt controllers?
I have a shiny new Sun X4100 here and it works pretty well (except that there is a bug in the ILOM bios that refuses to let the serial port console run at 115200!!!) I attached an external RAID array using an LSI fibre channel card, and now the boot disk is not found after the kernel boots. Ie, it can't find the root volume. This is because the fibre channel card is probed as mpt0 and the on-board disks are connected to mpt2. (Where's mpt1? no idea.) Once the RAID volume was initialized, the ordering of the disk device names changed. Is there some way to force the boot drive controller to be probed first and be mpt0? Or is there some way to force the boot drive to be a fixed device name? I'm planning to play with the RAID configuraitons and change partitions and add logical drives, etc., so this will be painful to reconfigure the OS every time I reconfigure the RAID. Any advice will be appreciated. Thanks! I'm running 6.2/amd64 from a fresh CD install. =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= Vivek Khera, Ph.D.Khera Communications, Inc. Internet: [EMAIL PROTECTED] Rockville, MD +1-301-869-4449 x806 ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: mfs and buildworlds on da SunFire x4600
On May 2, 2007, at 2:39 PM, Mars G. Miro wrote: - front USB ports wont work for a USB keyboard, just use da ports at da back. applies to X4100 as well. I think sun just makes them that way :-) ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: mount_nullfs in jail?
On Apr 19, 2007, at 5:17 AM, Vlad GALU wrote: Is there any way to have mount_nullfs working inside the jail? I mount nullfs from the host, that's how I share the ports directory across jails. /me too. easiest way is to create a file /etc/fstab.jailname with the mount in it, like this: /n/yertle1/sources/ports /u/data/jails/lsfe/usr/ports nullfs rw 0 0 which is how I map my ports tree mounted on the jail host via NFS from the main server into the /usr/ports directory of the jail named 'lsfe' in this case. I'm not sure if default jails read the /etc/fstab.jailname files, but ezjail's startup does, and makes for easy jail management.
Re: gmirror Issues
On Mar 25, 2007, at 11:59 PM, Christopher Schulte wrote: As I understand it now, the user has to manually account for this at OS install, and adjust the disk layout accordingly... yes? when was the last time you ran fdisk and it didn't leave some spare sectors at the end? i don't think you have to do anything special when this happens. at least we don't :-)
Re: WEB based project management software advice needed
On Mar 22, 2007, at 9:59 AM, ilya wrote: Therefore, we need WEB based, not Gnome version. It can use mysql and php. It's main goal is to serve 2-3 employees. It will be used for the simple tasks and projects performed by the junior system administrators. Take a look at RT (www.bestpractical.com) and Trac (trac.edgewall.com). We use Trac for projects, but RT can be adapted to it too. Both are in ports and both are customizable.
Re: Reverting to 6.2-RELEASE
On Mar 19, 2007, at 9:24 AM, LI Xin wrote:
I always use options INCLUDE_CONFIG_FILE for my kernel :-) Maybe we
should add it to DEFAULTS some day...
ew yucky
What I do is keep my kernel configs in subversion. I have a "common"
component which applies to all systems under my control, and an
architecture specific component that applies separately to i386 vs.
amd64 systems. In each, I take advantage of the fact that the config
file can have 'makeoptions' which are basically dumped right into the
generated Makefile.
So in my common file, KCICOMMON, I have this at the top:
makeoptions KCICOMMONREV="$Revision: 366 $"
makeoptions KCICOMMON="${KCICOMMONREV:C/[^0-9]//g}"
and in the i386 specific file, KCI32, I have this:
ident "[EMAIL PROTECTED]"
makeoptions KCIREV="$Revision: 358 $"
makeoptions KCI="${KCIREV:C/[^0-9]//g}"
Since some of my systems are SMP enabled, I have a minor variant
called "KCI32SMP" also, which is entirely this:
include KCI32
ident "[EMAIL PROTECTED]"
options SMP
now, my kernel identifies itself with uname:
% uname -i
[EMAIL PROTECTED]
So I know this is a 32-bit system running SMP with the version 358
i386 config and the version 366 common config.
and a trivial lookup in subversion tells me exactly what's in it.
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Xen Dom0, are we making progress?
On Mar 12, 2007, at 4:34 PM, Nikolas Britton wrote: What I'd really love to do is split up each service (httpd, postgres, samba/nfs, ldap/nis, asterisk, etc.) into discrete virtual machines. It's too much work trying to make them all play nice on one system, This is the purpose for which we (ab)use jails for too. Works great, less filling. Check out ezjail in the ports; it makes very lightweight jails by using nullfs to share the full install tree across multiple jails. This may not be what you want, but it is what I wanted. What you don't get is a private kernel per jail, and some services are not really virtualized like network, and SYSV IPC. And you can only assign one IP per jail. For what I need, Xen is overkill. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: any success with new sun "M2" product variant for X4100 and X2100
On Mar 8, 2007, at 4:45 PM, Jens Fallesen wrote: One issue I have is that the embedded management software can run on NIC 1 only. And once FreeBSD detects this, the embedded management software is disabled. Does anyone know of a way to make FreeBSD detect NIC 0 only? Did you spring for the $100 LOM card or are you just using the embedded software?
Re: Background process
On Mar 8, 2007, at 7:14 PM, Doug Barton wrote: Failing that, if you need to preserve anything that is emitted from the program, nohup is probably your best bet. If it isn't going to spit anything out on the terminal, take a look at daemon(8), which you probably will want to run with the -f option. I can't remember needing nohup to run *anything* since the ancient days of the old old old /bin/sh which would kill all of your processes upon logout. Modern shells do not do this. Just redirect the stdin/stdout/stderr appropriately and run in bg. The more appropriate tool, assuming the original program has no "run as daemon" flag is the daemon(8) program as mentioned above.
Re: any success with new sun "M2" product variant for X4100 and X2100
On Mar 9, 2007, at 8:19 AM, Thomas Hurst wrote: Also, if anyone knows which ethernet ports they put in that'd be helpful. I'd avoid them if they had broadcom chips :-( 2 nVidia nForce nve(4)'s and 2 Intel Pro/1000 em(4)'s. Quite a step back from the quad em(4)'s in !M2's, but 2 usable NIC's should be enough for most uses. Thanks for the info... I just need 2 NICs so that works for me. Now, if they'd rearrange the guts to take a full-height card I could go back to using LSI RAID cards instead of Adaptec ones :-)
Re: any success with new sun "M2" product variant for X4100 and X2100
On Mar 8, 2007, at 4:45 PM, Jens Fallesen wrote: One issue I have is that the embedded management software can run on NIC 1 only. And once FreeBSD detects this, the embedded management software is disabled. Does anyone know of a way to make FreeBSD detect NIC 0 only? what about something similar to this, how I disable atkbd on my sun boxes: hint.atkbdc.0.disabled=1 perhaps hint.bge.1.disabled=1 might work. you can test by breaking into the boot loader and typing "set hint..." then continue the normal boot. if it works, just plop that line (without set) into /boot/loader.conf.
Re: any success with new sun "M2" product variant for X4100 and X2100
On Mar 8, 2007, at 4:45 PM, Jens Fallesen wrote: Another funny thing is that the embedded management software works under MSIE only. Not exactly what I would expect from Sun. :-) ew gross. the description of the LOM on the X2100 claims the functionality is the same as the ILOM on the 4100, so that's very surprising to me. i'll probably splurge for the X4100 again, then. the ILOM on these is nothing short of spectacular. Thanks!
fibre channel cards
I see on the supported hardware list (http://www.freebsd.org/releases/ 6.2R/hardware-amd64.html) there are 4 LSI fibre channel cards supported by the mpt(4) driver. However, over on LSI's web site (http://www.lsi.com/storage_home/products_home/host_bus_adapters/ index.html) the fibre cards they are currently selling have rather different looking part numbers. Are the supported cards no longer made? Or did they just rename them? Are there any other fibre channel cards supported on FreeBSD? What card would one recommend to connect to an external RAID array for running a fairly busy database (several million inserts/selects/ updates per day)? Thanks!
any success with new sun "M2" product variant for X4100 and X2100
Has anyone successfully booted FreeBSD 6 on the new "M2" variants of sun's X2100 or X4100 boxes? I have three X4100 original versions that works stunningly well (but I don't use the internal disks) with FreeBSD 6.1. I was just curious how the new ones work, and the X2100 seems to fit the bill for what I currently need. Also, if anyone knows which ethernet ports they put in that'd be helpful. I'd avoid them if they had broadcom chips :-(
Re: SMP doesn't work without ACPI?
On Mar 7, 2007, at 2:14 PM, Sam Baskinger wrote: The 1950s that I have (IIRC as I installed them a few months ago) hang at about the same location when ACPI is enabled. I'll see if I can't pull one down and recreate the behavior. I should note that I'm running something after 6.2-RELEASE. Again, I'll try to recreate and get some data from the machines. Try this one: debug.acpi.disabled="timer" in your /boot/loader.conf or at the boot loader prompt type "set" followed by the above all in one line, then continue the boot. My Dell PE800 won't boot without that... hangs at the raid card probe (aac).
Re: Boot prompt for Intel AMT
On Mar 6, 2007, at 1:04 PM, Jack Vogel wrote: Yes, my bad, I spoke too quickly, it does use IP, sorry, I still find SOL much more descriptive of what I think about the whole apparatus however :) :-) Personally, I really like the Sun ILOM processors, even though they do boot an embedded linux, and the command set is, shall we say, confusing... It scares me to have something like SOL on an ethernet that's connected to the public wires.
Re: Intermittent network issues with Freebsd 6.2
On Feb 28, 2007, at 1:30 PM, Mike Tancsa wrote: Pretty well the same thing we are seeing. Our interrupt rate is a bit higher as this is a fairly busy DNS server. I am guessing this is more an issue with the bge driver then a general network issue as other similarly loaded boxes with em nics are just fine for us. My experience is that the bge driver works better for some broadcom chips than others. I have one box on which it is totally worthless, contributing to file system lockups of all things (a Dell PE800), and others on which it is pretty stable and fast (e.g., Dell PE SC1425, PE SC430). On our PE800, I had to disable the bge on BIOS and plug in an em- based NIC card. Made a world of difference in system stability and performance -- it is actually usable now :-) All boxes run FreeBSD 6.1 except the PE800 which runs 6.2. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
is localtime file binary compatible with older releases?
Is the compiled time zone info file binary compatible across FreeBSD versions? I have a couple of 4.x and one 5.x box still on my network, and I was wondering if it was possible to just copy the /etc/ localtime from a new 6.1 box on to all of them rather than having to install the updated zone file port. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: SVG-based traffic grapher
On Feb 21, 2007, at 4:17 AM, Dominik Zalewski wrote: I was wondering howto do a SVG-based traffic grapher like they did in pfSense project. pfSense is open source, so download the source and read it... there are no state secrets in there :-)
Re: 6.1BETA3 amd64 doesn't detect my floppy drive
On Jan 30, 2007, at 12:56 PM, Roland Smith wrote: I've built a kernel without "device fdc" on amd64 at least since 5.4 IIRC. I had problems with hangs when accessing the floppy drive. Haven't used floppies in years, don't miss them. A USB thumbdrive holds a lot more data anyway. I build all of my servers without CD and floppy drivers -- I configure them to build as loadable module just in case, but I've never yet had the need to load them... If I could get freebsd to install from a usb CD, i'd probably order the boxes without cd drives altogether, as it is used pretty much exactly once per life of server around here.
Re: second cpu not used on smp platform
On Jan 25, 2007, at 3:48 PM, Oles Hnatkevych wrote: Hello! Just cvsup-ed and upgraded to 6.2-STABLE. The box has hyperthreading processor: check value of machdep.hyperthreading_allowed sysctl. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: 6.2 Release - Adaptec 2130SLP driver?? issue - aac driver
On Jan 23, 2007, at 12:09 AM, Bruce Burden wrote: Sigh. Okay, thank you for the responses. I think I will go with "Plan 'C'", and find a PCI-X LSI MegaRAID card. I think there is some hope the megamgr port will work with them. My preferred card is the 320-2X dual channel card. It is wicked awesome fast and the megamgr program does work with them. Unfortunately, the Sun X4100 boxes have low-profile slots, and the only option for RAID cards is the Adaptec 2230SLP for dual channels. This is why I use the adaptec cards :-(
Re: 6.2 Release - Adaptec 2130SLP driver?? issue - aac driver
On Jan 20, 2007, at 2:06 AM, LI Xin wrote: My newer 2230SLP cards do not work with any extant command line tools for freebsd under amd64. The older cards did. I've tested FreeBSD 6.0 and 6.1. 6.2 is on the agenda to test soon. Do you mean Linux CLI tools on FreeBSD? I think I have missed my src/sys/dev/aac/aac_linux.c,v 1.4 change with re@ so I think there might be no change. Just MFC'ed that to RELENG_6. The linux tools have 0 chance of working on amd64 I have some newer version from one of the freebsd devs of adaptec CLI but it doesn't recognize the latest firmware in the 2230 card. I've been trying to work with that developer to sponsor some work to make the tools available and working on newer hardware and FreeBSD versions, but there has been some hold up getting necessary bits out of Adaptec.
Re: gmirror disks vs partitions
On Jan 19, 2007, at 12:42 AM, Vulpes Velox wrote: When ZFS comes available, I plan to actually run it across multiple mirrors. It has built in JBOD, but it does not do mirroring. It just does stripping. I think you misunderstand ZFS. It is robust against multiple disk failures. It doesn't do full disk mirroring, but does place multiple copies of data on multiple drives.
Re: 6.2 Release - Adaptec 2130SLP driver?? issue - aac driver
On Jan 19, 2007, at 11:52 AM, LI Xin wrote: I have some preliminary work on merging the Adaptec driver: http://people.freebsd.org/~delphij/for_review/patch-aac-vendor-b11518 But one of the reviewers has advised me to request boarder testing, especially against old cards and CLI tools, so I have hold the commit for now. My newer 2230SLP cards do not work with any extant command line tools for freebsd under amd64. The older cards did. I've tested FreeBSD 6.0 and 6.1. 6.2 is on the agenda to test soon. I shall have a look at your merged driver. It won't be a regression for me if the CLI tools stop working :-(
Re: aaccli on recent conrollers?
On Jan 9, 2007, at 7:39 AM, valiy volodin wrote: install /usr/ports/emulators/linux_base-fc4/ kldload aac_linux give linux/cmdline/arcconf from Adaptec CD or ftp://deps.ru/pub/ arcconf and run arcconf GETCONFIG 1 that doesn't work on aac(4) devices. aaccli usually does, and is native freebsd. nothing works on *recent* aac(4) devices with freebsd.
Re: aaccli on recent conrollers?
On Dec 27, 2006, at 10:31 AM, Andrew N. Below wrote: Latest Adaptec drivers released at 25 Oct 2006, aaccli says "Copyright 1998-2002"... Maybe someone already tried to contact Adaptec? I did a diff of the adaptec sources and the ones in freebsd 6.2- PRERELEASE and there are mostly minor differences (the device name changes, for example.) I'm in touch with Scott Long regarding sponsoring some work in this area to create a command line utility for monitoring the status on these new controllers. He's waiting for some libraries from Adaptec at this point. If you're interested in sharing the cost of this work please let me know. So far everyone else who's contacted me regarding this issue has not committed any money, which is fine. If I have to pay for the whole thing I will, because I believe in giving back to the community.
Re: Block IP
On Dec 21, 2006, at 3:59 PM, Graham Menhennitt wrote: Christopher Hilton wrote: If it's at all possible switch to using public keys for authentication with ssh and disallow password authentication. This completely stops the brute forcing attacks from filling up your periodic security mail. Are you sure about that? I only allow PublickeyAuthentication ssh2 connections but I get lots of security mail messages like: Be sure to disallow PAM auth also. I missed that one the first time I tried to disable interactive keyboard auth login.
Re: Possibility for FreeBSD 4.11 Extended Support
On Dec 21, 2006, at 1:35 AM, Colin Percival wrote: Now it is near the end of December, and FreeBSD 6.2 RC2 has yet to be seen anywhere. Chances are that FreeBSD 6.2 Release will come out earliest mid-January. This does not give much time for people to migrate to the newest FreeBSD release. I think it would be fair if support is extended for a few more months especially since 6.2 is so late in coming. Your opinion has been noted. FreeBSD 6.1 is a very nice stable release and has been out for a long time. You could migrate to that, too. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Serial console configured ... break to DDB still doesn't work ..
On Dec 17, 2006, at 12:34 AM, Marc G. Fournier wrote: I'm double checking with ALT_BREAK_TO_DEBUGGER set, to see if I can get *that* to work ... but, if anyone has any thoughts on this, please, I'm all ears ... I'm sooo close ... Definitely use ALT_BREAK_TO_DEBUGGER and turn off the regular BREAK_TO_DEBUGGER. The latter is dangerous depending on your serial console server device, or if you plug in a cable into the port on a running system...
Re: SunFire X4100 MPT Issues 6.2 RC1
On Dec 1, 2006, at 3:27 PM, Dave wrote: The upgrade to the ILOM card, and consequently the system BIOS, will not upgrade the LSI card and cause the boot problem that has been reported by me and others. As far as I know, the problem is only caused by upgrading the LSI MPT card to version 6.06.06.00. Ah so it doesn't affect external disk booting? I thought that was an issue too. I remember reading in the BIOS release notes that the LSI card bios had to be updated to use the newer system BIOS.
Re: SunFire X4100 MPT Issues 6.2 RC1
On Dec 1, 2006, at 11:29 AM, Dave wrote: We have talked to Sun about it and have not heard back on a fix for the latest BIOS. We have been given an older version of the BIOS that does not have this issue. Which version of bios is the latest that works for you? I have two of these X4100's and they both came with bios 1.0.0 (even though purchased 10 months apart). I'm now afraid to update the bios since we boot from an external RAID array.
Re: Problems unmounting/fssyncking extern UFS filesystem
On Nov 28, 2006, at 2:36 PM, Chuck Swiger wrote: The other choice would be to make sync [or the sync(2) system call, more precisely] blocking, so that it does not return until the buffer cache has been flushed and all dirty pages in VM have been written to disk. I would love a flag to sync(1) that would also make it wait until all softupdate pending actions are complete as well and force them to happen immediately.
