Re: Kernel panic

[Kevin Oberman]

On Wed, Jun 21, 2017 at 2:10 PM, Efraín Déctor 
wrote:

> 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  o:kill...@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 SizeLevel   Stripe  State   Cache   Name
>> mfid0 (  278G) RAID-1  64k OPTIMAL Disabled 
>> mfid1 ( 1905G) RAID-1  64k OPTIMAL Disabled 
>>
>> 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 r...@amd64-builder.daemonology.net> 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.k...@alogis.com  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>
>
>
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: rkober...@gmail.com
PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: Kernel panic

[Efraín Déctor]

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 
> 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 SizeLevel   Stripe  State   Cache   Name
mfid0 (  278G) RAID-1  64k OPTIMAL Disabled 
mfid1 ( 1905G) RAID-1  64k OPTIMAL Disabled 

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 
r...@amd64-builder.daemonology.net:/usr/obj/usr/src/sys/GENERIC
 amd64

___



Diplom-Mathematiker
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.k...@alogis.com  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!]


___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"


___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: Kernel panic

[Holger Kipp]

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 
> 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 SizeLevel   Stripe  State   Cache   Name
mfid0 (  278G) RAID-1  64k OPTIMAL Disabled 
mfid1 ( 1905G) RAID-1  64k OPTIMAL Disabled 

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 
r...@amd64-builder.daemonology.net:/usr/obj/usr/src/sys/GENERIC
 amd64

___



Diplom-Mathematiker
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.k...@alogis.com  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!]


___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: Kernel panic

[Steven Hartland]

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 SizeLevel   Stripe  State   Cache   Name
 mfid0 (  278G) RAID-1  64k OPTIMAL Disabled 
 mfid1 ( 1905G) RAID-1  64k OPTIMAL Disabled 

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 
r...@amd64-builder.daemonology.net:/usr/obj/usr/src/sys/GENERIC amd64


___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"


___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

11.1: HP DL360G5 Hang at CD during boot

[Larry Rosenman]

I just filed https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=220193 since 
I've now
seen this twice since we moved to 11.1-BETA.

Please let me know what else I can provide, bearing in mind that I'm remote 
from the box. 


-- 
Larry Rosenman http://people.FreeBSD.org/~ler
Phone: +1 214-642-9640 E-Mail: l...@freebsd.org
US Mail: 17716 Limpia Crk, Round Rock, TX 78664-7281
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Kernel panic

[Efraín Déctor]

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 SizeLevel   Stripe  State   Cache   Name
 mfid0 (  278G) RAID-1  64k OPTIMAL Disabled 
 mfid1 ( 1905G) RAID-1  64k OPTIMAL Disabled 

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 
r...@amd64-builder.daemonology.net:/usr/obj/usr/src/sys/GENERIC amd64


___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

vnode_pager_generic_getpages_done: I/O read error 5 caused by r318394 (was Re: FreeBSD 11.1-BETA1 Now Available)

[Guido Falsi]

On 06/13/17 13:44, Peter Blok wrote:
> Hi,
> 
> For a while now, I’m not able to build a RPI1-B image from -stable. I have 
> narrowed it dow to fix 318394, which adds a refresh option to geom_label. If 
> I undo this fix in today’s stable it works ok. If I don’t I’m getting 
> continuously:
> 
> vm_fault: pager read error, pid 1 (init)
> vnode_pager_generic_getpages_done: I/O read error 5
> 
> I have looked at the fix and I can’t figure out why it breaks the code.
> 
> And yes I have tried various other SD cards - they all have the same issue.
> 

Hi,

I'm seeing similar symptoms with NanoBSD images on PCEngines ALIX and
APU2 boards, using compactflash and SD card storage respectively. The
problem has appeared as soon as I started testing 11.1-BETA1 from the
stable branch.

Problem appears when I update the image, using a slightly modified
version of the standard nanobsd update and updatep[12] scripts. My
changes are not in the dd/gpart commands though, which are the same.
gpart seems the most likely candidate though.

I have just discovered this thread and I will test reverting r318394
soon. Thanks to Peter for narrowing it down!

Maybe this is related to having the disks mounted read-only?

Should I open a bug report to properly track this down?

P.S.  CCing freebsd-fs@

-- 
Guido Falsi 
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"