Without further ado, here is my top 10 of all time favorite passwords.

• 123456
• 12345
• 123456789
• Password
• iloveyou
• princess
• rockyou
• 1234567
• 12345678
• abc123

Thanks to DLS for making my list public!

You knew this day was coming: ZFS now has built-in deduplication. If you already know what dedup is and why you want it, you can skip the next couple of sections. For everyone else, let’s start with a little background.

Read more about it at http://blogs.sun.com/bonwick/en_US/entry/zfs_dedup.

The method below describes a way in which you can mount a new file system (UFS) to a running Solaris 10 zone without the need of a reboot.

Assumptions:
• All commands need to be run from the global zone as the root user unless otherwise specified.

Prerequisites:

• A Solaris 10 host with at least one running non-global zone.

Limitations:

• You can not unmount the file system from the non-global zone. Some say this is a benefit

Lets get started!

Log into the global zone and create the new file system like you normally would. In this example, I use SVM to create a new metadevice (d1000), one way mirror (d2000), and a 1Gig soft partition (d2001). Your mileage may vary.


# metainit d1000 1 1 c1t5d0s0 -i 128k
# metainit d2000 -m d1000
# metainit d2001 -p d2000 1g
# echo y | newfs -i 8192 /dev/md/rdsk/d2001


Create the block and character devices for the zone. Run “ls -lL” against the newly created soft partition (d2001) to find the major and minor character and block values.


# ls -lL /dev/md/*dsk/d2001
brw-r----- 1 root sys 85, 2001 Oct 6 13:46 /dev/md/dsk/d2001
crw-r----- 1 root sys 85, 2001 Oct 6 13:47 /dev/md/rdsk/d2001


NOTE: The major and minor values are 85 and 2001, respectively. Notice that the “dsk” device is a “block-type” file and “rdsk” device is a “character-type” file.

Run mknod to create the two special files for the zone. Keep in mind that the name of the two files need to be saved down the myzone device path.


# mknod /zones/myzone1/dev/md/dsk/d2001 b 85 2001
# mknod /zones/myzone1/dev/md/rdsk/d2001 c 85 2001


Correct the permissions and ownerships of the new d2001 block-type and character-type files.


# chmod 640 /zones/myzone1/dev/md/*dsk/d2001
# chown root:root /zones/myzone1/dev/md/*dsk/d2001


Create a mount point in the “myzone1″ non-global zone.


# mkdir /zones/myzone1/root/wandisimo


Confirm its not already mounted


# mount | grep wandisimo


You should not get anything back from the command above.

Mount the file system


# mount /dev/md/dsk/d2001 /zones/myzone1/root/wandisimo


You are probably thinking to your self, “Why couldn’t we just skip to this step and be done with it?” From my testing, if the block and character files are not created down the “myzone1″ device path first, it fails to mount. If you were to add the soft partition using zonecfg or by adding it to the zone XML file then rebooting the non-global zone, the boot process actually creates the block and character device for you.

NOTE: Even though the file system successfully gets mounted, it will not show up in a “df” output as actually being mounted.

Check to see if its mounted


# df -h | grep wandisimo


You should not get any output.

Confirm the file system is in fact mounted by running the mount command


# mount | grep wandisimo
/zones/myzone1/root/wandisimo on /dev/md/dsk/d2001 read/write/setuid/devices/intr/largefiles/logging/xattr/onerror=panic/dev=15407d3 on Tue Oct 6 14:11:45 2009


Log into the running non-global zone (myzone1) to confirm the file system is indeed mounted


# zlogin myzone1
(myzone1)# df -h /wandisimo
Filesystem size used avail capacity Mounted on
/wandisimo 1008M 1.0M 947M 1% /wandisimo


Done. No need to reboot the non-global zone!

If you would like to make this permanent, you will need to add it to the /etc/vfstab in the global zone.

http://xkcd.com/627/

“I like to use the analogy of door locks. WEP is closest to a bathroom or bedroom lock (the kind you can unlock with a stiff pin). It’ll let people know you don’t want them to enter, but anyone with a the slightest bit of knowledge can get past it. WPA is like a standard door lock; it’s a lot more secure, but it is still possible to get by for someone with the right tools, knowledge, and circumstances. WPA2 is like a bank safe. It may be possible to defeat, depending on how it’s been set up, but it’s not realistically possible for anybody to actually do so… yet. Just to continue the analogy to other Wifi security methods, not broadcasting your SSID is like taking the numbers off of your house – The house is still there and everyone can see it, it’s just a bit harder to find for people that don’t know what they are looking for already. Filtering by MAC address is like having a guard at the door that checks everyone’s name against a list to see if they can enter. The only problem is, he doesn’t ask for ID or remember what people look like, so anybody can and can listen in to see what names are allowed and then claim to be anybody else.” –MaribelAlligator on lifehaker.com

I like the description. I just may have to steal that. (tounge in cheek moment)


