Xymon Mailing List Archive search

Support for ZFS?

11 messages in this thread

list Benjamin Smith · Mon, 10 Mar 2014 18:03:21 -0700 ·
Xymon 4.3.7 doesn't seem to report on partitions created/mounted on ZFS.

Here's some sample output from df:

[root at hume db2]# df
Filesystem            1K-blocks       Used   Available Use% Mounted on
/dev/sdh2              20161204    3285836    15851228  18% /
tmpfs                   1461616          0     1461616   0% /dev/shm
/dev/sdh1                101086      71234       24633  75% /boot
/dev/sdm1            2884252924 2605050008   249900596  92% /media/a2012
bpart/db1            2995879424  728979328  2266900096  25% /bpart/db1
zfspool             12188961408        384 12188961024   1% /zfspool
zfspool/db          13033537920  844576896 12188961024   7% /mnt/db
zfspool/host          209715200   50983680   158731520  25% /backups/host

Is there a recommended way to set up support for ZFS? I'm not looking 
for anything elaborate; simple reporting of free space as is the default 
for other FS types would be fine for my needs.

-Ben
list Paul Root · Tue, 11 Mar 2014 02:29:36 +0000 ·
It does in Solaris. You may need to go take the code of out of the script in Solaris and put it in your machine's script.
quoted from Benjamin Smith

-----Original Message-----
From: Xymon [mailto:xymon-bounces at xymon.com] On Behalf Of Lists
Sent: Monday, March 10, 2014 8:03 PM
To: xymon at xymon.com
Subject: [Xymon] Support for ZFS?

Xymon 4.3.7 doesn't seem to report on partitions created/mounted on ZFS.

Here's some sample output from df:

[root at hume db2]# df
Filesystem            1K-blocks       Used   Available Use% Mounted on
/dev/sdh2              20161204    3285836    15851228  18% /
tmpfs                   1461616          0     1461616   0% /dev/shm
/dev/sdh1                101086      71234       24633  75% /boot
/dev/sdm1            2884252924 2605050008   249900596  92% /media/a2012
bpart/db1            2995879424  728979328  2266900096  25% /bpart/db1
zfspool             12188961408        384 12188961024   1% /zfspool
zfspool/db          13033537920  844576896 12188961024   7% /mnt/db
zfspool/host          209715200   50983680   158731520  25% /backups/host

Is there a recommended way to set up support for ZFS? I'm not looking 
for anything elaborate; simple reporting of free space as is the default 
for other FS types would be fine for my needs.

-Ben
list Brian Scott · Tue, 11 Mar 2014 06:40:44 +0000 ·
Also seems to work OK on FreeBSD. The pool shows up on the graphs as a separate device which should probably be excluded rather than doubling up. This means that xymon doesn't have anything against zfs in other environments.

Maybe the disk type needs to be included somewhere on your system?

Regards,

Brian Scott
quoted from Paul Root

-----Original Message-----
From: Xymon [mailto:xymon-bounces at xymon.com] On Behalf Of Root, Paul T
Sent: Tuesday, 11 March 2014 1:30 PM
To: 'Lists'; 'xymon at xymon.com'
Subject: Re: [Xymon] Support for ZFS?

It does in Solaris. You may need to go take the code of out of the script in Solaris and put it in your machine's script.

-----Original Message-----
From: Xymon [mailto:xymon-bounces at xymon.com] On Behalf Of Lists
Sent: Monday, March 10, 2014 8:03 PM
To: xymon at xymon.com
Subject: [Xymon] Support for ZFS?

Xymon 4.3.7 doesn't seem to report on partitions created/mounted on ZFS.

Here's some sample output from df:

