5.2-RELEASE - Show stopper problem
Ted Wisniewski
ted at ness.plymouth.edu
Sun Jan 11 08:21:58 PST 2004
Dan,
Thanks for your response... As you can see in this output from the
ps command you suggested, the processes are dfinitely waiting on the disk.
BTW.. The syste in question was a fresh install from yesterday with no
users other than myself (I did the cvsup to get it to 5.2-RELEASE). It
did hang when I did that with a similar result. One of the "install -s etc.."
processes went into the same state.
Output from PS:
692 wait ?? Is 0:00.00 /bin/sh -c periodic daily
1694 wait ?? I 0:00.00 /bin/sh - /usr/sbin/periodic daily
1701 wait ?? I 0:00.02 /bin/sh - /usr/sbin/periodic daily
1702 wait ?? I 0:00.00 /bin/sh - /usr/sbin/periodic daily
1703 piperd ?? I 0:00.00 mail -s testhost.plymouth.edu daily run output
1779 wait ?? I 0:00.00 /bin/sh /etc/periodic/daily/450.status-securit
1780 wait ?? I 0:00.00 /bin/sh - /usr/sbin/periodic security
1786 wait ?? I 0:00.00 /bin/sh - /usr/sbin/periodic security
1787 wait ?? I 0:00.00 /bin/sh - /usr/sbin/periodic security
1788 piperd ?? I 0:00.00 mail -s testhost.plymouth.edu security run out
1789 wait ?? I 0:00.00 /bin/sh - /etc/periodic/security/100.chksetuid
1795 wait ?? I 0:00.00 /bin/sh - /etc/periodic/security/100.chksetuid
1796 piperd ?? I 0:00.00 xargs -0 -n 20 ls -liTd
1797 piperd ?? I 0:00.00 sed s/^ *//
1798 piperd ?? I 0:00.00 sort -k 11
1799 wait ?? I 0:00.00 /bin/sh - /etc/periodic/security/100.chksetuid
1802 piperd ?? I 0:00.00 cat
1805 ufs ?? D 0:02.10 find /usr -xdev -type f ( -perm -u+x -or -perm
2779 sbwait ?? Is 0:00.02 sshd: sysop [priv] (sshd)
2782 select ?? S 0:00.01 sshd: sysop at ttyp0 (sshd)
737 getblk p0- D 0:02.14 find /usr -xdev -type f ( -perm -u+x -or -perm
2783 pause p0 Ss 0:00.01 -csh (csh)
2786 - p0 R+ 0:00.00 ps -axO wchan
These have been running for about 9 hours now, on a base system with nothing
extra installed. Originally, I thought it had something to do with the
raid controllers on the various machines I tried, however, I was able to
duplicate the condition on an ATA based system (I had to work a lot harder at
getting the condition to occur on it). It is almost like the I/O is too
fast and something happens..
On my test system the machine will run for days with this happening, however,
I have another system that is actually doing a lot of I/O.... eventually
it crashes (well locks up completely)... If there is any particular info you
might need, I am willing to do what I can.
Ted
(* In the last episode (Jan 10), Ted Wisniewski said:
(* > In 5.2-RC and 5.2-RELEASE there appears to be some issue with
(* > filesystem or I/O subsystem under 5.2-X. Now, You can install and do
(* > the normal kind of things, however, when you create a lot of I/O on
(* > the disk there seems to be a problem actually reading/writing it
(* > to/from disk. For example, If I do a "make buildworld"... It
(* > appears to go along ok. However, I have had a number of (repeatable)
(* > situations where the "make installworld" will go so far then will not
(* > be able to complete. In this case, there is an attempt to write data
(* > to disk that cannot complete; the process goes into a disk wait state
(* > (it cannot be killed, and will stay in this state ... forever).
(* >
(* > For example the standard daily security script:
(* >
(* > 727 p0 T 0:00.00 sh 100.chksetuid
(* > 737 p0 T 0:02.14 find /usr -xdev -type f ( -perm -u+x -or -perm -g+x -or -perm -o+x ) ( -perm -u+s -or -perm -g+s
(*
(* The 'T' state usually means that someone sent the process a STOP
(* signal. Try running "kill -CONT 727 737" to start them back up.
(*
(* Processes waiting on disk I/O will be in the 'D' state, and you can run
(* "ps axO wchan" to print the specific part of the kernel it's waiting
(* in.
(*
(* --
(* Dan Nelson
(* dnelson at allantgroup.com
(*
--
| Ted Wisniewski E-Mail: ted at mail.plymouth.edu |
| Manager, Systems Group WEB: http://oz.plymouth.edu/~ted/ |
| Information Technology Services |
| Plymouth State University Phone: (603) 535-2661 |
| Plymouth NH, 03264 Fax: (603) 535-2263 |
More information about the freebsd-questions
mailing list