From: David Sterba <dsterba@suse.cz>
To: "Björn Kalkbrenner" <terminar@cyberphoria.org>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: Problems with set-default, home subvolume and snapshot
Date: Mon, 5 Sep 2011 15:51:29 +0200 [thread overview]
Message-ID: <20110905135129.GI11678@ds.suse.cz> (raw)
In-Reply-To: <4E64A0C5.2060409@cyberphoria.org>
Hi,
On Mon, Sep 05, 2011 at 12:13:25PM +0200, Bj=F6rn Kalkbrenner wrote:
> Then i tried to
> "mount -o subvolumeid=3D256 /dev/mapper/root /home" (id of home subvo=
l)
> and the content of my home is back...
this is a known limitation and a fix is pending in Josef's development
tree
http://git.kernel.org/?p=3Dlinux/kernel/git/josef/btrfs-work.git;a=3Dco=
mmit;h=3D4fbb149dfc7454d0f233fa8e5b9167f3645c8fcc
"Btrfs: fix how we mount subvol=3D<whatever>
We've only been able to mount with subvol=3D<whatever> where whatever =
was
a subvol within whatever root we had as the default. This allows us t=
o
mount -o subvol=3Dpath/to/subvol/you/want relative from the normal
fs_tree root. Thanks,"
currently, the /home subvolume is searched inside the volume set by
'set-default'. When you change it to an alternative root snapshot, the
'/home' subvolume lookup fails as you've seen.
The patch changes it so that the subvolumes are always looked up to the
original default root subvolume (I don't know of a better name, interna=
l
id 5 or alse selectable by subvolid=3D0).
david
>=20
>=20
> My questions are:
>=20
> 1. where is the "original" root from today morning before i did
> set-default? Lost?
>=20
> 2. why can't i do "mount -o subvolume=3Dhome /dev/mapper/root /home"
> anymore? To be more exact, i can, but why is it empty and why is it
> working when i enter the subvolume id?
>=20
> 3. I am now using the snapshot /snapshots/20110902 but what is
> /snapshots/20110902 now and why is it still listed? It's empty?
>=20
> 4. can i now delete the snapshots/20110902 or will that drop my curre=
nt
> active working root?
>=20
> 5. can i rename snapshots, e.g. the snapshots/20110902 or "home" to
> "home-20110905"?
>=20
> 6. is my btrfs filesystem broken now and should i recreate the whole
> thing or is it safe to use it?
>=20
> Bye
> Bj=F6rn
> --
> 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
--
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
next prev parent reply other threads:[~2011-09-05 13:51 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-05 10:13 Problems with set-default, home subvolume and snapshot Björn Kalkbrenner
2011-09-05 10:30 ` Hugo Mills
2011-09-05 12:20 ` Björn Kalkbrenner
2011-09-05 12:45 ` Hugo Mills
2011-09-05 14:31 ` Björn Kalkbrenner
2011-09-07 6:47 ` Björn Kalkbrenner
2011-09-05 13:07 ` Ilya Dryomov
2011-09-05 14:43 ` Björn Kalkbrenner
2011-09-06 12:16 ` Calvin Walton
2011-09-05 13:51 ` David Sterba [this message]
2011-09-05 13:57 ` Hugo Mills
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=20110905135129.GI11678@ds.suse.cz \
--to=dsterba@suse.cz \
--cc=linux-btrfs@vger.kernel.org \
--cc=terminar@cyberphoria.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).