From: Olivier Bonvalet <btrfs.list@daevel.fr>
To: linux-btrfs@vger.kernel.org
Subject: [solved] Re: Can't umount a read-only FS ?
Date: Thu, 16 Aug 2012 00:29:14 +0200 [thread overview]
Message-ID: <502C22BA.2000509@daevel.fr> (raw)
In-Reply-To: <502BDC30.8060409@daevel.fr>
On 15/08/2012 19:28, Olivier Bonvalet wrote:
> Hi,
>
> I have a strange problem with a btrfs partition : after an error, btrfs was forced readonly.
>
> So I try to umount it, to launch btrfsck, but it doesn't work :
>
> root! sofia:~# umount /backup/
> root! sofia:~# btrfsck /dev/vg-sofia/backup
> /dev/vg-sofia/backup is currently mounted. Aborting.
> root! sofia:~# umount /backup/
> umount: /backup/: not mounted
> root! sofia:~# btrfsck /dev/vg-sofia/backup
> /dev/vg-sofia/backup is currently mounted. Aborting.
> root! sofia:~#
>
>
Well... I was using a "mount --bind" of a directory within that FS... So not btrfs related.
Sorry for noise, once again.
Olivier
prev parent reply other threads:[~2012-08-15 22:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-15 17:28 Can't umount a read-only FS ? Olivier Bonvalet
2012-08-15 17:32 ` Olivier Bonvalet
2012-08-15 17:43 ` David Sterba
2012-08-15 20:23 ` Olivier Bonvalet
2012-08-15 22:29 ` Olivier Bonvalet [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=502C22BA.2000509@daevel.fr \
--to=btrfs.list@daevel.fr \
--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).