linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: arand <ienorand@gmail.com>
To: linux-btrfs@vger.kernel.org
Subject: Re: Cannot set-default back to ID 0
Date: Fri, 1 Apr 2011 15:32:18 +0000 (UTC)	[thread overview]
Message-ID: <loom.20110401T172201-433@post.gmane.org> (raw)
In-Reply-To: ijrt29$onm$1@dough.gmane.org

Bernhard Schmidt <berni <at> birkenwald.de> writes:

> 
> Hi,
> 
> a recent Ubuntu upgrade killed my system. Luckily I had done a btrfs
> snapshot before, so I set the particular subvolume as default using
> 
> # btrfs subvolume set-default 261 /mnt
> 
> from a rescue system and was back up in no time. I then mounted the
> original volume with subvolid=0 and repaired it. So far so good.
> However, I fail to set the default volume back to the original.
> 
> # btrfs subvolume set-default 0 /
> 
> apparently does nothing, I don't get an error but I'm still on the
> snapshot after reboot. Currently I'm working around this adding
> rootflag=subvolid=0 on the kernel command line, but that is kind of
> inconvenient.
> 
> Is this expected?
> 
> Ubuntu natty amd64, Kernel 2.6.38-rc5, btrfs-tools 0.19+20100601 
> 
> Thanks
> Bernhard
> 
> --
> To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
> the body of a message to majordomo <at> vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> 
> 

I was asking a similar question in IRC, and the answer I got was:
"The "0" alias for the top-level subvol is implemented in the kernel, not the
userspace tools."

I was however able to do this using:
# btrfs subvolume set-default 5 /
Using 5 for "the _real_ subvolid"

Or alternatively:
# mount -o defaults,subvolid=0 /mnt
# btrfsctl -m /mnt/

It's a bit odd, agreed, and the people I spoke to seemed to agree as well =)

- arand


      reply	other threads:[~2011-04-01 15:32 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-20 20:20 Cannot set-default back to ID 0 Bernhard Schmidt
2011-04-01 15:32 ` arand [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=loom.20110401T172201-433@post.gmane.org \
    --to=ienorand@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;
as well as URLs for NNTP newsgroup(s).