Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 30 Apr 2012 17:57:07 +0000 (UTC)
From:      jb <jb.1234abcd@gmail.com>
To:        freebsd-questions@freebsd.org
Subject:   Re: UFS Crash and directories now missing
Message-ID:  <loom.20120430T194831-917@post.gmane.org>
References:  <201204301136.q3UBa8fj083478@mail.r-bonomi.com> <CAHieY7RyFZsDpwsaADrbgKes=i0GhCHmTNeprY-qn6SmAmANwg@mail.gmail.com> <4F9EC5E9.6060604@gmail.com> <CAHieY7QYmQKaXyCYfG2Jnc3eTu59BDAnSGgjwbiEv9ReUQWtQg@mail.gmail.com>

next in thread | previous in thread | raw e-mail | index | archive | help
Alejandro Imass <ait <at> p2ee.org> writes:

>... 
> If you have really followed the thread, all I have done is try to find
> some explanation for a strange behavior of the system under normal
> use. It hung, and some directories were moved, period. I have posted
> some ideas to share with other people expecting some insight and maybe
> similar experience from other users, which there probably are many,
> but many times afraid to speak up and avoid getting insulted.
> ...

Well, I try to help only, so I hope I do not get insulted ... I could become
vicious :-) 

Here it is.

You said you have your jail env on a separate disk.

I looked at problem reports for nullfs and there are quite few.
Hierarchical Jails
NOTES

You said you have your jail env on a separate disk.

I looked at problem reports for nullfs and there are quite few.
http://www.freebsd.org/cgi/query-pr-summary.cgi?category=&severity=&priority=&cl
ass=&state=&sort=none&text=nullfs&responsible=&multitext=&originator=&release=

As a matter of fact I just mounted a nullfs but was not able to unmount it
(device busy) - a Google search shows it as a problem reported for many many
years.
Nullfs does not seem to be stable.

Anyway, I found one PR
http://www.freebsd.org/cgi/query-pr.cgi?pr=kern/147420

that is about troubles with jails, nullfs, UFS, and NFS.
Synopsis:       [ufs] [panic] ufs_dirbad, nullfs, jail panic (corrupt inode)

Take a look at this paragraphs:
"...
After two more failures, I now found the offending inode ..."
"...
As one point, I found the inode in a directory which usually is mounted for
an (ez-) jail via nullfs."

This proves that problems with jails, nullfs, and fs corruption are possible.
So, they can not be excluded up front in your case too because nullfs is just
a simple "path translation".

jb





Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?loom.20120430T194831-917>