Date: Wed, 21 Jun 2017 16:10:37 -0500 From: =?UTF-8?B?RWZyYcOtbiBEw6ljdG9y?= <efraindector@motumweb.com> To: Holger Kipp <Holger.Kipp@alogis.com>, "freebsd-stable@freebsd.org" <freebsd-stable@freebsd.org> Cc: Steven Hartland <killing@multiplay.co.uk> Subject: Re: Kernel panic Message-ID: <3e2a7790-ff1d-ca7d-6652-a2597b05bd31@motumweb.com> In-Reply-To: <4C65608D-DDB4-4522-8CD8-84448993B608@alogis.com> References: <d86d21c6-f292-7cdd-78b2-e192f9772887@motumweb.com> <26bb2efd-cef6-d454-d2d6-ad869229ef19@multiplay.co.uk> <4C65608D-DDB4-4522-8CD8-84448993B608@alogis.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Hello. I found that link too, however gjournal is disabled on all of my filesystems, apart from that I only have trim enabled on one of my filesystem but when the error happened I was writing on another filesystem. Maybe WinSCP did something that FreeBSD didnt like, I am really clueless about this error. If it happens again I am going to update this system like you guys have been suggesting. Thank you very much for your help. El 21/06/2017 a las 03:18 p. m., Holger Kipp escribió: > I only found the following reference: > > https://forums.freebsd.org/threads/37824/ > > which contains some additional links and references, especially regarding journaling and softupdates, for your error message. > > Maybe this is helpful in your case? > > Apart from that - checking if the error is still there on a supported more current version like 10.3 or 11 might indeed be the better option. > > Best regards, > Holger > > On 21. Jun 2017, at 21:56, Steven Hartland <killing@multiplay.co.uk<mailto:killing@multiplay.co.uk>> wrote: > > Given how old 9.1 is, even if you did investigate its unlikely it would get fixed. > > I'd recommend updating to 11.0-RELEASE and see if the panic still happens. > > On 21/06/2017 17:35, Efraín Déctor wrote: > Hello. > > Today one of my servers crashed with a kernel panic. I got this message: > > panic: cancel_mkdir_dotdot: Lost inodedep > > I was just moving some files using WinSCP and then the server crashed. > > How can I trace the root of the problem?. I check and the raid seems to be ok: > > mfi0 Volumes: > Id Size Level Stripe State Cache Name > mfid0 ( 278G) RAID-1 64k OPTIMAL Disabled <OS_RAID1> > mfid1 ( 1905G) RAID-1 64k OPTIMAL Disabled <usr_R10> > > Thanks in advance. > > uname -a > FreeBSD server 9.1-RELEASE-p22 FreeBSD 9.1-RELEASE-p22 #0: Mon Nov 3 18:22:10 UTC 2014 root@amd64-builder.daemonology.net<mailto:root@amd64-builder.daemonology.net>:/usr/obj/usr/src/sys/GENERIC amd64 > > ___________________________ > > > > Diplom-Mathematiker > Holger Kipp > Senior Consultant [When logistics needs SAP competence] <https://www.alogis.com/> > > Fon: +49 30 436 58 114 > Fax: +49 30 436 58 214 > Mobil:?+49 178 36 58 114 > alogis AG > Alt-Moabit 90 B > 10559 Berlin > > > holger.kipp@alogis.com www.alogis.com<http://www.alogis.com/> > > alogis AG > Sitz/Registergericht: Berlin/AG Charlottenburg, HRB 71484 > Vorstand: Arne Friedrichs, Joern Samuelson > Aufsichtsratsvorsitzender: Dr. Christian Volkmann > > [Besuchen Sie uns auf dem SAP EAM 2017 vom 27. - 28. Juni, Potsdam!]<https://www.alogis.com> > > > _______________________________________________ > freebsd-stable@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org"
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3e2a7790-ff1d-ca7d-6652-a2597b05bd31>