Date: Tue, 4 Sep 2007 19:34:28 -0700 From: "Kip Macy" <kip.macy@gmail.com> To: "Kenneth Vestergaard Schmidt" <kvs@pil.dk> Cc: freebsd-current@freebsd.org Subject: Re: Unkillable and runaway processes Message-ID: <b1fa29170709041934p2362df45ga5110ca1905e646d@mail.gmail.com> In-Reply-To: <m1lkbmtw6z.fsf@binarysolutions.dk> References: <m1lkbmtw6z.fsf@binarysolutions.dk>
next in thread | previous in thread | raw e-mail | index | archive | help
- re-compile the kernel with DDB - drop into DDB when the problem occurs ddb> ps ddb> show proc <rsync pid> ddb> thread <threadno of rsync pid (in output of show proc)> ddb> bt Send the backtrace to pjd. -Kip On 9/4/07, Kenneth Vestergaard Schmidt <kvs@pil.dk> wrote: > Hello. > > Our ZFS testbed is experiencing some weird problems with rsync. We run a > nightly backup of about 1.6 TB data (that's how much is stored, not how > much is transferred), but after the initial sync I haven't been able to > get the machine through one full cycle. > > After many hours of rsyncing data from 50+ machines, suddenly one > rsync-process will hang, spinning on the CPU. > > It switches state between CPU0, CPU1, RUN and 'zfs:(&', but doesn't > really do anything. It can't be killed, and you can't reboot the machine > - it'll get past syncing disks, but won't shutdown or reboot. > > I can't do an 'ls' in the directory that rsync is running on - it'll > just hang, too. > > The machine is running current from August 29th. > > I could use some pointers on what to do - is there some way I can debug > this better, maybe give some better info? > > -- > Kenneth Schmidt > pil.dk > > _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?b1fa29170709041934p2362df45ga5110ca1905e646d>