>>>>> Ted Ts'o <tytso@xxxxxxx> writes:
[…]
> Yeah, the resize inode is a special case. It is specially
> constructed to reserve space for new block group descriptor blocks
> when doing an online resize. I would suggest for your purposes that
> you _not_ support the online-resizable file system feature, as it's
> unneeded complexity (from what I understand of what you're going to
> be doing with the file system).
I don't seem to understand why such a support would require a
specific handling of the resizable filesystems (other than that
EXT2_RESIZE_INO is to be ignored by e2dis.)
As I currently have no means of Ext2+ FS non-payload parts
extraction, I'm going to rely on e2image(8). Like:
# tar -C / -jcf image.files.tar.bz2 mnt/
$ /sbin/e2image -r image.ext2 image.e2image
$ e2dis image.index < image.ext2
Then, the image could be restored with:
$ tar -jxf image.files.tar.bz2
$ find mnt/ -type f -print0 \
| (cat < image.e2image && imrt image.index) \
> image.ext2
(Note that imrt is going to lseek(2) its stdout.)
That way, I assume that the resize inode is going to be
preserved thanks to e2image.
The point of the procedure above is that instead of passing a
complete .tar.bz2 archive with all the files, only the new files
may be passed, should it be necessary to produce a new version
of the image (like passing a diff instead of the whole source.)
Moreover, for system images, most of the files would likely to
be available from the regular OS packages' repositories.
> P.S. The code to create the reserved inode can be found in
> lib/ext2fs/res_gdt.c, in ext2fs_create_resize_inode().
ACK. Thanks.
--
FSF associate member #7257 Coming soon: Software Freedom Day
http://mail.sf-day.org/lists/listinfo/ planning-ru (ru), sfd-discuss (en)
--
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
