Hello! Earlier, my plextor px708a happily wrote almost 4700000000 bytes (4.7GB in marketing speak). A couple of weeks ago, the troubles began. Growisofs still writes that much without an error message. But reading them back gives an IO error at about 4300000000 Bytes: ~ # dd if=/dev/cdrecorder of=/dev/null 8388604+0 records in 8388604+0 records out 4294965248 bytes (4.3 GB) copied, 964.8 seconds, 4.5 MB/s My first guess was that the media (RW) was bad, so I tried some new ones. Then, I decided to change the burner, but Plextor px716a has the same problem. Now I noticed that the error is always at the same position. Please note that 4294965248==0xfffff800, which looks pretty much like an integer overflow to me. When I installed suse-10.0 (professional, ot opensuse), everything worked as expected. Since I run YOU regularly, I assume that one of the updates is responsible for this problem. But I can't say which update exactly. Any ideas? BTW: ~ $ uname -a Linux raven 2.6.13-15.8-default #1 Tue Feb 7 11:07:24 UTC 2006 i686 athlon i386 GNU/Linux PS: I tried to search bugzilla, but it looks like a login is required to search it?
On 03/04/06, Josef Wolf <jw@raven.inka.de> wrote:
Hello!
Earlier, my plextor px708a happily wrote almost 4700000000 bytes (4.7GB in marketing speak). A couple of weeks ago, the troubles began. Growisofs still writes that much without an error message. But reading them back gives an IO error at about 4300000000 Bytes:
~ # dd if=/dev/cdrecorder of=/dev/null 8388604+0 records in 8388604+0 records out 4294965248 bytes (4.3 GB) copied, 964.8 seconds, 4.5 MB/s
My first guess was that the media (RW) was bad, so I tried some new ones. Then, I decided to change the burner, but Plextor px716a has the same problem.
Now I noticed that the error is always at the same position. Please note that 4294965248==0xfffff800, which looks pretty much like an integer overflow to me.
When I installed suse-10.0 (professional, ot opensuse), everything worked as expected. Since I run YOU regularly, I assume that one of the updates is responsible for this problem. But I can't say which update exactly.
Any ideas?
BTW: ~ $ uname -a Linux raven 2.6.13-15.8-default #1 Tue Feb 7 11:07:24 UTC 2006 i686 athlon i386 GNU/Linux
PS: I tried to search bugzilla, but it looks like a login is required to search it?
--
You could always register with Bugzilla. That way you could do the search. It should be open for anybody to register. -- ============================================== I am only human, please forgive me if I make a mistake it is not deliberate. ============================================== Xmas may be over but, PLEASE DON'T drink and drive you'll make it to the next one that way. Kevan Farmer Linux user #373362 Cheslyn Hay Staffordshire WS6 7HR
On Tue, Apr 04, 2006 at 04:28:05PM +0100, Kevanf1 wrote:
On 03/04/06, Josef Wolf <jw@raven.inka.de> wrote:
PS: I tried to search bugzilla, but it looks like a login is required to search it?
You could always register with Bugzilla. That way you could do the search. It should be open for anybody to register.
It seems to grant access again without login, but I could not find anything appropriate. Google wasn't very helpful, either. The only thing that seems to be related to my problem is http://www.archivum.info/packet-writing@suse.com/2004-12/msg00000.html But I don't use pktcdvd and/or pktsetup (at least, I'm not aware of it. What is this?) The answer to this mail, http://www.archivum.info/packet-writing@suse.com/2004-12/msg00022.html suggests that bd_set_size() should be called before accessing the device. Is there any way I can trigger bd_set_size(), just to check whether this would fix the problem?
participants (2)
-
Josef Wolf -
Kevanf1