On 2019-07-08, faeychild <faeychild@afraid.org> wrote:copy
I was copying the hidden files in the home directory to a backup folder >>
I got a "file doesn't exist" message.
It was a firefox/xxx.default/cache2/entries/enormously-long-string does
not exist
Can someone explain how the copy function can't find a file that doesn't
exist.
It apparently doesn't - I can't find it either.
puzzled!!!!
It meas that between the time that the filename was sent to the copy
command (eg on the comandline) and the time that the cpy was
attemptempted, the file was erased/moved/... so that once the copy
command tried to copy it, it no longer existed with that name.
For example you were copying all the files in that firefox directory,
and they were large files so the copy of each took a while and by the time
got to that particular file, firefox has erased it. Or you had erased
it.
This is the danger of backing up a live (ie in use) filesystem. The othr
is more insidious-- between the time the copy of a file starts, and and
it ends, that file is used and changed, As a result the contents of the
file could be inconsistant. The database couod be corrupted. This is why
it is always recommended to not backup a live filesystem. Eg close all
users. unmount the filesystem you want to backup, remount it somewhere
else where any program that might use one of the files cannot find it,
then back it up.
Of course "noone" does that.
Regards
On 7/8/19 10:26 PM, William Unruh wrote:
On 2019-07-08, faeychild <faeychild@afraid.org> wrote:
I was copying the hidden files in the home directory to a backup folder >>>
I got a "file doesn't exist" message.
It was a firefox/xxx.default/cache2/entries/enormously-long-string does >>> not exist
Can someone explain how the copy function can't find a file that doesn't >>> exist.
It apparently doesn't - I can't find it either.
puzzled!!!!
It meas that between the time that the filename was sent to the copy
command (eg on the comandline) and the time that the cpy was
attemptempted, the file was erased/moved/... so that once the copy
command tried to copy it, it no longer existed with that name.
For example you were copying all the files in that firefox directory,
and they were large files so the copy of each took a while and by the time copy
got to that particular file, firefox has erased it. Or you had erased
it.
This is the danger of backing up a live (ie in use) filesystem. The othr
is more insidious-- between the time the copy of a file starts, and and
it ends, that file is used and changed, As a result the contents of the
file could be inconsistant. The database couod be corrupted. This is why
it is always recommended to not backup a live filesystem. Eg close all
users. unmount the filesystem you want to backup, remount it somewhere
else where any program that might use one of the files cannot find it,
then back it up.
Of course "noone" does that.
Regards
I beg to differ or else I will have to change my handle to
"noone".
I usually back up my system via a Live Clonezilla CD. I will
sadly admit that I do not do this often enough but when I can pull
it together that is what I do. My /home/bliss is another matter.
bliss
Sysop: | Keyop |
---|---|
Location: | Huddersfield, West Yorkshire, UK |
Users: | 368 |
Nodes: | 16 (2 / 14) |
Uptime: | 85:01:28 |
Calls: | 7,895 |
Calls today: | 1 |
Files: | 12,968 |
Messages: | 5,791,861 |