Doesn't the card's firmware have already anti-frag stuff built in?magicman5421 said:well for compatibility, i'd suggest fat32, if you want to use it with windows as well
otherwise, ext3 is good, b/c no need to defrag it ever.
Karel Jansens said:Doesn't the card's firmware have already anti-frag stuff built in?magicman5421 said:well for compatibility, i'd suggest fat32, if you want to use it with windows as well
otherwise, ext3 is good, b/c no need to defrag it ever.
I thought that was just bad sector blocking?
I'd hope not, because defragging flash memory is baaaaaaaaaaaddddd. Writing a lot on a card with finite writes is a no-no.Karel Jansens said:Doesn't the card's firmware have already anti-frag stuff built in?
I've actually done that before. to my psps mspd. I had no idea it was bad. I was thinking of defraging my ipod. is that ok?Balzac2m said:Why would you want to defrag flash memory?
Don't be so sure about that. If the defrager try's to write the blocks at the start of the sectors ( Where the defrag assumes its a HD, aka 0 -> xx ), and you run a defrag on a regulate basis, to me there is a rather high chance that the blocks that are defined as first might die faster then expected.Balzac2m said:defragment is for harddrives. If it spins, defrag it. You can defrag flash memory but its useless. Won't harm though as anex said.
Don't SD cards have built in wear leveling? It doesn't matter how often you write to sector zero because sector zero is never the same physical block twice. Or any sector for that matter. Or am I mistaken in how that works?Benjiro said:Don't be so sure about that. If the defrager try's to write the blocks at the start of the sectors ( Where the defrag assumes its a HD, aka 0 -> xx ), and you run a defrag on a regulate basis, to me there is a rather high chance that the blocks that are defined as first might die faster then expected.
You might expect 60gb to be 1024mb x 60 = 61440mb.Crasherball said:i recently formated a 60gb usbdrive with ext3
but it turned out to have only 55gb left after formatting...
5gb of it was kinda taken....eventhough the drive was empty (since i just formated it)
thats kinda sucky isnt it?
is this a ext3-general-"feature" to take a high percentage of discspace just for the filesystem?
1) 60 GB advertised in storage is actually 60 billion bytes, or 60'000'000'000 bytes, or 56 gigs of real space. This is because of marketing, and it really, really sucks.Crasherball said:i recently formated a 60gb usbdrive with ext3
but it turned out to have only 55gb left after formatting...
5gb of it was kinda taken....eventhough the drive was empty (since i just formated it)
thats kinda sucky isnt it?
is this a ext3-general-"feature" to take a high percentage of discspace just for the filesystem?
That has nothing to do with the files system that is due harddrive manufacturers using bytes instead of bits for measuring the capacity (1 byte = 8 bits). Your hardrive is advertised as 60Gb but is actually 60000000000 bytes or 55.87935447692871 GB.Crasherball said:i recently formated a 60gb usbdrive with ext3
but it turned out to have only 55gb left after formatting...
5gb of it was kinda taken....eventhough the drive was empty (since i just formated it)
thats kinda sucky isnt it?
is this a ext3-general-"feature" to take a high percentage of discspace just for the filesystem?
That's interesting. I read certain FS boot faster than others than others. I forget which ones.Megamixman said:EXT3 is journaled and does take some extra space in order to be able to recover if something happens to the filesystem. Personally, I like JFS. Powerful FS that doesn't use up a lot of CPU power.