Bug 461901

Summary: rcp does not return ENOSPC error on full NFS-File system
Product: Red Hat Enterprise Linux 4 Reporter: Tomas Smetana <tsmetana>
Component: rshAssignee: Adam Tkac <atkac>
Status: CLOSED CURRENTRELEASE QA Contact: qe-baseos-daemons
Severity: high Docs Contact:
Priority: urgent    
Version: 4.6CC: jplans, jwest, ovasik, rvokal, sghosh
Target Milestone: rcKeywords: EasyFix, Patch, ZStream
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-06-14 20:39:14 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 509363    
Attachments:
Description Flags
Proposed patch for rsh-0.17-25.4 none

Description Tomas Smetana 2008-09-11 09:54:33 UTC
Created attachment 316407 [details]
Proposed patch for rsh-0.17-25.4

When using rcp to copy files to/from a NFS volume rcp doesn't report an error if the filesystem is full already, e.g.:

rcp biglocalfile remoteserver:/nfsshare/

Where bigfile is big enough to fill the "nfsshare", no error appears.  This may lead to silent data loss.

This is caused by NFS not reporting an error (ENOSPC) during write(2) but just in the close(2) calls (more info in the close manual page).

Comment 1 Tomas Smetana 2008-09-11 09:55:41 UTC
The same bug for krb5: bug #461900

Comment 2 Adam Tkac 2008-09-16 11:17:40 UTC
Right you are and thanks for patch, looks fine for me

Comment 3 RHEL Program Management 2008-10-31 16:44:39 UTC
This request was evaluated by Red Hat Product Management for
inclusion, but this component is not scheduled to be updated in
the current Red Hat Enterprise Linux release. If you would like
this request to be reviewed for the next minor release, ask your
support representative to set the next rhel-x.y flag to "?".