Propose your solution
Attachments
No attachments.
Duplicates
Comments
|
edm1
wrote on the 8 Apr 08 at 15:54
|
|
|
|
This is one of the reasons for the recent implementation of GVFS as a nautilus backend. If the pause option isnt in hardy i'm sure it will be in Octobers Intrepid Ibex.
|
|
|
|
I voted it up, but, on second thought, what would be the use of such a feature?
|
|
sf_007
wrote on the 8 Apr 08 at 19:13
|
|
|
Absolutely, for example, when moving/copying more than 50 GB at a time...
it would be very usefull.
|
|
Garoth
wrote on the 8 Apr 08 at 19:27
|
|
|
So... I'm going to be coping 50 gb all the time between partitions and then suddenly realize that I want to put that off until I do something else and then come back to it? Meh, sounds like a wasteful feature. I know that copy operations might take a while and set aside time for them. They also don't happen very often for most people.
Regardless, this feature may be implemented by Gnome as part of the aforementioned GVFS move. I have actually heard that they plan to do this.
|
|
madneon
wrote on the 8 Apr 08 at 20:21
|
|
|
|
Last time I was making copy of my 300GB HDD on Ubuntu running on Core 2 Duo T7300 with 2xSATA disks I was forced to.. go shopping for an hour. ;)
|
|
bryhoyt
wrote on the 8 Apr 08 at 21:50
|
|
|
+1
It's useful when copying stuff from a medium that's slow to do random accesses. CDROMs are a good example. Try copying a lot of big photos from a CDROM to your hard drive. Then, while that's happening, try browsing another directory on the same CDROM. It's *incredibly* slow, because the laser has to jump all over the place, and spin the CD till it gets to the right place.
It has to keep doing that back-and-forth to try and keep up the appearance of being able to both simultaneously. But it's very bad at it. It's much quicker to do both operations sequentially.
Or, if we implement this feature, pause in the middle.
|
|
blindvic
wrote on the 10 Apr 08 at 06:35
|
|
|
|
And add operation queue like in Total Commander
|
|
orvils
wrote on the 10 Apr 08 at 06:42
|
|
|
|
agree... Keep it simple -1
|
|
elisee
wrote on the 10 Apr 08 at 10:36
|
|
|
... wow, you really think being able to pause means being complicated? come on it's just a button!
Of course it should be the simple by default, but one should never be prevented from using more advanced features if he knows what he does, by enabling them somewhere. Being simple and uncluttered does not mean being unconfigurable!
|
|
roberthr
wrote on the 24 Apr 08 at 17:03
|
|
|
|
I vote for this feature! I was a Total Commander user for ages and what I really miss on Linux is application like TCMD. Gnome added nice feature for copying files now, but it's not really nice for copying or moving large files to/from different directories to/from different hard drives. It really drives me crazy that I have to wait for each operation to finish and there could be something like "add to queue" or pause button on list of operations. Lats time I added 3 different directories including large files, I found out that one of those directories was the one I needed the most and first. I didn't want to cancel and do it all over again but I had to wait for another 30 minutes before I could continue working. In the perspective of usability, not having this implemented, makes in really unusable.
|
|
bobpaul
wrote on the 5 Aug 08 at 06:35
|
|
|
>"So... I'm going to be coping 50 gb all the time between partitions and then suddenly realize that I want to put that off until I do something else and then come back to it? Meh, sounds like a wasteful feature."
I use encfs to encrypt my home folder on my laptop. This slows down disk operations substantially (basically, I no longer have DMA on files in my home folder, as they all must be sent through the processor for decryption). I also regularly copy 2-3GB files to/from my home folder and a local network share. During these operations, CPU load increases as does network usage. There are times where, 15 min after a copy has started I realize I need to do something else that could benefit from these resources. Sometimes, it's important enough I cancel my move/copy and restart it later. What a drag!
Additionally, there are times I'll copy many different files such that I have multiple copy/move operations going on simultaneously. If I could pause and resume operations, I could ensure that the most important file copy finishes first without having to cancel operations already in progress. This would be an extremely useful feature.
|
|
JohnLM
wrote on the 16 Jan 09 at 16:36
|
|
|
Idea #16615 is related, but not a dupe! It is about queuing
I'm sure that idea is more useful and makes more sense... but both can be implemented at the same time!
|
|
Giwex
wrote on the 10 Jul 09 at 10:00
|
|
|
|
One of the reasons I would like this feature implemented is that using a laptop during large files copy/transfer the HD might become very hot and thus you could wish to pause the action to let the drive to cool down.
|
|
|
Currently, there are two things when a connection was interrupted - "Skip" and "Skip all". For this screen the "Retry" button should be added.
And in addition to the "Overwrite" button the "Resume" button should be added.
|
|
|
I think basic need is:
1) Cancel : in case of mistake
2) Pause/restart : in case of HD becoming hot, or system becoming slow
as the behaviour in Karmic is not convenient IMHO, i proposed Solution #5.
I believe more options would be too much. For those who want more options for special needs, some advanced copy softwares are available on Ubuntu, such as UltraCopier (http://ultracopier.first-world.info/)
|
|
robharg
wrote on the 6 Mar 10 at 11:29
|
|
|
I like every proposal on this page to enhance the copy/move functionality, and think it is necessary, I appreciate most want to keep it simple but a pause button, alongside a "simple/advanced" toggle would easily keep everyone happy.
As an addition to the proposed ideas, I would like to see a clearer bitrate readout, maybe in the form of a mini scrolling graph. This would be useful to determine instantaneous bitrate vs average. For example, i'm currently copying 75Gb of data between two USB disks and am just about to start transcoding some music (which will be processor intensive but not disk intensive). With a mini graph i'll be able to see how much I am affecting disk performance by using the processor-at the moment I know it is affecting it but the readout I currently have seems to be an average since the start of the copy. This may sound rather too much for some people, but anyone who regularly copies data and understands their hardware will be able to use this enhanced functionality to "improve productivity :-)". I will now be looking for alternative copy software but strongly believe an advanced option should be included by default.
|
|
EUGiNE
wrote on the 17 Nov 10 at 01:12
|
|
|
Very useful; use cases:
1. When copying multiple directories or large files, selected individually, all data transfers occur in parallel rather than sequentially. This is problematic when using sequential storage devices like disk drives.
2. Make a certain copy operation finish sooner by temporarily pausing a competing, lengthy copy operation.
Eg 1. While transferring a 10GB backup file over the network, need to retrieve a large folder of work documents and data from the network.
Eg 2. While copying a few videos at a time from a DVD, need to quickly copy a picture folder from the DVD onto a usb flash drive to give to someone.
3. When transferring data over an inconsistent wireless connection like that provided by low end routers whose transfer rate periodically drops to zero during a sustained data transfer operation. This occasionally causes a file transfer to time out, forcing the user to skip one or more files in the folder being transferred, and then find and transfer them manually. A "retry" option would allow the file transfer to be resumed instead in the same way as after a manual "pause".
4. Sustained data transfer over/to many low end devices (most visible consumer devices) such as usb wireless network adapters or external hard drives causes them to overheat and so large data transfers should be paused.
5. (Slowly) transferring a directory containing very many small files on a laptop causes a lot of disk thrashing that visibly kills the performance of all other tasks while the CPU repeatedly locks into io_wait state. Starting a browser, opening a menu, playing a small video, or opening a calendar all become visibly slow tasks. Instead of suddenly canceling the file transfer and resuming it a minute later, the user could simply pause it.
|
|
EUGiNE
wrote on the 17 Nov 10 at 01:32
|
|
|
6. When transferring files over an ftp or sftp connection using nautilus:
a) pausing the data transfer would free up network bandwidth for another task instead of saturating it with the file transfer.
b) resuming file transfers would allow recovery from inconsistent timeouts or disconnection from a dial-up connection, whether purposeful or not.
|
Post your comment
|
