POV-Ray : Newsgroups : povray.off-topic : Damn! Server Time
6 Sep 2024 13:18:05 EDT (-0400)
  Damn! (Message 11 to 12 of 12)  
<<< Previous 10 Messages Goto Initial 10 Messages
From: Darren New
Subject: Re: Damn!
Date: 31 Jan 2009 13:15:20
Message: <49849538$1@news.povray.org>
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

From: Eero Ahonen
Subject: Re: Damn!
Date: 31 Jan 2009 14:33:10
Message: <4984a776@news.povray.org>
Darren New wrote:
> 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.

Nice, but...

> 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. :-)

...exactly (why oh why would they leave out the alternate data streams
:p). OTOH it could be licencial politics from MS, still keeping NTFS as
theier own child and not let it out.

> 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.

Ah.

> You mean it *actually* set the dirty bit. :-)

Yes, and unset it also. It now boots up nicely again. :-)


-Aero


Post a reply to this message

<<< Previous 10 Messages Goto Initial 10 Messages

Copyright 2003-2023 Persistence of Vision Raytracer Pty. Ltd.