Mount command shows wrong information for nullfs mounts

2019-05-18 Thread Marko Turk
Hi,

I have the following nullfs mount:
/data/downloads on /usr/jails/dlna/mnt/data (nullfs, local, read-only)

For some reason, the mount command output shows this:
zroot/virtuals/bhyve/fbsd3@change-volmode/data/downloads on 
/usr/jails/dlna/mnt/data (nullfs, local, read-only)

This happened for all nullfs mounts, not just this one.

It appeared yesterday, after 40 days of uptime. Before that the mount
was shown properly.

This extra prefix is probably from the zfs volume that I'd created just
before the issue started appearing:
zroot/virtuals/bhyve/fbsd3

The zfs volume is not related to /data/downloads mountpoint.

I haven't rebooted the system since, does anyone know how to debug this?

I'm running:
FreeBSD shkatula 11.2-STABLE FreeBSD 11.2-STABLE #7 r343828: Wed Feb  6 
10:47:56 CET 2019 root@shkatula:/usr/obj/usr/src/sys/SHKATULA  amd64

BR/Marko


signature.asc
Description: PGP signature


11-STABLE system unbootable after update

2019-05-18 Thread Scott Bennett
 I have been running 11.2-STABLE for a while at r345498.  Last weekend it 
crashed,
so I took the opportunity to install the most recent build I had lying around, 
r347182.
I created a new boot environment and installed the r347182 kernel into it, shut 
the
system down, and rebooted.  The new kernel came up and appeared to be working 
okay, so
I continued with the mergemaster -p -F, make installworld, and mergemaster -F, 
then
shut it down again, and rebooted.  It asked for the GELI key for the boot pool, 
which
I then entered.  The spinning slash cursor appeared and may have changed for 
one frame
or so, and then I got a message beginning with "BTX" and followed by several 
lines of
hexadecimal, and then it stopped.  I tried it again just to be sure, and the 
result was
exactly the same.
 Does anyone know whether the PMBR boot block or the loader in the 
freebsd-boot
partition changed between r345498 and r347182?  I found no warning in 
/usr/src/UPDATING
about installworld potentially leaving a wasted system, so I don't have a clear 
idea
of what went wrong, much less whether I missed some instruction somewhere about 
source
updates.  If anyone can lend me a clue here, I would greatlyappreciate it.  I 
only had
one working machine, and now it is only working in a "rescue" mode by booting 
from a
DVD.  (Probably needless to say, but I will burn new DVDs with up-to-date stuff 
as soon
as my system is working the way it is supposed to again.)
 This motherboard is nearly 11 years old and does not boot from USB (in 
spite of
the BIOS menus say), so at the moment I am logged into SDF by running a long 
out-of-date
TrueOS installer DVD, which happens to be a pain to get to boot all the way, 
but I've
figured how to make it do it rather than get stuck with a logo on the screen 
that never
goes away.  Unfortunately, it includes no software to burn a CD or DVD, so I 
cannot
make a new bootable disk for the time being.  I will check email much later 
today or
this evening.
 Thanks in advance for any helpful ideas!


  Scott Bennett, Comm. ASMELG, CFIAG
**
* Internet:   bennett at sdf.org   *xor*   bennett at freeshell.org  *
**
* "A well regulated and disciplined militia, is at all times a good  *
* objection to the introduction of that bane of all free governments *
* -- a standing army."   *
*-- Gov. John Hancock, New York Journal, 28 January 1790 *
**
___
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"


nextcloud and collabora on freebsd-12-stable host

2019-05-18 Thread tech-lists

hi,

Does anyone run nextcloud with collabora on freebsd? If so, please tell
how you did it? Reading up on it, instructions are all in linux and use
of docker which I'm not keen on as my nextcloud is already a bhyve
instance.

thanks,
--
J.


signature.asc
Description: PGP signature