Bug 691644

Summary:	Filesystem logging
Product:	Red Hat Enterprise Linux 5	Reporter:	Anand Vaddarapu <avaddara>
Component:	kernel	Assignee:	Red Hat Kernel Manager <kernel-mgr>
Status:	CLOSED DUPLICATE	QA Contact:	Red Hat Kernel QE team <kernel-qe>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	5.4	CC:	esandeen, jwest, lczerner, rwheeler
Target Milestone:	rc
Target Release:	---
Hardware:	Unspecified
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2011-04-04 04:06:37 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:

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 ***