> > > Putting a sync just before the insmod when developing new drivers is a good
> > > idea btw
> >
> > I've been doing that most of the time. But I sometimes forget that.
> > But as I said, it's not something I expected from a journalled filesystem.
>
> You misunderstand journalling then
Yup, I guess I did.
> A journalling file system can offer different levels of guarantee. With
> metadata only journalling you don't take any real performance hit but your
> file system is always consistent on reboot (consistent as in fsck would pass
> it) but it makes no guarantee that data blocks got written.
I allways thought that it could/would roll back the changes that weren't
consistent. But I stand corrected. Thanks... :)
> Full data journalling will give you what you expect but at a performance hit
> for many applications.
Do any of the other journalled filesystems for linux do this? If not, I
guess I'll go back to ext2.
Bas Vermeulen
-- "God, root, what is difference?" -- Pitr, User Friendly"God is more forgiving." -- Dave Aronson
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/