rkoberman at gmail.com
Wed Jun 21 23:20:28 UTC 2017
On Wed, Jun 21, 2017 at 2:10 PM, Efraín Déctor <efraindector at motumweb.com>
> 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:
>> 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,
>> On 21. Jun 2017, at 21:56, Steven Hartland <killing at multiplay.co.uk<mailt
>> o:killing at 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:
>> 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 at amd64-builder.daemonology.net<mailto:root at amd64-
>> builder.daemonology.net>:/usr/obj/usr/src/sys/GENERIC amd64
>> Holger Kipp
>> Senior Consultant [When logistics needs SAP competence] <
>> 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 at 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!]<
This is probably not the issue, but I have had consistent issues using scp
and sftp to copy files to FUSE based file systems (or, possibly, just
NTFS). I have not had any issues with copies to/from UFS2 systems. I'm
guessing that your local file system is UFS2 or it would have been
mentioned. I should also mention that FUSE has had at least two versions
released since I had the problems. It's not something I do often and far
less often since I moved one of the file systems, the one I most commonly
used, to UFS2.
Kevin Oberman, Part time kid herder and retired Network Engineer
E-mail: rkoberman at gmail.com
PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683
More information about the freebsd-stable