All of lore.kernel.org
 help / color / mirror / Atom feed
From: Michael Monnerie <michael.monnerie@is.it-management.at>
To: XFS List <xfs@oss.sgi.com>
Subject: problem growing disk with xfs_growfs 2.9.4
Date: Thu, 29 Oct 2009 22:45:59 +0100	[thread overview]
Message-ID: <200910292245.59794@zmi.at> (raw)

# xfs_growfs -V
xfs_growfs version 2.9.4
# xfs_growfs /disks/db/
meta-data=/dev/xvdb1             isize=256    agcount=4, agsize=2621104 blks
         =                       sectsz=512   attr=2
data     =                       bsize=4096   blocks=10484412, imaxpct=25
         =                       sunit=16     swidth=64 blks, unwritten=1
naming   =version 2              bsize=4096
log      =internal               bsize=4096   blocks=5120, version=2
         =                       sectsz=512   sunit=16 blks, lazy-count=1
realtime =none                   extsz=4096   blocks=0, rtextents=0
data blocks changed from 10484412 to 577742125596490953
inode max percent changed from 25 to 2
log blocks changed from 5120 to 0
realtime blocks changed from 0 to -579257957264110720
realtime extent size changed from 1 to -134945223

I was very scared then, but obviously nothing happened. I had forgotten 
to resize the partition before calling growfs, just wanted to report in case 
that is still a bug. I resized the partition and used v3.0.3, works perfectly.
I made a metadump of that partition in case this is interesting.

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

                 reply	other threads:[~2009-10-29 21:45 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=200910292245.59794@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 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.