From: Chris Murphy <lists@colorremedies.com>
To: Hasse Hagen Johansen <hasse@hagenjohansen.dk>
Cc: Btrfs BTRFS <linux-btrfs@vger.kernel.org>
Subject: Re: Subvolumes cannot be mounted after raid1 conversion
Date: Wed, 4 May 2016 12:12:55 -0600 [thread overview]
Message-ID: <CAJCQCtQ3TRcQb4CBoxG1z5X4=ivP+22_RzECx9DM18cCJvvWgQ@mail.gmail.com> (raw)
In-Reply-To: <B66776EA-68EA-490F-862E-C49A1D51FCE5@hagenjohansen.dk>
On Tue, May 3, 2016 at 4:24 AM, Hasse Hagen Johansen
<hasse@hagenjohansen.dk> wrote:
> Ok. I can mount it manually just fine now using this command : sudo mount -t btrfs -o subvol=music /dev/sde /mnt/temp
>
> But somehow I cannot mount it at /music anymore(and I just found out that is what has been tricking me)
>
> I have also tried with this in fstab
>
> /dev/sde /music btrfs device=/dev/sdd,device=/dev/sde,subvol=music 0 2
I suggest you use volume UUID, and not /dev/ designation for anything,
it's not reliable so for all we know you're forcing systemd to
explicitly mount the wrong devices because their /dev/ letters are
different. Then you can drop device= and then you can also make
fs_passno 0 instead of 2, since it doesn't apply and just makes
systemd run fsck.btrfs which then does nothing.
If that doesn't work then you should add boot parameter
systemd.log_level=debug and then after startup put the output from
'journalctl -b -o short-monotonic > journal.log' up somewhere for
others to look at. It will be much larger than usual and will make it
easier to find out where things are getting confused.
--
Chris Murphy
next prev parent reply other threads:[~2016-05-04 18:12 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-03 8:52 Subvolumes cannot be mounted after raid1 conversion Hasse Hagen Johansen
2016-05-03 9:55 ` Hugo Mills
2016-05-03 10:24 ` Hasse Hagen Johansen
2016-05-03 10:27 ` Hugo Mills
2016-05-03 11:13 ` Hasse Hagen Johansen
2016-05-03 18:06 ` hasse
2016-05-03 16:30 ` Duncan
2016-05-03 18:31 ` hasse
2016-05-03 18:38 ` hasse
2016-05-04 9:54 ` Duncan
2016-05-04 18:12 ` Chris Murphy [this message]
2016-05-04 19:00 ` Hasse Hagen Johansen
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='CAJCQCtQ3TRcQb4CBoxG1z5X4=ivP+22_RzECx9DM18cCJvvWgQ@mail.gmail.com' \
--to=lists@colorremedies.com \
--cc=hasse@hagenjohansen.dk \
--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).