On Wed, Oct 3, 2012 at 5:11 PM, Øystein Sættem Middelthun <oyst...@middelthun.no> wrote: > On 10/03/2012 07:29 PM, Mitch Harder wrote: >> >> If you do not have a suitable backup for these files, please make an >> effort to do what you can with restore. Some of the repair methods >> out there have a possibility to make the situation worse. > > > We are talking about something like 50TB, so there is just no way I have the > available space on other disks for temporary storage. > > So in effect you are saying that there are no other available options than a > restore? If I understand correctly a feature along the lines of "mount -o > tree_root=14102764707840 /dev/ /path/" would solve my problem. > > The fs is unmountable because of a temporary loss of connection with an > underlying disk controller, and I don't think the device has a lot of errors > besides not being able to find the latest tree root. >
You should probably try to supply some more information about your situation. Was this btrfs volume build with RAID-1? If so, we should be able to mount in degraded mode. Even so, when I see the words "unable to find the tree root" and "temporary loss of connection with an underlying disk controller" along with the implication that you have no reliable backup of this data, I worry that your situation is potentially precarious. The possibility exists that recovering your data is your best option (as opposed to restoring to previous working condition). Using backup tree-roots and super-blocks has the potential to do irreversible damage. -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
