Date: Mon, 10 Sep 2007 09:14:36 +0300 From: Danny Braniss <danny@cs.huji.ac.il> To: "Lawrence Farr" <bsd-current@epcdirect.co.uk> Cc: freebsd-current@FreeBSD.org, 'cpghost' <cpghost@cordula.ws>, 'Gavin Atkinson' <gavin@FreeBSD.org> Subject: Re: dump problems Message-ID: <E1IUcXc-000NdZ-LH@cs1.cs.huji.ac.il> In-Reply-To: <046801c7f229$a4534510$ecf9cf30$@co.uk> References: <E1ISdQi-000GkC-4v@cs1.cs.huji.ac.il> <20070904233246.GA2409@epia-2.farid-hajji.net> <E1ISnig-000Nbm-Ep@cs1.cs.huji.ac.il> <043a01c7f202$a7ad0920$f7071b60$@co.uk> <E1IU10R-000MRT-T8@cs1.cs.huji.ac.il> <046801c7f229$a4534510$ecf9cf30$@co.uk>
next in thread | previous in thread | raw e-mail | index | archive | help
> > > > 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). danny
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?E1IUcXc-000NdZ-LH>