Thought I would let you know I did get things figured out. I used btrfs-progs from github https://github.com/josefbacik/btrfs-progs I also used the findroot function from there which generated more possibilities for the root objectid. By pluging in the guesses from findroot into -r objectid for the restore I was able to access the data from my subvolumes. thanks Nz On Tue, Mar 27, 2012 at 8:21 AM, Not Zippy <notzippy@xxxxxxxxx> wrote: > I had found that note on the restore but my restore.c does not allow > that flag (it is also missing the "m" flag as well), I used the branch > dangerousdonteveruse on > https://git.kernel.org/?p=linux/kernel/git/mason/btrfs-progs.git I > switched to the master branch to see if there was a difference but it > does not appear to be any different. (I did find a btrfs-progs on > git-hub which appears to have those flags, but i thought the best to > use would be on git.kernel. ) > > Assuming I can locate the correct restore.c, is there a some other > software to determine the object id of the subvolume ? the root > object id was 5 > > thanks > Nz > > On Tue, Mar 27, 2012 at 6:02 AM, Hugo Mills <hugo@xxxxxxxxxxxxx> wrote: >> On Tue, Mar 27, 2012 at 05:58:17AM -0700, Not Zippy wrote: >>> One entire subvolume was restored. But there were 4 subvolumes on that >>> partition. Is there a way to specify/force the restore of a different >>> subvolume ? >>> >>> find-root seems to only find a single root. >> >> There is only a single root tree, so that's understandable. If you >> have a look at the documentation for restore[1], it mentions (right >> near the bottom of the page) that -r will allow you to select an >> alternative subvolume to recover from. >> -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
