Date: Mon, 30 Jan 2012 15:38:05 +0100 From: Ivan Voras <ivoras@freebsd.org> To: freebsd-stable@freebsd.org Subject: Re: FreeBSD 9 crash/deadlock when dump(8)ing file system with journaling enabled. Message-ID: <jg6a0d$6rj$2@dough.gmane.org> In-Reply-To: <20120130120643.GA46785@icarus.home.lan> References: <4F267B14.4060200@ateamsystems.com> <20120130120643.GA46785@icarus.home.lan>
next in thread | previous in thread | raw e-mail | index | archive | help
On 30/01/2012 13:06, Jeremy Chadwick wrote: >> For now I've turned off journaling (soft updates seem fine) and that >> works around the issue. >> >> Let me know if I can provide more details etc! > > I'm not sure, but this may be an after-effect of known problems right > now with SU+J on 9.0. It would help if you could state if you're using > "dump -L" or not. > > I've seen the "deadlock" behaviour you describe on older FreeBSD > versions (dating back to at least 7.x) when using "dump -L", which > generates a fs snapshot. Obviously 7.x does not have SU+J, so I'm a > little surprised disabling journalling fixes the problem for you. It's a known bug: SU+J currently deadlocks when used with UFS snapshots.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?jg6a0d$6rj$2>