• Re: file does not exist

    From Bobbie Sellers@2:250/1 to All on Mon Aug 26 17:56:39 2019
    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

    --
    bliss dash SF 4 ever at dslextreme dot com

    --- MBSE BBS v1.0.7.12 (GNU/Linux-x86_64)
    * Origin: dis-organization (2:250/1@fidonet)
  • From William Unruh@2:250/1 to All on Mon Aug 26 18:41:17 2019
    On 2019-08-26, Bobbie Sellers <bliss@mouse-potato.com> wrote:
    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.

    Nuts. A backup where one file may be corrupted is a LOT LOT better than
    no backup at all. Anything that makes backups for difficult ( like
    having to manually umount stuff etc) means that no backup will be made.

    Of course if there is one crucial file ( like some large database file)
    it is a good idea to make sure it is not in use while the backup is
    being made. (eg at 3AM say). But usually the backup will not be
    corrupted. That it sometime might be just means make a backup every
    night and that way even it is is one night, the previous nights should
    be OK.


    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.

    And how often do you do that? It is far better to automate it and have a
    backup every night, even if occasionally it might be corrupted.



    bliss


    --- MBSE BBS v1.0.7.12 (GNU/Linux-x86_64)
    * Origin: A noiseless patient Spider (2:250/1@fidonet)