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
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
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
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:
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
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
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:
>
>