Bug#581339: bug reproduceable only via crontab

[Damon Timm]

(First time contributing a bug log here with Debian so bear with me.)

I am having the same problem on Debian Squeeze - however, I would add
that I only encounter this problem when running a lvcreate or lvremove
command via crontab.  Standard command line interaction does not produce
this bug.

Here is an example that reproduces the problem:

1. simple script (below)
2. run script as root (capture output)
3. run script in root's crontab (capture output)

The output is different between the crontab version and the command line
version.  The crontab version contains the errors.

[1] Here is the script I used:

# cat lv-test-script 
> #!/bin/bash
> /bin/date
> /bin/mkdir -p /mnt/tmp
> /sbin/lvcreate -L5G -s -n tmpdup /dev/raid5vg/home
> /bin/mount -t ext3 /dev/raid5vg/tmpdup /mnt/tmp-duplicity
> # this is where I do backup stuff, removed for brevity
> /bin/umount /mnt/tmp
> /sbin/lvremove -f /dev/raid5vg/tmpdup
> /bin/rmdir /mnt/tmp-duplicity
> /bin/date

[2] Here is the command I ran (first in the terminal then in crontab):

# /home/damon/Projects/sbin/lv-test-script >> /home/damon/logs/test.txt 2>&1

[3] And here is the output (first output is from command line and the bottom is from the cron task).

> Sun Jul 25 07:59:16 EDT 2010
>   Logical volume "tmpdup" created
>   Logical volume "tmpdup" successfully removed
> Sun Jul 25 07:59:18 EDT 2010
> Sun Jul 25 08:01:01 EDT 2010
> File descriptor 5 (/tmp/tmpf0sI4vF (deleted)) leaked on lvcreate invocation. Parent PID 22799: /bin/bash
>   Logical volume "tmpdup" created
> File descriptor 5 (/tmp/tmpf0sI4vF (deleted)) leaked on lvremove invocation. Parent PID 22799: /bin/bash
>   Logical volume "tmpdup" successfully removed
> Sun Jul 25 08:01:03 EDT 2010

Hope this helps shine some insight on the problem.  Am interested to know if the original submitter has the same circumstances.  

Am happy to test it further if I can be of assistance in fixing the bug.

Thanks,
Damon