fstrim: Needs to fire at the mp, not bd
It's a filesystem thing from this perspective.
+1b
Signed-off-by: Bernhard Reutner-Fischer <rep.dot.nop@gmail.com>
diff --git a/util-linux/fstrim.c b/util-linux/fstrim.c
index 84a6410..4d90fa7 100644
--- a/util-linux/fstrim.c
+++ b/util-linux/fstrim.c
@@ -60,7 +60,7 @@
int fstrim_main(int argc UNUSED_PARAM, char **argv)
{
struct fstrim_range range;
- char *arg_o, *arg_l, *arg_m, *bd;
+ char *arg_o, *arg_l, *arg_m, *mp;
unsigned opts;
int fd;
@@ -94,15 +94,15 @@
if (opts & OPT_m)
range.minlen = xatoull_sfx(arg_m, fstrim_sfx);
- bd = find_block_device(*(argv += optind));
- if (bd) {
- fd = xopen_nonblocking(bd);
+ mp = *(argv += optind);
+ if (find_block_device(mp)) {
+ fd = xopen_nonblocking(mp);
xioctl(fd, FITRIM, &range);
if (ENABLE_FEATURE_CLEAN_UP)
close(fd);
if (opts & OPT_v)
- printf("%s: %llu bytes were trimmed\n", bd, range.len);
+ printf("%s: %llu bytes were trimmed\n", mp, range.len);
return EXIT_SUCCESS;
}
return EXIT_FAILURE;