I am running an opennms server that stores performance related data in RRDs. they are stored under /opt/opennms/share/rrd/*. As I start to track more and more nodes with more specific OIDs (snmp), disk io is starting to climb steadily. What I am looking to do is move /opt/opennms/share/rrd from openpool and mount it under storage pool (storage/onms/rrd). more specifically, i want to do something like this:
Code:
cnjr-opennms>root$ zfs set mountpoint=/opt/opennms/share/rrd storage/onms/rrd
the problem here is i get:
Code:
cannot mount '/opt/opennms/share/rrd': directory is not empty
property may be set but unable to remount filesystem
So yes... the truth is there are plenty of directories beyond /opt/opennms/share/rrd/*. I'm just not sure how I can migrate this directory off openpool into storage.
Can anyone shed some light onto this. I am not 100% with zfs just yet but getting there
I was thinking about symbolic links but i'm not sure thats the best option here.
Hi all
I plan to install Solaris 10U6 on some SPARC server using ZFS as root pool, whereas I would like to keep the current setup done by VxVM:
- 2 internal disks: c0t0d0 and c0t1d0
- bootable root-volume (mirrored, both disks)
- 1 non-mirrored swap slice
- 1 non-mirrored slices for Live... (1 Reply)
I created a pool the other day. I created a 10 gig files just for a test, then deleted it.
I proceeded to create a few files systems. But for some reason the pool shows 10% full, but the files systems are both at 1%? Both files systems share the same pool.
When I ls -al the pool I just... (6 Replies)
Hi guys,
We had created a pool as follows:
zpool create filing_pool raidz c1t2d0 c1t3d0 ........
Due to some requirement, we need to destroy the pool and re-create another one. We wish to know now which disks have been included in the filing_pool, how do we list the disks used to create... (2 Replies)
I need to migrate an existing raidz pool to a new raidz pool with larger disks. I need the mount points and attributes to migrate as well. What is the best procedure to accomplish this. The current pool is 6x36GB disks 202GB capacity and I am migrating to 5x 72GB disks 340GB capacity. (2 Replies)
Other than export/import, is there a cleaner way to rename a pool without unmounting de FS?
Something like, say "zpool rename a b"?
Thanks. (2 Replies)
installed Solaris 11 Express on my server machine a while ago. I created a Z2 RAID over five HDDs and created a few ZFS filesystems on it.
Once I (unintentionally) managed to fill the pool completely with data and (to my surprise) the filesystems stopped working - I could not read/delete any... (3 Replies)
I have a branded zone txdjintra that utilizes a pool named Pool_djintra that is no longer required. There is a 150 Gig Lun assigned to the pool that I need to reassign to another branded zone txpsrsrv07 with a pool named Pool_txpsrsrv07 on the same sun blade. What is the process to do this?
... (0 Replies)
I accidently added a disk in different zpool instead of pool, where I want.
root@prtdrd21:/# zpool status cvfdb2_app_pool
pool: cvfdb2_app_pool
state: ONLINE
scan: none requested
config:
NAME STATE READ WRITE CKSUM
cvfdb2_app_pool ONLINE 0 0 0... (1 Reply)
I have a newly created zpool, and I have set compression on, for the whole pool:
# zfs set compression=on newPool
Now I have zfs send | zfs receive lot of snapshots to my newPool, but the compression is gone. I was hoping that I would be able to send snapshots to the new pool (which is... (0 Replies)
I have installed FreeBSD onto a raw image file using QEMU Emulator successfully. I have formatted the image file using the ZFS file system (ZFS POOL).
Using the following commands below I have successfully mounted the image file ready to be opened by zpool
sudo losetup /dev/loop0 .img sudo... (1 Reply)
Discussion started by: alphatron150
1 Replies
LEARN ABOUT DEBIAN
rrds
RRDs(3pm) User Contributed Perl Documentation RRDs(3pm)NAME
RRDs - Access RRDtool as a shared module
SYNOPSIS
use RRDs;
RRDs::error
RRDs::last ...
RRDs::info ...
RRDs::create ...
RRDs::update ...
RRDs::updatev ...
RRDs::graph ...
RRDs::fetch ...
RRDs::tune ...
RRDs::times(start, end)
RRDs::dump ...
RRDs::restore ...
RRDs::flushcached ...
DESCRIPTION
Calling Sequence
This module accesses RRDtool functionality directly from within Perl. The arguments to the functions listed in the SYNOPSIS are explained
in the regular RRDtool documentation. The command line call
rrdtool update mydemo.rrd --template in:out N:12:13
gets turned into
RRDs::update ("mydemo.rrd", "--template", "in:out", "N:12:13");
Note that
--template=in:out
is also valid.
The RRDs::times function takes two parameters: a "start" and "end" time. These should be specified in the AT-STYLE TIME SPECIFICATION
format used by RRDtool. See the rrdfetch documentation for a detailed explanation on how to specify time.
Error Handling
The RRD functions will not abort your program even when they can not make sense out of the arguments you fed them.
The function RRDs::error should be called to get the error status after each function call. If RRDs::error does not return anything then
the previous function has completed its task successfully.
use RRDs;
RRDs::update ("mydemo.rrd","N:12:13");
my $ERR=RRDs::error;
die "ERROR while updating mydemo.rrd: $ERR
" if $ERR;
Return Values
The functions RRDs::last, RRDs::graph, RRDs::info, RRDs::fetch and RRDs::times return their findings.
RRDs::last returns a single INTEGER representing the last update time.
$lastupdate = RRDs::last ...
RRDs::graph returns an ARRAY containing the x-size and y-size of the created image and a pointer to an array with the results of the PRINT
arguments.
($result_arr,$xsize,$ysize) = RRDs::graph ...
print "Imagesize: ${xsize}x${ysize}
";
print "Averages: ", (join ", ", @$averages);
RRDs::info returns a pointer to a hash. The keys of the hash represent the property names of the RRD and the values of the hash are the
values of the properties.
$hash = RRDs::info "example.rrd";
foreach my $key (keys %$hash){
print "$key = $$hash{$key}
";
}
RRDs::graphv takes the same parameters as RRDs::graph but it returns a pointer to hash. The hash returned contains meta information about
the graph. Like its size as well as the position of the graph area on the image. When calling with and empty filename than the contents of
the graph will be returned in the hash as well (key 'image').
RRDs::updatev also returns a pointer to hash. The keys of the hash are concatenated strings of a timestamp, RRA index, and data source name
for each consolidated data point (CDP) written to disk as a result of the current update call. The hash values are CDP values.
RRDs::fetch is the most complex of the pack regarding return values. There are 4 values. Two normal integers, a pointer to an array and a
pointer to a array of pointers.
my ($start,$step,$names,$data) = RRDs::fetch ...
print "Start: ", scalar localtime($start), " ($start)
";
print "Step size: $step seconds
";
print "DS names: ", join (", ", @$names)."
";
print "Data points: ", $#$data + 1, "
";
print "Data:
";
for my $line (@$data) {
print " ", scalar localtime($start), " ($start) ";
$start += $step;
for my $val (@$line) {
printf "%12.1f ", $val;
}
print "
";
}
RRDs::times returns two integers which are the number of seconds since epoch (1970-01-01) for the supplied "start" and "end" arguments,
respectively.
See the examples directory for more ways to use this extension.
NOTE
If you are manipulating the TZ variable you should also call the POSIX function tzset(3) to initialize all internal state of the library
for properly operating in the timezone of your choice.
use POSIX qw(tzset);
$ENV{TZ} = 'CET';
POSIX::tzset();
AUTHOR
Tobias Oetiker <tobi@oetiker.ch>
perl v5.14.2 2012-01-24 RRDs(3pm)