From plug-discuss-bounces@lists.phxlinux.org Wed Sep 26 17:34:38 2018 Return-Path: X-Original-To: lurker@lists.phxlinux.org Delivered-To: lurker@lists.phxlinux.org Received: from phxlinux.org (localhost [127.0.0.1]) by phxlinux.org (Postfix) with ESMTP id 74B6F32A0008; Wed, 26 Sep 2018 17:34:38 -0700 (MST) X-Original-To: plug-discuss@lists.phxlinux.org Delivered-To: plug-discuss@lists.phxlinux.org Received: from mail-ot1-f52.google.com (mail-ot1-f52.google.com [209.85.210.52]) by phxlinux.org (Postfix) with ESMTPS id 08B7332A0007 for ; Wed, 26 Sep 2018 17:34:37 -0700 (MST) Received: by mail-ot1-f52.google.com with SMTP id m23-v6so885971otf.0 for ; Wed, 26 Sep 2018 17:34:37 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to; bh=VCriXTzoooni5Gxol+UTYoxkky4BHoq9XL5SgECkEvo=; b=SHkGPFSHd5JFmJzIWb+Y+C9rDwO/HUQAlsz+8CpzlU6q4mXg0Eh+3WoZvqODQFiKO/ k9VKryupIRXMuLzQx4VYGSaSjr/k4wsdYbrivBAZDcZ48Lrb2Mbolnlh7fPpZ1b6fvcX CmerKE1yadk51zV53ksX/KGCDrW9uKf1lkaLugpJogHVr80LbVoh/e2c0wi7+8QS+oJQ 98linrexnGk1mZYFCu++yoGZtcur9jq+mCx1hQy/JKM1z3n94X0EbBfxVi3cQY0m90+2 mzlJ+BRCVpudR0byoyKnjBvDxXz1Ppd11UDPz0+FQsaGNMttOwxVteVkYTDCcc96/Utn KQ6g== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to; bh=VCriXTzoooni5Gxol+UTYoxkky4BHoq9XL5SgECkEvo=; b=PU5oJQ8qwaTuRnwgFt7bknFn6E8lA9MfU07QEDJR60gY7QKKjTfSMxlZxUh0n2WTdm doubhGaHJR+xl1kYQDUnWg7zRwXjD0G1tRxzHVdMKdW76AI3ppBGjMQTL/8AmwSxajRE gBqqG02RK6mgQr4eRGHihcYq+YEKgL4z/XSamrnIOQ5kn1ri/wbLaXfnZkLdPcfdNlOY jITvTOb7cbymirizIw5vowifGp5h3Hdx3Ifu0SCZOp7uoDpILqGR33r+vadR+UW6LA1r kkO8K5rueq5PRww/oOObuGJiwkNx2Rq1uDpDCHjGKz1pyxgi+GKkvhS8541flAxdYETZ IN6g== X-Gm-Message-State: ABuFfojkmc+HoUDTwvPAHE9jgEcGaqsNXkDOoL79h+0qbqRKKCT2MZOp LM5vNadbgI1G1W376RQDs2E7FoL+uYbUYxnI/9Nr2w== X-Google-Smtp-Source: ACcGV61EZNOGIOtT0rLY1AKDiYtk26LpKBDcSbgDAiLbYhQptFRwRUceyTBCWJlo0mtbLec0+svmxbvzNYlM9saC9h8= X-Received: by 2002:a9d:3437:: with SMTP id v52-v6mr6127409otb.231.1538008476233; Wed, 26 Sep 2018 17:34:36 -0700 (PDT) MIME-Version: 1.0 References: <9ccd23aa1938e4ffe61af2e0d37f51dd@crow202.org> <9663be79fc94753f509775ace732f247@crow202.org> In-Reply-To: <9663be79fc94753f509775ace732f247@crow202.org> From: Bob Elzer Date: Wed, 26 Sep 2018 17:34:23 -0700 Message-ID: Subject: Re: rsync problem To: Main PLUG discussion list X-BeenThere: plug-discuss@lists.phxlinux.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Main PLUG discussion list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Reply-To: Main PLUG discussion list Content-Type: multipart/mixed; boundary="===============6707748931409556507==" Errors-To: plug-discuss-bounces@lists.phxlinux.org Sender: "PLUG-discuss" --===============6707748931409556507== Content-Type: multipart/alternative; boundary="000000000000e333d30576cf80f7" --000000000000e333d30576cf80f7 Content-Type: text/plain; charset="UTF-8" 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 wrote: > On 2018-09-26 14:41, Michael wrote: > >> On Wed, Sep 26, 2018 at 5:27 PM Matt Graham > >> wrote: > >>>> On Tue, Sep 25, 2018 at 4:20 PM Michael wrote: > >>> bmike1@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@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@lists.phxlinux.org > To subscribe, unsubscribe, or to change your mail settings: > http://lists.phxlinux.org/mailman/listinfo/plug-discuss --000000000000e333d30576cf80f7 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
I think the real question might be how do you remove the = drive from the system.

