From: Eric Sandeen <sandeen@sandeen.net>
To: richard.ems@cape-horn-eng.com
Cc: xfs@oss.sgi.com
Subject: Re: xfs_growfs: XFS_IOC_FSGROWFSDATA xfsctl failed: Invalid argument
Date: Sat, 23 May 2009 14:25:32 -0500 [thread overview]
Message-ID: <4A184DAC.8060400@sandeen.net> (raw)
In-Reply-To: <4A1844AF.7030906@sandeen.net>
Eric Sandeen wrote:
> richard.ems@cape-horn-eng.com wrote:
>> Quoting Eric Sandeen <sandeen@sandeen.net>:
>>> Not sure ... how big is the current fs and how big is the device? Can
>>> you provide:
>>>
>>> # xfs_info /mnt
>>> # grep sda1 /proc/partitions
>> It is a 16TB FS, and I add 4 x 1 TB HDDs to the RAID 6 array, so the
>> device went from 16 TB to 20 TB.
>>
>> c3m:~ # xfs_info /backup/IFT
>> meta-data=/dev/sda1 isize=256 agcount=52, agsize=76288719 blks
>> = sectsz=512 attr=1
>> data = bsize=4096 blocks=3905982455, imaxpct=25
>> = sunit=0 swidth=0 blks
>> naming =version 2 bsize=4096 ascii-ci=0
>> log =internal bsize=4096 blocks=32768, version=1
>> = sectsz=512 sunit=0 blks, lazy-count=0
>> realtime =none extsz=4096 blocks=0, rtextents=0
>>
>>
>> c3m:~ # grep sda1 /proc/partitions
>> 8 1 19529912286 sda1
>
> thanks, with that info I can reproduce it, I'll look into it soon... but
> not today.
Actually I lied, I looked at it ;)
if you growfs to a nr of blocks that is about 55 blocks less than the
actual device size, it should succeed for you. There's a case where the
last AG would be too small and it tries to compensate but there's an
overflow, I'll send a patch.
-Eric
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2009-05-23 19:25 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-23 15:01 xfs_growfs: XFS_IOC_FSGROWFSDATA xfsctl failed: Invalid argument Richard Ems
2009-05-23 15:50 ` Eric Sandeen
2009-05-23 16:07 ` richard.ems
2009-05-23 17:35 ` Eric Sandeen
2009-05-23 17:45 ` richard.ems
2009-05-23 18:47 ` Eric Sandeen
2009-05-23 19:25 ` Eric Sandeen [this message]
2009-05-25 9:54 ` Richard Ems
2009-06-01 14:32 ` Richard Ems
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=4A184DAC.8060400@sandeen.net \
--to=sandeen@sandeen.net \
--cc=richard.ems@cape-horn-eng.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