Hello bob!

Saturday November 02 2019 23:29, you wrote to All:

If, the Samsung EVO is a SSD are you running fstrim -av once a day?
fstrim does a process called garbage collection that resets a unused sectors 
that did hold
valid data/programs but is no longer used and tells the SSD that these are 
free to use.
Over time regardles of the SSD size it will show all the signs of being full 
despite *nix
thinking it has loads of free space to the point that the system will just 
lock up.

The Samsungs have a fast internal controller that does this process while the 
system is in use
but many other brands controller needs the system being totally idle to 
complete this process
and this can take 8 hours or more - Crucial is but one brand that comes to 
mind from bitter
experience :(

If it is a SD card then one possible is fragmentation and yes a drive can 
become over time
so.

As there is no clean up tools for this as technically you do not get it, it 
does happen where
sectors of a file or more importantly large executables can be spread all over 
a drive and a
slow down can be noticed some times HOWEVER it is very slight as against a 
DASD.

The only fix for this is to mount the original SD and a freshly formatted one 
and copy over all
content on a file by file basis. {For a SD this should not be appearing but it 
could indicate
a reduction in free sectors that have not been as used as others that have had 
a high usage and
are wearing out.  One of the drawbacks of using SD cards.



 > Some months ago I bought a Samsung Evo + microSD card as a boot
 > device for an RPI3B (under FreeBSD-current). Initially it seemed
 > as fast or faster than Sandisk Extreme cards used previously.

 > Lately, it's become extremely slow. At first I thought it might be
 > FreeBSD's fault, but now I'm starting to wonder if the card is the
 > culprit.

 > Has anybody observed similar behavior under Raspbian?

 > Thanks for reading,

 > bob prohaska



Vince

--- Mageia Linux v7.1 X64/Mbse v1.0.7.12A/GoldED+/LNX 1.1.5-b20180707