On Nov 21, 2007 6:28 AM, David Leimbach <[EMAIL PROTECTED]> wrote: > > On Nov 20, 2007 4:21 PM, andrey mirtchovski <[EMAIL PROTECTED]> wrote: > > the best way to catch timesync-related issues is to use a stop watch > > to measure the duration of 'sleep 60'. seriously :) > > > > > > On Nov 20, 2007 5:08 PM, erik quanstrom <[EMAIL PROTECTED]> wrote: > > > > > > On Tue Nov 20 17:38:05 EST 2007, [EMAIL PROTECTED] wrote: > > > > I figured maybe something is going on with venti and an initial > > > > snapshot after an install, but it's been doing this now for > 6hours. > > > > > > > > I've got gnot showing about 15000 and higher interrupts per second... > > > > > > could be timesync misconfiguration. i did this to myself once by > > > starting several timesyncs. do you have any clues as to what the > > > machine is doing? > > Oh timesync isn't what I thought it was I guess.
Would timesync cause venti or something else disk I/O related to go completely fubar? It looks like my plan 9 box is now hosed again and will not boot. My hard disk activity LED was almost solid on during this interrupt storm that was going on almost all day yesterday. Not sure if timesync can cause that kind of behavior, and I've no idea why a fresh install with no post-configuration should behave that way. Dave
