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 11:55:17 -0500 [thread overview]
Message-ID: <8eb2b6e0-e997-4206-d935-3f4a716f8fea@gmail.com> (raw)
In-Reply-To: <m3a70we6le.wl-covici@ccs.covici.com>
[-- Attachment #1: Type: text/plain, Size: 1846 bytes --]
John Covici wrote:
> On Sun, 21 Jun 2020 10:50:46 -0400,
> Franz Fellner wrote:
>> On Sun Jun 21 09:21:36 2020, Dale <rdalek1967@gmail.com> wrote:
>>> 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.
>> That wasn't my intention!
>> I thought you should just select one file (remember its name), delete it,
>> unmount, remount and see if the file is still there.
>> So you can be sure that you really have a different issue than just performance.
>> Trying to delete a folder takes ages and you don't see the file names.
> Definitely unmount, the sectors sometimes don't write to disk for
> quite a while, and your unmount should take a few seconds to more than
> a minute and so unmount and wait till it returns, and then remount and
> see what happens.
>
It appears the cards I have is faster or something. ;-) Those class 10
cards are the fastest I think. I got them since it throws video onto
the card. I got one that should work fine in a video camera, since one
trail camera is essentially that. I used Device Notifier to unmount.
It took it a second or so but it said it was safe to remove. From my
understanding, it syncs the file system before unmounting, right?
Surely it wouldn't unmount if the files were still being changed, right?
I may change the cards tomorrow and do some more testing. I'm curious
as to what is up with them. I wasn't sure if that is a sign they are
going bad or just some weird quirk.
I'll try deleting just a couple pics or a single video and see what it
does. I'm not sure it will matter but it's worth testing to see. I'm
curious if nothing else. ;-)
Dale
:-) :-)
[-- Attachment #2: Type: text/html, Size: 2565 bytes --]
next prev parent reply other threads:[~2020-06-21 16:55 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
2020-06-21 14:50 ` Franz Fellner
2020-06-21 16:17 ` John Covici
2020-06-21 16:55 ` Dale [this message]
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=8eb2b6e0-e997-4206-d935-3f4a716f8fea@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