Displaying 3 results from an estimated 3 matches for "msg05135".
Did you mean:
msg00135
2018 Jul 28
1
Re: [PATCH] file: Fix zero/trim with block device
...re closely follow the flags (use
> FALLOC_FL_ZERO_RANGE when may_trim is false, and
> FALLOC_FL_PUNCH_HOLE when it is true; as well as tweak the
> .discard() callback to use
> FALLOC_FL_PUNCH_HOLE|FALLOC_FL_NO_HIDE_STALE).
>
> https://lists.gnu.org/archive/html/qemu-devel/2018-07/msg05135.html
>
> >@@ -254,7 +254,7 @@ file_zero (void *handle, uint32_t count, uint64_t offset, int may_trim)
> > #ifdef FALLOC_FL_ZERO_RANGE
> > r = fallocate (h->fd, FALLOC_FL_ZERO_RANGE, offset, count);
> >- if (r == -1 && errno != EOPNOTSUPP) {
> >+ if...
2018 Jul 27
4
[PATCH] file: Fix zero/trim with block device
When using block device on RHEL 7.5, file plugin fails to zero with this
error (copied from strace):
[pid 39551] fallocate(8, FALLOC_FL_ZERO_RANGE, 1536, 64000) = -1 ENODEV (No such device)
This is expected error according to the manual:
ENODEV fd does not refer to a regular file or a directory. (If fd is a
pipe or FIFO, a different error results.)
Treat this error as EOPNOSUPP.
Tested only
2018 Jul 27
0
Re: [PATCH] file: Fix zero/trim with block device
...gic in this
function to more closely follow the flags (use FALLOC_FL_ZERO_RANGE when
may_trim is false, and FALLOC_FL_PUNCH_HOLE when it is true; as well as
tweak the .discard() callback to use
FALLOC_FL_PUNCH_HOLE|FALLOC_FL_NO_HIDE_STALE).
https://lists.gnu.org/archive/html/qemu-devel/2018-07/msg05135.html
> @@ -254,7 +254,7 @@ file_zero (void *handle, uint32_t count, uint64_t offset, int may_trim)
>
> #ifdef FALLOC_FL_ZERO_RANGE
> r = fallocate (h->fd, FALLOC_FL_ZERO_RANGE, offset, count);
> - if (r == -1 && errno != EOPNOTSUPP) {
> + if (r == -1 &&a...