Bug 691644 - Filesystem logging
Summary: Filesystem logging
Keywords:
Status: CLOSED DUPLICATE of bug 457787
Alias: None
Product: Red Hat Enterprise Linux 5
Classification: Red Hat
Component: kernel
Version: 5.4
Hardware: Unspecified
OS: Linux
medium
medium
Target Milestone: rc
: ---
Assignee: Red Hat Kernel Manager
QA Contact: Red Hat Kernel QE team
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-03-29 06:13 UTC by Anand Vaddarapu
Modified: 2011-04-04 04:06 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-04-04 04:06:37 UTC
Target Upstream Version:

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Description Anand Vaddarapu 2011-03-29 06:13:00 UTC 
Description of problem:
I would like to enable logging to /var/log/messages whenever a filesystem reaches 100%. How would I enable that? Logging kern.* does not seem to pick it up. 


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


How reproducible:


Steps to Reproduce:
1.
2.
3.
  
Actual results:


Expected results:


Additional info:
Comment 1 Ondrej Vasik 2011-03-29 07:40:08 UTC 
Filesystem is package with basic system directory layout. It has nothing to do with logging of kernel information. Reassigning to kernel guys.
Comment 2 Eric Sandeen 2011-03-31 15:33:11 UTC 
I think this is a dup of Bug #457787

ENOSPC can come about a few different ways; (no blocks left; no inodes left; no space left in xattr, etc) but we should be able to get tracepoints in reasonable spots to detect this, I'd think.
Comment 3 Jeremy West 2011-04-04 04:06:37 UTC 
Thanks for the input Eric.  Indeed, the customer request here matches the problem stated in BZ 457787

*** This bug has been marked as a duplicate of bug 457787 ***
Note You need to log in before you can comment on or make changes to this bug.