jail.conf ignoring exec.fib?
I'm running 9.2-RC2 amd64 on a system, with a number of jails. The jails
are setup using '/etc/jail.conf' - but the exec.fib in jail.conf seems to
be being ignored?
e.g. in /etc/jail.conf I have:
testjail {
jid = 100;
exec.fib = 1; Set FIB 1
path = /usr2/jails/testjail;
host.hostname = testjail.somedomain.com;
ip4.addr = 192.168.0.40;
mount.devfs;
}
But if I run up that jail and connect to it, 'netstat -r -n' shows it's
still using fib 0 (i.e. the default gateway is set).
If before running the jail, I do 'setfib 1 route add default 192.186.0.90'
- when the jail is run up, again - netstat within it still shows the
systems default gateway, not the gateway from fib 1?
-Karl
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: sysvipc only for one jail
On 12.08.2013 19:46, Trond Endrestøl wrote:
On Mon, 12 Aug 2013 14:09+0200, Trond Endrestøl wrote:
On Mon, 12 Aug 2013 13:57+0200, David Demelier wrote:
2013/8/12 Trond Endrestøl trond.endres...@fagskolen.gjovik.no:
On Mon, 12 Aug 2013 12:40+0200, David Demelier wrote:
2013/8/11 Maciej Suszko mac...@suszko.eu:
Maciej Suszko mac...@suszko.eu wrote:
[...]
You can specify different params for each jail using _parameters, for
example:
jail_jailname_params=allow.chflags=1 allow.sysvipc=1
Sorry, my mistake - it should be jail_jailname_parameters= of course.
--
regards, Maciej Suszko.
Thanks for your message,
However, I could not find this setting in the manual of rc.conf(5)
neither in /etc/rc.d/jail :(. It does not seems to be applied.
Have a look at jail(8) and the last lines of /etc/default/rc.conf.
I see,
I've added what Maciej Suszko told me but the sysctls in the jail is
not set as it should be :
security.jail.param.allow.sysvipc: 0
security.jail.param.allow.chflags: 0
And thus, it's not enabled as postgresql tells:
creating template1 database in /usr/local/pgsql/data/base/1 ... FATAL:
could not create shared memory segment: Function not implemented
I'll look into this by creating a new jail for PostgreSQL 9.2 when I
get home.
My host is running 9.2-PRERELEASE, r254150, in VirtualBox 4.2.16.
The jails are running world, also at r254150.
I added the following to the host's /etc/rc.conf:
jail_enable=YES
jail_list=postgresql
jail_postgresql_rootdir=/jails/postgresql
jail_postgresql_hostname=postgresql.bsd.net
jail_postgresql_interface=vtnet0
jail_postgresql_fib=0
jail_postgresql_ip=10.0.2.103,2001:db8::103
jail_postgresql_exec_start=/bin/sh /etc/rc
jail_postgresql_exec_stop=/bin/sh /etc/rc.shutdown
jail_postgresql_devfs_enable=YES
jail_postgresql_parameters=enforce_statfs=1 allow.chflags=1 allow.sysvipc=1
allow.mount=1 allow.mount.zfs=1
I added the following to the host's /etc/jail.conf:
postgresql {
path = /jails/postgresql;
enforce_statfs = 1;
allow.chflags;
allow.sysvipc;
allow.mount;
allow.mount.zfs;
mount.devfs;
host.hostname = postgresql.bsd.net;
ip4.addr = 10.0.2.103;
ip6.addr = 2001:db8::103;
interface = vtnet0;
exec.start = /bin/sh /etc/rc;
exec.stop = /bin/sh /etc/rc.shutdown;
}
PostgreSQL 9.2.4 had no problems running initdb nor running postgres
inside the jail:
root@freebsd-jails:/ # jexec 4 csh
root@postgresql:/ # /usr/local/etc/rc.d/postgresql status
pg_ctl: server is running (PID: 46623)
/usr/local/bin/postgres -D /usr/local/pgsql/data
root@postgresql:/ #
If you start the jail manually using jail(8), then /etc/jail.conf
comes into play, whereas the lines in /etc/rc.conf is used during
automatic startup of the jails when the host is rebooted. The whole
arrangement seems unnecessary redundant, and I truly wish this can be
merged sooner rather than later.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
I've updated to 9.2-RC1 and the _parameters did the trick, thanks!
Cheers,
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: SolarFlare 10GB card
Don't use the driver on their website. It's very old. Use the driver that comes with FreeBSD 9.1 which you don't have to compile. Someone should ask them to remove the link on their website... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: jail.conf ignoring exec.fib?
Karl Pielorz wrote:
I'm running 9.2-RC2 amd64 on a system, with a number of jails. The jails
are setup using '/etc/jail.conf' - but the exec.fib in jail.conf seems
to be being ignored?
e.g. in /etc/jail.conf I have:
testjail {
jid = 100;
exec.fib = 1; Set FIB 1
path = /usr2/jails/testjail;
host.hostname = testjail.somedomain.com;
ip4.addr = 192.168.0.40;
mount.devfs;
}
But if I run up that jail and connect to it, 'netstat -r -n' shows it's
still using fib 0 (i.e. the default gateway is set).
If before running the jail, I do 'setfib 1 route add default
192.186.0.90' - when the jail is run up, again - netstat within it still
shows the systems default gateway, not the gateway from fib 1?
-Karl
The jail(8) man page lacks details about how to use exec.fib.
It requires either a new kernel (with options ROUTETABLES=2 or however
many you want), or a boot-time setting with net.fibs=2 in
/boot/loader.conf (requiring a reboot).
setfib 1 route add default 198.192.64.21
creates routing table number 1 with that IP address.
In this example exec.fib=1 would be coded.
See setfib(8) and setfib(2) for details.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
ZFS Snapshots Not able to be accessed under .zfs/snapshot/name
I have a few systems running on ZFS with a backup script that creates snapshots, then backs up the .zfs/snapshot/name directory to make sure open files are not missed. This has been working great but all of the sudden one of my systems has stopped working. It takes the snapshots fine, zfs list -t spnapshot shows the snapshots, but if you do an ls command, on the .zfs/snapshot/ directory it returns not a directory. part of the zfs list output: NAMEUSED AVAIL REFER MOUNTPOINT zroot 4.48G 29.7G31K none zroot/ROOT 2.92G 29.7G31K none zroot/ROOT/91p5-20130812 2.92G 29.7G 2.92G legacy zroot/home 144K 29.7G 122K /home part of the zfs list -t snapshot output: NAMEUSED AVAIL REFER MOUNTPOINT zroot/ROOT/91p5-20130812@91p5-20130812--bsnap 340K - 2.92G - zroot/home@home--bsnap 22K - 122K - ls /.zfs/snapshot/91p5-20130812--bsnap/ Does work at the right now, since the last reboot, but wasn't always working, this is my boot environment. if I do ls /home/.zfs/snapshot/, result is: ls: /home/.zfs/snapshot/: Not a directory if I do ls /home/.zfs, result is: ls: snapshot: Bad file descriptor shares I have tried zpool scrub zroot, no errors were found, if I reboot the system I can get one good backup, then I start having problems. Anyone else ever ran into this, any suggestions as to a fix? System is running FreeBSD 9.1-RELEASE-p5 #1 r253764: Mon Jul 29 15:07:35 CDT 2013, zpool is running version 28, zfs is running version 5 -- Thanks, Dean E. Weimer http://www.dweimer.net/ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: FreeBSD on ThinkPad W530
Hi and thanks for reply ;) Yay another FreeBSD laptop user! I use FreeBSD for dekstop/workstation for I do not remember how long: http://vermaden.deviantart.com/art/CorporateBSD-FreeBSD-at-Work-190680188 Please do this: * join the freebsd-mobile list;* create PRs for each of your problems with -10 above!; Here are created PRs: http://www.freebsd.org/cgi/query-pr.cgi?pr=181281 stack trace after successfull 'umount /mnt' (SDHC card mounted as msdosfs) http://www.freebsd.org/cgi/query-pr.cgi?pr=181282 3h of work on battery on FreeBSD while 10h on Windows http://www.freebsd.org/cgi/query-pr.cgi?pr=181283 acpi_ibm module is useless on ThinkPad W530 http://www.freebsd.org/cgi/query-pr.cgi?pr=181285 x11/xorg does not start if Nvidia Optimus is enabled on * the power utilisation thing is going to be fun to track down - what kind of CPU is in there? Is it a recent Intel? I'm playing around with their tools at the moment; maybe we can look at the power the CPU is consuming and then add on the power from each of the other parts in your laptop until we figure out what's drawing said power * the brightness thing is known; a bunch of us have this issue and the fix is known. Trouble is, there's no (yet) clean fix that's made it into acpi_ibm. I'm glad there's another person who cares; it means we have more chance of getting a real fix that works for multiple people into the tree. As for suspend/resume - I'm glad it at least works for you. Right now I don't even get video output upon resume. But, it's a starting point. Let's get the PRs filed, the brightness thing pushed into -HEAD, and then start down the path of figuring out where the power consumption is coming from. Here is the hardware information: Lenovo ThinkPad W530 cpu: Intel Core i7-3630QM (http://ark.intel.com/products/71459) (powerd works) ram: 16 GB DDR3 hdd: 256 GB SSD gfx: Intel HD 4000 (works with Optimus disabled in BIOS) gfx: Nvidia Quadro K2000 2 GB (works with Optimus disabled in BIOS) sdh: RICOH R5CE823 (SD/SDHC card reader works) wif: Intel Centrino Ultimate-N 6300 (works) The complete information (dmesg/dmidecode) is in the submitted PRs. Regards, vermaden | Hi, | | I have just tried FreeBSD on ThinkPad W530 and I must say that its very disapointing experience ... | | The FreeBSD 9.2-RC1 and PC-BSD 9.2-BETA2 does not even boot from the USB drive - instant kernel panic and reboot. | | The FreeBSD 10.0-CURRENT was able to boot successfully and I could install FreeBSD onto the drive with 'ZFS Madnss' style. | | After installation with extended battery charged to 100% I have about 3 hours of work ... while having about 10 hours on Windows (haven't tried Linux yet). I disabled discrete graphics (Nvidia) in the BIOS and also added set hw.pci.do_power_nodriver to 3, but that also did not solved the 'battery' problem. The powerd daemon was of course running and worked ok. | | After compiling new x11/xorg (with WITH_NEW_XORG in /etc/make.conf) along with x11-wm/openbox I was able to get X11 working, but I can not go back to console as its not implemented yet. | | The screen is 100% bright all the time because acpi_ibm module probably does not support this model yet (changing the dev.acpi_ibm.0.lcd_brightness is pointless, no effects). | | Suspend and resume works very poor, after resume the resolution is 640x640 with all colors broken, requires restarting X11 in 'blind mode' (not implemented console switching). | | Of course as all of the above is not possible, using the Nvidia Optimus technology (graphics card switching) is probably also not possible, which is possible with Bumblebee on Linux, any plans on merging that functionality into FreeBSD? | | At least WiFi and LAN worked out of the box ... | | | Now ... how can I help, what information can I provide to help resolve these issues: | | 1. disable power for discrete graphics card | 2. have working screen brightness changing and working other Fn + X shotrcuts | 3. I guess I will have to 'just wait' for the console switching implementation? | | ... or maybe I am doing it 'wrong' someone have W530 there and uses FreeBSD with any more degree of success then I? | | | Regards, | vermaden ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: jail.conf ignoring exec.fib?
--On 14 August 2013 08:58 -0400 Fbsd8 fb...@a1poweruser.com wrote: The jail(8) man page lacks details about how to use exec.fib. It requires either a new kernel (with options ROUTETABLES=2 or however many you want), or a boot-time setting with net.fibs=2 in /boot/loader.conf (requiring a reboot). Yup, done that :) setfib 1 route add default 198.192.64.21 creates routing table number 1 with that IP address. In this example exec.fib=1 would be coded. See setfib(8) and setfib(2) for details. Yeah, I do that as well - but 'netstat -r -n' from within the jail shows the systems default routing table. As opposed to 'setfib 1 netstat -r -n' (outside the jail) which shows fib either has no default gateway, or the one I set (which is right). Just within the jail, it only every shows it's using the systems default routing table :( Fib's work fine outside the jail (i.e. I can show them, set differing default gateways) - but no matter what I do, the 'exec.fib=' line in jail.conf seems to be ignored, when the jail is run up - it only ever sees the default routing table :( -Karl ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: SolarFlare 10GB card
On Aug 14, 2013, at 5:49 AM, Mark Felder wrote: Don't use the driver on their website. It's very old. Use the driver that comes with FreeBSD 9.1 which you don't have to compile. Yea, that driver sux actually. But how would I compile the driver in 9.2RC1 as I see the source is included? - aurf ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: SolarFlare 10GB card
On Wed, 14 Aug 2013 10:51:03 -0700 aurfalien aurfal...@gmail.com wrote: On Aug 14, 2013, at 5:49 AM, Mark Felder wrote: Don't use the driver on their website. It's very old. Use the driver that comes with FreeBSD 9.1 which you don't have to compile. Yea, that driver sux actually. But how would I compile the driver in 9.2RC1 as I see the source is included? Why do you believe the driver in 9.1-RELEASE sucks? Do you have a specific issue? FYI, the driver in 9.1-RELEASE, upcoming 9.2-RELEASE, and even CURRENT are almost 100% identical: http://svnweb.freebsd.org/base/release/9.1.0/sys/dev/sfxge/ http://svnweb.freebsd.org/base/head/sys/dev/sfxge/ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: SolarFlare 10GB card
On Aug 14, 2013, at 11:34 AM, Mark Felder wrote: On Wed, 14 Aug 2013 10:51:03 -0700 aurfalien aurfal...@gmail.com wrote: On Aug 14, 2013, at 5:49 AM, Mark Felder wrote: Don't use the driver on their website. It's very old. Use the driver that comes with FreeBSD 9.1 which you don't have to compile. Yea, that driver sux actually. But how would I compile the driver in 9.2RC1 as I see the source is included? Why do you believe the driver in 9.1-RELEASE sucks? Do you have a specific issue? I meant the driver off there site. I'm trying the one with 9.1 in a few. Didn't meant to sound like a barney. Unsure why the SolarFlare driver is even up on there site, seems unstable. - aurf ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: SolarFlare 10GB card
On Wed, 14 Aug 2013 11:48:52 -0700 aurfalien aurfal...@gmail.com wrote: On Aug 14, 2013, at 11:34 AM, Mark Felder wrote: On Wed, 14 Aug 2013 10:51:03 -0700 aurfalien aurfal...@gmail.com wrote: On Aug 14, 2013, at 5:49 AM, Mark Felder wrote: Don't use the driver on their website. It's very old. Use the driver that comes with FreeBSD 9.1 which you don't have to compile. Yea, that driver sux actually. But how would I compile the driver in 9.2RC1 as I see the source is included? Why do you believe the driver in 9.1-RELEASE sucks? Do you have a specific issue? I meant the driver off there site. I'm trying the one with 9.1 in a few. Didn't meant to sound like a barney. Unsure why the SolarFlare driver is even up on there site, seems unstable. - aurf Ahhh, I see. You won't have to compile anything with FreeBSD 9.1 or later. Just boot up the OS and you'll see sfxge in the output of ifconfig. Enjoy! :) ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: SolarFlare 10GB card
On Aug 14, 2013, at 11:56 AM, Mark Felder wrote: On Wed, 14 Aug 2013 11:48:52 -0700 aurfalien aurfal...@gmail.com wrote: On Aug 14, 2013, at 11:34 AM, Mark Felder wrote: On Wed, 14 Aug 2013 10:51:03 -0700 aurfalien aurfal...@gmail.com wrote: On Aug 14, 2013, at 5:49 AM, Mark Felder wrote: Don't use the driver on their website. It's very old. Use the driver that comes with FreeBSD 9.1 which you don't have to compile. Yea, that driver sux actually. But how would I compile the driver in 9.2RC1 as I see the source is included? Why do you believe the driver in 9.1-RELEASE sucks? Do you have a specific issue? I meant the driver off there site. I'm trying the one with 9.1 in a few. Didn't meant to sound like a barney. Unsure why the SolarFlare driver is even up on there site, seems unstable. - aurf Ahhh, I see. You won't have to compile anything with FreeBSD 9.1 or later. Just boot up the OS and you'll see sfxge in the output of ifconfig. Well my fine feathered friend, thats my dilemma. I do not see the SolarFlare via ifconfig. Now pciconf -l shows much stuff, even my built in 1Gb nics but not my 10Gb Solars. I'm sure one of the many PCI devices is listed, but not as a SlarFlare, but some generic device. Any guidance? - aurf ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: SolarFlare 10GB card
On Wed, 14 Aug 2013 12:05:56 -0700 aurfalien aurfal...@gmail.com wrote: Well my fine feathered friend, thats my dilemma. I do not see the SolarFlare via ifconfig. Now pciconf -l shows much stuff, even my built in 1Gb nics but not my 10Gb Solars. I'm sure one of the many PCI devices is listed, but not as a SlarFlare, but some generic device. Any guidance? - aurf Just logged into the only Solarflare box I have access to -- /boot/loader.conf has sfxge_load=YES So on a running system you'll have to # kldload sfxge And my pciconf -l has these entries: sfxge0@pci0:6:0:0: class=0x02 card=0x71041924 chip=0x08131924 rev=0x00 hdr=0x00 sfxge1@pci0:6:0:1: class=0x02 card=0x71041924 chip=0x08131924 rev=0x00 hdr=0x00 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: SolarFlare 10GB card
On Aug 14, 2013, at 12:20 PM, Mark Felder wrote: On Wed, 14 Aug 2013 12:05:56 -0700 aurfalien aurfal...@gmail.com wrote: Well my fine feathered friend, thats my dilemma. I do not see the SolarFlare via ifconfig. Now pciconf -l shows much stuff, even my built in 1Gb nics but not my 10Gb Solars. I'm sure one of the many PCI devices is listed, but not as a SlarFlare, but some generic device. Any guidance? - aurf Just logged into the only Solarflare box I have access to -- /boot/loader.conf has sfxge_load=YES So on a running system you'll have to # kldload sfxge And my pciconf -l has these entries: sfxge0@pci0:6:0:0: class=0x02 card=0x71041924 chip=0x08131924 rev=0x00 hdr=0x00 sfxge1@pci0:6:0:1: class=0x02 card=0x71041924 chip=0x08131924 rev=0x00 hdr=0x00 Bingo! Still getting used to loader.conf, thanks man! - aurf ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: AMD Phenom II X4 temperature issues (was Re: hardware monitor)
On 08/04/13 17:22, Gary Aitken wrote: Ok, so now I see that my cpu temperature shoots up pretty dang fast when a build is going on. I'm running an AMD Phenom II X4 with the AMD-supplied fan in an ASUS M4A89TD PRO / USB3 motherboard. The system works fine unless I start a cpu-intensive build. If I leave it unattended, after some time the system shuts down abruptly. I'm guessing it's because of excessive cpu temperatures. When doing port builds, or any cpu-intensive job, the temperature of the CPU goes from 45 to 50 in about 30 seconds. I pretty much have to manually suspend and resume the build process to keep it down. If I do that, I avoid the abrupt shutdown. Needless to say, this makes unattended operation a non-starter... Does anyone else have a similar setup they can provide me some related experience on? Thanks, Gary Thanks, all, for the replies and insights. Just a followup: The factory heatsink was basically incapable of keeping the temp down under a heavy-processing port build, and BIOS was shutting down when the temp eventually climbed too high. xmbmon was my friend for tracking this; using ctls and ctlq on the output stream of the build effectively suspended it when it got around 60C so I could wait until the processor cooled down enough to continue. Doing a sync every second or so also postponed the eventual overheating for a while, but eventually it would creep up to the shutdown point. Replacing the heatsink with a gonzo big one seems to have solved the problem. As an aside, this is probably what also made me think some time ago that my SSD was flaky. Things just ran faster so the cpu overheated sooner. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: ZFS Snapshots Not able to be accessed under .zfs/snapshot/name
On 14/08/2013 22:57, dweimer wrote: I have a few systems running on ZFS with a backup script that creates snapshots, then backs up the .zfs/snapshot/name directory to make sure open files are not missed. This has been working great but all of the sudden one of my systems has stopped working. It takes the snapshots fine, zfs list -t spnapshot shows the snapshots, but if you do an ls command, on the .zfs/snapshot/ directory it returns not a directory. part of the zfs list output: NAMEUSED AVAIL REFER MOUNTPOINT zroot 4.48G 29.7G31K none zroot/ROOT 2.92G 29.7G31K none zroot/ROOT/91p5-20130812 2.92G 29.7G 2.92G legacy zroot/home 144K 29.7G 122K /home part of the zfs list -t snapshot output: NAMEUSED AVAIL REFER MOUNTPOINT zroot/ROOT/91p5-20130812@91p5-20130812--bsnap 340K - 2.92G - zroot/home@home--bsnap 22K - 122K - ls /.zfs/snapshot/91p5-20130812--bsnap/ Does work at the right now, since the last reboot, but wasn't always working, this is my boot environment. if I do ls /home/.zfs/snapshot/, result is: ls: /home/.zfs/snapshot/: Not a directory if I do ls /home/.zfs, result is: ls: snapshot: Bad file descriptor shares I have tried zpool scrub zroot, no errors were found, if I reboot the system I can get one good backup, then I start having problems. Anyone else ever ran into this, any suggestions as to a fix? System is running FreeBSD 9.1-RELEASE-p5 #1 r253764: Mon Jul 29 15:07:35 CDT 2013, zpool is running version 28, zfs is running version 5 I can say I've had this problem. Not certain what fixed it. I do remember I decided to stop snapshoting if I couldn't access them and deleted existing snapshots. I later restarted the machine before I went back for another look and they were working. So my guess is a restart without existing snapshots may be the key. Now if only we could find out what started the issue so we can stop it happening again. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
