At 09:19 -0400 4/10/13, Hoffkids wrote:
So if I make 20 changes and hit save (not even publish or upload),
then I close my laptop (no shutdown), open it up in 1 hour from
sleep, my keyboard is frozen and I have to hold power button and
restart system, those 20 changes should all still be there?
I feel like I have hit save and sometimes they are not all there and
I have to recall them- not 100% sure.
The FW file won’t be a series of changes, it will be a file that
describes your site at the time of save. If you make a 20 changes
then what is saved is the result of all of those changes. We all know
that FW has only one level of undo, therefore there is nothing to
indicate whether the effect of change 19 is recent or was in the
design when you last opened the file, therefore it’s an
all-or-nothing save. If the save doesn’t complete for some system
reason, and Journaling is turned on, then the partial save may be
‘unwound’ at reboot so all the changes since the previous save are
lost - but not only some of them. If Journaling is off then the file
would be corrupted at a filesystem level and you’d have to use the
backup.
At 09:02 -0400 4/10/13, Walter Lee Davis wrote:
When you save a file, the changes are written to the disk journal,
and then the journal is synchronized with the physical disk at some
point later. (This is “later” in computer science terms – meaning
milliseconds or seconds at the most.) If a hard crash of the OS
itself occurs within this window, then at the next restart, the
journal will be re-played and the disk made whole.
The changes aren’t written to the Journal but to ‘Buffer Cache’
before being synchronised to disk. This is nothing more than an area
of memory that has to be used as an intermediary anyway. It’s called
Buffer Cache because the data in it doesn’t have to be written to
disk before the program is allowed to continue, and also it remains
available should the program decide it has to read the data just
written. It acts as a cache of the corresponding disk block(s).
What is written to the Journal is the details of changes to the
filesystem rather than the data. If a file has to be extended (more
blocks are allocated to it) (or shrunk), or a new directory is
created etc., then the details are journaled. If the extension,
shrink, new directory, change does not complete due to a system
crash or power fail then the Journal is used to undo or complete the
action at boot time so that the filesystem is self-consistent again.
The data itself is not journaled.
David
–
David Ledger - Freelance Unix Sysadmin in the UK.
email@hidden
www.ivdcs.co.uk
freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options