From: Eric Sandeen <sandeen@sandeen.net>
To: kkeller@sonic.net
Cc: xfs@oss.sgi.com
Subject: Re: xfs_growfs doesn't resize
Date: Sun, 03 Jul 2011 10:59:03 -0500 [thread overview]
Message-ID: <4E1091C7.5040906@sandeen.net> (raw)
In-Reply-To: <47455.1309470147@sonic.net>
On 6/30/11 4:42 PM, kkeller@sonic.net wrote:
> # uname -a
> Linux sahara.xxx 2.6.18-128.1.6.el5 #1 SMP Wed Apr 1 09:10:25 EDT 2009 x86_64 x86_64 x86_64 GNU/Linux
>
> Yes, it's not a completely current kernel. This box is running CentOS 5
> with some yum updates.
try
# rpm -qa | grep xfs
If you see anything with "kmod" you're running an exceptionally old xfs codebase.
2.6.18-138 and beyond should have a newer xfs backport built into the kernel
rpm itself, as shipped from Red Hat. But the ancient xfs-kmod (or similar)
provided xfs.ko will take precedence even if you update that kernel.
* Fri Apr 03 2009 Don Zickus <dzickus@redhat.com> [2.6.18-138.el5]
...
- [fs] xfs: update to 2.6.28.6 codebase (Eric Sandeen ) [470845]
If at all possible I'd try an updated kernel, especially if your xfs.ko
is provided by the very, very, very old centos xfs-kmod rpm.
-Eric
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2011-07-03 15:59 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-30 21:42 xfs_growfs doesn't resize kkeller
2011-07-03 15:59 ` Eric Sandeen [this message]
2011-07-03 16:01 ` Eric Sandeen
[not found] ` <20110703193822.GA28632@wombat.san-francisco.ca.us>
2011-07-03 22:14 ` Eric Sandeen
2011-06-30 23:30 kkeller
2011-07-01 10:46 ` Dave Chinner
2011-07-01 16:44 kkeller
2011-07-03 19:42 kkeller
2011-07-04 4:34 kkeller
2011-07-04 4:41 ` Eric Sandeen
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
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=4E1091C7.5040906@sandeen.net \
--to=sandeen@sandeen.net \
--cc=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 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.