From: don fisher <hdf3@comcast.net>
To: "linux-btrfs@vger.kernel.org" <linux-btrfs@vger.kernel.org>
Subject: Re: nube trying to backup my systems
Date: Thu, 19 Mar 2015 18:49:32 -0700 [thread overview]
Message-ID: <550B7CAC.6030005@comcast.net> (raw)
In-Reply-To: <CAJCQCtRj6MWc=YzvEepjiZTQYrN7CKbO0EivotZNjS218Gz56Q@mail.gmail.com>
>
> # btrfs sub list /
> ID 257 gen 1703 top level 5 path root
> ID 258 gen 1662 top level 5 path home
> ID 259 gen 1681 top level 5 path boot
> ID 262 gen 1629 top level 257 path var/lib/machines
>
> To mount machines, either
> subvol=root/var/lib/machines
> OR
> subvolid=262
>
> Why root/var/lib/machines? Because var/lib/machines is created inside
> subvol 257, a.k.a. root, therefore the path relative to the top level
> 5 subvolume is root/var/lib/machines. It might be easier to figure
> this out for a while to use -a switch.
>
> # btrfs sub list -a /mnt/btraid0/
> ID 257 gen 1705 top level 5 path <FS_TREE>/root
> ID 258 gen 1662 top level 5 path <FS_TREE>/home
> ID 259 gen 1681 top level 5 path <FS_TREE>/boot
> ID 262 gen 1705 top level 257 path root/var/lib/machines
The use of the IDs worked. I did not know where they came from, or if
they would be repeatable across boots. So I assumed ID => UUID. My
bad:-( My rot is mounted at /usr11. I tried:
UUID=26d63d99-92f4-4a49-878b-236f5e88af69 /usr11/srv btrfs
subvol=usr11/srv 0 0
but /usr11/srv did not mount. I replaced the number and it did mount.
Would like to use string like you suggested since they are more
understandable. Do you see what I did wrong? Any thoughts on stability
of the IDs across boots?
Thanks,
Don
next prev parent reply other threads:[~2015-03-20 1:49 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-19 23:31 nube trying to backup my systems don fisher
2015-03-20 0:16 ` Chris Murphy
2015-03-20 1:49 ` don fisher [this message]
2015-03-20 2:15 ` Chris Murphy
2015-03-20 2:34 ` don fisher
2015-03-20 3:04 ` Chris Murphy
2015-03-20 4:34 ` Duncan
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=550B7CAC.6030005@comcast.net \
--to=hdf3@comcast.net \
--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