Solaris

Hurray! At last, for the first time ever in more than a year, my blog stats show that the Firefox browser tops the list among my visitors!

Way to go, Firefox!

And you can download Firefox 1.5 for Solaris right here:

http://ftp.mozilla.org/pub/mozilla.org/firefox/releases/1.5/contrib/solaris_pkgadd/

I've finally found time to start yet another good tradition on my blog. From now on, I'll maintain an index of links to all my articles on DTrace, which will also include links to all other resources on DTrace I've found useful.

This link repositary can be found at the following URL: http://solaris.reys.net/english/dtrace

There is quite a number of ZFS filesystems properties, and I will cover most useful ones today.

I'll begin with refreshing your knowledge a bit. As I've told before, I'm going to create a number of ZFS filesystems on my server for the next few blog entires on ZFS. So, right now I have the following:


To get a value of some ZFS property, we normally use a command like this:


But such output isn't always convenient for us - it's formatted this way to make the data more human readable. But if we're going to use zfs get to obtain some ZFS parameters from our scripts, we really don't need anything fancy. So we're probably better off using a special -H command line option:


One more thing - a useful, yet very obvious feature which allows you specifying few properties names in one command line:


Okay, now let's move on and look at some useful ZFS filesystems properties.

For instance, the mountpoint property name speaks for itself. By default, the filesystem which you change the mountpoint for, will be automatically remounted at a new location:



One more potentially useful option is an on-disk compression. It happens on the fly, and it is planned to eventually have a number of compression methods available to a ZFS administrator, but at the moment you can use only one method - lzjb.

Still, results are impressive:


No wonder the compression ratio is so good for this filesystem:


Unfortunately, only few types of files can be so wonderfully compressed, and text files (for instance, my Apache2 logs) belong to them too. Executable files, of course, will compress with a much lower ratio.

I think that should do for today's entry. Let me tell you right now: I have a whole series of ZFS blog entries planned ahead, and that's the reason I haven't covered some of the simpler ZFS filesystem options yet. I promise to write more in the nearest few days.

Hi!

Unbelievable - this turns out to be the very first entry of mine in 2006! I couldn't postpone new entires anymore, so here's one for you :)

It's been quite a while since I've cleared one of internal disks in my Netra t105 to bring it under ZFS control. As a result, I now have a 33Gb zfs-pool to experiment with. Today I had some spare time, so I've decided to share the very basics of managing ZFS filesystems.

So this is the pool I have:



And like I said, it has only one drive in it:


By default, when you create a zfs-pool, all of its disk space is represented as a single filesystem with the same name. This filesystem also gets a mountpoint with the same name and is automatically mounted off /. So, after doing a zpool create (here is my example) you can immediately start working with your newly made filesystem.

At the moment I've got only 1 additional filesystem created, I use it for Oracle 10g. So here's how it looks:


According to ZFS concepts, all the newly made filesystems may use all the available disk space of the zfs-pool they belong to. So, when I create another filesystem in my stock pool, this filesystem has more than 30Gb available to it:


To make sure that some of your filesystems don't eat up all the available disk space, you have to limit them. And it's very easily done so:


As you have probably guessed, quota is the parameter name, while set is a keyword to alter parameters values. There is quite a number of ZFS filesystem parameters, and most of them you can modify, but there are also some which are read-only. Here's an example of such a parameter, and you can see what happens if you try modifying them:


You can find the full list of ZFS filesystem parameters on the man page for zfs, as for me - I'll show you only 1 more parameter today, and a very useful one in my opinion: a mount point. As all the rest things about ZFS, this parameter is very easy to change, and you even have the filesystem automatically remounted for you:


I left the df output intentionally here, to show that there were no additional manipulations made to the try filesystem - it really is this easy!

I guess that's enough for today - so next time I'll tell you about few more useful ZFS filesystem parameters. Good luck with your experiments!