corrupted ubi after reboot while busy

[Hamish Moffatt <hamish@cloud.net.au>]

I'm trying UBI for the first time; I have the kernel 2.6.24 with UBI
backported from 2.6.25-rc7.

I created a static volume (on NAND) and wrote a JFFS2 image to it with 
ubiupdatevol. mount succeeded, but the image was built wrongly so the
jffs2 garbage collector thread to fix it. I then rebooted the system
while this was running (using a proper reboot, which succeeded).

After rebooting, I can't attach the UBI volume at all:

Jan  1 00:16:34 elaraboot user.err kernel: [  994.310000] UBI error: validate_vid_hdr: inconsistent VID header at PEB 664                         
Jan  1 00:16:34 elaraboot user.err kernel: [  994.320000] UBI error: cannot attach mtd7                                                           
Jan  1 00:16:34 elaraboot user.err kernel: [  994.320000] UBI error: cannot initialize UBI, error -22 

I don't understand how a corrupt volume can cause the whole UBI to be
unusable?

As an aside, is a static volume not read-only?

thanks
Hamish
-- 
Hamish Moffatt VK3SB <hamish@debian.org> <hamish@cloud.net.au>