Lexar 128GB flash drives have less storage than other 128GB flash drive brands. I found this out when cloning flash drives with dd failed because the Lexar ran out of space. They also come formatted out of the box as FAT32, so you couldn't fit 128GB even if the drive wasn't shit.
TL;DR: Lexar is a double nigger.
@RegalBeagle probably 128 GB vs GiB. fat32 means that drive must be really old, otherwise it should be exfat.
@Justicar Bought a pack at Costco the other day. Drive to clone is 117.19 GiB and the Lexar is 116.06GiB. Both of these marketed as '128GB'.
Can't even assume drive sizes will be the same anymore because we live in clown world. Are NVMEs also like this?
@RegalBeagle maybe there is a secondary 10GB volume? who knows these days. but lexar is not a bad brand. i remember them from the cd/dvd days. so if they are still around they must be doing something right.
@Justicar lsblk is reporting them as different sizes. Between that and coming formatted FAT32 out of the box, I'm calling them shit.
Ordinarily I wouldn't care about a 1GiB capacity difference, but the only reason I got these was to make a bunch of clones of an existing drive and these are not fit for purpose.
I remember Lexar as a good brand as well but clearly the times have changed. Could be the Costco packs are slop but Costco usually does a good job keeping crap out of their stores.
Something like this for an rsync mirror:
args=(
"--archive"
"--verbose"
"--human-readable"
"--compress"
"--ignore-existing"
"--delete"
"--progress"
)
rsync "${args[@]}" "${path_src}" "${path_dest}"
Done.
@UncleIroh @Justicar I'll make note of this. I ended up just copy/pasting the files between drives minus a few files for the size differences.
Still annoyed that apparently 128GB can mean any size from 116 to 117 GiB. I thought we standardized this shit years ago.
Never go full double nigger, use rsync!
That was as fun as I knew it would be.
@RegalBeagle @Justicar
"double nigger" is a goated insult, stealing that.
dd is usually my go-to too, but as you say, it will copy the entire contents of the source drive, including unused space, to the destination drive resulting in an image that contains the full source drive layout.
You can fuck around with range/count sectors but honestly, it's best just to use rsync for a data-mirror at that point. Plus, rsync gives you small, quick incremental diffs on subsequent use. Win.