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)? > 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, -- dexen deVries [[[↓][→]]] "all dichotomies are either true or false" is a true paradox because it's paradoxical only if it is a paradox ;) -- 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
