Re: NFS Locking Issue
User Freebsd writes: What are others using for ethernet? Of our two machines having the problem 1 has BGE and the other one has EM (Intel). Doesn't seem to make much of a difference. Except for the network cards, these two machines are identical. Same motherboard, same RAID controller, same amount of RAM, same RAID configuration... ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: NFS Locking Issue
User Freebsd writes: I believe, in Francisco's case, they are willing to pay someone to fix the NFS issues they are having, which, i'd assume, means easy access to the problematic server(s) to do proper testing in a "real life scenario" ... Correct. As long as the person is someone "trusted in the community" we could do that. And yes we are willing to come to some agreement for compensation for the help. Needless to say our introduction of new machines will go through a more rigourous test in the future.. specially when jumping to a new Release number in FreeBSD. We lost 1 big customer and after today we likely will loose 2 or 3 more.. of the big ones.. when it's all said and done we are likely to loose several thousand dollars/month due to this 6.X incidents. We are fairly new to NFS and that's why we were hoping to get someone to help us.. or at least point us in the right direction. I plan to go over the link you sent me and try to prepare at least one machine. As for paying someone, yes we have been actively looking for someone to help us since we are relatively new to NFS.. and much more newer to troubleshooting this type of prolbems ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: NFS Locking Issue
Robert Watson writes: It's not impossible. It would be interesting to see if ps axl reports that rpc.lockd is in the kqread state Found my post in another thread. 0 354 1 0 96 0 1412 1032 select Ss??0:07.06 /usr/sbin/rpcbind It was not in kqread state.. and that was from a point where the machine was totally locked up.. had to do a physical reset.. could not even kill nfsd that time. I had also more output from several different ps. You need to do "view more" to see them all. http://tinyurl.com/kpejr ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: NFS Locking Issue
Robert Watson writes: It's not impossible. It would be interesting to see if ps axl reports that rpc.lockd is in the kqread state, which would suggest it was blocked in the resolver. Just tried "ps axl | grep rpc" in the machine giving us the most grief.. Only got one line back: root 367 0.0 0.0 1368 960 ?? Ss 25Jun06 0:05.52 /usr/sbin/rpcbin 0 1 0 4 0 select Is that what one of the lines I should keep an eye, next time the machine is locked up? ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: NFS Locking Issue
Robert Watson writes: can you trigger it using work on just one client against a server, without client<->client interactions? This makes tracking and reproduction a lot easier Personally I am experiencing two problems. 1- NFS clients freeze/hang if the server goes away. We have clients with several mounts so if one of the servers dies then the entire operation of the client is put in jeopardy. This I can reproduce every single time with a 6.X client.. with both a 5.X and a 6.X server. "umount -f" hangs too. as multi-client test cases are really tricky! The second case only happens under heavy load and restarting nfsd makes it go away. Basically 'b' column in vmstat goes high and the performnance of the machine falls to the floor. Going to try http://www.freebsd.org/doc/en_US.ISO8859-1/books/developers-handbook/kerneld ebug-deadlocks.html And reading up on how to debug with DDB. Have another user who volunteered to give me some pointers.. so will try that.. so I am able to actually produce more helpfull info. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: NFS Locking Issue
Scott Long writes: For what it's worth, I recently spent a lot of time putting FreeBSD 6.1 to the test as both an NFS client and server in a mixed OS environment. I have a few debugging settings/suggestions that have been sent my way and I plan to try them tonight, but this is just another report.. FreeBSD only environment. Today after hours going crazy with horrible performance I brought down nfsd and brought it back up.. that simple process got vmstat 'b' column down and everything was back to normal. Again this will not help anyone troubleshoot, but just to mention that it happens even with a FreeBSD only environment. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: NFS Locking Issue
Kostik Belousov writes: I think that then 6.2 and 6.3 is not for you either. Problems cannot be fixed until enough information is given. I am trying.. but so far only other users who are having the same problem are commenting on this and other simmilar threads. We just need some guidance.. Mark gave me a URL to turn on debugging and volunteered ot give me some pointers.. I will try, but I will likely try on my own time, on my own machines.. I can not tell the owner of the company I work for to let me "try".. or "play around" in production machines.. as we loose customers because of current problems with the 6.X line. Since nobody except you experience that problems (at least, only you notified about the problem existence) Did you miss the part of: User Freebsd writes: Since there are several of us experiencing what looks to be the same sort of deadlock issue, I beseech you not to give up I am not the only one reporting or having the issue. Is this for intr mounts? "intr" ? improved handling of signals in nfs client. If you could test it, that would be useful. Does it matter if the OS is i386 or am64? Have an amd64 machine I can more easily play with... with no risk to production. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: NFS Locking Issue
User Freebsd writes: Since there are several of us experiencing what looks to be the same sort of deadlock issue, I beseech you not to give up I will try to setup the environment, but to be honest no more 6.X for us until 6.2 or 6.3.. We have lost clients already. Is this a problem that you can easily recreate There is one thing I can easily recreate that would very helpfull to solve. The 6.X NFS clients freeze if the NFS server goes away. I have been able to reproduce that every single time.. both in test and production. machine? In my case, I have one machine fully configured for debugging, Although solving both, server and client, would be great for us if we could at least solve the client.. it would be very helpfull.. until our next server comes.. in which we are going to install 5.5 information to the developers to debug this, the faster it will get fixed Agree.. but with 4+ crashes in less than a week it has reached the point where we have moved workload away from the most problematic machine.. to try to aliviate the problem.. but still was not enough.. to prevent at least one big customer of ours to go.. We don't keep tight track of the smaller ones. :-) different then your auto-mechanic ... try telling him there is a 'knocking under the hood, please tell me how to fix it, but you can't have my car', and he'll brush you off ... give him 30 minutes under the hood, and not only will he have identified it, but he'll probably fix it too ... The problem is when you are a taxi driver... and it cost you money to have the car off the streets.. and you don't know when the 'knocking' will occur... :-) Will setup my laptop with the debug settings and will then work on trying to debug the client problem... depending on how that goes will then possibly try the server that is giving us problems. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: NFS Locking Issue
John Hay writes: I only started to see the lockd problems when upgrading the server side to FreeBSD 6.x and later. I had various FreeBSD clients, between 4.x and 7-current and the lockd problem only showed up when upgrading the server from 5.x to 6.x. It confirms the same we are experiencing.. constant freezing/locking issues. I guess no more 6.X for us.. for the foreseable future.. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
High vmstat, filesystem unresponsive then hang 6.1 Stable
I believe this may be related to the NFS issues mentioned recent, but hopefully I may have captured enough info to help others troubleshoot.. I got the header of some ps commands.. and when was about to do full listing of the same ps commands to files.. the machine hung up. The machine is 6.1 Stable around 6-25 ( plus or minus 1 day). iostat 5 (not much of a load) tty da0 cpu tin tout KB/t tps MB/s us ni sy in id 0 31 17.71 125 2.17 20 0 5 1 74 0 26 8.57 23 0.19 0 0 1 0 99 09 33.73 10 0.34 0 0 0 0 99 0 21 8.42 18 0.15 0 0 1 1 99 09 15.92 58 0.90 0 0 0 0 99 09 15.18 7 0.10 0 0 0 0 99 0 53 12.93 9 0.11 0 0 1 0 99 0 31 5.17 58 0.29 0 0 1 1 99 vmstat 5 (very high 'b' column) procs memory page disk faults cpu r b w avmfre flt re pi po fr sr da0 in sy cs us sy id 0 248 2 1410436 110728 1519 2 0 0 1644 264 0 4481 8862 9168 20 6 74 0 248 0 1410436 1107960 0 0 0 13 0 4 700 40 1426 0 1 99 0 248 0 1410436 1107641 0 0 0 39 0 14 1253 722 2615 0 1 99 0 248 0 1410436 1107201 0 0 0 10 0 5 407 396 899 0 1 99 0 248 0 1410436 1107041 0 0 0 60 0 21 2822 360 5695 0 2 98 0 248 0 1410436 1106841 0 0 0 10 0 7 538 434 1166 0 1 99 0 248 0 1410436 1106680 0 0 0 75 0 51 576 163 1026 0 0 99 0 248 0 1410436 1106960 0 0 0 23 0 31 1171 190 2271 0 1 99 vmstat 5 procs memory page disk faults cpu r b w avmfre flt re pi po fr sr da0 in sy cs us sy id 0 250 1 1399688 152000 1517 2 0 0 1643 264 0 4479 8853 9163 20 6 74 0 250 0 1399688 1519682 0 0 0 25 0 28 1395 966 2852 0 2 98 0 250 0 1399692 1518921 0 0 0 12 0 6 446 540 986 0 0 99 0 250 2 1399692 1516041 0 0 0 50 0 37 803 675 1611 0 1 99 Don't recall which ps.. 411 1 0 ufs ?? Ds 0:04.81 /usr/sbin/mountd -r 37675 650 0 ufs ?? D 0:00.46 /usr/bin/perl /data/backaway/mailarchive/client/bin/smtpproxy 127.0.0.1:10026 127.0.0.1:10025 (perl5.8.7) 37919 650 0 ufs ?? D 0:00.46 /usr/bin/perl /data/backaway/mailarchive/client/bin/smtpproxy 127.0.0.1:10026 127.0.0.1:10025 (perl5.8.7) 39306 650 0 ufs ?? D 0:00.39 /usr/bin/perl /data/backaway/mailarchive/client/bin/smtpproxy 127.0.0.1:10026 127.0.0.1:10025 (perl5.8.7) 40214 386494100 ufs ?? Ds 0:00.00 /usr/local/bin/maildrop -d [EMAIL PROTECTED] 40220 329434100 ufs ?? Ds 0:00.00 /usr/local/bin/maildrop -d [EMAIL PROTECTED] 40223 332574100 ufs ?? Ds 0:00.00 /usr/local/bin/maildrop -d [EMAIL PROTECTED] 40226 329424100 ufs ?? Ds 0:00.00 /usr/local/bin/maildrop -d [EMAIL PROTECTED] 40228 331994100 ufs ?? Ds 0:00.00 /usr/local/bin/maildrop -d [EMAIL PROTECTED] 40231 385994100 ufs ?? Ds 0:00.00 /usr/local/bin/maildrop -d [EMAIL PROTECTED] 40233 328964100 ufs ?? Ds 0:00.00 /usr/local/bin/maildrop -d [EMAIL PROTECTED] 40236 332244100 ufs ?? Ds 0:00.00 /usr/local/bin/maildrop -d [EMAIL PROTECTED] 40238 328764100 ufs ?? Ds 0:00.00 /usr/local/bin/maildrop -d [EMAIL PROTECTED] 40240 329764100 ufs ?? Ds 0:00.00 /usr/local/bin/maildrop -d [EMAIL PROTECTED] 40242 355804100 ufs ?? Ds 0:00.00 /usr/local/bin/maildrop -d [EMAIL PROTECTED] 40246 355934100 ufs ?? Ds 0:00.00 /usr/local/bin/maildrop -d [EMAIL PROTECTED] 40248 329234100 ufs ?? Ds 0:00.00 /usr/local/bin/maildrop -d [EMAIL PROTECTED] 40252 355964100 ufs ?? Ds 0:00.01 /usr/local/bin/maildrop -d [EMAIL PROTECTED] 40253 298334100 ufs ?? Ds 0:00.01 /usr/local/bin/maildrop -d [EMAIL PROTECTED] ps ax -O ppid,flags,mwchan | awk '$6 ~ /^D/ || $6 == "STAT"' PID PPID F MWCHAN TT STAT TIME COMMAND 2 0 204 - ?? DL 0:17.68 [g_event] 3 0 204 - ?? DL 9:14.85 [g_up] 4 0 204 - ?? DL10:50.81 [g_down] 5 0 204 - ?? DL 0:02.93 [thread taskq] 6 0 204 - ?? DL 0:00.00 [acpi_task0] 7 0 204 - ?? DL 0:00.00 [acpi_task1] 8 0 204 - ?? DL 0:00.00 [acpi_task2] 9 0 204 - ?? DL 0:00.00 [kqueue taskq] 15 0 204 - ?? DL 8:47.55 [yarrow] 27 0 204 - ?? DL 0:01.72 [fdc0] 28 0 204 psleep ?? DL 0:43.74 [pagedaemon] 29 0 204 psleep ?? DL 0:00.00 [vmdaemon] 30 0 20c pgzero ?? DL 7:35.27 [pagezero] 31 0 204 psleep ?? DL 0:57.11 [bufdaemon] 32 0 204 syncer ?? DL 8:46.07 [syncer] 33 0 204 vlruwt ?? DL 0:28.29 [vnlr
Re: em device hangs on ifconfig alias ...
Doug Ambrisko writes: Can you try: http://www.ambrisko.com/doug/bge_ipmi_3.patch and see if that helps. I need one minor tweak to it before I can commit it. We have a brand new machine getting readied.. Passed along the patch URL to the tech building the machine. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: NFS Locking Issue
User Freebsd writes: the one thing that sticks out to me about this report is that they upgraded teh NFS server to FC5 I wonder if the FreeBSD 6.X client would freeze with a non FreeBSD NFS server. Would be interesting to have that info for comparison. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: em device hangs on ifconfig alias ...
Atanas writes: I have some newer machines with 2 Broadcom chips on-board. I plan to give them a try at some point in the future, but I'm not sure how stable the bge driver For us they have been a problem. Primarily because it causes all kinds of freezing/crashes when having an IPMI board. I believe it has performed ok in machines where we don't have an IPMI card. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: NFS Locking Issue
Michel Talon writes: Strange, since i upgraded to FreeBSD-6.1 and the NFS server to Fedora Core 5, my machine, NFS client is happy, and lockd works. What volume are we talking about? My own problems and other reports I see are all under heavy load. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Weird problem upgrading 5.4 to 6.1
Sergey Shyman writes: Can't work out which disk we are booting from. Guessed BIOS device 0x not found by probes, defaulting to disk0. Is that a RAID you are booting from? Booting with old kernel works fine. Also BIOS see IDE drive. Single IDE drive? ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: NFS Locking Issue
Michael Collette writes: This last week I had been working on a test network to test out 6.1 prior to upgrading our production boxes from 5.4. I wish I had done that.. :-( That's when I ran across the rpc.lockd issues that have been discussed earlier. I am not familiar with that, but I can tell you from experience that the nfs client code in 6.X has issues.. In particular if the server goes down the client machine doesn't allow you to unmount the volume.. and if you have programs trying to acces the downed mount, the whole machine may end up freezing. ... I also have my mail server delivering messages to a file server via NFS. We use NFS as our "storage" sever for pop/imap, but use the MTA to deliver to the machine. Is NFS a big deal for most other users, or am I out here on the fringe using it as much as I do? It is for us.. I am even trying to see if we can even pay someone to expedite getting NFS fixed in 6. Unfortunately we decided to increase our NFS usage after I had installed 6.X in a number of new machines. Is anyone working on a fix for this? If there is I have not read about it. I guess I'm still just a bit stunned that a bug this obvious not only found it's way into the STABLE branch, but is still there. I am fairly new to NFS.. but I am getting the impression that FreeBSD's NFS is not as mature as other platforms. I also think it has a lot to do with usage patterns. I have seen mentions of people having hundreds of clients connected to a single NFS server... yet I see problems with just a handfull of clients. Maybe the issue is only with the 6.X branch. Sadly part of the reason I moved some newer machines to 6.X was because of some comments I saw on how NFS had been improved in 6.X :-( ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: 6.1-R ? 6-Stable ? 5.5-R ?
Kostik Belousov writes: This seems to be a different issue. BTW, I have already heard complaints about deadlocks caused by combination of nfsd and snapshots. I think you can add: nfsd + background fsck too. Probably, I will look into this, but cannot give you estimations when. Thank!! For now, you could turn off background fsck. We did.. and it was horrible.. It seems mysql was crashing the machine so we had 4 reboots in about 5 days. Since we had to give up on background fsck, that meant 2 hours every time the machine rebooted (the machine in question has 10+ million files in the volume which takes the 2 hours to fsck). ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: 6.1-R ? 6-Stable ? 5.5-R ?
Mark Linimon writes: It's not easily possible for a FreeBSD developer to put these kinds of stresses on a machine, so we rely on our users to help us with these problems. And this is why I have been trying to someone to PAY him/her to help us. I have been trying to find if anyone that works with the NFS code in FreeBSD would have time to work with us on a consulting bases to get the NFS client in 6 fixed. As for the vmstat problem with that machine.. the same.. if someone was willing to help us track down what in 6.X .. or even our settings.. is causing this heavy load we would definitely be willing to pay. Should I contact the FreeBSD foundation for this? In particular the NFS client is a killer problem for us. Anyone can recommend who to talk to? Should I be writing to the filesystem list? I am not sure how much of a problem the nfs server side is, but the client in the whole 6.X line has been problematic for us. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: FreeBSD 6 and MySQL with DBs on a NAS
[EMAIL PROTECTED] writes: I wasn't able to find anyone seeing a similar problem as what I describe. I'm using FreeBSD 6.1, MySQL 5.0.21 built from ports and a NetApp share provided over NFS. Recently we have been having problems with Mysql in 6.X (1 machine 6.0 stable and another 6.1 Stable). In our case it seems the Mysql (4.X from ports) was either causing or contributing to the machine crashing. Has anyone else ever seen the issue as described in the e-mail below? I also saw another thread describing Mysql problems in 6.X.. that is what made me check in our system if the crashes were related to mysql. One machine crashed 4 times in 5 days. So far since removing mysql it has been ok.. but it has only been 2 days since we removed mysql from the machine. I currently have MySQL 5.0.22 built from ports on a FreeBSD 6.1 machine with the DB data residing on a NetApp share connected via NFS. Isn't this a bad idea to begin with? Using an NFS mount to do database work. Also NFS in 6.X... specially the client seems to have issues. I am even considering to move my 6.X machines that are NFS clients back to 5.5 if I can't find a fix. In particular if a server dies, the client in 6.X freezes the machine if you try to connect to the path that was mounted on the NFS server. Soft mount did not help. strange thing happens often after a few hours or a couple of days, some tables that are very active start to crash for no apparent reason as far as I can tell. I could be wrong, but I think doing a database over NFS is likely not a good idea from a performance and stability standpoint. Specially a heavily used database. Upon moving the DB data to a local drive, the system operates flawlessly and has done so for many weeks, but I really need to keep these data on the networked share. Why do you need it in the networked share? The problem didn't happen when I was using FreeBSD 4.11, it only started after upgrading to FreeBSD 6.0 or 6.1. As I wrote above.. I have very little (approaching none) faith in the NFS client in 6.X Where I work we are even tying to see if we can get a hold of one of the NFS developers in FreeBSD and even pay to have this issue looked at.. So far I wrote to two of them, but have not heard back from them. I believe I have 2 more names to try, beyond that I am not sure we can remain with 6.X on the nfs clients. I have yet to try automaunt to see if that would help, but in general even when the server is up I kind of wonder if the client is stable. A poster on a MySQL mailing list suggested perhaps it could be a file locking issue at the OS level and so I post my inquiry here. That is one of the reasons I am suggesting against using a NFS share to do DB work. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: 6.1-R ? 6-Stable ? 5.5-R ?
Kostik Belousov writes: > Approved by:pjd (mentor) > Revision ChangesPath > 1.156.2.3 +16 -0 src/sys/nfsserver/nfs_serv.c > 1.136.2.3 +4 -0 src/sys/nfsserver/nfs_srvsubs.c The above files are what I have. Yes from a 6.1 stable around 6-25-06 What this means ? That you have _this_ revisions of the files, and your LA skyrocketed ? LA = load average? Our problem is vmstat 'b' column growing and nfs causing locks on the server side. When the machine locked it was running a background fsck. I saw "Giant" a lot in the status of the nfsd. I am really wondering if 6.1 is ready for production under heavy load. And for sure the NFS client in the whole 6.X line seems problematic (see my post in the stable list under subject: NFS clients freeze and can not disconnect). As for the vmstat, about the only thing doing anything even remotely appearing to be doing work is NFS. For instance I saw this in another thread: ps ax -O ppid,flags,mwchan | awk '($6 ~ /^D/ || $6 == "STAT") && $3 !~ /^20.$/' And in the machine in question it shows PID PPID F MWCHAN TT STAT TIME COMMAND 16124 16123 0 biowr ?? D 46:24.76 nfsd: server (nfsd) 16125 16123 0 biowr ?? D 16:05.58 nfsd: server (nfsd) 16126 16123 0 biowr ?? D 11:05.53 nfsd: server (nfsd) 16127 16123 0 biowr ?? D 8:01.21 nfsd: server (nfsd) 16128 16123 0 biowr ?? D 6:19.15 nfsd: server (nfsd) 16129 16123 0 biowr ?? D 5:01.27 nfsd: server (nfsd) 16130 16123 0 biowr ?? D 3:55.56 nfsd: server (nfsd) 16131 16123 0 biowr ?? D 3:13.11 nfsd: server (nfsd) 16132 16123 0 biowr ?? D 2:43.26 nfsd: server (nfsd) 16133 16123 0 biowr ?? D 2:16.40 nfsd: server (nfsd) 16134 16123 0 biowr ?? D 1:57.00 nfsd: server (nfsd) 16135 16123 0 biowr ?? D 1:41.02 nfsd: server (nfsd) 16136 16123 0 biowr ?? D 1:27.07 nfsd: server (nfsd) 16137 16123 0 biowr ?? D 1:15.25 nfsd: server (nfsd) 16138 16123 0 biowr ?? D 1:06.54 nfsd: server (nfsd) 16139 16123 0 biowr ?? D 0:57.57 nfsd: server (nfsd) 16140 16123 0 biowr ?? D 0:50.65 nfsd: server (nfsd) 16141 16123 0 biowr ?? D 0:44.60 nfsd: server (nfsd) 16142 16123 0 biowr ?? D 0:38.29 nfsd: server (nfsd) 16143 16123 0 biowr ?? D 0:34.21 nfsd: server (nfsd) 16144 16123 0 biowr ?? D 0:29.34 nfsd: server (nfsd) 16145 16123 0 biowr ?? D 0:26.35 nfsd: server (nfsd) 16146 16123 0 biowr ?? D 0:22.25 nfsd: server (nfsd) 16147 16123 0 biowr ?? D 0:18.17 nfsd: server (nfsd) 16148 16123 0 biowr ?? D 0:15.95 nfsd: server (nfsd) 16149 16123 0 biowr ?? D 0:13.66 nfsd: server (nfsd) 16150 16123 0 biowr ?? D 0:10.81 nfsd: server (nfsd) 16151 16123 0 biowr ?? D 0:08.92 nfsd: server (nfsd) 16152 16123 0 biowr ?? D 0:06.82 nfsd: server (nfsd) 16153 16123 0 biowr ?? D 0:05.16 nfsd: server (nfsd) 84338 100434100 ufs ?? D 0:02.00 qmgr -l -t fifo -u 91632 100434100 biowr ?? D 0:00.02 cleanup -z -t unix -u 91650 100434100 ufs ?? D 0:00.04 [smtpd] 91912 866354100 biowr ?? Ds 0:00.01 /usr/local/bin/maildrop -d [EMAIL PROTECTED] 91916 905794100 biowr ?? Ds 0:00.01 /usr/local/bin/maildrop -d [EMAIL PROTECTED] 71677 716724002 ppwait p1 D 0:00.15 -su (csh) The iostat for that machine shows: iostat 5 tty da0pass0 cpu tin tout KB/t tps MB/s KB/t tps MB/s us ni sy in id 0 130 15.35 109 1.63 0.00 0 0.00 6 0 6 1 87 0 36 10.43 230 2.34 0.00 0 0.00 3 0 2 1 93 0 12 10.81 280 2.96 0.00 0 0.00 6 0 2 0 92 0 12 13.03 259 3.30 0.00 0 0.00 0 0 1 1 98 0 12 12.87 259 3.26 0.00 0 0.00 5 0 2 1 91 0 12 17.17 228 3.82 0.00 0 0.00 8 0 3 1 87 0 12 18.38 306 5.49 0.00 0 0.00 3 0 2 1 94 0 12 14.53 284 4.04 0.00 0 0.00 6 0 3 1 89 0 12 26.03 213 5.41 0.00 0 0.00 5 0 3 2 91 Before that machine went into production, during the stress test I saw the machine do 700+ tps and substantially more MB/s. We also have another machine identical hardware wise and although it's tps is 50 to 100 less than this one.. the machine is always ver low in the 'b' column. I am trying now to read up in vmstat.. to see if I can see anything wrong in vmstat -s 1660720108 cpu context switches 736683712 device interrupts 46973243 software interrupts 99310719 traps 3405487756 system calls 46 kernel threads created 385149 fork() calls 7785 vfork() calls 0 rfork() calls 2809 swap pager pageins 4449 swap pager pages paged in 2027 swap pager pageouts 4609 swap pager pages pag
Re: 6.1-R ? 6-Stable ? 5.5-R ?
Rink Springer writes: FreeBSD src repository Modified files:(Branch: RELENG_6) sys/nfsservernfs_serv.c nfs_srvsubs.c Log: MFC of the temporary fix for nfsd leaking GIANT. src/sys/nfsserver/nfs_serv.c rev. 1.165 src/sys/nfsserver/nfs_srvsubs.c rev. 1.141 Both of those files were older. Approved by:pjd (mentor) Revision ChangesPath 1.156.2.3 +16 -0 src/sys/nfsserver/nfs_serv.c 1.136.2.3 +4 -0 src/sys/nfsserver/nfs_srvsubs.c The above files are what I have. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: 6.1-R ? 6-Stable ? 5.5-R ?
Rink Springer writes: On Wed, Jun 28, 2006 at 04:09:14AM -0400, Francisco Reyes wrote: So far 6.X has been for the most part stable as NFS sever for us.. but one of our servers has been hanging crashing and NFSD was showing as status "GIANT" You'll want to upgrade to the latest 6-STABLE, where this bug has been fixed. RELENG_6? From what I can tell that is stable RELENG_6 The line of development for FreeBSD-6.X, also known as FreeBSD 6-STABLE FreeBSD 6.1-STABLE #4: Sun Jun 25 < Was it fixed after Jun 25? ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
NFS clients freeze and can not disconnect
I have a series of machines 6.0 stable (various dates), 6.1 stable (various dates) that freeze if the NFS sever they are connected to becomes unresponsive or crashes. Was able to confirm this behavior for both i386 and AMD64. A 5.3 machine connected to the same nfs server was able to "umount -f" the volume. I was able to reproduce the problem in a test environment. Tried TCP, UDP connections, soft mount and a retry count of 1. It doesn't seem to matter whether the server is 6.X or 5.X (tested in both), it is the 6.X client that has the problem. Searching the archives seem to be a known issue. Is there a patch? Or has it recently being fixed? The dates of my 6.X client machines varies, but are 6.0 stable up to 6.1Stable may 29. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: 6.1-R ? 6-Stable ? 5.5-R ?
Albert Shih writes: I've nfs server running 6-Stable (5 April 2006) with some trouble but ... well approx stable. But today he crash again (after ~1.5 mounth). Now I'm like have some advise : 1/ I can upgrade to 6.1-Release, but I've see many problem with nfsd heavy load. And the only purpose of this server is .. nfsd. We have been upgrading to 6.X.. including 6.1 and so far the server seems, for the most part stable, until a few days ago(more below). What is a HUGE problem for us so far is that if the server hanks.. all clients that are 6.X can't unmount. 6.0 stable, 6.1 stable.. recent 6.1.. not so recent 6.1.. UDP, TCP, softmount with retrycount 1... In short. Right now I would not recommend 6.X for nfs client. 3/ I can downgrade to 5.5. I known this is legacy release but if it's workthat's enought for me... So far 6.X has been for the most part stable as NFS sever for us.. but one of our servers has been hanging crashing and NFSD was showing as status "GIANT"... and locking.. It had 6.0 stable and upgrading it to 6.1 stable (6-26) has not helped. But other machines are ok.. so may be an application. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
6 Stable freezes upon bootup, but Release 6.0 works
Have a machine that once we upgraded to 6 Stable the machine would freeze at the bootup menu. We tried disabling ACPI and AIPC and it did not help. Usually the freezing occurs after 2 or 3 seconds out of the 10 second countdown. To make it more interesting... if we press enter right after the menu comes up the machine boots perfectly fine and the machine works without any problems. Motherboard Tyan S515G3NR, 3WARE 2 port controller, 2GB RAM. Tried stable from 12-6-05 (initial stable cvsup we did).. and after we discovered the problem we also tried stable as of 12-12-05. Strangely enough we have a second machine with the same motherboard, same amount of memory, same 3Ware controller, but with different drives. the machine that is Freezing has 10K RPM SATA raptors and the other has some 7200RPM western digitals (same brand as the raptors). That second machine works fine with 12-6 stable. We looked at the bios levels and as far as we can tell they have the same bios level. On the trouble machine I did do a custom kernel, but I don't believe the kernel is even loading yet at the point it freezes. :-( Is there a verbose mode or log for the boot menu and/or the boot process? Given some recent bug fixes on 6 stable that correct a problem with Raid controllers I really would like to get both machines to 6 Stable. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Disk 100% busy
On Thu, 3 Nov 2005, michael meltzer wrote: Controller: http://www.3ware.com/products/serial_ata2-9000.asp 16 port muili-lane, with BU and 265meg, cheaper than most SCSI controller From what I gather, the ARECA controllers have significantly better performance. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Disk 100% busy
On Thu, 3 Nov 2005, Chuck Swiger wrote: If you're using maildir, that is one of the situations which works pretty well with RAID-5, although RAID-10 is also (always? :-) a good choice. How about for database? In particular postgresql. How bad would RAID 5 be for it? I still have some, limited, hopes I can convince the owner of the company to go with RAID 10 with 10K rpm drives.. the most likelyhood we will go with RAID 5, 7200rpm drives for a database project ahead. Alternatively I will see how RAID 5 with 10K rpm SCSI drives compares price wise, but I am sure it will be substantially more. :-( ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: SATA vs SCSI ...
On Tue, 28 Jun 2005, Don Lewis wrote: BTW, even with an UPS monitored by sysutils/nut, I've had a non-trival number of ungraceful shutdowns caused by power problems (power cord between UPS and computer falls out, sudden battery death, etc.). For this reason, all of my machines (other than my PVR) use SCSI disks with WCE set to 0. Going through an old thread and saw your comment... What is the sysctl parameter to use to turn off WCE? ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: /usr/local/etc/rc.d/*.sh not working?
On Tue, 14 Jun 2005, Michael W. Lucas wrote: a) old-style .sh scripts are not supported, Michael needs to rewrite them for rcNG b) old-style .sh scripts are supported, Michael has some other system problem Have you tried moving out most of the scripts and leaving a subset.. if those start then the problem may be related to the number of scripts. If they still don't work at least you know the problem is not related to the number of scripts. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Lifetime of FreeBSD branches
On Thu, 26 May 2005, Scott Long wrote: Is the goal to have a new major branch every 2 years? Yes. This will allow us to pace our major development projects much better than we have in the past. Someone mentioned 5.X will be supported till 2007 (or at least that's the plan). So will, in average, branches be supported 2 years after a new one takes over? Sounds like a good strategy for most shops. I can imagine that for a big shop with lots of machines it may be a bit agressive, but I am not one of them. :-).. besides big shops likely have developed entire systems around how to deploy the OS to many machines. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Lifetime of FreeBSD branches
On Tue, 24 May 2005, Scott Long wrote: Again, please don't take the abrupt switch to 6.0 to mean that 5.x is flawed or that 6.x will also have a short lifespan. The real purpose of the switch is nothing but positive; it'll keep us focused and prevent us from overreaching and overextending ourselves. It's a very good and very postive strategy. So why have a 6.X naming convention to begin with? Why not just stay in 5.X name wise? Is there a thread that sheds some light on that topic? Is the goal to have a new major branch every 2 years? ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Size of / partition?
On Sat, 29 Dec 2001, Julio Merino wrote: > On Fri, Dec 28, 2001 at 11:32:36PM -, David Reid wrote: > > Just cvsup'd to stable and I've almost run out of room on /! How big should > > I create it when I reinstall as I now don't have enough to do another build. > > I allocate 70Mb for / on a 20gb disk and never ran out of space. You may > have old /modules and/or kernels laying around, as well as files in > /root. Also check your /tmp (which I mount on its own partition, > or with mfs!). On a new machine with a big drive I would recommend people used at least 100MB. In particular I have found that some programs when they crash and create a core file it may end up filling up "/". On my newer machines at work with lots of space I made / 1GB, /var 1GB and the rest to /usr. These are machines where I have much more free space than they will probably ever need anyway so space wasn't much of an issue. On a machine which is tighter with space I would suggest still to try and get 100MB root. Another possible approach may be to leave /var on / and give / 150MB. Space ALWAYS comes down to what are you going to do with the machine. On most instances / is rarelly used. /var can sometimes be a problem if you have a runaway log which you forgot to add to newsyslog and this is why many people like to have /var separate from /. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: HEADS UP! GENERIC/Kernel configs using maxusers of 0 willautosize but require new config binary.
On Thu, 13 Dec 2001, Matthew Dillon wrote: > The simplified version of the maxusers auto-sizing has been MFCd but > people need to be aware that to use it you need to update your kernel > source AND recompile /usr/src/usr.sbin/config. So will the following sequence be ok? make buildworld make installworld make kernel To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: Undesirable behaviour of burncd erase
On Thu, 28 Jun 2001, Andrew Reilly wrote: > The other disks are masters on each of the two ATA controllers: > > ad0: 6149MB [13328/15/63] at ata0-master UDMA33 > ad1: 6149MB [13328/15/63] at ata1-master UDMA33 > > After producing a non-working CD with burncd, probably because of > the ill-advised placement of a "data" file, I tried to erase the > CD-RW disk before trying again. So I did something like: > > burncd -e -f /dev/acd0c erase Andrew how about using blank instead of erase? Doesn't seem to freeze or have any problems on my machine. >From the man page: Blank a CD-RW medium. This uses the fast blanking method, so data are not physically overwritten, only those areas that make the media appear blank for further usage are erased. Any benefits of using erase over blank? Also I don't know if it would matter, but on which channel do you have the CD? I have it on the secondary as to not affect/interfere with the OS. I have few things on my second disk so I rarely access the CD and the second disk at the same time. Another inmediate work around until the changes Soren mentioned may be to perhaps get an IDE card. This way the IDE channels would not be the same. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: Can't newfs big filesystem (twe/4.3-stable)
On Wed, 13 Jun 2001, Jaye Mathisen wrote: > Trying to newfs the following fs is giving me fits: > > newsfeed-inn# disklabel -r twed0 > # /dev/twed0c: > bytes/sector: 512 > sectors/track: 63 > tracks/cylinder: 255 > sectors/cylinder: 16065 > cylinders: 65418 > sectors/unit: 1050940800 > 8 partitions: > #size offsetfstype [fsize bsize bps/cpg] > c: 10509408000unused0 0 # (Cyl.0 - >65418*) > d: 105094080004.2BSD0 0 0 # (Cyl.0 - >65418*) > > Frankly, I need a whopping about 10 files on this FS, but: Did you try updating the bios of that 3ware card? In the past I had all kind of problems with 2 3ware cards and they all went away aftera flashing with a recent bios. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: New KERNCONF option
On Tue, 13 Mar 2001, Torben Baecker wrote: > make buildworld > make kernel KERNCONF=JUPITER So this new procedure replaces the old? Can one put the KERNCONF variable on /etc/rc.conf and just do "make kernel" Where is this explained in /usr/src/UPDATIN? To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
How to burn ISO? (was New 4.3 BETA (BETA2)... )
On Tue, 13 Mar 2001, Jordan Hubbard wrote: > Since there has been a sudden spate of changes post-BETA (not a huge > number, but more than the usual amount in -stable since the freeze) > I decided it would be a good idea to roll a BETA2 snapshot, and > it's now on: > >ftp://ftp.freebsd.org/pub/FreeBSD/releases/i386/4.3-BETA2/ How can I make a bootable CD from this? Could not find anything on the archives, FAQ or handbook. I know how to create disk from ISO images, but last I tried the CD was not bootable. The line I use to create disks from ISO images is: burncd -f /dev/acd0c -s 10 data fixate To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: New US CVSup mirrors
On Mon, 20 Nov 2000 18:17:02 +1100, Zero Sum wrote: >If you are going to try a second mirror within a short timeframe, it has to >be further up the food chain. > >If the server you select is not available, then an automatic switch to the >next one up the CVS mirror food chain might work. It may still be easier if the servers reported a last update date or some other unique way of identifying last update. The client could use this flag(s) to detect a mirror less up to date than the source tree been updated and display an error which would require some kind of override flag. After a little more thought there is another problem with your approach. It would basically require some server to always be able to indicate the next machine on the "food chain", but what happens when that machine is too busy? In other words that approach simply adds another possible step which may lessen the bottleneck and is more scalable, but is not a distributed approach. IMHO it is best to try to use schemes which distribute the load/tasks as much as possible. francisco Moderator of the Corporate BSD list http://www.egroups.com/group/BSD_Corporate To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: Upcoming rc.conf changes not loading certain currently loaded daemons
On Thu, 24 Aug 2000 15:07:15 +0200, Neil Blakey-Milner wrote: >(and when I'm through with it, sendmail won't be listening on port 25 by >default either *evil.grin*) So where will it be listening? Any plans on moving this part of stable on the long term? francisco Moderator of the Corporate BSD list http://www.egroups.com/group/BSD_Corporate To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: Upcoming rc.conf changes not loading certain currently loaded daemons
On Thu, 24 Aug 2000 15:41:45 +0100, Nik Clayton wrote: >> I know this is currently in "current", but won't this eventually >> make it to stable? > >Maybe. I would have thought that's unlikely though. However, even if >it is, there'll be a HEADS UP posted to this mailing list, so you'll be >aware that it's an issue. Not all things make it to "HEADS UP" messages. I recall a few months back I found something which there had not been such message and the email I got was ... yes, but it is on the UPDATING document. It is a matter of experience to know to check UPDATING and I guess that I didn't have it at that point.. I am also sure many others new to tracking stable may not know of such file. Perpahs we could have a monthly "Staying stable file". Any opposition for such file? francisco Moderator of the Corporate BSD list http://www.egroups.com/group/BSD_Corporate To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: Upcoming rc.conf changes not loading certain currently loaded daemons
On Thu, 24 Aug 2000 10:13:52 +0100, Nik Clayton wrote: >> What was the reason for these daemons been set to not start? > >Now, if you have an empty /etc/rc.conf then (in theory) no network services >are running. This also means that if you want to find out what services are >started at boot time you only have to look in /etc/rc.conf, rather than >having to look at /etc/defaults/rc.conf as well. Then shouldn't we add the current programs which get started to /etc/rc.conf? >> Wouldn't this "break" working machines? > >Only if you (1) Are running -current, and (2) don't read the mailing lists >and the diffs mergemaster shows you. > >If both (1) and (2) are true then you shouldn't be running -current anyway. I know this is currently in "current", but won't this eventually make it to stable? francisco Moderator of the Corporate BSD list http://www.egroups.com/group/BSD_Corporate To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: Upcoming rc.conf changes not loading certain currently loaded daemons
On Thu, 24 Aug 2000 10:11:03 +0200 (SAST), fingers wrote: >Hi > >> What was the reason for these daemons been set to not start? >> Wouldn't this "break" working machines? > >I don't know what percentage of installers are doing the same, That is the problem. Most likely nobody knows the percentage of people that use them vs the percentage that turns them off. >but the first thing I do is disable them and kill 'em dead. Perhaps this could be an installation flag. francisco Moderator of the Corporate BSD list http://www.egroups.com/group/BSD_Corporate To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
How often to run mergemaster?
I recently started to track 4.X Stable. How often does one need to run mergemaster, or even better how does one even know that it needs to be run? To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Taking over Updating for Stable
Who do I need to talk to to take over the /etc/UPDATING file for stable I got a computer just to do daily MakeWorlds. What info would you all find usefull on this file? For the most part it should be fairly uneventfull. Would it be usefull to have info about some of the auxiliary files/daemons such as bind/sendmail? For instance I just had some issues with DNS because there was a chance some time back and I had not adjusted my DNS files. When I re-started after a make-world DNS was giving some errors in one box and stopped working on another. This is not directly related to FreeBSD, but it will bite those doing MakeWorld... I will be ready in a few days to do the daily builds. I am doing a little project I always wanted to do... compute sizes for some of the default distribution. So far did 3.3 Release FreeBSD Sizes Dist/ /usr Min 20 55 User21 90 Xuser 21 125 X-Kern Developer 21 170 No ports. Selecting SVGA, VGA and Mono as X servers. 75 and 100 dpi fonts. Next I am going to do 3.4 ... just out of curiosity.. don't expect it to be too different from 3.3 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: Does sendmail.cf gets replaced by stable?
On Sat, 26 Feb 2000 23:50:41 -0800, Doug Barton wrote: >Francisco Reyes wrote: >> >> Does the /etc/sendmail.cf gets replaced by stable? > > Not sure what you mean by "replaced by stable." It does not get >replaced in a make/build world. Apparently that is not the case. According to another email I got builds a sendmail.cf from /usr/src/etc/sendmail/freebsd.mc and installs it. There seems to be a parameter in /etc/rc.conf where one can indicate which ".mc" file to use at make world. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: Reading CVS messages.. how to tell if affects stable?
On Fri, 11 Feb 2000 10:55:38 -0700, Warner Losh wrote: >In message <[EMAIL PROTECTED]> "Francisco Reyes" writes: >: I don't see how one can tell if a change will require a user to >: do any kind of change for his/her Stable system to compile with >: the latest sources. Have I missed something? > >Look for the string RELENG_3 in the first little bit of the commit >message. that will tell you that something has changed on the -stable >branch. That worked. Seems like not many messages apply to the stable branch when compared to the number of messages in cvs-all. >Judging whether or not if this will impact your ability to rebuild >your system is much harder. In particular the messages in cvs-all are not very informative. I guess I could go to the web and see what the change was. >The UPDATING file will soon have new maintainers in -stable and when Who will this be? I just ordered a (old/cheap) computer so I could do daily Makeworlds on stable with the purpose of helping out with the UPDATING file. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
