Hi Dexen, On Mon, 2012-07-23 at 11:24 +0200, dexen deVries wrote: > Hi Vyacheslaw, > > > On Monday 23 of July 2012 13:17:28 you wrote: > > It exits second superblock at the end of NILFS volume. But it can be not > > in fully synchronous state with primary ones (as I guess). > > Theoretically, it is possible to copy secondary superblock on the place > > of primary. But I am afraid that the NILFS volume can be in inconsistent > > state anyway. > > any hints how to locate the superblock? what offset to look at, and what's > the > magic number(s)?
Usually, secondary superblock is located in the last block (4 KB) of the volume. In nilfs2_fs.h exists such #define NILFS_SB2_OFFSET_BYTES(devsize) ((((devsize) >> 12) - 1) << 12) which define placement of the secondary superblock (devsize is size of the device in bytes). Magic number of NILFS2 is 0x3434. It is located on 0x0006 bytes offset from superblock's begin. > > > Do you sure that this volume doesn't contain another damaged sectors? > > > in my case, that doesn't matter: all the data i want to recover is either in > Git (which does internal consistency checks) or in MySQL, which also does > /some/ consistency checks. > > > Cheers, With the best regards, Vyacheslav Dubeyko. -- To unsubscribe from this list: send the line "unsubscribe linux-nilfs" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
