On Tue, Mar 6, 2012 at 5:54 PM, Ryusuke Konishi <[email protected]> wrote: > Hmmm. Did you shrink the filesystem with nilfs-resize tool > before shrinking the partition ? > > This error (I/O error) also looks undesirable to me.
I couldn't shrink the filesystem, because I couldn't mount it because of the bug. The filesystem was large and I was in desparate need of some spare diskspace. At first, I was going to completely get rid of it, but then I thought you might want to have a look at the superblock, or some othe block, or whatever else to analyze the bug. Since the bug was some sort of initialization issue, I finally decided to keep the first 500 MB of the filesystem and reclaimed the rest of it (by shrinking the partition). And all that had happened *before* I posted the bug report on this mailing list. Luckily, when I tried to mount the "broken" filesystem today, the nilfs driver exposed the very same oops again. I applied your patch/recompiled the kernel and the oops disappeared. So, no. I didn't use any nilfs-resize. And those IO error are pretty much expected to me. -- To unsubscribe from this list: send the line "unsubscribe linux-nilfs" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
