First check your current swap size and details;

swap -lh

or

zfs list

Then create a temp swap zfs store and delete and increase swap

Done.

If you are happy to reboot…

zfs set volsize=8G rpool/swap
reboot

Related posts:

1. OpenSolaris – Samba server Time to share your newly created ZFS volume via samba...

Related posts brought to you by Yet Another Related Posts Plugin.

http://www.eject.name/2009/07/opensolaris-and-hp-smartarray.html

Related posts:

1. OpenSolaris – Samba server Time to share your newly created ZFS volume via samba...

Related posts brought to you by Yet Another Related Posts Plugin.

BUT…

The one thing the store didn’t mention to me is the new 4K cluster sizing on the drive. I guess they assume most people run windows (though the issues are also present in XP). See these posts…

http://blog.temeletry.co.uk/2010/05/wd-green-wd10ears/

Unfortunately they really don’t work as well as you’d like in a server 

• They come with a 5 second head spin down setting that causes them to park their heads if they have been left idle for more than 5 seconds. As it takes a second or two to spin back up this can result in a very laggy experience during interactive sessions.
• They do not have NCQ or any form of command queing/optimisation. This means that (on FreeBSD at least) you are stuck in the LOOK elevator. In particular this was noticed when doing sequential read & write (think dump|restore tar|untar etc) and interactive tasks simultaneously
• They really suck with FreeBSD and ZFS…

http://community.wdc.com/t5/Desktop/Poor-performace-in-OpenSolaris-with-4K-sector-drive-WD10EARS-in/m-p/21132

While the other 512-byte sector HDDs were reading/writing at 30MB/s sustained, this EARS model did not exceeded the 1MB/s barrier.

I know for sure that this is related to the 512-byte sector firmware emulation, because the disk works perfectly well if I partition it in a 4k-sector alignment.

The thing is that even in that way, using it in a ZFS RAIDZ configuration the performance is very poor because RAIDZ uses a dynamic stripe size.

The bottom line here is that folks like me, that use different versions of Unix, need the firmware to present the disk as a 4K-sector disk to unleash the full potential of the technology. The OS is already prepared to support that sector size, no need for emulation here.

http://opensolaris.org/jive/thread.jspa?threadID=125702

Some preliminary testing that I have done…the WD20EARS (2TB advanced format drives) actually presents emulated 512byte sectors to the host o/s.

The drive documentation indicates that jumpers 7-8 should be enabled if the o/s does not support advanced format drives – the drive still present 512 bytes sectors.

I have attempted to raise a support ticket querying this, and how one can disable 512byte sector emulation in the drive (perhaps through a firmware upgrade) but I have not received any response to date.

Hopefully is enough people raise support tickets, WD may release firmware that allows the drive to natively present 4k blocks. Other doco indicates several other jumper combinations – all do not seem to make the drive present 4k byte blocks.

Perhaps someone internal to sun that has a relationship with WD may be able to shed some light on this? It would be fantastic to find out that I was just doing something wrong -> then I can get the drives to be seen on 32bit systems (ie – our embedded kit for osol, velitium)

Tested using b133 (64bit intel).

Try to avoid the green drives in ZFS for now. Remember to do your research before you buy a bunch of disks. I was caught off guard by this small change (works fine in win7 etc) which kills performance in ZFS. Ouch.

No related posts.

Related posts brought to you by Yet Another Related Posts Plugin.

pkg: Requested “install” operation would affect files that cannot be modified in live image.

Please retry this operation on an alternate boot environment.

This is the fix….

mkdir /mnt/osol-134fix
beadm create osol-134fix
beadm mount osol-134fix /mnt/osol-134fix
pkg -R /mnt/osol-134fix fix –accept
beadm activate osol-134fix

Then reboot your machine into the new boot image

Related posts:

1. opensolaris – increase swap I found this on opensolaris forums…. A nice way to...
2. OpenSolaris – iSCSI Want iSCSI in opensolaris? Grab SUNWiscsitgt via package manager. enable...

Related posts brought to you by Yet Another Related Posts Plugin.

netstat -rn

No related posts.

Related posts brought to you by Yet Another Related Posts Plugin.

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

Related posts:

1. OpenSolaris – Samba server Time to share your newly created ZFS volume via samba...

Related posts brought to you by Yet Another Related Posts Plugin.

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.

Related posts:

1. Opensolaris – ZFS recovery after kernel panic Recently i hit what i thought was a huge disaster...
2. OpenSolaris – iSCSI Want iSCSI in opensolaris? Grab SUNWiscsitgt via package manager. enable...
3. zfs compression and latency Since im using ZFS as storage via NFS for my...

Related posts brought to you by Yet Another Related Posts Plugin.

Grab SUNWiscsitgt via package manager.

enable the server via svcadm;

svcadm enable iscsitgt

create your zfs iscsi pool;  (this command will limit iscsi drive to 500GB in size)

zfs create -V 500G tank/iscsi

set isci on via zfs command;

zfs set shareiscsi=on tank/iscsi

check that target is up and running;

iscsitadm list target -v

Done. Should be able to connect via ip from another machine. I have not covered CHAP or any client side configuration. Assumed isolated LAN.

Related posts:

1. vSphere and Multipathing iSCSI This is just a quick reference to create a multiplathing...
2. Jumbo Frames on your vSphere ESXi box Continuing on from this http://sigtar.com/2010/02/04/vsphere-and-multipathing-iscsi/ you may want to implement...
3. vmware – measuring iscsi write performance I picked this trick up off vmware support. If you’ve...

Related posts brought to you by Yet Another Related Posts Plugin.

When i tried to import with zpool import -f tank the machine would lockup and reboot (panic).

The kernel panic;  (key line)

> genunix: [ID 361072 kern.notice] zfs: freeing free segment (offset=3540185931776 size=22528)

Nothing i could do would fix it… tried both of these options in the system file with no success;

set zfs:zfs_recover=1
set aok=1

After a quick email from a Sun Engineer (kudos to Victor), the zdb command line that fixed it;

zdb -e -bcsvL <poolname>

zdb is a read only diagnostic tool, but seemed to read through the sectors that had the corrupt data and fix things??  (not sure how a read only tool does that) – the run took well over 15hrs.

Updated: 20/10/2009

Apparently if you have set zfs:zfs_recover=1 in your system file the zdb command will operate in a different manner fixing the issues it encounters.

Remember to run a zpool scrub <poolname> if you are lucky enough to get it back online.

Related posts:

1. zfs – now has dedup! Cool. zfs as of version 21 has deduplication built in....
2. OpenSolaris – Samba server Time to share your newly created ZFS volume via samba...

Related posts brought to you by Yet Another Related Posts Plugin.

To fix you’ll need to logon using a “failsafe terminal” session, then run gnome-cleanup from the command line. This will blow away any of your gnome settings (although they are actually backed up to a file), but it’ll mean you’ll be able to logon again without issue.

No related posts.

Related posts brought to you by Yet Another Related Posts Plugin.