Date: Fri, 06 Apr 2012 10:21:29 -0700 From: Kirk McKusick <mckusick@mckusick.com> To: "Desai, Kashyap" <Kashyap.Desai@lsi.com> Cc: "freebsd-fs@freebsd.org" <freebsd-fs@freebsd.org>, "Kenneth D.Merry" <ken@freebsd.org>, Pawel Jakub Dawidek <pjd@freebsd.org>, "McConnell, Stephen" <Stephen.McConnell@lsi.com> Subject: Re: Kernel crash at "softdep_deallocate_dependencies" Message-ID: <201204061721.q36HLTj6030692@chez.mckusick.com> In-Reply-To: <20120406130006.GC1336@garage.freebsd.pl>
next in thread | previous in thread | raw e-mail | index | archive | help
Following through on Pawel Jakub Dawidek's comments, there is no way that the filesystem can recover when a large piece of its has disappeared. The panic that you are getting is because the soft updates system realizes that allowing writes to continue on the filesystem will cause it to be corrupted in an unrepairable way. As it has no way to cleanly downgrade it to read-only or unmount it, its only choice is to panic. If you do not like this panic, you can disable soft updates using: tunefs -n disable <filesystem> Absent the soft updates integrity checking, the filesystem will carry on a good bit longer (though after a reboot it will likely be unrecoverable even if you have put the disk back into it). Kirk McKusick
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?201204061721.q36HLTj6030692>