search for: write_io_err

Displaying 11 results from an estimated 11 matches for "write_io_err".

Did you mean: write_io_errs
2013 Aug 16
2
[PATCH] xfstests: update filters and output of btrfs/006
...nt - <NUMDEVS> [SCRATCH_DEV].corruption_errs <NUM> - <NUMDEVS> [SCRATCH_DEV].flush_io_errs <NUM> - <NUMDEVS> [SCRATCH_DEV].generation_errs <NUM> - <NUMDEVS> [SCRATCH_DEV].read_io_errs <NUM> - <NUMDEVS> [SCRATCH_DEV].write_io_errs <NUM> + <NUMDEVS> [SCRATCH_DEV].corruption_errs <NUM> + <NUMDEVS> [SCRATCH_DEV].flush_io_errs <NUM> + <NUMDEVS> [SCRATCH_DEV].generation_errs <NUM> + <NUMDEVS> [SCRATCH_DEV].read_io_errs <NUM> + <NUMDEVS> [SCRATCH_DEV].write_io_errs &lt...
2015 Jun 17
2
Re: [PATCH] New API: btrfs_device_stats
...(argv, i, NULL); >> + >> + r = commandv (&out, &err, argv); >> + if (r == -1) { >> + reply_with_error ("%s: %s", path, err); >> + return NULL; >> + } >> + >> + /* Output pattern is: >> + * >> + * [/dev/sda].write_io_errs 0 >> + * [/dev/sda].read_io_errs 0 >> + * [/dev/sda].flush_io_errs 0 >> + * [/dev/sda].corruption_errs 0 >> + * [/dev/sda].generation_errs 0 >> + * >> + */ >> + >> + /* Read the lines and split into "key: value". */ &...
2015 Jun 17
0
Re: [PATCH] New API: btrfs_device_stats
...; + if (add_string (&ret, value) == -1) > >> + return NULL; > >> + > >> + p = analyze_line(p, &key, &value, ' '); > >> + } > > > > This means that the return "hash" will have keys like: > > [/dev/sda].write_io_errs > > ? Wouldn't it better to just return the name of the attribute, i.e. > > write_io_errs > > ? > > In the condition that the btrfs have multi devices, its original output > is going to this way: > [/dev/sda].write_io_errs 0 > [/dev/sda].read_io_er...
2015 Jun 16
2
[PATCH] New API: btrfs_device_stats
...ERO_BITMASK) && zero) { + ADD_ARG (argv, i, "-z"); + } + + ADD_ARG (argv, i, NULL); + + r = commandv (&out, &err, argv); + if (r == -1) { + reply_with_error ("%s: %s", path, err); + return NULL; + } + + /* Output pattern is: + * + * [/dev/sda].write_io_errs 0 + * [/dev/sda].read_io_errs 0 + * [/dev/sda].flush_io_errs 0 + * [/dev/sda].corruption_errs 0 + * [/dev/sda].generation_errs 0 + * + */ + + /* Read the lines and split into "key: value". */ + p = analyze_line(out, &key, &value, ' '); + while(key...
2015 Jun 19
2
[PATCH v2 1/2] Modify the function: analyze_line, make it more flexible
Mofify the function from a fixed delimiter to a variable. So, it can be used in more APIs later. Also modified the existing callers Signed-off-by: Cao jin <caoj.fnst@cn.fujitsu.com> --- daemon/btrfs.c | 14 +++++++------- 1 file changed, 7 insertions(+), 7 deletions(-) diff --git a/daemon/btrfs.c b/daemon/btrfs.c index 39392f7..caa28ca 100644 --- a/daemon/btrfs.c +++ b/daemon/btrfs.c @@
2015 Jun 18
3
Re: [PATCH] New API: btrfs_device_stats
...(&ret, value) == -1) >>>> + return NULL; >>>> + >>>> + p = analyze_line(p, &key, &value, ' '); >>>> + } >>> >>> This means that the return "hash" will have keys like: >>> [/dev/sda].write_io_errs >>> ? Wouldn't it better to just return the name of the attribute, i.e. >>> write_io_errs >>> ? >> >> In the condition that the btrfs have multi devices, its original output >> is going to this way: >> [/dev/sda].write_io_errs 0 >...
2015 Jun 16
0
Re: [PATCH] New API: btrfs_device_stats
...uot;); > + } > + > + ADD_ARG (argv, i, NULL); > + > + r = commandv (&out, &err, argv); > + if (r == -1) { > + reply_with_error ("%s: %s", path, err); > + return NULL; > + } > + > + /* Output pattern is: > + * > + * [/dev/sda].write_io_errs 0 > + * [/dev/sda].read_io_errs 0 > + * [/dev/sda].flush_io_errs 0 > + * [/dev/sda].corruption_errs 0 > + * [/dev/sda].generation_errs 0 > + * > + */ > + > + /* Read the lines and split into "key: value". */ > + p = analyze_line(out, &am...
2015 Jun 19
3
[PATCH v3 1/2] Modify the function: analyze_line, make it more flexible
Mofify the function from a fixed delimiter to a variable. So, it can be used in more APIs later. Also modified the existing callers Signed-off-by: Cao jin <caoj.fnst@cn.fujitsu.com> --- daemon/btrfs.c | 14 +++++++------- 1 file changed, 7 insertions(+), 7 deletions(-) diff --git a/daemon/btrfs.c b/daemon/btrfs.c index 39392f7..caa28ca 100644 --- a/daemon/btrfs.c +++ b/daemon/btrfs.c @@
2015 Jun 19
0
[PATCH v2 2/2] New API: btrfs_device_stats
...;device"); + ADD_ARG (argv, i, "stats"); + ADD_ARG (argv, i, buf); + ADD_ARG (argv, i, NULL); + + r = commandv (&out, &err, argv); + if (r == -1) { + reply_with_error ("%s: %s", path, err); + return NULL; + } + + /* Output pattern is: + * [/dev/sda].write_io_errs 0 + * [/dev/sda].read_io_errs 0 + * [/dev/sda].flush_io_errs 0 + * [/dev/sda].corruption_errs 0 + * [/dev/sda].generation_errs 0 + * [/dev/sdb].write_io_errs 0 + * [/dev/sdb].read_io_errs 0 + * [/dev/sdb].flush_io_errs 0 + * [/dev/sdb].corruption_errs...
2015 Jun 19
0
[PATCH v3 2/2] New API: btrfs_device_stats
...;device"); + ADD_ARG (argv, i, "stats"); + ADD_ARG (argv, i, buf); + ADD_ARG (argv, i, NULL); + + r = commandv (&out, &err, argv); + if (r == -1) { + reply_with_error ("%s: %s", path, err); + return NULL; + } + + /* Output pattern is: + * [/dev/sda].write_io_errs 0 + * [/dev/sda].read_io_errs 0 + * [/dev/sda].flush_io_errs 0 + * [/dev/sda].corruption_errs 0 + * [/dev/sda].generation_errs 0 + * [/dev/sdb].write_io_errs 0 + * [/dev/sdb].read_io_errs 0 + * [/dev/sdb].flush_io_errs 0 + * [/dev/sdb].corruption_errs...
2015 Jun 17
3
[PATCH v2 1/2] Modify public function: analyze_line, make it more flexible
Mofify the function from fixed dilemiter to variabler. So, it could be used in more APIs later. Also modified the existed caller Signed-off-by: Cao jin <caoj.fnst@cn.fujitsu.com> --- daemon/btrfs.c | 14 +++++++------- 1 file changed, 7 insertions(+), 7 deletions(-) diff --git a/daemon/btrfs.c b/daemon/btrfs.c index 39392f7..caa28ca 100644 --- a/daemon/btrfs.c +++ b/daemon/btrfs.c @@