linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Josef Bacik <josef@redhat.com>
To: Ahmet Inan <ainan@mathematik.uni-freiburg.de>
Cc: Josef Bacik <josef@redhat.com>,
	Calvin Walton <calvin.walton@kepstin.ca>,
	linux-btrfs@vger.kernel.org, Chris Mason <chris.mason@oracle.com>
Subject: Re: Boot speed/mount time regression with 3.4.0-rc2
Date: Wed, 11 Apr 2012 13:04:22 -0400	[thread overview]
Message-ID: <20120411170422.GA2506@localhost.localdomain> (raw)
In-Reply-To: <CAFDW0j+=qe49pX3frjEoozOMz-gKKxqJ+jeeTgyXEskDL_9W8w@mail.gmail.com>

On Wed, Apr 11, 2012 at 05:26:29PM +0200, Ahmet Inan wrote:
> On Tue, Apr 10, 2012 at 5:16 PM, Josef Bacik <josef@redhat.com> wrote=
:
> > On Mon, Apr 09, 2012 at 05:20:46PM -0400, Calvin Walton wrote:
> >> On Mon, 2012-04-09 at 16:54 -0400, Josef Bacik wrote:
> >> > On Mon, Apr 09, 2012 at 01:10:04PM -0400, Calvin Walton wrote:
> >> > > On Mon, 2012-04-09 at 11:53 -0400, Calvin Walton wrote:
> >> > > > Hi,
> >> > > >
> >> > > > I have a system that's using a dracut-generated initramfs to=
 mount a
> >> > > > btrfs root. After upgrading to kernel 3.4.0-rc2 to test it o=
ut, I've
> >> > > > noticed that the process of mounting the root filesystem tak=
es much
> >> > > > longer with 3.4.0-rc2 than it did with 3.3.1 - nearly 30 sec=
onds slower!
> >>
> >> > > And the bisect results are in:
> >> > > 285ff5af6ce358e73f53b55c9efadd4335f4c2ff is the first bad comm=
it
> >> > > commit 285ff5af6ce358e73f53b55c9efadd4335f4c2ff
> >> > > Author: Josef Bacik <josef@redhat.com>
> >> > > Date: =A0 Fri Jan 13 15:27:45 2012 -0500
> >> > >
> >> > > =A0 =A0 Btrfs: remove the ideal caching code>
> >> >
> >> > Ok can you give this a whirl? =A0You are going to have to boot/r=
eboot a few times
> >> > to let the cache get re-generated again to make sure it's taken =
effect, but
> >> > hopefully this will help out. =A0Thanks,
> >>
> >> Unfortunately, it doesn't seem to help. Even after 3 or 4 reboots =
with
> >> this patch applied I'm still seeing the same delay.
> >>
> >
> > Ok drop that previous patch and give this one a whirl, it helped on=
 my laptop.
> > This is only =A0half of the problem AFAICS, but it's the easier hal=
f to fix, in
> > the meantime I need to lock down why we're not writing out cache fo=
r a bunch of
> > block groups, but thats trickier since the messages I need are spit=
 out while
> > I'm shutting down, so I need to get creative. =A0Let me know if/how=
 much this
> > helps. =A0Thanks,
>=20
> i have tried your patch and my system still needs several minutes to =
boot
> until it can be used.
> Also tried to reboot several times - it doesn't look like its getting=
 better.
> The last thing the system does when its shutting down is a read-only
> remount of "/" so no umount.
> Booting was much faster before i pulled for-linus a few weeks ago but
> i couldn't find the time to bisect it yet ..
>=20
> please also look at the attached dmesg.txt.
> this is an core i3 system with 2x2TB BTRFS RAID1 and lots of
> home directories and snapshots.
>=20
> I'm going to test this patch on twenty more computers but with
> smaller HDDs and less files and see if it helps to speed up their
> boot times.
>=20

Ok looks like you are running into a different problem.  Could you mayb=
e run
bootchart and upload the resulting png somewhere so I can look and see =
what all
is running while you boot?  Thanks,

Josef
--
To unsubscribe from this list: send the line "unsubscribe linux-btrfs" =
in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

  reply	other threads:[~2012-04-11 17:04 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-09 15:53 Boot speed/mount time regression with 3.4.0-rc2 Calvin Walton
2012-04-09 16:08 ` cwillu
2012-04-09 17:10 ` Calvin Walton
2012-04-09 17:14   ` Josef Bacik
2012-04-09 20:54   ` Josef Bacik
2012-04-09 21:20     ` Calvin Walton
2012-04-10 13:08       ` Josef Bacik
2012-04-10 15:16       ` Josef Bacik
2012-04-10 16:04         ` Calvin Walton
2012-04-10 16:29           ` David Sterba
2012-04-10 16:34             ` Calvin Walton
2012-04-11 15:26         ` Ahmet Inan
2012-04-11 17:04           ` Josef Bacik [this message]
2012-04-12  9:22             ` Ahmet Inan
2012-04-12 13:37               ` Josef Bacik
2012-04-12 14:23                 ` Josef Bacik
2012-04-13  6:26                   ` Ahmet Inan
2012-04-13  6:49                     ` cwillu
2012-04-13 11:22                       ` Ahmet Inan
     [not found]                         ` <CAFDW0jKMEQ+oMN41euh1cMy4h+6Qntt5UL9+0HZw4r9SpDJVvQ@mail.gmail.com>
2012-04-13 12:57                           ` cwillu
2012-04-13 13:20                             ` Ahmet Inan
2012-04-13 13:47                           ` Josef Bacik
2012-04-21 20:54                             ` Ahmet Inan
2012-04-22  7:59                               ` Sergei Trofimovich
2012-04-22  9:16                                 ` Ahmet Inan
2012-04-22 13:57                                   ` Ahmet Inan
2012-05-03 13:40                               ` Ahmet Inan
2012-04-11 16:38 ` Chester
2012-04-11 18:24   ` Josef Bacik

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=20120411170422.GA2506@localhost.localdomain \
    --to=josef@redhat.com \
    --cc=ainan@mathematik.uni-freiburg.de \
    --cc=calvin.walton@kepstin.ca \
    --cc=chris.mason@oracle.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).