All of lore.kernel.org
 help / color / mirror / Atom feed
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 12:35:19 -0500	[thread overview]
Message-ID: <4A1833D7.30608@sandeen.net> (raw)
In-Reply-To: <20090523180721.94212hyfjppuupmo@webmail.df.eu>

richard.ems@cape-horn-eng.com wrote:
> Quoting Eric Sandeen <sandeen@sandeen.net>:
> 
>> Richard Ems wrote:

...

>>> I tried different 2.6.27 versions, one 2.6.29 and one 2.6.30-rc6
>>> version, all gave the same error, check
>>> https://bugzilla.novell.com/show_bug.cgi?id=506361 for the different
>>> kernel versions and errors.
>> I don't see in that bug where you tested .29 or .30, or what the results
>> were...
> 
> Sorry, I wrote a 2nd comment into bugzilla but forgot to submit it 8( .
> Now it's there, please check again (  
> https://bugzilla.novell.com/show_bug.cgi?id=506361#c1 ) .
> 
>>
>>> Is this fix still not included in Linus / openSUSE trees?
>> As for Linus' tree, AFAIK everything works; I can't speak to what SuSE has.
> 
> So the Vanilla kernel I tried should have this fix included, is it  
> then a new bug?

Not sure ... how big is the current fs and how big is the device?  Can
you provide:

# xfs_info /mnt
# grep sda1 /proc/partitions

-Eric

_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs

  reply	other threads:[~2009-05-23 17:35 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 [this message]
2009-05-23 17:45       ` richard.ems
2009-05-23 18:47         ` Eric Sandeen
2009-05-23 19:25           ` Eric Sandeen
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=4A1833D7.30608@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 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.