Next3 on-disk format change request

[Amir Goldstein <amir73il@gmail.com>]

Hi Ted,

As you may have read, Next3 release 1.0.11 automatically migrates to
new on-disk format.
(see http://next3.sf.net)

Also, I would like to ask you again to promote Next3/Ext4 merge as a
topic on LSF,
if you think it is an appropriate topic.

My on-disk format change request is to re-assign a ro_compat feature
for IS_SNAPSHOT (currently in s_flags).

The reason for this request is the following scenario, which was
posted on next3-users list:

"If I use dd to restore a full snapshot image to another volume, can I
mount it as Next3?"

The answer to this question is that read-only mount is ok, but for
read-write mount,
fsck needs to be run first to fix the free blocks counters.

The restored image is identified with the IS_SNAPSHOT flag.
If it was a ro_compat feature, it would prevent users from mistakingly
mounting it read-write before the fix.
Also, 'tune2fs -O ^is_snapshot' could be used to fix the counters,
without running full fsck.

Please assign me a constant for the feature if you agree,
Thanks,
Amir.