Hi!
> >You might not damage the underlying filesystem, but you
> >could sure go
> >off in the weeds trying to read it, if you stumbled
> >upon some
> >half-updated metadata... so while it may be safe for
> >the filesystem, I'm
> >not convinced that it's safe for the host reading the
> >filesys
Just a quick note before I forget. I thought there was a call in ext4
to set JBD2_FEATURE_INCOMPAT_64BIT at mount time if the filesystem has
more than 2^32 blocks? I don't see that anywhere in the 2.6.20 ext4.
Is that in the upstream git repo?
Cheers, Andreas
--
Andreas Dilger
Principal Software
