Date: Mon, 10 Sep 2007 12:28:25 +0100 From: Thomas Sparrevohn <Thomas.Sparrevohn@btinternet.com> To: freebsd-current@freebsd.org Subject: Re: dump problems Message-ID: <200709101228.25867.Thomas.Sparrevohn@btinternet.com> In-Reply-To: <E1IUcXc-000NdZ-LH@cs1.cs.huji.ac.il> References: <E1ISdQi-000GkC-4v@cs1.cs.huji.ac.il> <046801c7f229$a4534510$ecf9cf30$@co.uk> <E1IUcXc-000NdZ-LH@cs1.cs.huji.ac.il>
next in thread | previous in thread | raw e-mail | index | archive | help
On Monday 10 September 2007 07:14:36 Danny Braniss wrote: > > > > > > the only indication I can see, is that one of the dump procs. is > > > waiting on > > > sbwait, and probably it's some deadlock, which is similar to what I > > > keep > > > seeing here, i'll try now with SCHED_ULE to see if it make a > > > difference. > > > > > > I'm running SCHED_ULE on these already, if your not I guess it's not the > > scheduler? > > > I can get it to 'work' by fiddling with the b flag (blocksize), which still > points to some timming/deadlock problem. > ie: > dump 0abf 64 /some/backup/file /file/to/backup > now works, but > dump 0abf 64 - | restore rbf 64 - > hangs as before. (i don't think the b 64 in restore is needed). I have been able to reproduce the deadlock with any configuration - just using the dump part - never found out what caused it.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200709101228.25867.Thomas.Sparrevohn>