Only vaguely. The current size of the journal is mostly guesswork, because
we don't have any tools to measure if the journal is full or not anyways.
> Journal size has more to do with activity when you are in data journaling
> mode. Otherwise you will be hard pressed to fill a 32MB journal with
> meta-data.
Correct.
> > 2. If so, does resize2fs change the journal size properly?
No, neither does ext2resize.
> As long as resize2fs doesn't change the inode of the journal file you should
> be fine.
Correct.
> > When I have resized ext3 filesystems, I have removed then recreated the
> > journal manually because it wasn't clear from the documentation whether
> > resize2fs does the appropriate thing.
Like Mike says, there should be very minimal impact to the filesystem
operation, unless you are going from, say, a 16MB filesystem to a 500GB
filesystem. You also have to watch out if you start with a filesystem
smaller than 500MB - you will get 1kB blocks, and you don't want to have
a large filesystem (10's of GB) with a 1kB blocksize. There is nothing
that resize2fs or ext2resize can do about that, unfortunately.
> I haven't actually resized any ext2/3 partitions. Didn't need to. I'll do
> some tests though.
It works just fine with ext2resize, and I'm pretty sure resize2fs also
works on ext3 filesystems.
Cheers, Andreas
-- Andreas Dilger http://sourceforge.net/projects/ext2resize/ http://www-mddsp.enel.ucalgary.ca/People/adilger/- 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/