public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Dale <rdalek1967@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Memory cards and deleting files.
Date: Sun, 21 Jun 2020 09:21:36 -0500	[thread overview]
Message-ID: <4d784f1d-751a-aae7-732a-eeb817918684@gmail.com> (raw)
In-Reply-To: <1592742728-ner-8.985@TPL520>

[-- Attachment #1: Type: text/plain, Size: 1307 bytes --]

Franz Fellner wrote:
> On Sat Jun 20 12:09:02 2020, Dale <rdalek1967@gmail.com> wrote:
>> I then right clicked on the
>> directory and chose move to trash.
> Never tried deleting just single files?
> Probably you need to wait longer, those cards are slow.
> I personally do not like to use "move to trash" as the copy takes ages.
> In dolphin you also have "Delete" now (probably you need to press shift
> to turn the "trash" menu item into a "delete")
>
> Formatting usually is the fastest way to get rid of everything on the cards.
>
>


The cards I use are class 10, slow but pretty fast for the type of
card.  Generally, I can download several hundred MBs in a minute or
two.  Deleting sometimes over a 1,000 pics one at a time just isn't
feasible.  That could take a long time.  I'm not sure it would give a
different result either.  Doing a rm -rfv has always worked in the
past.  I've never had it fail on a regular hard drive.  I might add,
even tho I use a wildcard, it still shows it is deleting each file
individually. 

I think the thing that makes the most sense so far, bad file system and
it needs to be reformatted.  It's been a while since I've reformatted
them and this type of cards is known to have weird issues.  If it
continues after that, new card it is.

Dale

:-)  :-) 

[-- Attachment #2: Type: text/html, Size: 1901 bytes --]

  reply	other threads:[~2020-06-21 14:21 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-20 17:09 [gentoo-user] Memory cards and deleting files Dale
2020-06-20 22:14 ` Neil Bothwick
2020-06-20 23:08   ` Wols Lists
2020-06-20 23:11     ` Michael
2020-06-20 23:26       ` Wols Lists
2020-06-21 11:52         ` Michael
2020-06-22 10:28           ` Neil Bothwick
2020-06-22 10:56             ` Walter Dnes
2020-06-22 11:12               ` Neil Bothwick
2020-06-22 13:19                 ` Dale
2020-06-22 13:46                   ` Neil Bothwick
2020-06-22 15:04                     ` Dale
2020-06-22 18:25                   ` antlists
2020-06-22 18:50                     ` Dale
2020-06-22 19:34                       ` antlists
2020-06-22 20:35                         ` Dale
2020-06-22 18:25               ` antlists
2020-06-22 18:52                 ` Dale
2020-06-22 19:22                 ` Neil Bothwick
2020-06-22 19:40                   ` antlists
2020-06-22 20:42                     ` Neil Bothwick
2020-06-23 15:49                       ` antlists
2020-06-21 12:23       ` Dale
2020-06-21 12:32 ` Franz Fellner
2020-06-21 14:21   ` Dale [this message]
2020-06-21 14:50     ` Franz Fellner
2020-06-21 16:17       ` John Covici
2020-06-21 16:55         ` Dale
2020-06-22 10:30         ` Neil Bothwick
2020-06-22 13:47           ` [gentoo-user] " Grant Edwards

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4d784f1d-751a-aae7-732a-eeb817918684@gmail.com \
    --to=rdalek1967@gmail.com \
    --cc=gentoo-user@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox