Bug 461901 - rcp does not return ENOSPC error on full NFS-File system
Summary: rcp does not return ENOSPC error on full NFS-File system
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Enterprise Linux 4
Classification: Red Hat
Component: rsh
Version: 4.6
Hardware: All
OS: Linux
urgent
high
Target Milestone: rc
: ---
Assignee: Adam Tkac
QA Contact: qe-baseos-daemons
URL:
Whiteboard:
Depends On:
Blocks: 509363
TreeView+ depends on / blocked
 
Reported: 2008-09-11 09:54 UTC by Tomas Smetana
Modified: 2018-11-14 20:01 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-06-14 20:39:14 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
Proposed patch for rsh-0.17-25.4 (541 bytes, patch)
2008-09-11 09:54 UTC, Tomas Smetana
no flags Details | Diff

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 "?".


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