you hav= e had a lot of problems with flash drives doing the same thing and we alway= s thought it was the flash going bad, so we recommended a external hard dri= ve.

Questions would be a= re you unmounting before you remove it.

where do you keep it and how do you treat it.=C2=A0

do you keep it you glove compar= tment and go off roading everyday?

my guess would be you are not unmounting it correctly. if you ya= nk it out before unmounting it, you could be interrupting some write operat= ions. which could corrupt something.

was this a new drive or a refurbished drive, or maybe an old u= sed drive?

I would only = recommend using a new drive to store backups on.


On Wed, Sep 26, 2018, 3:04 PM Matt Graham <mhgraham@crow202.org> wrote:
On 2018-09-26 14:41, Michael wrote:
>> On Wed, Sep 26, 2018 at 5:27 PM Matt Graham <mhgraham@crow202= .org>
>> wrote:
>>>> On Tue, Sep 25, 2018 at 4:20 PM Michael <bmike1@gmail.com= > wrote:
>>> bmike1@MikesBeast ~ $ rsync -aWuq --delete-before
>>> /home/bmike1/Documents /media/bmike1/"Seagate Expansion D= rive"
>>> 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@MikesBeast ~ $ ls -l /media/bmike1
> drwxr-xr-x 3 root=C2=A0 =C2=A0root=C2=A0 =C2=A04096 Sep 25 19:16 Seaga= te Expansion Drive
> drwxrwxrwx 1 bmike1 bmike1 4096 Sep 25 19:57 Seagate Expansion Drive1<= br>
Have a good look at the ls -l output and the output from mount.=C2=A0 This =
is a problem people run into with automounters and sometimes mounting by device identifiers.=C2=A0 I had an older removable drive that would sometim= es
show up with a /dev/disk/by-id/ unique string that ended in
"1870-0:0-part1" and sometimes "187-0:0-part1", which m= ight confuse an
automounter in a very similar way.

Or you have multiple disks with identical volume labels.=C2=A0 That's a= lways
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@lists.phxlinux.org
To subscribe, unsubscribe, or to change your mail settings:
http://lists.phxlinux.org/mailman/= listinfo/plug-discuss --000000000000e333d30576cf80f7-- --===============6707748931409556507== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: base64 Content-Disposition: inline LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tClBMVUct ZGlzY3VzcyBtYWlsaW5nIGxpc3QgLSBQTFVHLWRpc2N1c3NAbGlzdHMucGh4bGludXgub3JnClRv IHN1YnNjcmliZSwgdW5zdWJzY3JpYmUsIG9yIHRvIGNoYW5nZSB5b3VyIG1haWwgc2V0dGluZ3M6 Cmh0dHA6Ly9saXN0cy5waHhsaW51eC5vcmcvbWFpbG1hbi9saXN0aW5mby9wbHVnLWRpc2N1c3M= --===============6707748931409556507==--