(global-zone)# zoneadm list -vic
ID NAME STATUS PATH BRAND IP
0 global running / native shared
8 ngzone1 shutting_down /z/host/ngzone1 native shared
9 ngzone2 running /z/host/ngzone2 native shared


From the global zone, I fixed the problem by killing the process that was hanging up the ngzone1 zone:


(global-zone)# ps -efZ | grep ngzone1
global root 7623 1 0 May 24 ? 0:04 zoneadmd -z ngzone1
ngzone1 root 11679 1 0 May 31 ? 0:00 zsched
ngzone1 server 23527 1 0 Jun 06 ? 13:20 batchResearch1


Sending a SIGKILL to PID 23527 enabled the ngzone1 to properly shutdown. Don’t kill zoneadmd or zsched as that’s handled by the global zone. Everything else should be fair game. The only thing left now is to figure out what caused the process to hang preventing ngzone1 from properly being shut down.

http://www.sunsolarisadmin.com/hardware/how-to-find-the-wwn-world-wide-name-in-sun-solaris/

I started with 500Meg disks and worked my way down to 50Meg disks. Keep in mind that these are not real disks. They are empty files created by the mkfile command and stored in /tmp/ that I am using as disks. I would not recommend using files in a live system but they work great for tests and experiments.

All my tests were as expected until I created the 50Meg disk/files.

Using the Bash shell, here is what I did:

1. Create the 50Meg disk files

# for i in {1..5}; do mkfile 50m /tmp/disk${i}; done

This created 5 x 50Meg files in /tmp.

2. I then attempted to create a raidz ZFS pool using those files as my disks.

# zpool create fort raidz /var/tmp/{1..5}
cannot create 'fort': one or more devices is less than the minimum size (64M)

3. Changing the size to 64Meg files worked.

#  for i in {1..5}; do mkfile 64m /tmp/disk${i}; done
# zpool create fort raidz /tmp/disk{1..5}
# zpool list
NAME                    SIZE    USED   AVAIL    CAP  HEALTH     ALTROOT
fort                    296M    143K    296M     0%  ONLINE     -

# zfs list
NAME   USED  AVAIL  REFER  MOUNTPOINT
fort   109K   204M  39.1K  /fort

# zpool status -v
  pool: fort
 state: ONLINE
 scrub: none requested
config:

        NAME            STATE     READ WRITE CKSUM
        fort            ONLINE       0     0     0
          raidz1        ONLINE       0     0     0
            /tmp/disk1  ONLINE       0     0     0
            /tmp/disk2  ONLINE       0     0     0
            /tmp/disk3  ONLINE       0     0     0
            /tmp/disk4  ONLINE       0     0     0
            /tmp/disk5  ONLINE       0     0     0

errors: No known data errors

For future reference, your disks must be a equal to or greater than 64Megs in size. Great for 64Meg USB drives, sarcasm included…

could not verify fs /test: zfs ‘tank/test’ mountpoint is not “legacy”
zoneadm: zone non-global-zone failed to verify

The fix would be to update/create the ZFS dataset as a legacy mount point. For this post, I assume that you have both basic understanding of Solaris zone technology and zfs file systems.

In the version of Solaris that I run, (Solaris 10 11/06, sparc) here are the steps you would need to follow in order to add a ZFS file system to a Solaris non-global zone.

1. Create a legacy zfs pool from the global zone
   

   # zpool create tank c0t0d0s0

2. Create a zfs dataset using the new tank zfs pool
   

   # zfs create tant/test
   

3. Display the zfs pool
   

   # zfs list
   NAME                USED  AVAIL  REFER  MOUNTPOINT
   tank               6.57G   120G  26.5K  /tank
   tank/test          24.5K   120G  24.5K  /tank/test
   

4. Set the new tank/test dataset as a legacy mount point
   

   # zfs set mountpoint=legacy tank/test
   

5. Display the zfs pool
   

   # zfs list
   NAME                USED  AVAIL  REFER  MOUNTPOINT
   tank               6.57G   120G  24.5K  /tank
   tank/test          24.5K   120G  24.5K  legacy
   

Notice the mount point for tank/test changed from the actual mount point /tank/test to legacy.

6. Create a Solaris non-global zone with similar options as below
   

   # zonecfg -z non-global-zone info
   
   ...
   fs:
           dir: /test
           special: tank/test
           raw not specified
           type: zfs
           options: []
   dataset:
           name: tank/test
   ...
   

After the zone has been created and booted, login into the non-global-zone and running a “df” will show you the new ZFS pool is mounted and ready to satisfy your ZFS needs.

The key line to adding the SVM Metadevice to the non-global zone is the following:

zonecfg:myzone:net> add device
zonecfg:myzone:net> set match=/dev/md/*dsk/d610
zonecfg:myzone:net> end

I used an asterisk to signify that I want both the the dsk and rdsk devices.

Assuming all went well, you should be able to mount and unmount the SVM Metadevice from the non-global zone. Why would you want to provide the ability for a non-global zone to mount and un-mount a file system at will? In my case, the mount point assigned to d110 in the example above is cloned daily using EMC clone technology.