All of lore.kernel.org
 help / color / mirror / Atom feed
From: Duncan <1i5t5.duncan@cox.net>
To: linux-btrfs@vger.kernel.org
Subject: Re: nube trying to backup my systems
Date: Fri, 20 Mar 2015 04:34:15 +0000 (UTC)	[thread overview]
Message-ID: <pan$e1cc0$a6e97544$c3eaa670$f3bcb382@cox.net> (raw)
In-Reply-To: 550B7CAC.6030005@comcast.net

don fisher posted on Thu, 19 Mar 2015 18:49:32 -0700 as excerpted:

> Any thoughts on stability of the IDs across boots?

Btrfs subvolIDs are a property of the btrfs and thus stable across boots.

(They're actually the root-tree ID, with ID=5 the main root tree for the 
entire filesystem, various other low-digit IDs being the root trees for 
various sets of filesystem metadata like the chunk tree and the free-
space tree, and IDs above 256 being subvolumes, with snapshots being a 
particular type of subvolume and thus having IDs above 256 as well.  Were 
these numbers to randomly change, therefore, btrfs would be in a world of 
hurt as it couldn't find various critical root trees it needs to parse in 
ordered to function!  So rest assured, if those numbers start changing 
and it's not because you deliberately decided to put a different subvolume 
there and forgot to change your fstab, it's a serious bug in btrfs!)

-- 
Duncan - List replies preferred.   No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master."  Richard Stallman


      parent reply	other threads:[~2015-03-20  4:34 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
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 [this message]

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='pan$e1cc0$a6e97544$c3eaa670$f3bcb382@cox.net' \
    --to=1i5t5.duncan@cox.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.