In message
<6d57ef06d84b5541af530227504bb68f5c4f4ef...@34093-mbx-c06.mex07a.mlsrvr.c
om>, George Gallen <[email protected]> writes
This I will have to look into. Right now I'm deciding if I want to
setup the partitions in an LVM or not.
To follow up a little further, look at log-based file systems. TuxFS for
one is an example I believe (snag is, I don't know of any production
grade FS's).
Basically, the way they work is "copy on write". Let's say, I update the
file /home/wol/directory/file.
It will write my changes to a NEW block, and update the "directory"
inode info in ram. Then it will write the changes to "directory" to a
NEW block and update "wol" similarly. Likewise "home", and finally "/".
So, should the system crash at any point, the ONLY danger to the
filesystem is if it falls over while updating "/" itself. But the thing
about a file-system like this, if you want to take a backup you just
lock "/" and backup a single instance of it. No matter what changes are
going on around you, you have a disk instance that is frozen in time for
safe backup. Finished? Unlock your "/" and let the FS throw it away. I
gather some filesystems will lock "/" "long term" so you can get to
stuff you've long deleted/corrupted, only clearing and freeing the
instances as disk space is required. And it's pretty efficient, only
saving changes to files, not a copy of the entire file every change.
Cheers,
Wol
--
Anthony W. Youngman <[email protected]>
'Yings, yow graley yin! Suz ae rikt dheu,' said the blue man, taking the
thimble. 'What *is* he?' said Magrat. 'They're gnomes,' said Nanny. The man
lowered the thimble. 'Pictsies!' Carpe Jugulum, Terry Pratchett 1998
Visit the MaVerick web-site - <http://www.maverick-dbms.org> Open Source Pick
_______________________________________________
U2-Users mailing list
[email protected]
http://listserver.u2ug.org/mailman/listinfo/u2-users