[root at hume db2]# df
Filesystem            1K-blocks       Used   Available Use% Mounted on
/dev/sdh2              20161204    3285836    15851228  18% /
tmpfs                   1461616          0     1461616   0% /dev/shm
/dev/sdh1                101086      71234       24633  75% /boot
/dev/sdm1            2884252924 2605050008   249900596  92% /media/a2012
bpart/db1            2995879424  728979328  2266900096  25% /bpart/db1
zfspool             12188961408        384 12188961024   1% /zfspool
zfspool/db          13033537920  844576896 12188961024   7% /mnt/db
zfspool/host          209715200   50983680   158731520  25% /backups/host

Is there a recommended way to set up support for ZFS? I'm not looking 
for anything elaborate; simple reporting of free space as is the default 
for other FS types would be fine for my needs.

-Ben


**********************************************************************

This message is intended for the addressee named and may contain
privileged information or confidential information or both. If you
are not the intended recipient please delete it and notify the sender.
**********************************************************************
list John Thurston · Tue, 11 Mar 2014 08:35:00 -0800 ·
quoted from Brian Scott
On 3/10/2014 5:03 PM, Lists wrote:
Xymon 4.3.7 doesn't seem to report on partitions created/mounted on ZFS.

Here's some sample output from df:

[root at hume db2]# df
Filesystem            1K-blocks       Used   Available Use% Mounted on
/dev/sdh2              20161204    3285836    15851228  18% /
tmpfs                   1461616          0     1461616   0% /dev/shm
/dev/sdh1                101086      71234       24633  75% /boot
/dev/sdm1            2884252924 2605050008   249900596  92% /media/a2012
bpart/db1            2995879424  728979328  2266900096  25% /bpart/db1
zfspool             12188961408        384 12188961024   1% /zfspool
zfspool/db          13033537920  844576896 12188961024   7% /mnt/db
zfspool/host          209715200   50983680   158731520  25% /backups/host

Is there a recommended way to set up support for ZFS? I'm not looking
for anything elaborate; simple reporting of free space as is the default
for other FS types would be fine for my needs.
It is my understanding that the newer Xymon clients for Solaris report 
on zfs. What operating system and client are you running?

I use an old BB client to report to my Xymon servers. By modifying 
'etc/bbsys.local' on the client, I was able to make it report zfs 
information. I modified the definition of 'DF' to include zfs.
   DF="( /bin/df -F zfs -kl ; /bin/df -F tmpfs -kl )"

[ By digging through the email archives, I determined that the lack of 
reporting for zfs dated back to 1999 when this DF definition was 
introduced. The DF was introduced to provide better reporting of 
information for swap. At that time, zfs didn't exist, so there was no 
reason to consider how the improvement to swap-reporting might affect it. ]

-- 
    Do things because you should, not just because you can.

John Thurston    XXX-XXX-XXXX
user-ce4d79d99bab@xymon.invalid
Enterprise Technology Services
Department of Administration
State of Alaska
list Ryan Novosielski · Tue, 11 Mar 2014 16:36:21 -0400 ·
These things are configured now in $XYMONCLIENT/bin/xymonclient-$OSTYPE.sh.

--
____ *Note: UMDNJ is now Rutgers-Biomedical and Health Sciences*
 || \\UTGERS      |---------------------*O*---------------------
 ||_// Biomedical | Ryan Novosielski - Sr. Systems Programmer
 || \\ and Health | user-46c89e614701@xymon.invalid - 973/972.0922 (2x0922)
 ||  \\  Sciences | OIT/EI-Academic Svcs. - ADMC 450, Newark
