Bug 41282 - Strange errors when trying to copy data from a DVD to my HDD
Summary: Strange errors when trying to copy data from a DVD to my HDD
Status: RESOLVED OBSOLETE
Alias: None
Product: File System
Classification: Unclassified
Component: Other (show other bugs)
Hardware: All Linux
: P1 normal
Assignee: fs_other
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-08-17 05:34 UTC by Diego Viola
Modified: 2012-08-30 10:36 UTC (History)
1 user (show)

See Also:
Kernel Version: 3.0.1-ARCH
Subsystem:
Regression: No
Bisected commit-id:


Attachments
dmesg (263.01 KB, text/plain)
2011-08-17 05:34 UTC, Diego Viola
Details

Description Diego Viola 2011-08-17 05:34:59 UTC
Created attachment 69032 [details]
dmesg

I tried mounting a ISO file I have on my hard disk to /mnt, then copying the data from the ISO file to my HDD, both the ISO file and all the data are in the same HDD/partition.

Here is what I tried:

$ mount -o uid=1000 -t iso9660 /home/diego/tmp/Dead\ Space\ 2/flt-ds2a.iso /mnt
$ cp -a /mnt/* ~/ds

However, after a while of waiting for the data to copy, I noticed the HDD I/O and CPU utilization stopped at all. I tried to kill the process but the machine just froze, and I got tons of errors in dmesg (please see the file attached).

I tried to get the ISO file again, but the problem still persisted. I read this ISO and game has some DRM on it, could this be the cause? The size of this ISO file is about 5.5 GB.

I will try to reproduce the problem with other ISOs also and report back anything I find.

My machine specs:

Intel(R) Core(TM)2 Duo CPU     E7500  @ 2.93GHz
Arch Linux x86-64
2 GB of RAM.
kernel 3.0.1

Thanks.
Comment 1 Diego Viola 2011-08-17 05:35:53 UTC
I tried running a $(badblocks /dev/sda) in case if it was my HDD that was failing but it didn't found any errors.
Comment 2 Diego Viola 2011-08-17 05:37:27 UTC
oh I actually mounted the ISO file with this:

$ mount -o uid=1000 -t iso9660 -o loop /home/diego/tmp/Dead\ Space\ 2/flt-ds2a.iso /mnt

I believe I forgot to add the -o loop option. Sorry.

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