Date: Fri, 27 Jan 2012 09:39:34 +0100 From: Yamagi Burmeister <lists@yamagi.org> To: freebsd@jdc.parodius.com Cc: antonio.trindade@gmail.com, freebsd-fs@freebsd.org, dougb@FreeBSD.org, freebsd-stable@freebsd.org Subject: Re: kernel: panic: softdep_sync_buf: Unknown type jnewblk Message-ID: <20120127093934.ae7ca125.lists@yamagi.org> In-Reply-To: <20120127015430.GA66235@icarus.home.lan> References: <315A1E95-9064-494F-A3B8-48F1C4951624@gmail.com> <4F21FE96.7070805@FreeBSD.org> <20120127015430.GA66235@icarus.home.lan>
next in thread | previous in thread | raw e-mail | index | archive | help
--Signature=_Fri__27_Jan_2012_09_39_34_+0100_HXMDEpTt9rOFnD29 Content-Type: text/plain; charset=US-ASCII Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Hi :) On Thu, 26 Jan 2012 17:54:30 -0800 Jeremy Chadwick <freebsd@jdc.parodius.com> wrote: > I'll also point out, though the OP isn't using snapshots, that it's > confirmed use of snapshots on SU+J can result in a full filesystem hang. > Confirmation is from Kirk McKusick (author of SU and designer of SU+J): >=20 > http://lists.freebsd.org/pipermail/freebsd-fs/2012-January/013429.html >=20 > Something really needs to be done about this combination of problems. >=20 > Since SU+J is the default choice for all UFS filesystems on 9.0-RELEASE, > the only solution I can think of is to send a massive announcement to > relevant mailing lists, AND put something on the freebsd.org home page > about these issues. The problem was analyzed but no immediate solution found. Therefor snapshots on filesystems with SU+J (but not SU alone) were disabled by Kirk McKusick in SVN r230250. The MFC to 9-STABLE has still to be done. Maybe this fix is a candidate for an errata notice / patch, distributed by freebsd-update? > For the snapshot issue, I believe not using SU+J (and only SU) works > around the problem, so possibly that would be the best choice of > recommendation at this time. Yes, snapshots with SU alone are working. > I urge key members of the community and (as always) kernel developers to > chime in here with advice. Something needs to be done, users need to be > made aware of these problems, and so on. Due to lack of time and not being the author of the rather complex code Kirk McKusick was not able to fix the problem. We're now waiting for Jeff Roberson to step up, but I was told that he is very busy and has no time too. > --=20 > | Jeremy Chadwick jdc@parodius.com | > | Parodius Networking http://www.parodius.com/ | > | UNIX Systems Administrator Mountain View, CA, US | > | Making life hard for others since 1977. PGP 4BD6C0CB | >=20 > _______________________________________________ > freebsd-fs@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-fs > To unsubscribe, send any mail to "freebsd-fs-unsubscribe@freebsd.org" >=20 --=20 Homepage: www.yamagi.org XMPP: yamagi@yamagi.org GnuPG/GPG: 0xEFBCCBCB --Signature=_Fri__27_Jan_2012_09_39_34_+0100_HXMDEpTt9rOFnD29 Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.18 (FreeBSD) iEYEARECAAYFAk8iYtAACgkQWTjlg++8y8vsuQCgwHdjqZupfrQa9/MvR65JIyQQ r44An2u0CaN9Oh1Q2b7hf2RIjXn88+aa =qxCQ -----END PGP SIGNATURE----- --Signature=_Fri__27_Jan_2012_09_39_34_+0100_HXMDEpTt9rOFnD29--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20120127093934.ae7ca125.lists>