search for: write_byte

Hi gurus, I like zpool iostat and I like system monitoring, so I setup a script within sma to let me get the zpool iostat figures through snmp. The problem is that as zpool iostat is only run once for each snmp query, it always reports a static set of figures, like so: root at exodus:snmp # zpool iostat -v capacity operations bandwidth pool used avail read

...-- 1 files changed, 5 insertions(+), 18 deletions(-) diff --git a/fs/btrfs/file.c b/fs/btrfs/file.c index dfe15dc..c1faded 100644 --- a/fs/btrfs/file.c +++ b/fs/btrfs/file.c @@ -57,15 +57,11 @@ static noinline int btrfs_copy_from_user(loff_t pos, int num_pages, PAGE_CACHE_SIZE - offset, write_bytes); struct page *page = prepared_pages[pg]; again: - /* - * Copy data from userspace to the current page - * - * Disable pagefault to avoid recursive lock since the pages - * are already locked - */ - pagefault_disable(); - copied = iov_iter_copy_from_user_atomic(page, i, offset,...

...raffic check I can see there is about 15 times more email traffic pulled from mail server than sent. The problem I am trying to track down is which users are the culprit. I have enabled doevcot stats and I can do a doveadm stats dump user but I get a 0 for disk_input, disk_output, read_bytes and write_bytes. I do get mail_read_bytes numbers but I am not sure these numbers are correct. I there a top utility that works well so I can see email traffic from users mailboxes. The doveadm top does not work well. I also tried the perl scripts and that does not do a much better job. Thanks Kilburn

...trfs/file.c @@ -1059,7 +1059,7 @@ static int prepare_uptodate_page(struct page *page, u64 pos) static noinline int prepare_pages(struct btrfs_root *root, struct file *file, struct page **pages, size_t num_pages, loff_t pos, unsigned long first_index, - unsigned long last_index, size_t write_bytes) + size_t write_bytes) { struct extent_state *cached_state = NULL; int i; @@ -1159,7 +1159,6 @@ static noinline ssize_t __btrfs_buffered_write(struct file *file, struct btrfs_root *root = BTRFS_I(inode)->root; struct page **pages = NULL; unsigned long first_index; - unsigned long...

...et errors like the following: RangeError: 1502 out of char range from /Users/szagerman/.rvm/gems/ruby-1.8.7-p249@eveo-vapps/gems/ openpgp-0.0.3/lib/openpgp/buffer.rb:138:in `chr'' from /Users/szagerman/.rvm/gems/ruby-1.8.7-p249@eveo-vapps/gems/ openpgp-0.0.3/lib/openpgp/buffer.rb:138:in `write_byte'' from /Users/szagerman/.rvm/gems/ruby-1.8.7-p249@eveo-vapps/gems/ openpgp-0.0.3/lib/openpgp/message.rb:129 from /Users/szagerman/.rvm/gems/ruby-1.8.7-p249@eveo-vapps/gems/ openpgp-0.0.3/lib/openpgp/message.rb:126:in `each'' from /Users/szagerman/.rvm/gems/ruby-1.8.7-p249@eveo-va...

V1->V2: Check to see if our current ppos is >= i_size after a short DIO read, just in case it was actually a short read and we need to just return. This is similar to what already happens in the write case. If we have a short read while doing O_DIRECT, instead of just returning, fallthrough and try to read the rest via buffered IO. BTRFS needs this because if we encounter a compressed or

...l" and "doveadm stats dump user/session", but talking about "doveadm stats dump user" and its output fields: user reset_timestamp last_update num_logins num_cmds user_cpu sys_cpu min_faults maj_faults vol_cs invol_cs disk_input disk_output read_count read_bytes write_count write_bytes mail_lookup_path mail_lookup_attr mail_read_count mail_read_bytes mail_cache_hits I'm not sure which of those fields can help me and I can't find any relevant documentation. So here are my questions: 1. is there a documentation for those 21 fields and for 'doveadm stats' in gene...

...s dump user/session", > > but talking about "doveadm stats dump user" and its output fields: > > > > user reset_timestamp last_update num_logins num_cmds user_cpu sys_cpu min_faults maj_faults vol_cs invol_cs disk_input disk_output read_count read_bytes write_count write_bytes mail_lookup_path mail_lookup_attr mail_read_count mail_read_bytes mail_cache_hits > > > > I'm not sure which of those fields can help me > > and I can't find any relevant documentation. > > > > So here are my questions: > > > > 1. is there a doc...

...ding = 0; + } else if (last_token == -2) { + run_start = token; + + } else if (nb != 0 || token != last_token + 1 + || token >= run_start + 65536) { + + /* output previous run */ + r = run_start - last_run_end; + n = last_token - run_start; + + if (r >= 0 && r <= 63) { + write_byte(f, (n==0? TOKEN_REL: TOKENRUN_REL) + r); + } else { + write_byte(f, (n==0? TOKEN_LONG: TOKENRUN_LONG)); + write_int(f, run_start); + } + if (n != 0) { + write_byte(f, n); + write_byte(f, n >> 8); + } + last_run_end = last_token; + run_start = token; + } + + last_token = token; +...

...Jun24 ? 00:06:25 /usr/bin/qemu-system-x86_64 ... [unrelevant data fields are ignored] Command line "virsh domblkstat $vmname vda” get the results below: vda rd_bytes 639415808 vda wr_bytes 728186880 Command line "cat /proc/4438/io” get the result below: read_bytes: 772415488 write_bytes: 734040064 I execute the above two commands consecutively using “&&", but we can that the results vary a lot, especially for the read_bytes. Since libvirt virDomainBlockStats API reads data from qemu i should ask the qemu folks for the answers. Great thanks, anyway. On Jun 25,...

.../session", >> > but talking about "doveadm stats dump user" and its output fields: >> > >> > user reset_timestamp last_update num_logins num_cmds user_cpu sys_cpu min_faults maj_faults vol_cs invol_cs disk_input disk_output read_count read_bytes write_count write_bytes mail_lookup_path mail_lookup_attr mail_read_count mail_read_bytes mail_cache_hits >> > >> > I'm not sure which of those fields can help me >> > and I can't find any relevant documentation. >> > >> > So here are my questions: >> > >&g...

...ing the output of the stats dump incorrectly): [root at wardentest3 mailtest]# doveadm stats dump -s /var/run/dovecot/mailtest/stats command user=warden cmd args session user last_update user_cpu sys_cpu min_faults maj_faults vol_cs invol_cs disk_input disk_output read_count read_bytes write_count write_bytes mail_lookup_path mail_lookup_attr mail_read_count mail_read_bytes mail_cache_hits select inbox 27fb87218302984f084c0000ae899e04 warden 1335362182.950250 0.000000 0.000000 172 0 46 0 0 12288 13 7883 4 381 0 0 0 0 0 search text "warden" 27fb87218302984f084c0000ae899e04 warden 1335362186.58...

This is a PoC patch for NFSv4/ZFS ACLs. The objective of the patch is that rsync --acls support NFSv4/ZFS ACLs without requiring a new command line option NFSv4 ACLs can't be represented using POSIX draft ACLs, if an NFSv4 ACL is present a separate POSIX draft ACL will not be present and there are new APIs to access NFSv4 ACLs. So we need to distinguish between NFSv4 ACLs and POSIX ACLs in

> Just curious: what about the rsync+ patch? Thanks for the reminder. I've just committed Jos's rsync+ patch onto the "branch_mbp_rsyncplus_merge" branch. If it works OK and nobody screams I will move it across onto the main tree tomorrow or Wednesday. I see the patch doesn't add documentation about the new options to the man page, so we should fix that in the future.

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Thu, 15 Oct 2015, Kilburn Abrahams wrote: > I have enabled doevcot stats and I can do a doveadm stats dump user but I > get a 0 for disk_input, disk_output, read_bytes and write_bytes. I do get > mail_read_bytes numbers but I am not sure these numbers are correct. my stats contain numbers greater than zero, except for very few users. Did you tested it with some account and waited a bit, incl. logins/logouts? - -- Steffen Kaiser -----BEGIN PGP SIGNATURE----- Version: Gnu...

...l reset_timestamp last_update num_logins num_cmds num_connected_sessions auth_successes auth_master_successes auth_failures auth_db_tempfails auth_cache_hits auth_cache_misses user_cpu sys_cpu clock_time min_faults maj_faults vol_cs invol_cs disk_input disk_output read_count read_bytes write_count write_bytes mail_lookup_path mail_lookup_attr mail_read_count mail_read_bytes mail_cache_hits 1478031539 0.000000 0 0 0 0 0 0 0 0 0 0.0 0.0 0.0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 Cheers, Ruud

...-02-06 11:37:39.000000000 -0500 +++ b/file.c 2008-02-06 16:46:23.000000000 -0500 @@ -37,6 +37,7 @@ #include "ordered-data.h" #include "ioctl.h" #include "print-tree.h" +#include "compat.h" static int btrfs_copy_from_user(loff_t pos, int num_pages, int write_bytes, @@ -790,7 +791,11 @@ static ssize_t btrfs_file_write(struct f goto out_nolock; if (count == 0) goto out_nolock; +#ifdef REMOVE_SUID_PATH + err = remove_suid(&file->f_path); +#else err = remove_suid(fdentry(file)); +#endif if (err) goto out_nolock; file_update_time(file);...

...rd wrote: [please don't top-post on technical lists] > Command line "virsh domblkstat $vmname vda” get the results below: > vda rd_bytes 639415808 > vda wr_bytes 728186880 > > Command line "cat /proc/4438/io” get the result below: > read_bytes: 772415488 > write_bytes: 734040064 Bear in mind that for some file formats, such as qcow2, qemu must read (and write) additional I/O to manage the metadata of the file in comparison to the amount of read and writes performed on behalf of the guest; the qemu numbers are reported from the guest perspective, not what qemu...

...ot;doveadm stats dump user/session", > but talking about "doveadm stats dump user" and its output fields: > > user reset_timestamp last_update num_logins num_cmds user_cpu sys_cpu min_faults maj_faults vol_cs invol_cs disk_input disk_output read_count read_bytes write_count write_bytes mail_lookup_path mail_lookup_attr mail_read_count mail_read_bytes mail_cache_hits > > I'm not sure which of those fields can help me > and I can't find any relevant documentation. > > So here are my questions: > > 1. is there a documentation for those 21 fields and...

Hi, all. While monitoring KVM VMs’ disk utilisation using libvirt API “virDomainBlockStats", I find that the results acquired is not consistent with the value read from /proc/[vm_pid]/io(i only care about “rd_bytes" and “wr_bytes” fields). Since libvirt doesn’t support host level monitoring, i have to calculate the host’s disk utilisation by reading from the /proc/diskstats file.