From: Michael Monnerie <michael.monnerie@is.it-management.at>
To: xfs@oss.sgi.com
Subject: Re: problems with xfs_growfs after lvextend
Date: Wed, 23 Sep 2009 23:47:05 +0200 [thread overview]
Message-ID: <200909232347.05945@zmi.at> (raw)
In-Reply-To: <4ABA8D56.2040101@phy.duke.edu>
On Mittwoch 23 September 2009 Jimmy Dorff wrote:
> Any suggestions ? Any help understanding why this didn't work ?
Hm, hasn't there been a problem with growing more than 2TB at once?
I search in my local box and found this, might help:
May 09: [PATCH] fix overflow in xfs_growfs_data_privat
Maybe kernel update?
mfg zmi
--
// Michael Monnerie, Ing.BSc ----- http://it-management.at
// Tel: 0660 / 415 65 31 .network.your.ideas.
// PGP Key: "curl -s http://zmi.at/zmi.asc | gpg --import"
// Fingerprint: AC19 F9D5 36ED CD8A EF38 500E CE14 91F7 1C12 09B4
// Keyserver: wwwkeys.eu.pgp.net Key-ID: 1C1209B4
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
prev parent reply other threads:[~2009-09-23 21:46 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-23 21:04 problems with xfs_growfs after lvextend Jimmy Dorff
2009-09-23 21:12 ` Eric Sandeen
2009-09-23 21:37 ` Russell Cattelan
2009-09-23 23:21 ` Jimmy Dorff
2009-09-24 0:00 ` Russell Cattelan
2009-09-24 0:54 ` Jimmy Dorff
2009-09-23 21:47 ` Michael Monnerie [this message]
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=200909232347.05945@zmi.at \
--to=michael.monnerie@is.it-management.at \
--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