public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: antlists <antlists@youngman.org.uk>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Memory cards and deleting files.
Date: Mon, 22 Jun 2020 19:25:11 +0100	[thread overview]
Message-ID: <fdc86bd4-19e3-4eb7-7844-e46621a8aeaf@youngman.org.uk> (raw)
In-Reply-To: <20200622105643.GA7037@waltdnes.org>

On 22/06/2020 11:56, Walter Dnes wrote:
> On Mon, Jun 22, 2020 at 11:28:17AM +0100, Neil Bothwick wrote
>
>> The SD standard says >33G should use exFAT, this is why many devices
>> state they only support cards up to 32G. The really mean they only
>> support FAT. My Dashcam is like this but it happily works with a 128G
>> card, once I reformatted it with FAT.
> Warning; that still does not change the fact that each individual file
> cannot exceed 4G in size on regular FAT.
>
Warning 2: I did exactly that, and it LOOKED like it was working 
happily, until it overflowed some internal limit and my 1G card turned 
into a 128M card or whatever it was. Have you actually TESTED that card 
IN THE DASHCAM and made sure it can actually use that 128G? Or will it 
only be able to use 4G of that card?

Oh - and 32GB cards are physically different from 128GB cards because 
they work to different standards. That's why so many of the old "real 
SD" card devices only ever use up to 2GB. You CAN (or could) get 4GB SD 
cards, but they were rare, so most people couldn't find them. The SD 
standard was replaced by SDHC, which is why your fileformat changes at 
32GB, which is the maximum capacity of an SDHC card. Above 32GB it's 
SDXC, which is another reason why sticking a larger card into a device 
which says "up to 32GB" is a bad idea - it may not be able to handle SDXC.

Cheers,
Wol



  parent reply	other threads:[~2020-06-22 18:25 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 [this message]
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
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=fdc86bd4-19e3-4eb7-7844-e46621a8aeaf@youngman.org.uk \
    --to=antlists@youngman.org.uk \
    --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