From: Dave Chinner <david@fromorbit.com>
To: Ed Cashin <ecashin@coraid.com>
Cc: xfs@oss.sgi.com, Adrian Bunk <bunk@kernel.org>
Subject: Re: xfs_growfs fix backport for 2.6.16.y
Date: Tue, 26 Aug 2008 12:01:01 +1000 [thread overview]
Message-ID: <20080826020101.GU5706@disturbed> (raw)
In-Reply-To: <20080825153931.GD7575@coraid.com>
On Mon, Aug 25, 2008 at 11:39:31AM -0400, Ed Cashin wrote:
> Dave Chinner, hello.
>
> Your fix for the counters that had been preventing an XFS from growing
> by more than two terabytes went into 2.6.21, after the introduction of
> the per-cpu in-core superblock counters. The per-cpu in-core
> superblock counters are not in the latest version of the long-lived
> stable kernel 2.6.16.y, maintained by Adrian Bunk.
>
> The problem with growing by more than two terabytes appears to be
> there, though. The 2.6.16.62 kernel will not allow me to grow an XFS
> by, e.g., 10 terabytes, so xfs_growfs does not report any change in
> the data blocks.
>
> I backported your fix,
>
> commit 20f4ebf2bf2f57c1a9abb3655391336cc90314b3
> Author: David Chinner <dgc@sgi.com>
> Date: Sat Feb 10 18:36:10 2007 +1100
>
> [XFS] Make growfs work for amounts greater than 2TB
>
> The free block modification code has a 32bit interface, limiting the size
> the filesystem can be grown even on 64 bit machines. On 32 bit machines,
> there are other 32bit variables in transaction structures and interfaces
> that need to be expanded to allow this to work.
>
> SGI-PV: 959978
> SGI-Modid: xfs-linux-melb:xfs-kern:27894a
>
> Signed-off-by: David Chinner <dgc@sgi.com>
> Signed-off-by: Christoph Hellwig <hch@infradead.org>
> Signed-off-by: Tim Shimmin <tes@sgi.com>
>
> ... to the 2.6.16.y git tree, and the result is included below. When
> I apply this backported fix to 2.6.16.62, I can grow an online XFS by
> 10 terabytes without any trouble.
>
> Do you see any problems with this backport? If not, I will submit it
> for inclusion in the next 2.6.16.y release.
I suggest you make sure it passes test 078 in the xfsqa suite (part
of the xfs-cmds tree) as that tests all the nasty growfs corner
cases. You'll need to test it on 32 bit and 64 bit machines....
If it passes that then I don't see any problems - SGI backported
this for sles10 which is based on 2.6.16 a long time ago.
Cheers,
Dave.
--
Dave Chinner
david@fromorbit.com
next prev parent reply other threads:[~2008-08-26 1:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-25 15:39 xfs_growfs fix backport for 2.6.16.y Ed Cashin
2008-08-26 2:01 ` Dave Chinner [this message]
2008-09-03 18:27 ` Ed Cashin
2008-09-04 23:14 ` Dave Chinner
2008-09-05 16:29 ` Ed Cashin
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=20080826020101.GU5706@disturbed \
--to=david@fromorbit.com \
--cc=bunk@kernel.org \
--cc=ecashin@coraid.com \
--cc=xfs@oss.sgi.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox