Package: quotatool
Version: 1.4.9-2
Severity: normal

*** Please type your report below this line ***
Hi,

this may need a retitle once we narrow down what is actually going wrong.

I was doing some tests of quotatool and found that on some combinations
of package versions it would fail because it was trying to do a quotactl()
call to a block device name with an extra octal byte appended, e.g.
  quotactl(Q_GETFMT|USRQUOTA, "/dev/loop0\362", ...) = -1 ENOENT

The specific test I was doing was running a simple dump:
  /usr/sbin/quotatool -u <user> -d /local/mnt
For speed, these tests are being done with an ext3 filesystem image,
which is why /dev/loop0 is involved.

The problem occurs on two separate systems running etch, but not on a third.
The only relevant difference I can see is that for the third host I was
using a host that is a local user, not one in the NIS user map. If I try
using a local user (username 'user', uid=1000) then quotatool works ok.

I also tested on a sarge system and a sarge+backports system, which
are in the same autofs+NIS environment as the etch boxes above.
On those hosts, quotatool (1.4.7-1) works.

Given the above, it may be that the bug is in some other package but
I thought I should start here. Something does seem to have changed
for the worse between 1.4.7-1 and 1.4.9-2, possibly an off-by-one
error in a string handling function.

I have shell scripts that can reproduce the problem and strace output
if you need that stuff.

Kind regards
Vince

-- System Information:
Debian Release: 4.0
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.18-4-686
Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8)

Versions of packages quotatool depends on:
ii  libc6                       2.3.6.ds1-13 GNU C Library: Shared libraries

Versions of packages quotatool recommends:
ii  quota                         3.14-5     implementation of the disk quota s

-- no debconf information



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to