Popen()ing: sysctl -b kern.geom.confxml - message?

[globus999]

Hi,
I just installed a clean FN 8.0.1. B4 x64 and noticed a bunch of messages / errors? in system processes that were not there in x32:

Jul 17 07:15:10 freenas freenas[1196]: Popen()ing: sysctl -b kern.geom.confxml
Jul 17 07:15:10 freenas freenas[1198]: Popen()ing: sysctl -b kern.geom.confxml
Jul 17 07:15:11 freenas freenas[1200]: Popen()ing: sysctl -b kern.geom.confxml
Jul 17 07:15:11 freenas freenas[1202]: Popen()ing: sysctl -b kern.geom.confxml
Jul 17 07:15:11 freenas freenas[1204]: Popen()ing: sysctl -b kern.geom.confxml
Jul 17 07:15:11 freenas freenas[1210]: Popen()ing: sysctl -b kern.geom.confxml
Jul 17 07:15:12 freenas freenas[1218]: Popen()ing: sysctl -b kern.geom.confxml
Jul 17 07:15:12 freenas freenas[1223]: Popen()ing: sysctl -b kern.geom.confxml
Jul 17 07:15:13 freenas freenas[1348]: Popen()ing: sysctl -b kern.geom.confxml
Jul 17 07:15:13 freenas kernel: re0: link state changed to UP
Jul 17 07:15:13 freenas freenas[1362]: Popen()ing: sysctl -b kern.geom.confxml
Jul 17 07:15:13 freenas freenas[1368]: Popen()ing: sysctl -b kern.geom.confxml
Jul 17 07:15:13 freenas freenas[1374]: Popen()ing: sysctl -b kern.geom.confxml
Jul 17 07:15:14 freenas freenas[1380]: Popen()ing: sysctl -b kern.geom.confxml
Jul 17 07:15:14 freenas freenas[1390]: Popen()ing: sysctl -b kern.geom.confxml
Jul 17 07:15:14 freenas freenas[1402]: Popen()ing: sysctl -b kern.geom.confxml
Jul 17 07:15:14 freenas freenas[1411]: Popen()ing: sysctl -b kern.geom.confxml

Is this a bug?
Should I be worried?

 

[jim82]

Not errors, probably there because you select force 4K sector size when creating your array.

 

[Milhouse]

I get those messages too on AMD64/4K. Also these, which are quite "nasty" and should be fixed/suppressed if they're not a problem:

Code:

Jul 17 19:27:13 freenas kernel: Starting lockd.
Jul 17 19:27:13 freenas kernel: /etc/rc: WARNING: failed precmd routine for vmware_guestd
Jul 17 19:27:13 freenas kernel: generate_smartd_cfg > /usr/local/etc/smartd.conf
Jul 17 19:27:17 freenas kernel: tdbsam_open: Converting version 0.0 database to version 4.0.
Jul 17 19:27:17 freenas kernel: tdbsam_convert_backup: updated /var/etc/private/passdb.tdb file.
Jul 17 19:27:17 freenas kernel: account_policy_get: tdb_fetch_uint32 failed for type 1 (min password length), returning 0
Jul 17 19:27:17 freenas kernel: account_policy_get: tdb_fetch_uint32 failed for type 2 (password history), returning 0
Jul 17 19:27:17 freenas kernel: account_policy_get: tdb_fetch_uint32 failed for type 3 (user must logon to change password), returning 0
Jul 17 19:27:17 freenas kernel: account_policy_get: tdb_fetch_uint32 failed for type 4 (maximum password age), returning 0
Jul 17 19:27:17 freenas kernel: account_policy_get: tdb_fetch_uint32 failed for type 5 (minimum password age), returning 0
Jul 17 19:27:17 freenas kernel: account_policy_get: tdb_fetch_uint32 failed for type 6 (lockout duration), returning 0
Jul 17 19:27:17 freenas kernel: account_policy_get: tdb_fetch_uint32 failed for type 7 (reset count minutes), returning 0
Jul 17 19:27:17 freenas kernel: account_policy_get: tdb_fetch_uint32 failed for type 8 (bad lockout attempt), returning 0
Jul 17 19:27:17 freenas kernel: account_policy_get: tdb_fetch_uint32 failed for type 9 (disconnect time), returning 0
Jul 17 19:27:17 freenas kernel: account_policy_get: tdb_fetch_uint32 failed for type 10 (refuse machine password change), returning 0
Jul 17 19:27:17 freenas kernel: Importing account for fred...ok

(The above is with BETA3, to which I uploaded a BETA2 config, which may itself have been created in BETA1).

 

[globus999]

Not errors, probably there because you select force 4K sector size when creating your array.

That is correct, yes indeed! I did since 8.0 had no 4K hdd support and had to force it from CLI. When I upgraded to 8.0.1 B4 x64 I started getting those messages. Tx!

 

[jim82]

That is correct, yes indeed! I did since 8.0 had no 4K hdd support and had to force it from CLI. When I upgraded to 8.0.1 B4 x64 I started getting those messages. Tx!

You're welcome, glad to help :)

 

[survive]

Hi globus999,

Best I can tell that's just the FreeNAS polling the system for details on your storage, at least that what it looks like when I ran the command on my system.

-Will