From: Tomasz Chmielewski <tch@virtall.com>
To: linux-btrfs <linux-btrfs@vger.kernel.org>
Subject: btrfs won't mount to /home
Date: Mon, 11 Jul 2016 22:45:13 +0900 [thread overview]
Message-ID: <b44f915ca2d728f0fde9848f09524ecb@admin.virtall.com> (raw)
This is kind of strange (kernel 4.6.3, Ubuntu 16.04):
# mount -t btrfs /dev/sda4 /home
# echo $?
0
# dmesg -c
[382148.588847] BTRFS info (device sda4): disk space caching is enabled
[382148.588851] BTRFS: has skinny extents
So it worked?
# ls /home
<empty, should be showing data>
# df | grep home
# mount | grep /home
# lsof -n | grep /home
All give no output.
So, weird, isn't it?
Now, let's try to mount to /home2:
# mkdir /home2
# mount /dev/sda4 /home2
# mount | grep home
/dev/sda4 on /home2 type btrfs
(rw,relatime,space_cache,subvolid=5,subvol=/)
# dmesg -c
[382190.199363] BTRFS info (device sda4): disk space caching is enabled
[382190.199370] BTRFS: has skinny extents
What's wrong there?
Tomasz Chmielewski
https://wpkg.org
next reply other threads:[~2016-07-11 13:45 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-11 13:45 Tomasz Chmielewski [this message]
2016-07-11 13:56 ` btrfs won't mount to /home Roman Mamedov
2016-07-11 14:12 ` Tomasz Chmielewski
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=b44f915ca2d728f0fde9848f09524ecb@admin.virtall.com \
--to=tch@virtall.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).