So, I had btrfs_pool1 that was trashed/lost as discussed here recently.
I did btrfs send btrfs_pool2/root_ro.date | btrfs receive /mnt/btrfs_pool1
Then btrfs subvolume snapshot root_ro.date root
Now, after I delete root_ro.date on btrfs_pool1, shouldn't root become a
parent subvolume?
Right now, I have:
legolas:/mnt/btrfs_pool1# btrfs subvolume list -q .
ID 390 gen 5954 top level 5 parent_uuid faea7df8-d51a-6b4b-994b-887d55267cce
path root
legolas:/mnt/btrfs_pool1# btrfs subvolume list -u . |grep
faea7df8-d51a-6b4b-994b-887d55267cce
legolas:/mnt/btrfs_pool1#
Is it possible not to have a parent?
If so, shouldn't you become a parent at that time?
Thanks,
Marc
--
"A mouse is a device used to point at the xterm you want to type in" - A.S.R.
Microsoft is to operating systems ....
.... what McDonalds is to gourmet cooking
Home page: http://marc.merlins.org/ | PGP 1024R/763BE901
--
To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
