All of lore.kernel.org
 help / color / mirror / Atom feed
From: Eric Sandeen <sandeen@sandeen.net>
To: Lance Reed <lreed@brightcove.com>
Cc: "xfs@oss.sgi.com" <xfs@oss.sgi.com>
Subject: Re: Problems with xfs_grow on large LVM + XFS filesystem 20TB size check 2 failed
Date: Wed, 30 Apr 2008 18:24:59 -0500	[thread overview]
Message-ID: <4818FFCB.5060106@sandeen.net> (raw)
In-Reply-To: <6A32BC807C106440B7E23208F280DDAF01D21F3BA8@bcmail1.VIDMARK.LOCAL>

Lance Reed wrote:
> Great!
> That is exactly what I needed to know.
> 
> One follow up question:
> 
> Can I assume that the bug:
> TAKE 959978 - growing an XFS filesystem by more than 2TB is broken
> is a problem only with the the xfs_growfs code?  The reason I asked is that when I first made the original filesystem, I created it using mkfs.xfs and it succeeded fine for 10.5 TB.
> 
> # mkfs.xfs /dev/VolGroupNAS200/LogVolNAS200
> meta-data=/dev/VolGroupNAS200/LogVolNAS200 isize=256    agcount=32, agsize=83886080 blks
>          =                       sectsz=512   attr=0
> data     =                       bsize=4096   blocks=2684354560, imaxpct=25
>          =                       sunit=0      swidth=0 blks, unwritten=1
> naming   =version 2              bsize=4096
> log      =internal log           bsize=4096   blocks=32768, version=1
>          =                       sectsz=512   sunit=0 blks, lazy-count=0
> realtime =none                   extsz=4096   blocks=0, rtextents=
> 
> so I am assuming the rest of the XFS setup can handle large Filesystems fine.  I am just trying to confirm that the probem is TAKE 959978 and that doing it in less than 2 TB increments should be fine.

yes, it was just in the growth path.

-Eric

  reply	other threads:[~2008-04-30 23:24 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-28 21:42 Problems with xfs_grow on large LVM + XFS filesystem 20TB size check 2 failed Lance Reed
2008-04-28 22:34 ` Eric Sandeen
2008-04-28 22:40   ` Lance Reed
2008-04-28 23:00     ` Eric Sandeen
2008-04-29  0:38       ` Mark Goodwin
2008-04-29  0:43         ` Eric Sandeen
2008-04-29 16:15           ` Lance Reed
2008-04-29 16:43             ` Eric Sandeen
2008-04-29 16:52               ` Lance Reed
2008-04-29 16:55                 ` Eric Sandeen
2008-04-30 21:53                   ` Lance Reed
2008-04-30 23:24                     ` Eric Sandeen [this message]
2008-04-30 11:31           ` CentOS project? <- (Re: Problems with xfs_grow on large LVM + XFS filesystem 20TB size check 2 failed) Tru Huynh
2008-04-30 14:54             ` Eric Sandeen
2008-04-29  1:59   ` Problems with xfs_grow on large LVM + XFS filesystem 20TB size check 2 failed David Chinner

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=4818FFCB.5060106@sandeen.net \
    --to=sandeen@sandeen.net \
    --cc=lreed@brightcove.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 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.