From: Russell Coker <russell@coker.com.au>
To: Jose Ildefonso Camargo Tolosa <ildefonso.camargo@gmail.com>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: 40TB volume taking over 16 hours to mount, any ideas?
Date: Sat, 09 Aug 2014 13:38:34 +1000 [thread overview]
Message-ID: <2242759.aOKEuU2TTR@xev> (raw)
In-Reply-To: <CAETJ_S-BOjatUFPVPwKCmgMRfWG6K0WEJgE=F_Di2i=52fqGCQ@mail.gmail.com>
On Fri, 8 Aug 2014 16:35:29 Jose Ildefonso Camargo Tolosa wrote:
> uname -a
> Linux server1 3.15.8-031508-generic #201407311933 SMP Thu Jul 31
> 23:34:33 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux
>
> The complete story:
>
> The filesystem was created on Ubuntu 12.04, running kernel 3.11.
> mount options included compress=zlib .
>
> After having some issues with it, specifically that it would mount
> itself read-only, and would then be "stuck" while trying to mount it
> again, we decided to upgrade 14.04, kernel 3.13, and 3.12 btrfs tools.
[...]
> Then, after reading here and there, decided to try to use a newer
> kernel, tried 3.15.8. Well, it is still mounting after ~16 hours, and
> I got messages like these at first:
I recommend trying a 3.14 kernel. I had ongoing problems with kernels before
3.14 which included infinite loops in kernel space. Based on reports on this
list I haven't been inclined to test 3.15 kernels. But 3.14 has been working
well for me on many systems.
Trying 3.14 can't hurt.
--
My Main Blog http://etbe.coker.com.au/
My Documents Blog http://doc.coker.com.au/
next prev parent reply other threads:[~2014-08-09 3:38 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-08 21:35 40TB volume taking over 16 hours to mount, any ideas? Jose Ildefonso Camargo Tolosa
2014-08-09 3:38 ` Russell Coker [this message]
2014-08-09 14:32 ` Andy Smith
2014-08-09 14:58 ` Jose Ildefonso Camargo Tolosa
2014-08-09 16:06 ` Jose Ildefonso Camargo Tolosa
2014-08-09 17:01 ` Duncan
2014-08-09 18:21 ` Marc MERLIN
2014-08-10 4:03 ` Duncan
2014-08-10 12:43 ` Holger Hoffstätte
2014-08-10 14:39 ` Fixing the btrfs deadlocks Marc MERLIN
2014-08-10 15:42 ` Holger Hoffstätte
2014-08-10 16:36 ` Marc MERLIN
2014-08-09 18:38 ` 40TB volume taking over 16 hours to mount, any ideas? Jose Ildefonso Camargo Tolosa
2014-08-09 21:02 ` Jose Ildefonso Camargo Tolosa
2014-08-10 3:58 ` Jose Ildefonso Camargo Tolosa
2014-08-10 8:24 ` Duncan
2014-08-10 8:50 ` Timofey Titovets
2014-08-10 10:16 ` Duncan
2014-08-10 16:25 ` Chris Murphy
2014-08-11 21:33 ` Jose Ildefonso Camargo Tolosa
2014-08-12 4:15 ` Duncan
2014-08-12 14:24 ` Marc MERLIN
2014-08-13 2:02 ` Jose Ildefonso Camargo Tolosa
2014-08-10 4:21 ` Duncan
2014-08-10 4:57 ` Mitch Harder
2014-08-10 7:21 ` Duncan
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=2242759.aOKEuU2TTR@xev \
--to=russell@coker.com.au \
--cc=ildefonso.camargo@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.