I really doubt there is any solution that would take less than a few hours. I am sure it is possible to recover much of the data but to the best of my knowledge no tool exists that can recover from an abandoned root node (for reiser4). Though I believe recovery in this case would just involve finding the root node (think that is reasonably tractable, but slow) fixing the superblock to point to that and let fsck do its thing.
I don't think the root node has a magic number that advertises root, but internal nodes do have a recognizable signature and in principal one could deduce which is the root from a collection of the internal nodes. Note that reiser4 packs lots of data in single nodes. If you create a fresh fs with only a few small files they will reside entirely in the root node, which will be clobbered by a mkfs. There is a very good change that mkfs will clobber a little bit of data, but less than 4K. I am sure a few thousand dollars would buy you a solution. Maybe less. On Tuesday 19 December 2006 1:20 pm, Christian Trefzer wrote: > Hi folks, > > a buggy script I wrote dared to mkfs a reiser4 partition after failing > to properly tar up its contents - not that my life would depend on them, > but it would save me a few hours if I could get the stuff back. > > Other than mkfs.reiser4, mount and unmount, nothing was done to the > device ; ) Is there any way to recover most of what was stored on the > now nuked fs? > > TIA, > Chris
