Errr, I cant find the CIFS service in the 134 build.
I know it was renamed to as per below but still cant see it anywhere?
> system/file-system/smb (was SUNWsmbfs*)
> service/file-system/smb (was SUNWsmbs*)
Anyone have any ideas?
pkg search *smb gets me these… but i cant install them.
require depend service/file-system/smb@0.5.11-0.134 pkg:/redistributable@0.1-0.134
require depend service/file-system/smb@0.5.11-0.134 pkg:/storage/storage-server@0.1-0.134
require depend service/file-system/smb@0.5.11-0.134 pkg:/system/security/kerberos-5@0.5.11-0.134
require depend service/file-system/smb@0.5.11-0.134 pkg:/storage/storage-nas@0.1-0.134
require depend system/file-system/smb@0.5.11-0.134 pkg:/redistributable@0.1-0.134
require depend system/file-system/smb@0.5.11-0.134 pkg:/storage/storage-server@0.1-0.134
require depend system/file-system/smb@0.5.11-0.134 pkg:/slim_install@0.1-0.134
pkg install system/file-system/smb
No updates necessary for this image.
pkg install service/file-system/smb
Creating Plan
pkg: The following pattern(s) did not match any packages in the current catalog.
Try relaxing the pattern, refreshing and/or examining the catalogs:
service/file-system/smb
Update 23/05/2010
Problem was due to errors within package manager — see this post
Cool. zfs as of version 21 has deduplication built in. And thats the good dedup – synchronous dedup. i.e. deduped on the fly!
How easy is it to turn on? – very!
Once you have upgraded your zpool to 21 or above you can run the following command at the pool level and deduplication will be over all your data from that point onwards.
zpool set dedup=on tank
Done
Note : Watch your performance, it will drop like a rock if you do not have enough ram for your dedup tables. Do some tests after enabling this feature.
http://hub.opensolaris.org/bin/view/Community+Group+zfs/dedup
The following is some notes i have around the parameters i usually use during testing. There is a good document at ixbt labs on the various tests and settings….
For a 1GB test set the sectors to : 2048000
Typical benchmarks; (which you will need to add)
128K 100% Read – Sequential
128K 100% Write – Sequential
Remember to bump the workers up to 5 or so. You can set the mixes across all the workers if you select the PC object.
http://ixbtlabs.com/articles/hddide2k1feb/iometer.html
Straight from : http://community.spiceworks.com/how_to/show/662
I’m using ESXi 4.0, and i was facing the problem of “Another task is already in progress” error, practically the VM could not be used at all (turn on restart or even force off).
in ESXi 4.0 SSH console, using the command “service mgmt-vmware restart” will do no good :-(
therefore the solution is by using: services.sh restart command, quite simple and it doesn’t kill the whole VM process which is currently running on production, the only thing that is affected is the VCB backup, it failed when that command issued. Finally in your vCenter console, right click on your ESXi host in which you run the command and then click on reconnect.
So on the ESXi box hosting the troubled VM run;
services.sh restart
Then reconnect to that ESX box via VI Client. Shouldnt effect any of the other already running virtual machines.
Continuing on from this http://sigtar.com/2010/02/04/vsphere-and-multipathing-iscsi/
you may want to implement jumbo frames to your iSCSI backend…
Enable jumbo frames on your iSCSI target and switches then complete the following on the ESXi hosts (iSCSI initiators)…
This to list your current switch details and port group names…
esxcfg-vswitch -l
The follownig to allow jumbo frames onto your vswtich (insert your vSwich in following)
esxcfg-vswtich -m 9000 vSwitch0
Then delete and recreate your kernel port groups that you setup for iscsi, my commands looked like this… (repeat for each iscsi kernel port you have)
esxcfg-vmknic -d iSCSI-1
esxcfg-vmknic -i 10.0.0.101 -n 255.255.0.0 -m 9000 iSCSI-1
to confirm you have set the MTU (frame size) correctely, run the following….
esxcfg-vmknic -l
you should see your iSCSI kernel ports with a MTU of 9000 all going well.