Date: Fri, 3 Feb 2012 11:29:01 -0500 From: Maxim Khitrov <max@mxcrypt.com> To: Ivan Voras <ivoras@freebsd.org> Cc: freebsd-stable@freebsd.org Subject: Re: FreeBSD 9 crash/deadlock when dump(8)ing file system with journaling enabled. Message-ID: <CAJcQMWdcTNoinhcxcURjZseAd19CvmgGcOr1P9ngB%2B%2BYA5PTuw@mail.gmail.com> In-Reply-To: <jg6a0d$6rj$2@dough.gmane.org> References: <4F267B14.4060200@ateamsystems.com> <20120130120643.GA46785@icarus.home.lan> <jg6a0d$6rj$2@dough.gmane.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, Jan 30, 2012 at 9:38 AM, Ivan Voras <ivoras@freebsd.org> wrote: > 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. =C2=A0It would help if you could state if you're u= sing >> "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. =C2=A0Obviously 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. Is there any additional information somewhere on when this is expected to be fixed? Seems like a fairly significant problem to me, especially since SU+J is the default when creating new file systems with bsdinstall. - Max
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAJcQMWdcTNoinhcxcURjZseAd19CvmgGcOr1P9ngB%2B%2BYA5PTuw>