Re: [zfs-discuss] ZFS monitoring

2013-02-12 Thread Borja Marcos
On Feb 12, 2013, at 11:25 AM, Pawel Jakub Dawidek wrote: I made kstat data available on FreeBSD via 'kstat' sysctl tree: Yes, I am using the data. I wasn't sure about how getting something meaningful from it, but I've found the arcstats.pl script and I am using it as a model. Suggestions

[zfs-discuss] ZFS monitoring

2013-02-11 Thread Borja Marcos
Hello, I'n updating Devilator, the performance data collector for Orca and FreeBSD to include ZFS monitoring. So far I am graphing the ARC and L2ARC size, L2ARC writes and reads, and several hit/misses data pairs. Any suggestions to improve it? What other variables can be interesting? An

Re: [zfs-discuss] ZFS monitoring

2013-02-11 Thread Borja Marcos
On Feb 11, 2013, at 4:56 PM, Tim Cook wrote: The zpool iostat output has all sorts of statistics I think would be useful/interesting to record over time. Yes, thanks :) I think I will add them, I just started with the esoteric ones. Anyway, still there's no better way to read it than

[zfs-discuss] Puzzling problem with zfs receive exit status

2012-03-29 Thread Borja Marcos
Hello, I hope someone has an idea. I have a replication program that copies a dataset from one server to another one. The replication mechanism is the obvious one, of course: zfs send -Ri from snapshot(n-1) snapshot(n) file scp file remote machine (I do it this way instead of using a

Re: [zfs-discuss] Puzzling problem with zfs receive exit status

2012-03-29 Thread Borja Marcos
On Mar 29, 2012, at 11:59 AM, Ian Collins wrote: Does zfs receive produce any warnings? Have you tried adding -v? Thank you very much Ian and Carsten. Well, adding a -v gave me a clue. Turns out that one of the old snapshots had a clone created. zfs receive -v was complaining that it

Re: [zfs-discuss] Puzzling problem with zfs receive exit status

2012-03-29 Thread Borja Marcos
On Mar 29, 2012, at 5:11 PM, Richard Elling wrote: Thank you very much Ian and Carsten. Well, adding a -v gave me a clue. Turns out that one of the old snapshots had a clone created. zfs receive -v was complaining that it couldn't destroy an old snapshot, which wasn't visible but had