From: Eric Sandeen <sandeen@sandeen.net>
To: xfs@oss.sgi.com
Subject: Re: can I shrink an xfs?
Date: Tue, 11 Mar 2008 12:47:39 -0500 [thread overview]
Message-ID: <47D6C5BB.4040106@sandeen.net> (raw)
In-Reply-To: <20080311172958.GA31833@apartia.fr>
Louis-David Mitterrand wrote:
> Hi,
>
> Is it possible to shrink an xfs? I tried using xfs_growfs to no avail.
Nope.
http://oss.sgi.com/projects/xfs/faq.html#resize
-Eric
> zenon:~# xfs_growfs -D 650000000 /backup
> meta-data=/dev/md2 isize=256 agcount=32, agsize=20539552 blks
> = sectsz=4096 attr=1
> data = bsize=4096 blocks=657265248, imaxpct=25
> = sunit=16 swidth=48 blks
> naming =version 2 bsize=4096
> log =internal bsize=4096 blocks=32768, version=2
> = sectsz=4096 sunit=1 blks, lazy-count=0
> realtime =none extsz=196608 blocks=0, rtextents=0
> data size 650000000 too small, old size is 657265248
>
> ... even though the fs is 80% full only.
>
> Thanks,
>
>
next prev parent reply other threads:[~2008-03-11 18:39 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-11 17:29 can I shrink an xfs? Louis-David Mitterrand
2008-03-11 17:47 ` Eric Sandeen [this message]
2008-03-11 18:02 ` Josef 'Jeff' Sipek
2008-03-12 9:17 ` David Chinner
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=47D6C5BB.4040106@sandeen.net \
--to=sandeen@sandeen.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