SOLVED System Dataset missing

[Alecmascot]

In 9.2.1.8 I had a .system folder in the root of my pool (vol1).
Since upgrading to 9.3 Beta there is no .system folder.
In the gui I go to System-System Dataset and do "save" I get this in the console messages :

Nov 20 11:00:48 freenas notifier: mount: vol1/.system: Device busy
Nov 20 11:00:48 freenas notifier: mount: vol1/.system/cores: Device busy
Nov 20 11:00:48 freenas notifier: mount: vol1/.system/samba4: Device busy
Nov 20 11:00:48 freenas notifier: mount: vol1/.system/syslog-4cb80125ae2d45a0998909377577eae9: Device busy
Nov 20 11:00:48 freenas notifier: mount: vol1/.system/rrd-4cb80125ae2d45a0998909377577eae9: Device busy
Nov 20 11:00:48 freenas notifier: kern.corefile: /var/db/system/cores/%N.core -> /var/db/system/cores/%N.core
Nov 20 11:00:52 freenas notifier: Stopping syslog_ng.
Nov 20 11:00:52 freenas syslog-ng[8230]: syslog-ng shutting down; version='3.5.6'
Nov 20 11:00:52 freenas syslog-ng[9055]: syslog-ng starting up; version='3.5.6'
Nov 20 11:00:55 freenas generate_smb4_conf.py: [common.pipesubr:58] Popen()ing: /sbin/sysctl -n 'kern.maxfilesperproc'
Nov 20 11:00:56 freenas generate_smb4_conf.py: [common.pipesubr:58] Popen()ing: zfs list -H -o mountpoint,name
Nov 20 11:00:56 freenas generate_smb4_conf.py: [common.pipesubr:58] Popen()ing: zfs list -H -o mountpoint
Nov 20 11:00:56 freenas generate_smb4_conf.py: [common.pipesubr:58] Popen()ing: zfs list -H -o mountpoint
Nov 20 11:00:56 freenas generate_smb4_conf.py: [common.pipesubr:58] Popen()ing: /usr/local/bin/pdbedit -d 0 -i smbpasswd:/tmp/tmpN_ccaF -s /usr/local/etc/smb4.conf -e tdbsam:/var/etc/private/passdb.tdb
Nov 20 11:00:56 freenas generate_smb4_conf.py: [common.pipesubr:58] Popen()ing: /usr/local/bin/pdbedit -L

FreeNAS 9.3-BETA 2014-11-20 06:09:50 GMT

Where do I go next ?
Thanks

 

[dlavigne]

Create a report at bugs.freenas.org and post the issue number here.

 

[Alecmascot]

Create a report at bugs.freenas.org and post the issue number here.

Bug #6727

 

[jkh]

It didn't disappear, it just moved (to /var/db/system) out of harm's way because people kept blasting .system with recursive pool operations from the top!

 

[Alecmascot]

Bug #6727

Extract from the Bug dialogue:

"OK, so, first of all: your system behaves correctly. Everything is fine - .system folder is no longer visible under volume root, it's now remapped under /var/db/system. These error messages can be safely ignored - it only means that GUI tries to mount .system again, but one is already mounted.

However, I'm gonna add a check for .system already mounted and skip mounting part if so to not scary any more users (but again, that will be only cosmetic change to hide these error messages)."