From: MASAKI Haruka <yek@reasonset.net>
To: linux-btrfs@vger.kernel.org
Subject: Unable mount subvolume with "File exists" error
Date: Sat, 2 Mar 2019 01:11:52 +0900 [thread overview]
Message-ID: <20190302011152.2893c2f5@hydrangea> (raw)
Hi.
When run this script
***
#!/bin/zsh
setopt RC_EXPAND_PARAM
if [[ $1 == start ]]
then
if iscsiadm -m node -L all && mount /mnt/worldvol && mount /MasterVol && mount ~foo/local
...
***
failed with
mount: /MasterVol: mount(2) system call failed: File exists.
message after last month Manjaro update.
in /etc/fstab
***
LABEL=MasterBtr /MasterVol btrfs defaults,relatime,space_cache,compress=lzo,subvol=world,noauto 0 0
LABEL=MasterBtr /mnt/worldvol btrfs defaults,relatime,space_cache,compress=lzo,noauto 0 0
/MasterVol/local /home/foo/local none rbind,noauto 0 0
***
I could mount every volume by unmount /mnt/worldvol and mount each volume manually, but the script always failed with "File exists."
next reply other threads:[~2019-03-01 16:21 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-01 16:11 MASAKI Haruka [this message]
-- strict thread matches above, loose matches on Subject: below --
2019-03-03 12:36 Unable mount subvolume with "File exists" error MASAKI Haruka
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=20190302011152.2893c2f5@hydrangea \
--to=yek@reasonset.net \
--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).