From: "Holger Hoffstätte" <holger.hoffstaette@googlemail.com>
To: unlisted-recipients:; (no To-header on input)
Cc: Linux Btrfs <linux-btrfs@vger.kernel.org>
Subject: Re: problem with long running btrfs mount operation
Date: Tue, 22 Sep 2015 16:57:35 +0200 [thread overview]
Message-ID: <56016C5F.6010406@googlemail.com> (raw)
In-Reply-To: <20150922144312.GB14395@sfserver>
On 09/22/15 16:43, S. Fricke wrote:
>> On Tue, Sep 22, 2015 at 9:53 AM, Holger Hoffstätte
>> <holger.hoffstaette@googlemail.com> wrote:
>>> On 09/22/15 15:38, S. Fricke wrote:
>>>> I have a problem with one of my btrfs hdds. If I mount it, it needs more than
>>>> 135 minutes for this operation. After the mounting it works normaly. This is
>>>> reproducible only with this hdd.
>>>>
>>>> Maybe someone has a clue what is going wrong here.
>>>
>>> On remount it tries to continue a previously started balance, which fails with
>>> an error (as can be seen at the end of your log). You should:
>>>
>>> a) immediately stop what you're doing on that fs and unmount it
>>> b) get btrfs-progs-4.2.1 (not 4.2) and see what it says
>
> What should it say to me? I have to send a command? Should I try to mount the
> device after I have unmount it? BTW: Is btrfs-progs needed for mounting?
I should have been more clear and say "run btrfs check", which I originally
intended to write but then somehow didn't. Sorry. :-)
btrfs-progs is not needed for mounting, only for administrative commands.
-h
next prev parent reply other threads:[~2015-09-22 14:57 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-22 13:38 problem with long running btrfs mount operation S. Fricke
2015-09-22 13:53 ` Holger Hoffstätte
2015-09-22 14:31 ` Richard Michael
2015-09-22 14:43 ` S. Fricke
2015-09-22 14:57 ` Holger Hoffstätte [this message]
2015-09-22 15:13 ` Hugo Mills
2015-09-23 5:42 ` S. Fricke
2015-09-23 9:36 ` Holger Hoffstätte
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=56016C5F.6010406@googlemail.com \
--to=holger.hoffstaette@googlemail.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).