cp command problem
cp command problem
Hi,
I am using Lucid puppy 5.2.0, full installation.
Yesterday I tried to copy a 2 gb file from pen drive to hard disk.
After 1.6 gb copied, there was a message in terminal, "KILLED".
and copy couldn't complete.
I tried again and there was a message, "I/O error".
And surprisingly my pen drive mount point changed from sdb to sdc.
Have you ever seen any such problem?
Does cp command work for >= 2 GB file?
I tried to see what is causing error. htop was showing memory usage for cp as follows:
Mem [********||@@@@@@@@@@@@@ 78/378MB]
where,
****** = used
|| = buffers
@@@@@@@@@@@@ = cache
Sincerely,
Srinivas Nayak
I am using Lucid puppy 5.2.0, full installation.
Yesterday I tried to copy a 2 gb file from pen drive to hard disk.
After 1.6 gb copied, there was a message in terminal, "KILLED".
and copy couldn't complete.
I tried again and there was a message, "I/O error".
And surprisingly my pen drive mount point changed from sdb to sdc.
Have you ever seen any such problem?
Does cp command work for >= 2 GB file?
I tried to see what is causing error. htop was showing memory usage for cp as follows:
Mem [********||@@@@@@@@@@@@@ 78/378MB]
where,
****** = used
|| = buffers
@@@@@@@@@@@@ = cache
Sincerely,
Srinivas Nayak
1. "Have you ever seen any such problem?"
(a) Yes, when I was attempting to copy files from an external [USB2.0 connected] HDD with "bad blocks".
Most of the files would copy OK, but whenever I attempted to copy a file, part of which resided on a bad region of the drive...
The copy would fail at that point.
(b) Perhaps you should use GParted to "check"->[scan & fix] the file systems of the source and destination partitions.
2. "my pen drive mount point changed from sdb to sdc"
(a) Did the OS suddenly detect the presence of another partition [file system] at that instant in time?
3. "yep...2gig limit for FAT drive"
Wouldn't it be OK to copy a 2GB file?
Within the 2GB limit?
(a) Yes, when I was attempting to copy files from an external [USB2.0 connected] HDD with "bad blocks".
Most of the files would copy OK, but whenever I attempted to copy a file, part of which resided on a bad region of the drive...
The copy would fail at that point.
(b) Perhaps you should use GParted to "check"->[scan & fix] the file systems of the source and destination partitions.
2. "my pen drive mount point changed from sdb to sdc"
(a) Did the OS suddenly detect the presence of another partition [file system] at that instant in time?
3. "yep...2gig limit for FAT drive"
Wouldn't it be OK to copy a 2GB file?
Within the 2GB limit?
2. Yes, OS suddenly show me presence of sdc on desktop. But sdb was not there any more.Sylvander wrote:1. "Have you ever seen any such problem?"
(a) Yes, when I was attempting to copy files from an external [USB2.0 connected] HDD with "bad blocks".
Most of the files would copy OK, but whenever I attempted to copy a file, part of which resided on a bad region of the drive...
The copy would fail at that point.
(b) Perhaps you should use GParted to "check"->[scan & fix] the file systems of the source and destination partitions.
2. "my pen drive mount point changed from sdb to sdc"
(a) Did the OS suddenly detect the presence of another partition [file system] at that instant in time?
3. "yep...2gig limit for FAT drive"
Wouldn't it be OK to copy a 2GB file?
Within the 2GB limit?
3. Actually I made a 2 gb img file for using with qemu. that 2gb file I was transferring from pendrive to disk.
And, why there is such a limit on file size to copy? I think other linux OSs don't have that!
Many thanks for your suggestions on pen drive checking.
I'll do that.
Sincerely,
Srinivas
Is split command comes by default with puppy 5.2.0?jpeps wrote:It appears not...I'd try split. Then again, never trust a pen drive.Sylvander wrote:
3. "yep...2gig limit for FAT drive"
Wouldn't it be OK to copy a 2GB file?
Within the 2GB limit?
Or I need to install some PET package?
Sincerely,
Srinivas