Nfs – Getting ZFS per dataset IO statistics (or NFS per export IO statistics)

nfsopenindianaopensolarissolariszfs

Where do I find statistics about how IO is divided between zfs datasets? (zpool iostat only tells me how much IO a pool is experiencing.)

All the relevant datasets are used through NFS, so I'd be happy with per export NFS IO statistics also.

We're currently running OpenIndiana

[edit]

It seems that operation and byte counter are available in kstat

kstat -p unix:*:vopstats_???????
...
unix:0:vopstats_2d90002:nputpage        50
unix:0:vopstats_2d90002:nread   12390785
...
unix:0:vopstats_2d90002:read_bytes      22272845340
unix:0:vopstats_2d90002:readdir_bytes   477996168
...

…but the strange hexadecimal ID numbers have to be resolved from /etc/mnttab (better ideas?)

rpool/export/home/jkj /export/home/jkj zfs rw,...,dev=2d90002 1308471917

Now writing a munin plugin to use the data…

Best Answer

How about this... In this instance I have a ZFS filesystem '/volumes/lab3_pool_a/data02/alpha/' and I am using fsstat to get some basic statistics about it. Notice, I am getting stats for both, ZFS as a whole, and this one filesystem. By the way, fsstat has some good options and may give you just what you need.

# fsstat zfs /volumes/lab3_pool_a/data02/alpha/ 1

 new  name   name  attr  attr lookup rddir  read read  write write
 file remov  chng   get   set    ops   ops   ops bytes   ops bytes
    0     0     0    27     0     27     0     0     0     1   208 zfs
    0     0     0     0     0      0     0     0     0     0     0 /volumes/lab3_pool_a/data02/alpha

Related Solutions

Cannot destroy ZFS snapshot: dataset already exists

This issue has now been answered, courtesy of Cindy Swearingen (cindys) here: http://opensolaris.org/jive/thread.jspa?messageID=484242&tstart=0

Summary: If you do incremental receives, this might be CR 6860996:

A temporary clone is created for an incremental receive and in some cases, is not removed automatically.

1. Determine clone names:

# zdb -d <poolname> | grep %

2. Destroy identified clones:

# zfs destroy <clone-with-%-in-the-name>

It will complain that 'dataset does not exist', but you can check
again(see 1)

3. Destroy snapshot(s) that could not be destroyed previously

Linux – How to share ZFS features over NFS

You can create snapshots through NFS by creating directories in the .zfs directory of each dataset. That special directory can be hidden or not (but still accessible).

ZFS is a hierarchical filesystem, just create individual datasets for each user within other datasets (e.g department/user1 department/user2 etc). They will inherit the properties or you can overwrite those too.

With clones you can save some disk space. If all your users need a initial set of files in their directories, put them in a dataset, snapshot it and clone for each user. You won't be able to delete the snapshot while there are clones depending on it.

Custom dataset properties and clones must be managed from the server side. As far as I know, there are proprietary plug-ins that export ZFS specifics to VMware and the like. There is not a distributed FS protocol that will allow that though. You could create a web front-end and let users manipulate them.

Best Answer

Related Solutions

Cannot destroy ZFS snapshot: dataset already exists

Linux – How to share ZFS features over NFS

Related Topic