quoted from Brian Scott
      `'
From: Xymon [xymon-bounces at xymon.com] On Behalf Of Scott, Brian [user-42b55c414c28@xymon.invalid]
Sent: Tuesday, March 11, 2014 2:40 AM
To: Root, Paul T; 'Lists'; 'xymon at xymon.com'
Subject: Re: [Xymon] Support for ZFS?

Also seems to work OK on FreeBSD. The pool shows up on the graphs as a separate device which should probably be excluded rather than doubling up. This means that xymon doesn't have anything against zfs in other environments.

Maybe the disk type needs to be included somewhere on your system?

Regards,

Brian Scott

-----Original Message-----
From: Xymon [mailto:xymon-bounces at xymon.com] On Behalf Of Root, Paul T
Sent: Tuesday, 11 March 2014 1:30 PM
To: 'Lists'; 'xymon at xymon.com'
Subject: Re: [Xymon] Support for ZFS?

It does in Solaris. You may need to go take the code of out of the script in Solaris and put it in your machine's script.

-----Original Message-----
From: Xymon [mailto:xymon-bounces at xymon.com] On Behalf Of Lists
Sent: Monday, March 10, 2014 8:03 PM
To: xymon at xymon.com
Subject: [Xymon] Support for ZFS?

Xymon 4.3.7 doesn't seem to report on partitions created/mounted on ZFS.

Here's some sample output from df:

[root at hume db2]# df
Filesystem            1K-blocks       Used   Available Use% Mounted on
/dev/sdh2              20161204    3285836    15851228  18% /
tmpfs                   1461616          0     1461616   0% /dev/shm
/dev/sdh1                101086      71234       24633  75% /boot
/dev/sdm1            2884252924 2605050008   249900596  92% /media/a2012
bpart/db1            2995879424  728979328  2266900096  25% /bpart/db1
zfspool             12188961408        384 12188961024   1% /zfspool
zfspool/db          13033537920  844576896 12188961024   7% /mnt/db
zfspool/host          209715200   50983680   158731520  25% /backups/host

Is there a recommended way to set up support for ZFS? I'm not looking
for anything elaborate; simple reporting of free space as is the default
for other FS types would be fine for my needs.

-Ben


**********************************************************************
This message is intended for the addressee named and may contain
privileged information or confidential information or both. If you
are not the intended recipient please delete it and notify the sender.
**********************************************************************
list Mark Felder · Tue, 11 Mar 2014 18:19:32 -0500 ·
quoted from Ryan Novosielski
On Mar 10, 2014, at 21:29, Root, Paul T <user-76fdb6883669@xymon.invalid> wrote:
It does in Solaris. You may need to go take the code of out of the script in Solaris and put it in your machine's script.
I'd love to see this working out of the box on FreeBSD as well...
list Ryan Novosielski · Tue, 11 Mar 2014 19:49:16 -0400 ·
Didn't you see the other e-mail? Scott Brian says it does.
quoted from Mark Felder
 

----- Original Message -----
From: Mark Felder [mailto:user-db141d317836@xymon.invalid]
Sent: Tuesday, March 11, 2014 07:19 PM
To: Root, Paul T <user-76fdb6883669@xymon.invalid>
Cc: xymon at xymon.com <xymon at xymon.com>
Subject: Re: [Xymon] Support for ZFS?


On Mar 10, 2014, at 21:29, Root, Paul T <user-76fdb6883669@xymon.invalid> wrote:
It does in Solaris. You may need to go take the code of out of the script in Solaris and put it in your machine's script.
I'd love to see this working out of the box on FreeBSD as well...
list Mark Felder · Tue, 11 Mar 2014 19:19:24 -0500 ·
On Mar 11, 2014, at 18:49, Novosielski, Ryan <user-6e4f7a3bb37f@xymon.invalid> wrote:
Didn't you see the other e-mail? Scott Brian says it does.

Whoops, my apologies. It does seem to graph it strangely on FreeBSD; I wasn't aware this was expected behavior. I was hoping it would do a better job of being able to determine the true amount of free space.
list Ryan Novosielski · Tue, 11 Mar 2014 21:41:48 -0400 ·
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
quoted from Mark Felder

On 03/11/2014 08:19 PM, Mark Felder wrote:
On Mar 11, 2014, at 18:49, Novosielski, Ryan 
<user-6e4f7a3bb37f@xymon.invalid> wrote:
Didn't you see the other e-mail? Scott Brian says it does.
Whoops, my apologies. It does seem to graph it strangely on 
FreeBSD; I wasn't aware this was expected behavior. I was hoping
it would do a better job of being able to determine the true amount
of free space.
None needed; I'm curious, is it handled differently on FreeBSD than
Solaris? Solaris shows the total field for all of the FS in the same
pool as the same value. So for example, pool1/fs1, pool1/fs2, etc. all
have the same "total" space and the usage is a percentage of that
total space. A different pool would have a different same value for
the total size. You can change that, though, by assigning ZFS quotas;
it sets a size cap for an FS, so the usage will be a percent of the
capped size.
quoted from Ryan Novosielski

- -- 
 ____*Note: UMDNJ is now Rutgers-Biomedical and Health Sciences*
 || \\UTGERS      |---------------------*O*---------------------
 ||_// Biomedical | Ryan Novosielski - Sr. Systems Programmer
 || \\ and Health | user-46c89e614701@xymon.invalid - 973/972.0922 (2x0922)
 ||  \\  Sciences | OIT/EI-Academic Svcs. - ADMC 450, Newark
      `'

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iEYEARECAAYFAlMfu1wACgkQmb+gadEcsb78ogCfcLg4f5VTPlCyQn0QQvOe8z1F
Nm8Anj7fQp83+XzodWIt2ftfOqUdUuL4
=Zv19
-----END PGP SIGNATURE-----
list Benjamin Smith · Thu, 13 Mar 2014 18:41:00 -0700 ·
I sent the below message a few days ago, but sent it to Ryan rather than the list. I'd really like to see if there's a "more righter" way to do this than the somewhat hackish response below.

