very slow file copying on same disk
Clash Royale CLAN TAG#URR8PPP up vote
0
down vote
favorite
On Ubuntu 16.02 LTS the copying time for a 1 MB file between directories on the same disk starts at about 0.02 seconds and increases to over 10 seconds as the session progresses. I am mainly using my own Fortran programs and none of them show any specific problems.
files copy
asked Apr 21 at 23:09
davd
11
add a comment |Â
up vote
0
down vote
favorite
On Ubuntu 16.02 LTS the copying time for a 1 MB file between directories on the same disk starts at about 0.02 seconds and increases to over 10 seconds as the session progresses. I am mainly using my own Fortran programs and none of them show any specific problems.
files copy
asked Apr 21 at 23:09
davd
11
1
I suspect its a fortran coding issue or compiler option and not Ubuntu related (assuming acpof the same files is quick). I'd suggest checking your code, then check compiler options (even the C code generated depending on compiler you are using). there was no february release in 2016, its 16.04 as it was in April
– guiverc
Apr 21 at 23:26
In a separate terminal window, watchjournalctl --followas you do your copies. That will show all log messages, including disk failures. Also, do you have swap space defined?
– waltinator
Apr 22 at 3:21
add a comment |Â
up vote
0
down vote
favorite
up vote
0
down vote
favorite
On Ubuntu 16.02 LTS the copying time for a 1 MB file between directories on the same disk starts at about 0.02 seconds and increases to over 10 seconds as the session progresses. I am mainly using my own Fortran programs and none of them show any specific problems.
files copy
asked Apr 21 at 23:09
davd
11
On Ubuntu 16.02 LTS the copying time for a 1 MB file between directories on the same disk starts at about 0.02 seconds and increases to over 10 seconds as the session progresses. I am mainly using my own Fortran programs and none of them show any specific problems.
files copy
asked Apr 21 at 23:09
davd
11
asked Apr 21 at 23:09
davd
11
asked Apr 21 at 23:09
davd
11
asked Apr 21 at 23:09
davd
11
11
1
I suspect its a fortran coding issue or compiler option and not Ubuntu related (assuming acpof the same files is quick). I'd suggest checking your code, then check compiler options (even the C code generated depending on compiler you are using). there was no february release in 2016, its 16.04 as it was in April
– guiverc
Apr 21 at 23:26
In a separate terminal window, watchjournalctl --followas you do your copies. That will show all log messages, including disk failures. Also, do you have swap space defined?
– waltinator
Apr 22 at 3:21
add a comment |Â
1
I suspect its a fortran coding issue or compiler option and not Ubuntu related (assuming acpof the same files is quick). I'd suggest checking your code, then check compiler options (even the C code generated depending on compiler you are using). there was no february release in 2016, its 16.04 as it was in April
– guiverc
Apr 21 at 23:26
In a separate terminal window, watchjournalctl --followas you do your copies. That will show all log messages, including disk failures. Also, do you have swap space defined?
– waltinator
Apr 22 at 3:21
1
1
I suspect its a fortran coding issue or compiler option and not Ubuntu related (assuming a
cp of the same files is quick). I'd suggest checking your code, then check compiler options (even the C code generated depending on compiler you are using). there was no february release in 2016, its 16.04 as it was in April– guiverc
Apr 21 at 23:26
I suspect its a fortran coding issue or compiler option and not Ubuntu related (assuming a
cp of the same files is quick). I'd suggest checking your code, then check compiler options (even the C code generated depending on compiler you are using). there was no february release in 2016, its 16.04 as it was in April– guiverc
Apr 21 at 23:26
In a separate terminal window, watch
journalctl --follow as you do your copies. That will show all log messages, including disk failures. Also, do you have swap space defined?– waltinator
Apr 22 at 3:21
In a separate terminal window, watch
journalctl --follow as you do your copies. That will show all log messages, including disk failures. Also, do you have swap space defined?– waltinator
Apr 22 at 3:21
add a comment |Â
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
Â
draft saved
draft discarded
Â
draft saved
draft discarded
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
var $window = $(window),
onScroll = function(e)
var $elem = $('.new-login-left'),
docViewTop = $window.scrollTop(),
docViewBottom = docViewTop + $window.height(),
elemTop = $elem.offset().top,
elemBottom = elemTop + $elem.height();
if ((docViewTop elemBottom))
StackExchange.using('gps', function() StackExchange.gps.track('embedded_signup_form.view', location: 'question_page' ); );
$window.unbind('scroll', onScroll);
;
$window.on('scroll', onScroll);
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1027057%2fvery-slow-file-copying-on-same-disk%23new-answer', 'question_page');
);
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
var $window = $(window),
onScroll = function(e)
var $elem = $('.new-login-left'),
docViewTop = $window.scrollTop(),
docViewBottom = docViewTop + $window.height(),
elemTop = $elem.offset().top,
elemBottom = elemTop + $elem.height();
if ((docViewTop elemBottom))
StackExchange.using('gps', function() StackExchange.gps.track('embedded_signup_form.view', location: 'question_page' ); );
$window.unbind('scroll', onScroll);
;
$window.on('scroll', onScroll);
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
var $window = $(window),
onScroll = function(e)
var $elem = $('.new-login-left'),
docViewTop = $window.scrollTop(),
docViewBottom = docViewTop + $window.height(),
elemTop = $elem.offset().top,
elemBottom = elemTop + $elem.height();
if ((docViewTop elemBottom))
StackExchange.using('gps', function() StackExchange.gps.track('embedded_signup_form.view', location: 'question_page' ); );
$window.unbind('scroll', onScroll);
;
$window.on('scroll', onScroll);
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
var $window = $(window),
onScroll = function(e)
var $elem = $('.new-login-left'),
docViewTop = $window.scrollTop(),
docViewBottom = docViewTop + $window.height(),
elemTop = $elem.offset().top,
elemBottom = elemTop + $elem.height();
if ((docViewTop elemBottom))
StackExchange.using('gps', function() StackExchange.gps.track('embedded_signup_form.view', location: 'question_page' ); );
$window.unbind('scroll', onScroll);
;
$window.on('scroll', onScroll);
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
1
I suspect its a fortran coding issue or compiler option and not Ubuntu related (assuming a
cpof the same files is quick). I'd suggest checking your code, then check compiler options (even the C code generated depending on compiler you are using). there was no february release in 2016, its 16.04 as it was in April– guiverc
Apr 21 at 23:26
In a separate terminal window, watch
journalctl --followas you do your copies. That will show all log messages, including disk failures. Also, do you have swap space defined?– waltinator
Apr 22 at 3:21