Sounds like the symptoms recently experienced by some Linux servers caused by the 61st (leap) second: http://www.wired.com/wiredenterprise/2012/07/leap-second-bug-wreaks-havoc-with-java-linux/- if so, it will require a reboot.
On Sun, Jul 8, 2012 at 4:37 PM, <[email protected]> wrote: > I have QNAP NAS running disk for security cameras, it was setup as snb > access, it has been in service for over a year, no issues > > just had a look, it seems since about 2 weeks ago, it's running 100% cpu > > I've tried to 'kill 20450' but it's not killing it, > what else can I do short of rebooting it ? > > top: > Mem: 697324K used, 324376K free, 0K shrd, 24504K buff, 470756K cached > Load average: 1.06, 1.12, 1.13 (State: S=sleeping R=running, W=waiting) > > PID USER STATUS RSS PPID %CPU %MEM COMMAND > 20450 mxcam R 772 1 99.9 0.0 smbd > 2295 admin R 992 23424 0.5 0.0 top > ... > > [/usr/local/samba/sbin] # ps ax | grep smbd > 2605 admin 484 S grep smbd > 20450 mxcam 772 R /usr/local/samba/sbin/smbd -l /var/log -D -s > /etc/config/smb.conf > > Linux NAS01 2.6.33.2 #1 SMP Sat Nov 26 04:34:14 CST 2011 i686 unknown > > > -- > SLUG - Sydney Linux User's Group Mailing List - http://slug.org.au/ > Subscription info and FAQs: http://slug.org.au/faq/mailinglists.html > -- SLUG - Sydney Linux User's Group Mailing List - http://slug.org.au/ Subscription info and FAQs: http://slug.org.au/faq/mailinglists.html
