From: Justin Piszcz <jpiszcz@lucidpixels.com>
To: linux-kernel@vger.kernel.org
Cc: linux-raid@vger.kernel.org, Neil Brown <neilb@suse.de>, xfs@oss.sgi.com
Subject: Raid5 Reshape Status + xfs_growfs = Success! (2.6.17.3)
Date: Tue, 11 Jul 2006 12:03:46 -0400 (EDT) [thread overview]
Message-ID: <Pine.LNX.4.64.0607111159470.12230@p34.internal.lan> (raw)
Neil,
It worked, echo'ing the 600 > to the stripe width in /sys, however, how
come /dev/md3 says it is 0 MB when I type fdisk -l?
Is this normal?
Disk /dev/md0 doesn't contain a valid partition table
Disk /dev/md3: 0 MB, 0 bytes
2 heads, 4 sectors/track, 0 cylinders
Units = cylinders of 8 * 512 = 4096 bytes
Disk /dev/md3 doesn't contain a valid partition table
Disk /dev/md2: 71.9 GB, 71954661376 bytes
2 heads, 4 sectors/track, 17567056 cylinders
Units = cylinders of 8 * 512 = 4096 bytes
Furthermore, the xfs_growfs worked beautifully!
p34:~# df -h
/dev/md3 2.2T 487G 1.8T 22% /raid5
p34:~# xfs_growfs /raid5
meta-data=/dev/md3 isize=256 agcount=32, agsize=18314368
blks
= sectsz=4096 attr=0
data = bsize=4096 blocks=586059776, imaxpct=25
= sunit=128 swidth=768 blks, unwritten=1
naming =version 2 bsize=4096
log =internal bsize=4096 blocks=32768, version=2
= sectsz=4096 sunit=1 blks
realtime =none extsz=3145728 blocks=0, rtextents=0
data blocks changed from 586059776 to 683740288
p34:~# df -h
Filesystem Size Used Avail Use% Mounted on
/dev/md3 2.6T 487G 2.1T 19% /raid5
p34:~# umount /raid5
p34:~# mount /raid5
p34:~# dmesg | tail -5
[4354159.367000] disk 7, o:1, dev:sdc1
[4360850.548000] XFS mounting filesystem md3
[4360850.803000] Ending clean XFS mount for filesystem: md3
[4360868.121000] XFS mounting filesystem md3
[4360868.189000] Ending clean XFS mount for filesystem: md3
Very nice stuff.
Thanks Neil & XFS team for the information and help!
Justin.
next reply other threads:[~2006-07-11 16:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-11 16:03 Justin Piszcz [this message]
2006-07-18 0:48 ` Neil Brown
2006-07-21 23:06 ` Jan Engelhardt
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=Pine.LNX.4.64.0607111159470.12230@p34.internal.lan \
--to=jpiszcz@lucidpixels.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-raid@vger.kernel.org \
--cc=neilb@suse.de \
--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
all inboxes | Powered by JetHome®