Messages in this thread |  | | | Date | Wed, 8 Dec 1999 01:16:10 -0500 (EST) | | From | "Albert D. Cahalan" <> | | Subject | Re: Ext3 Filesystem |
| |
Stephen C. Tweedie writes: > <brion@gizmo.usc.edu> said:
>> I'm not sure how much I like having hidden mysterious things in my >> filesystems that I can't see... of course if I can't see them, I can't ... > Yes. You will be able to remove the journal and add a new, > differently sized on. You will have to have the filesystem unmounted > to do this, though. > >> e2fsck would probably need to be taught not to treat the journal >> as a lost file too, > > There is already a range of inode numbers which e2fsck treats as > reserved. e2fsck will also have to be taught about journal recovery,
Ext2 does not put inodes or bitmaps in files. Why do this for the log? Using a file seems inconsistent with the rest of ext2/3.
(a file is natural for NTFS, which puts inodes and bitmaps in files too)
Well, I know this is a retrofit... is that it?
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu Please read the FAQ at http://www.tux.org/lkml/
|  |