From: Ryusuke Konishi <ryusuke-sG5X7nlA6pw@public.gmane.org>
To: jir-hfpbi5WX9J54Eiagz67IpQ@public.gmane.org
Cc: konishi.ryusuke-Zyj7fXuS5i5L9jVzuh4AOg@public.gmane.org,
linux-nilfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: regression in 2.6.37?
Date: Mon, 28 Feb 2011 13:52:56 +0900 (JST) [thread overview]
Message-ID: <20110228.135256.149497634.ryusuke@osrg.net> (raw)
In-Reply-To: <20110228.112146.55852337.ryusuke-sG5X7nlA6pw@public.gmane.org>
On Mon, 28 Feb 2011 11:21:46 +0900 (JST), Ryusuke Konishi wrote:
> On Mon, 28 Feb 2011 10:58:36 +0900, Jiro SEKIBA wrote:
> >
> > At Mon, 28 Feb 2011 10:33:24 +0900,
> > Jiro SEKIBA wrote:
> > >
> > > Hi,
> > >
> > > I found that none of the checpoints are flagged 'i'.
> > > It looks like it happens after 2.6.37.
> > >
> > > So whenever I only execute "chcp ss <cp>" without any filesystem change,
> > > nilfs volume create new cp without 'i'.
> > > Before 2.6.37, it creates new cp with 'i'.
> >
> > This, by the way, causes that nilfs2_ss_manager creates
> > snapshots forever and useless as a result.
> >
> > So I would really like to turn it back to the normal behavior.
> > It is really critical for the application.
> >
> > thanks
> >
> > regards,
>
> Arrh, that sounds so bad. Ok, I'll look into the problem ASAP.
>
> Ryusuke Konishi
Actually, this tourned out to be a regression on 2.6.37.
The following patch will fix this.
Could you confirm that it corrects your problem?
Thanks,
Ryusuke Konishi
---
From: Ryusuke Konishi <konishi.ryusuke-Zyj7fXuS5i5L9jVzuh4AOg@public.gmane.org>
nilfs2: fix regression that i-flag is not set on changeless checkpoints
According to the report from Jiro SEKIBA titled "regression in
2.6.37?" (Message-Id: <8739n8vs1f.wl%jir-27yqGEOhnJbQT0dZR+AlfA@public.gmane.org>), on 2.6.37 and
later kernels, lscp command no longer displays "i" flag on checkpoints
that snapshot operations or garbage collection created.
This is a regression of nilfs2 checkpointing function, and it's
critical since it broke behavior of a part of nilfs2 applications.
For instance, snapshot manager of TimeBrowse gets to create
meaningless snapshots continuously; snapshot creation triggers another
checkpoint, but applications cannot distinguish whether the new
checkpoint contains meaningful changes or not without the i-flag.
This patch fixes the regression and brings that application behavior
back to normal.
Reported-by: Jiro SEKIBA <jir-hfpbi5WX9J54Eiagz67IpQ@public.gmane.org>
Signed-off-by: Ryusuke Konishi <konishi.ryusuke-Zyj7fXuS5i5L9jVzuh4AOg@public.gmane.org>
Cc: stable <stable-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org> [2.6.37]
---
fs/nilfs2/segment.c | 3 ++-
1 files changed, 2 insertions(+), 1 deletions(-)
diff --git a/fs/nilfs2/segment.c b/fs/nilfs2/segment.c
index 55ebae5..2de9f63 100644
--- a/fs/nilfs2/segment.c
+++ b/fs/nilfs2/segment.c
@@ -430,7 +430,8 @@ static void nilfs_segctor_begin_finfo(struct nilfs_sc_info *sci,
nilfs_segctor_map_segsum_entry(
sci, &sci->sc_binfo_ptr, sizeof(struct nilfs_finfo));
- if (inode->i_sb && !test_bit(NILFS_SC_HAVE_DELTA, &sci->sc_flags))
+ if (NILFS_I(inode)->i_root &&
+ !test_bit(NILFS_SC_HAVE_DELTA, &sci->sc_flags))
set_bit(NILFS_SC_HAVE_DELTA, &sci->sc_flags);
/* skip finfo */
}
--
1.7.3.5
--
To unsubscribe from this list: send the line "unsubscribe linux-nilfs" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2011-02-28 4:52 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-28 1:33 regression in 2.6.37? Jiro SEKIBA
[not found] ` <87aahhuemz.wl%jir-27yqGEOhnJbQT0dZR+AlfA@public.gmane.org>
2011-02-28 1:58 ` Jiro SEKIBA
[not found] ` <8739n8vs1f.wl%jir-27yqGEOhnJbQT0dZR+AlfA@public.gmane.org>
2011-02-28 2:21 ` Ryusuke Konishi
[not found] ` <20110228.112146.55852337.ryusuke-sG5X7nlA6pw@public.gmane.org>
2011-02-28 4:52 ` Ryusuke Konishi [this message]
[not found] ` <20110228.135256.149497634.ryusuke-sG5X7nlA6pw@public.gmane.org>
2011-02-28 11:08 ` Jiro SEKIBA
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=20110228.135256.149497634.ryusuke@osrg.net \
--to=ryusuke-sg5x7nla6pw@public.gmane.org \
--cc=jir-hfpbi5WX9J54Eiagz67IpQ@public.gmane.org \
--cc=konishi.ryusuke-Zyj7fXuS5i5L9jVzuh4AOg@public.gmane.org \
--cc=linux-nilfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.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