FreeBSD 9 crash/deadlock when dump(8)ing file system with
max at mxcrypt.com
Fri Feb 3 16:57:58 UTC 2012
On Mon, Jan 30, 2012 at 9:38 AM, Ivan Voras <ivoras at 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. 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.
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
More information about the freebsd-stable