GNU bug report logs - #6970
gnu cp problem

Previous Next

To add a comment to this bug, you must first unarchive it, by sending
a message to control AT debbugs.gnu.org, with unarchive 6970 in the body.
You can then email your comments to 6970 AT debbugs.gnu.org in the normal way.

Toggle the display of automated, internal messages from the tracker.

Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):

From: Eric Blake <eblake <at> redhat.com>
To: Glenn Fowler <gsf <at> research.att.com>, bug-coreutils <bug-coreutils <at> gnu.org>
Subject: Re: gnu cp problem
Date: Wed, 01 Sep 2010 19:36:41 -0600

[adding bug-coreutils]

On 09/01/2010 06:14 PM, Glenn Fowler wrote:
>
> this is not related to posix / austin group
> feel free to forward this to the appropriate list

Hello Glenn, and thanks for the report.

>
> while trying to restore my daughters ipod after a
> catastrophic loss of the pc that held itunes I
> ran across a gnu cp problem
>
> --
> /bin/cp --version
> cp (GNU coreutils) 6.10
> Copyright (C) 2008 Free Software Foundation, Inc.

Would you mind trying again with coreutils 8.5?  A lot has changed in 
two years.

> 3 / ~3K files on the ipod had bad files
> ast pax those bad files reported EIO
> strace on ast pax on an EIO file showed something like
>
> 	read bufsize =>  bufsize
> 	read bufsize =>  bufsize
> 	...
> 	read bufsize =>  some-number-less-than-bufsize
> 	read bufsize =>  -1 EIO
>
> ast cp has a similar trace leading to non-zero exit
> but strace gnu cp on the same EIO file showed
>
> 	read bufsize =>  bufsize
> 	read bufsize =>  bufsize
> 	...
> 	read bufsize =>  some-number-less-than-bufsize
> 	...
> 	exit 0
>
> without looking at the gnu code my guess is that on
> the first read that returns>0 but less than the requested
> size it assumes it reached normal end of file -- had it done
> one more read it would have discovered the reason for the
> short read =>  EIO

I believe this particular bug was fixed in 2009, with this commit:
http://git.sv.gnu.org/cgit/coreutils.git/commit/?id=c74fbae

which, although it was written with /proc in mind, looks like it has the 
nice side effect of also dealing with your EIO problem.

-- 
Eric Blake   eblake <at> redhat.com    +1-801-349-2682
Libvirt virtualization library http://libvirt.org

Message #10 received at 6970 <at> debbugs.gnu.org (full text, mbox):

From: Bob Proulx <bob <at> proulx.com>
To: Eric Blake <eblake <at> redhat.com>
Cc: gsf <at> research.att.com, 6970 <at> debbugs.gnu.org
Subject: Re: bug#6970: gnu cp problem
Date: Wed, 12 Sep 2012 15:17:55 -0600

It has been quite a while since 01 Sep 2010 when this bug ticket last
had any activity.

  http://debbugs.gnu.org/cgi/bugreport.cgi?bug=6970

Has the relevance of this issue expired?

Thanks,
Bob

Message #13 received at 6970 <at> debbugs.gnu.org (full text, mbox):

From: Assaf Gordon <assafgordon <at> gmail.com>
To: 6970 <at> debbugs.gnu.org
Subject: Re: bug#6970: gnu cp problem
Date: Mon, 22 Oct 2018 20:43:10 -0600

close 6970
stop

(triaging old bugs)

On 12/09/12 03:17 PM, Bob Proulx wrote:
> It has been quite a while since 01 Sep 2010 when this bug ticket last
> had any activity.
> 
>    http://debbugs.gnu.org/cgi/bugreport.cgi?bug=6970
> 
> Has the relevance of this issue expired?
> 

With no further comments in 6 years
(when Bob asked about no activity for 2 more years),
I'm closing this bug.

-assaf

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.