All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andy Smith <andy@strugglers.net>
To: linux-btrfs@vger.kernel.org
Subject: Re: 40TB volume taking over 16 hours to mount, any ideas?
Date: Sat, 9 Aug 2014 14:32:06 +0000	[thread overview]
Message-ID: <20140809143206.GJ11855@bitfolk.com> (raw)
In-Reply-To: <2242759.aOKEuU2TTR@xev>

Hello,

On Sat, Aug 09, 2014 at 01:38:34PM +1000, Russell Coker wrote:
> On Fri, 8 Aug 2014 16:35:29 Jose Ildefonso Camargo Tolosa wrote:
> > 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.

I'm in a similar position with a filesystem that won't mount except
read-only, but am already on 3.14 and am also wondering whether to
try a 3.16 kernel.

    https://bugzilla.kernel.org/show_bug.cgi?id=81981

Jose, maybe you could try -oro in the hope of at least getting back
to a read-only mount?

Cheers,
Andy

-- 
"I remember the first time I made love.  Perhaps it was not love exactly but I
 made it and it still works." — The League Against Tedium

  reply	other threads:[~2014-08-09 14:50 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
2014-08-09 14:32   ` Andy Smith [this message]
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=20140809143206.GJ11855@bitfolk.com \
    --to=andy@strugglers.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 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.