rsync problem

[Bob Elzer]

yes I know it's a flash drive, thats why I asked those questions, they all
apply to hard drives.


On Wed, Sep 26, 2018, 5:36 PM Michael <bmike1 at gmail.com> wrote:

> it isn't a flash drive. it is an external hard drive.
>
> On Wed, Sep 26, 2018 at 8:34 PM Bob Elzer <bob.elzer at gmail.com> wrote:
>
>> I think the real question might be how do you remove the drive from the
>> system.
>>
>> you have had a lot of problems with flash drives doing the same thing and
>> we always thought it was the flash going bad, so we recommended a external
>> hard drive.
>>
>> Questions would be are you unmounting before you remove it.
>>
>> where do you keep it and how do you treat it.
>>
>> do you keep it you glove compartment and go off roading everyday?
>>
>> my guess would be you are not unmounting it correctly. if you yank it out
>> before unmounting it, you could be interrupting some write operations.
>> which could corrupt something.
>>
>> was this a new drive or a refurbished drive, or maybe an old used drive?
>>
>> I would only recommend using a new drive to store backups on.
>>
>>
>>
>> On Wed, Sep 26, 2018, 3:04 PM Matt Graham <mhgraham at crow202.org> wrote:
>>
>>> On 2018-09-26 14:41, Michael wrote:
>>> >> On Wed, Sep 26, 2018 at 5:27 PM Matt Graham <mhgraham at crow202.org>
>>> >> wrote:
>>> >>>> On Tue, Sep 25, 2018 at 4:20 PM Michael <bmike1 at gmail.com> wrote:
>>> >>> bmike1 at MikesBeast ~ $ rsync -aWuq --delete-before
>>> >>> /home/bmike1/Documents /media/bmike1/"Seagate Expansion Drive"
>>> >>> rsync: mkdir "/media/bmike1/Seagate Expansion Drive" failed:
>>> >>> Permission denied (13)
>>> >> Post the output of "mount | grep bmike1" and "ls -l
>>> >> /media/bmike1" and "dmesg | tail".
>>>
>>> > /dev/sdc1 on /media/bmike1/Seagate Expansion Drive1 type fuseblk
>>> > bmike1 at MikesBeast ~ $ ls -l /media/bmike1
>>> > drwxr-xr-x 3 root   root   4096 Sep 25 19:16 Seagate Expansion Drive
>>> > drwxrwxrwx 1 bmike1 bmike1 4096 Sep 25 19:57 Seagate Expansion Drive1
>>>
>>> Have a good look at the ls -l output and the output from mount.  This
>>> is a problem people run into with automounters and sometimes mounting by
>>> device identifiers.  I had an older removable drive that would sometimes
>>> show up with a /dev/disk/by-id/ unique string that ended in
>>> "1870-0:0-part1" and sometimes "187-0:0-part1", which might confuse an
>>> automounter in a very similar way.
>>>
>>> Or you have multiple disks with identical volume labels.  That's always
>>> a recipe for disaster, kind of like putting a moose in a blender.
>>>
>>> --
>>> Crow202 Blog: http://crow202.org/wordpress
>>> There is no Darkness in Eternity
>>> But only Light too dim for us to see.
>>> ---------------------------------------------------
>>> PLUG-discuss mailing list - PLUG-discuss at lists.phxlinux.org
>>> To subscribe, unsubscribe, or to change your mail settings:
>>> http://lists.phxlinux.org/mailman/listinfo/plug-discuss
>>
>> ---------------------------------------------------
>> PLUG-discuss mailing list - PLUG-discuss at lists.phxlinux.org
>> To subscribe, unsubscribe, or to change your mail settings:
>> http://lists.phxlinux.org/mailman/listinfo/plug-discuss
>
>
>
> --
> :-)~MIKE~(-:
> ---------------------------------------------------
> PLUG-discuss mailing list - PLUG-discuss at lists.phxlinux.org
> To subscribe, unsubscribe, or to change your mail settings:
> http://lists.phxlinux.org/mailman/listinfo/plug-discuss
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.phxlinux.org/pipermail/plug-discuss/attachments/20180926/ef080aac/attachment.html>