fstab nullfs entries lost on new Jail creation

[CaptSammy]

I hope someone out there can help, my system fell apart creating a new Jail in TheBrig.

I created my first jail, and configured the fstab entries in TheBrig's UI. All went great and ran for the last month or two. I decided to create a second and set the exact same entries into that fstab section, but with read-only. It would not connect. So while troubleshooting a went into my first and those are no longer mounting. I am a noob, and not sure how to start one of these Brig Jails from command line, nor do I know where to look for logs.

I have since shut down the second but the first still does not mount proper.

My new entry is (the original had rw rather than ro):
/mnt/Tank/Media/NewArrivals /mnt/Tank/Jail/Mule/Media/NewArrivals nullfs ro 0 0
/mnt/Tank/Media/SickBeard /mnt/Tank/Jail/Mule/Media/SickBeard nullfs ro 0 0

Whats odd is that the nulfs I did not attempt to mount in the new jail still works.

Can two jails mount the same host directory at the same time? I cant even find the fstab it augments.

TheBrig is a cool thing, but in using it I left myself without learning the tools to troubleshoot.

Thanks!

[CaptSammy]

To be clear, I still have the following in the original jail:

/mnt/SSDstriped/WorkBench /mnt/Tank/Jail/Mule/SabNZBD/Temp nullfs rw 0 0
/mnt/Tank/Media/NewArrivals /mnt/Tank/Jail/Mule/Media/NewArrivals nullfs rw 0 0
/mnt/Tank/Media/SickBeard /mnt/Tank/Jail/Mule/Media/SickBeard nullfs rw 0 0
/mnt/Tank/Media/Books /mnt/Tank/Jail/Mule/Media/Books nullfs rw 0 0

But I see nothing listed in the jail within the /Media/Sickbeard directory. I can see everything fine in the host machine at /mnt/Tank/Media/SickBeard. This worked prior to my attempt to create a second Jail. The Books and Temp locations are still functional.

[CaptSammy]

OK, I found the user error in the new jail, I did the copy paste thing and forgot to change the path to the new jail.

The old jail is still not working, and it has the original settings that it has used for a couple months. Digging deeper.

[CaptSammy]

OK, found the root of the problem. When I miss set the new jail and had it set to read only it changed the originals filesystems to read only, now it cant attach. I tried to remove and recreate, or even chmod those mount points and it will not let me as the filesystem is read only. How do I get around that? Even as root in the host system I can not remove/recreate/chmod those mount points. I get a "read only filesystem" error.

[CaptSammy]

I am feeling schitzo talking to myself but worked thru it.

I realized that I can type "mount" and get a list of mounted systems. I noticed the parent directory was mounted as read only. I then remembered I attempted just attaching the parent and it didnt work so I removed that entry from TheBrig. It didnt umount it though so it still had hold of it.

I ran a umount of the parent (umount /mnt/Tank/Jail/Mule/Media) and bounced that Jail and all is now good to go.

I also found where the fstab's were located, /etc/fstab.<jailname> of the host.

Hope my user errors and walking thru the fix helps another.