Package: xfsprogs
Version: 4.9.0+nmu1
Severity: normal

Dear Maintainer,

I've discovered (in the hard way) that xfs_fsr does not report errors
by returning non-zero exit code.

Here's some examples:

# xfs_fsr /some/nonexiting/path; echo $?
xfs_fsr: could not stat: /some/nonexiting/path: No such file or
directory
0

# xfs_fsr /tmp/not_xfs; echo $?
xfs_fsr: cannot defragment: /tmp/not_xfs: Not XFS
0

This means there is no diagnostics for, let's say, failed
deframentation by cron job or systemd timer.


-- System Information:
Debian Release: 9.0
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: amd64 (x86_64)

Kernel: Linux 4.9.0-2-amd64 (SMP w/3 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages xfsprogs depends on:
ii  libblkid1     2.29.2-1
ii  libc6         2.24-9
ii  libreadline5  5.2+dfsg-3+b1
ii  libuuid1      2.29.2-1

xfsprogs recommends no packages.

Versions of packages xfsprogs suggests:
ii  acl      2.2.52-3+b1
pn  attr     <none>
pn  quota    <none>
pn  xfsdump  <none>

-- no debconf information

Reply via email to