Public bug reported:
Package version 3.4.1-0ubuntu1
Architecture: AMD64
I had a large file-set to roll up into a zip file (a Clonezilla image: A
folder containing 44 files totalling 47GB on a USB drive). I call this
"Drive A". I connected a second drive ("Drive B") to the machine with
the intent that I would read the data from Drive A and write the zip
file to Drive B in order to avoid head-thrashing on Drive A and maximise
throughput.
I right clicked on the folder on Drive A and clicked "Compress..." I
used the destination pulldown to indicate I wanted the zip file to be
created on Drive B. I started the compression operation.
File-roller created the .zip.tmp file on Drive A in the same folder as
the object being compressed instead of on Drive B. This caused the drive
head-thrashing I'd been trying to avoid. When the operation was
complete, this file was moved to Drive B. This whole process obviously
took longer than it would have taken to do the compression just on Drive
A. I consider this behaviour sub-optimal.
Please will you modify File-roller's behaviour to create it tmp file on
the destination drive?
Thank you.
** Affects: file-roller (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to file-roller in Ubuntu.
https://bugs.launchpad.net/bugs/1241784
Title:
File roller creates tmp file on source drive regardless of where the
file destination is
Status in “file-roller” package in Ubuntu:
New
Bug description:
Package version 3.4.1-0ubuntu1
Architecture: AMD64
I had a large file-set to roll up into a zip file (a Clonezilla image:
A folder containing 44 files totalling 47GB on a USB drive). I call
this "Drive A". I connected a second drive ("Drive B") to the machine
with the intent that I would read the data from Drive A and write the
zip file to Drive B in order to avoid head-thrashing on Drive A and
maximise throughput.
I right clicked on the folder on Drive A and clicked "Compress..." I
used the destination pulldown to indicate I wanted the zip file to be
created on Drive B. I started the compression operation.
File-roller created the .zip.tmp file on Drive A in the same folder as
the object being compressed instead of on Drive B. This caused the
drive head-thrashing I'd been trying to avoid. When the operation was
complete, this file was moved to Drive B. This whole process obviously
took longer than it would have taken to do the compression just on
Drive A. I consider this behaviour sub-optimal.
Please will you modify File-roller's behaviour to create it tmp file
on the destination drive?
Thank you.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/file-roller/+bug/1241784/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
