|
![](/i/fill.gif) |
Eero Ahonen wrote:
> Maybe FAT some day will be designed for huge medias then :). I hope and
> think they don't end up with just pumping up the address space (which
> AFAIK pretty much is what they did with FAT-32).
They added a bitmap for free space lists, ACLs (which would seem to imply
ownership), different timestamps and different limits on various things like
directory size, some transaction safety (which would seem to imply
journaling of some sort), and so on.
I.e., all the good stuff of NTFS, shoehorned into FAT. Bleh. The whole
point of FAT was that it was trivial to understand and implement. :-)
> That schedules the check for next reboot, and it was doing that already
> ;).
The dirty bit is stored in a different place than the scheduled chkdsk, so I
was guessing it might ignore and clear the dirty bit if you invoked it manually.
> Anyway, it crashed couple a days ago, which seems to have fixed the
> problem :D.
You mean it *actually* set the dirty bit. :-)
--
Darren New, San Diego CA, USA (PST)
"Ouch ouch ouch!"
"What's wrong? Noodles too hot?"
"No, I have Chopstick Tunnel Syndrome."
Post a reply to this message
|
![](/i/fill.gif) |