Bug 231475 - zz-disk_space verifies non-local partitions
zz-disk_space verifies non-local partitions
Product: Red Hat Enterprise Linux 4
Classification: Red Hat
Component: coreutils (Show other bugs)
i386 Linux
medium Severity low
: ---
: ---
Assigned To: Ondrej Vasik
Depends On:
  Show dependency treegraph
Reported: 2007-03-08 11:35 EST by Andrew Pierson
Modified: 2009-07-11 16:34 EDT (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2009-07-11 16:34:48 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Andrew Pierson 2007-03-08 11:35:34 EST
Description of problem:

Connecting to a multi-homed nfs server through a firewall causes this to hang. 
Adding the -l option to df causes it to only check local filesystems.

Version-Release number of selected component (if applicable):

Logwatch 5.2.2 (released 06/23/04)

How reproducible:


Steps to Reproduce:
1. Connect to multi-homed nfs server
2. Hide behind a nat
3. logwatch runs.
Actual results:

zz-disk_space hangs

Expected results:

Timeout, failure, or cease checking remote filesystems.

Additional info:

Have a nice day!  The file is located here on my system:

I put it at low severity, since nfs through nat to multi-homed systems doesn't
work to begin with.  The problem is once you enter that configuration, the
logwatch processes will stack up as they hang.
Comment 1 Ivana Varekova 2007-10-26 04:41:16 EDT
This seems to be coreutils problem - logwatch uses df to generate disk_space report.
Comment 2 Kamil Dudka 2008-09-18 08:56:21 EDT
Could you please try to run 'df' on that machine? If 'df' hangs, can you attach the output of 'strace df'? Thanks in advance.

Can you access the mount-points with something else than 'df' or 'logwatch'?
Comment 3 Ondrej Vasik 2009-07-11 16:34:48 EDT
Closing insufficient data, in needinfo for very long time. Feel free to reopen bugzilla once you provide data requested in comment #2.

Note You need to log in before you can comment on or make changes to this bug.