From: Eric Sandeen <sandeen@sandeen.net>
To: David Bernick <dbernick@gmail.com>
Cc: xfs@oss.sgi.com
Subject: Re: xfs_repair problem.
Date: Sun, 21 Dec 2008 16:20:46 -0600 [thread overview]
Message-ID: <494EC13E.2060303@sandeen.net> (raw)
In-Reply-To: <7bcfcfff0812211408u6e08bf81r1c19ab5ba938b0e2@mail.gmail.com>
David Bernick wrote:
> So I ran an xfs_repair -v on my filesystem. While the FS was originally
> 12T and 95% full. I ran xfs_repair and it throw many "out of space
> errors" when it was running. That makes some sense.
>
> I expanded it with a new device with xfs_grow. It seems to work, because
> the disk is now bigger when I mount it.
I should have pointed out; growing less than 2T at a time is safe, even
with that bug ...
> When I ran xfs_repair on that (latest version), it reverts back to the
> original size. Is there anything I need to do to make the xfs_growfs
> permanent?
No, it should just work. But 2T at a time on that older code w/ teh bug.
> If I can make the XFS partition bigger, I can likely make it work
> because then it won't run out of space! But the partition, despite
> saying its "bigger" here, doesn't seem to "take" after the xfs_repair.
> Any ideas?
Add a terabyte at a time :)
(or backport that patch...)
-Eric
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2008-12-21 22:20 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-21 15:03 xfs_repair problem David Bernick
2008-12-21 15:55 ` Eric Sandeen
2008-12-21 16:52 ` David Bernick
2008-12-21 17:01 ` Eric Sandeen
2008-12-21 17:07 ` David Bernick
2008-12-21 22:08 ` David Bernick
2008-12-21 22:14 ` David Bernick
2008-12-21 22:20 ` Eric Sandeen [this message]
2008-12-21 17:12 ` Eric Sandeen
-- strict thread matches above, loose matches on Subject: below --
2007-12-06 16:10 XFS_Repair PRoblem Kingghost
2007-12-06 21:06 ` David Chinner
2007-12-07 0:51 ` Kingghost
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=494EC13E.2060303@sandeen.net \
--to=sandeen@sandeen.net \
--cc=dbernick@gmail.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