Re: Where to start?

I'd like to see the ability to run gjournal without reformatting.
If you could create a dummy file inside the filesystem, then use
that area for the journal, it might be possible ...

I am not sure about gjournal internals but what if a system crash
occurs in the middle of a transaction and the fs gets corrupted
and the data, necessary to fix it is in the journal, but you
cannot access the journal because the file, which contains the
journal, is on a corrupted fs?

Looking at this as purely a data-integrity problem, and knowing
nothing whatsoever about gjournal internals :)

I would guess that if a way could be found to preallocate the
journal space (as with mkfile(8) in sufficiently-old systems),
and then record its location in a reasonably-secure location
(the superblock?), it could be accessed during recovery without
reference to possibly-corrupt filesystem metadata.
_______________________________________________
freebsd-hackers@xxxxxxxxxxx mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to "freebsd-hackers-unsubscribe@xxxxxxxxxxx"

Relevant Pages

  • Re: Filesystem silent crash with EXT3
    ... (fsck thought the filesystem was clean before I forced it). ... Filesystem clean = the "dirty" flag is not set. ... A system crash or especially power failure shouldn't damage ext3fs. ...
    (Linux-Kernel)
  • Re: iBook G4 running really slowly
    ... system crash. ... disk and that will bring the disk up-to-date and to the last consistent ... The journal replay is a single procedure that happens when you mount the filesystem, and only after it finishes can anything else use the filesystem. ...
    (uk.comp.sys.mac)
  • Re: ext3 mount (safe?)
    ... Itīs safe mount in write mode? ... If the filesystem is unmounted cleanly each time, ... The journal really comes into play in the event of a system crash. ... Linux crashes, make sure to boot back into Linux so the filesystem can ...
    (freebsd-questions)