From: Qu Wenruo <quwenruo.btrfs@gmx.com>
To: Jay <j4y0t15@gmail.com>, linux-btrfs@vger.kernel.org
Subject: Re: Btrfs restore error
Date: Fri, 17 Nov 2017 13:38:08 +0800 [thread overview]
Message-ID: <ad8010db-9e11-e205-d77a-d15a11b4da56@gmx.com> (raw)
In-Reply-To: <2382a8cf-2137-9622-6074-a082bcbe2b94@gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 1854 bytes --]
On 2017年11月17日 11:56, Jay wrote:
> Hello,
>
> I thought I should report something since there was little information
> on this error. The situation is I have 2 external hard drives on
> Xubuntu. One is not working and I need to move the data over to the
> other.
"btrfs replace" should be your first option, not "btrfs restore", unless
it's totally damaged and you want to salvage as much as possible.
> I used 'sudo btrfs restore -v /dev/sde1 /mnt/Old4TB' and
> received 'Error mkdiring /mnt/Old4TB/Jayda TV:2'.
No extra info like something restored succefully? Just 'Error mkdiring
/mnt/Old4TB/Jayda TV:2'?
At least it's ENOENT, checking mkdir(3p) should gives your the reason:
---
ENOENT A component of the path prefix specified by path does
not name
an existing directory or path is an empty string.
---
Did the dir "/mnt/Old4TB" exists in first place?
Thanks,
Qu
> I found one forum
> post that said I needed to make the destination folder manually, then
> restore. That did not work. looking at your code 2(%d) is a kernel
> message? not sure what to make of it. I decided to enter a root
> environment with 'sudo su' and the restore worked(the folder still
> existed from previous troubleshoot step). The console is showing files
> being restored. I tried a dry run first which did not show an error.
> Just some feedback and reference.
>
> uname -a
>
> Linux emb 4.10.0-38-generic #42-16.04.1-Ubuntu SMP Tue Oct 10 16:21:20
> UTC 2017 x86_64 x86_64 x86_64 GNU/Linux
>
> btrfs --version
>
> btrfs-progs v4.4
>
> Thank you,
>
> Jayotis
> --
> To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 520 bytes --]
next prev parent reply other threads:[~2017-11-17 5:38 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-17 3:56 Btrfs restore error Jay
2017-11-17 5:38 ` Qu Wenruo [this message]
2017-11-17 15:20 ` Jay
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=ad8010db-9e11-e205-d77a-d15a11b4da56@gmx.com \
--to=quwenruo.btrfs@gmx.com \
--cc=j4y0t15@gmail.com \
--cc=linux-btrfs@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox