From: Tomasz Chmielewski <tch@virtall.com>
To: Roman Mamedov <rm@romanrm.net>
Cc: linux-btrfs <linux-btrfs@vger.kernel.org>
Subject: Re: btrfs won't mount to /home
Date: Mon, 11 Jul 2016 23:12:28 +0900 [thread overview]
Message-ID: <9e72fca1a009ae3e0cd97ad34a3fcb38@admin.virtall.com> (raw)
In-Reply-To: <20160711185613.0f03d47b@natsu>
On 2016-07-11 22:56, Roman Mamedov wrote:
> On Mon, 11 Jul 2016 22:45:13 +0900
> Tomasz Chmielewski <tch@virtall.com> wrote:
>
>> So, weird, isn't it?
>>
>> What's wrong there?
>
> Your systemd unmounts it immediately from /home, search the archives
> there's
> been a funny story like that recently.
Yes, could be similar to this one: https://bugs.archlinux.org/task/44658
In my case, the entry did exist in /etc/fstab, but was different than at
the time of booting the system.
Tomasz Chmielewski
https://wpkg.org
prev parent reply other threads:[~2016-07-11 14:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-11 13:45 btrfs won't mount to /home Tomasz Chmielewski
2016-07-11 13:56 ` Roman Mamedov
2016-07-11 14:12 ` Tomasz Chmielewski [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=9e72fca1a009ae3e0cd97ad34a3fcb38@admin.virtall.com \
--to=tch@virtall.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=rm@romanrm.net \
/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).