From: Andrew Morton <akpm@linux-foundation.org>
To: Ryusuke Konishi <konishi.ryusuke@lab.ntt.co.jp>
Cc: slava@dubeyko.com, splavgm@gmail.com,
linux-nilfs@vger.kernel.org, linux-fsdevel@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] nilfs2: fix very long mount time issue
Date: Mon, 14 Jan 2013 15:00:41 -0800 [thread overview]
Message-ID: <20130114150041.d57e5e03.akpm@linux-foundation.org> (raw)
In-Reply-To: <20130113.160723.135185368.konishi.ryusuke@lab.ntt.co.jp>
On Sun, 13 Jan 2013 16:07:23 +0900 (JST)
Ryusuke Konishi <konishi.ryusuke@lab.ntt.co.jp> wrote:
> On Sat, 12 Jan 2013 19:34:48 +0400, Vyacheslav Dubeyko wrote:
> > From: Vyacheslav Dubeyko <slava@dubeyko.com>
> > Subject: [PATCH] nilfs2: fix very long mount time issue
> >
> > DESCRIPTION:
> > It exists situation when GC can work in background alone without any other filesystem activity during significant time. The nilfs_clean_segments() method calls nilfs_segctor_construct() that updates superblocks in the case of NILFS_SC_SUPER_ROOT and THE_NILFS_DISCONTINUED flags are set. But when GC is working alone the nilfs_clean_segments() is called with unset THE_NILFS_DISCONTINUED flag. As a result, the update of superblocks doesn't occurred all this time and in the case of SPOR superblocks keep very old values of last super root placement.
> >
> > SYMPTOMS:
> > Trying to mount a NILFS2 volume after SPOR in such environment ends with very long mounting time (it can achieve about several hours in some cases).
> >
> > REPRODUCING PATH:
> > 1. It needs to use external USB HDD, disable automount and doesn't make any additional filesystem activity on the NILFS2 volume.
> > 2. Generate temporary file with size about 100 - 500 GB (for example, dd if=/dev/zero of=<file_name> bs=1073741824 count=200). The size of file defines duration of GC working.
> > 3. Then it needs to delete file.
> > 4. Start GC manually by means of command "nilfs-clean -p 0". When you start GC by means of such way then, at the end, superblocks is updated by once. So, for simulation of SPOR, it needs to wait sometime (15 - 40 minutes) and simply switch off USB HDD manually.
> > 5. Switch on USB HDD again and try to mount NILFS2 volume. As a result, NILFS2 volume will mount during very long time.
> >
> > REPRODUCIBILITY: 100%
> >
> > FIX:
> > This patch adds checking that superblocks need to update and set THE_NILFS_DISCONTINUED flag before nilfs_clean_segments() call.
> >
> > Reported-by: Sergey Alexandrov <splavgm@gmail.com>
> > Signed-off-by: Vyacheslav Dubeyko <slava@dubeyko.com>
> > Tested-by: Vyacheslav Dubeyko <slava@dubeyko.com>
>
> Acked-by: Ryusuke Konishi <konishi.ryusuke@lab.ntt.co.jp>
>
> Thanks, Vyacheslav. I confirmed the issue and could reproduce it.
> Your patch fixed it.
>
> Andrew, please apply.
I added a Cc:stable so the fix will be backported into earlier kernels.
40 minutes mount time is pretty bad!
next prev parent reply other threads:[~2013-01-14 23:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-12 15:34 [PATCH] nilfs2: fix very long mount time issue Vyacheslav Dubeyko
2013-01-12 15:34 ` Vyacheslav Dubeyko
2013-01-13 7:07 ` Ryusuke Konishi
2013-01-14 23:00 ` Andrew Morton [this message]
[not found] ` <20130114150041.d57e5e03.akpm-de/tnXTf+JLsfHDXvbKv3WD2FQJk+8+b@public.gmane.org>
2013-01-14 23:38 ` Ryusuke Konishi
2013-01-14 23:38 ` Ryusuke Konishi
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=20130114150041.d57e5e03.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=konishi.ryusuke@lab.ntt.co.jp \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nilfs@vger.kernel.org \
--cc=slava@dubeyko.com \
--cc=splavgm@gmail.com \
/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.