From: kkeller@sonic.net
To: xfs@oss.sgi.com
Subject: Re: xfs_growfs doesn't resize
Date: Thu, 30 Jun 2011 16:30:20 -0700 [thread overview]
Message-ID: <55283.1309476620@sonic.net> (raw)
Hello again all,
I apologize for following up my own post, but I found some new information.
On Thu 30/06/11 2:42 PM , kkeller@sonic.net wrote:
> http://oss.sgi.com/archives/xfs/2008-01/msg00085.html
I found a newer thread in the archives which might be more relevant to my issue:
http://oss.sgi.com/archives/xfs/2009-09/msg00206.html
But I haven't yet done a umount, and don't really wish to. So, my followup questions are:
==Is there a simple way to figure out what xfs_growfs did, and whether it caused any problems?
==Will I be able to fix these problems, if any, without needing a umount?
==Assuming my filesystem is healthy, will a simple kernel update (and reboot of course!) allow me to resize the filesystem in one step, instead of 2TB increments?
Again, many thanks!
--keith
--
kkeller@sonic.net
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next reply other threads:[~2011-06-30 23:30 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-30 23:30 kkeller [this message]
2011-07-01 10:46 ` xfs_growfs doesn't resize Dave Chinner
-- strict thread matches above, loose matches on Subject: below --
2011-07-06 22:51 kkeller
2011-07-07 18:25 ` Keith Keller
2011-07-07 19:34 ` Eric Sandeen
2011-07-07 22:23 ` Keith Keller
2011-07-07 22:30 ` Eric Sandeen
2011-07-04 4:34 kkeller
2011-07-04 4:41 ` Eric Sandeen
2011-07-03 19:42 kkeller
2011-07-01 16:44 kkeller
2011-06-30 21:42 kkeller
2011-07-03 15:59 ` Eric Sandeen
2011-07-03 16:01 ` Eric Sandeen
[not found] ` <20110703193822.GA28632@wombat.san-francisco.ca.us>
2011-07-03 22:14 ` Eric Sandeen
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=55283.1309476620@sonic.net \
--to=kkeller@sonic.net \
--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