-Ben

/////////////////

On 03/11/2014 01:36 PM, Novosielski, Ryan wrote:
These things are configured now in $XYMONCLIENT/bin/xymonclient-$OSTYPE.sh.
Thanks for the tip! It appears that this line is the culprit:

EXCLUDES=`cat /proc/filesystems | grep nodev | awk '{print $2}' | xargs echo | sed -e 's! ! -x !g'`;

It produces a bunch of "-x $filetype -x $filetype..." output used as an exclusion for the df command. The output
of this line includes "-x zfs" in the output. Sadly, zfs is marked "nodev" because it isn't mounted on a normal block device! So a quick hack is to change to

EXCLUDES=`cat /proc/filesystems | grep nodev | grep -v zfs | awk '{print $2}' | xargs echo | sed -e 's! ! -x !g'`;

This is by no means a good idea. Better suggestions? Perhaps it would be a good idea to add a whitelist or something?

Thanks. Ben
list Ryan Novosielski · Thu, 13 Mar 2014 21:59:07 -0400 ·
I actually don't think that's the worst solution. 
quoted from Benjamin Smith

----- Original Message -----
From: Lists [mailto:user-bd60c1f964ce@xymon.invalid]
Sent: Thursday, March 13, 2014 09:41 PM
To: xymon at xymon.com <xymon at xymon.com>
Subject: Re: [Xymon] Support for ZFS?

I sent the below message a few days ago, but sent it to Ryan rather than the list. I'd really like to see if there's a "more righter" way to do this than the somewhat hackish response below.

-Ben

/////////////////

On 03/11/2014 01:36 PM, Novosielski, Ryan wrote:
These things are configured now in $XYMONCLIENT/bin/xymonclient-$OSTYPE.sh.
Thanks for the tip! It appears that this line is the culprit:

EXCLUDES=`cat /proc/filesystems | grep nodev | awk '{print $2}' | xargs echo | sed -e 's! ! -x !g'`;

It produces a bunch of "-x $filetype -x $filetype..." output used as an exclusion for the df command. The output
of this line includes "-x zfs" in the output. Sadly, zfs is marked "nodev" because it isn't mounted on a normal block device! So a quick hack is to change to

EXCLUDES=`cat /proc/filesystems | grep nodev | grep -v zfs | awk '{print $2}' | xargs echo | sed -e 's! ! -x !g'`;

This is by no means a good idea. Better suggestions? Perhaps it would be a good idea to add a whitelist or something?

Thanks. Ben