linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Björn Kalkbrenner" <terminar@cyberphoria.org>
To: linux-btrfs@vger.kernel.org
Subject: Problems with set-default, home subvolume and snapshot
Date: Mon, 05 Sep 2011 12:13:25 +0200	[thread overview]
Message-ID: <4E64A0C5.2060409@cyberphoria.org> (raw)

Hi,

i've got an interesting btrfs subvolume problem which i can't
understand... Maybe someone here can give me a tip because i think
that's only a user error...

I had a root btrfs on / and made a subvolume some month ago for my home
on /home (i think cwd was / and i used "btrfs subvolume create /home").

On friday i wanted to try an update of my distribution, so i
created a snapshot on /snapshots/20110902 (cwd was / and i entered
"btrfs subvolume snapshot / /snapshots/20110902).

Today i realized that my update failed, so i did
"btrfs set-default 257 /" (257 is the id of the snapshot from friday)..=
=2E

When i rebooted, the trouble began. The mounted "home" subvolume was
empty (even if mounted) and the new root from today which i used before
trying the set-default seems to be lost. Ok, not the main problem...

The snapshot from friday was mounted correctly on boot as root.

The directory /snapshots/20110902 is empty but it is still listed as
subvolume. My "home" was also empty but still listed as subvolume.
I tried to remove the subvolume, i tried to remove the directory, both
not working.

Then i tried to
"mount -o subvolumeid=3D256 /dev/mapper/root /home" (id of home subvol)
and the content of my home is back...


My questions are:

1. where is the "original" root from today morning before i did
set-default? Lost?

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?

3. I am now using the snapshot /snapshots/20110902 but what is
/snapshots/20110902 now and why is it still listed? It's empty?

4. can i now delete the snapshots/20110902 or will that drop my current
active working root?

5. can i rename snapshots, e.g. the snapshots/20110902 or "home" to
"home-20110905"?

6. is my btrfs filesystem broken now and should i recreate the whole
thing or is it safe to use it?

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

             reply	other threads:[~2011-09-05 10:13 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-09-05 10:13 Björn Kalkbrenner [this message]
2011-09-05 10:30 ` Problems with set-default, home subvolume and snapshot 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
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=4E64A0C5.2060409@cyberphoria.org \
    --to=terminar@cyberphoria.org \
    --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).