Skip site navigation (1)Skip section navigation (2)
Date:      Sun, 08 Feb 2004 21:43:19 +1030
From:      Michael Ritchie <michaeljritchie@bigpond.com>
To:        freebsd-questions@freebsd.org
Subject:   Growfs Vinum on 5.2-RELEASE
Message-ID:  <402619CF.9030900@bigpond.com>

next in thread | raw e-mail | index | archive | help
I have followed the method advocated by Drew Tomlinson on this list
(October 2002) to create a Vinum volume without losing data.  Everything
worked ok for the first drive... and then I added the second, and grew
the file system using growfs ... and then added the third subdisk to the
plex, and tried to growfs again, and got the following message:


# growfs -N /dev/vinum/data
new file systemsize is: 195366077 frags
Warning: 157556 sector(s) cannot be allocated.
growfs: 381497.4MB (781306752 sectors) block size 16384, fragment size 2048
        using 2076 cylinder groups of 183.77MB, 11761 blks, 23552 inodes.
        with soft updates
super-block backups (for fsck -b #) at:
625120832, 625497184, 625873536, 626249888, 626626240, 627002592, 627378944,
627755296, 628131648, 628508000, 628884352, 629260704, 629637056,
630013408,
... etc ...
775285280, 775661632, 776037984, 776414336, 776790688, 777167040,
777543392,
777919744, 778296096, 778672448, 779048800, 779425152, 779801504,
780177856,
780554208, 780930560
growfs: bad inode number 1 to ginode
#

Here's my vinum configuration summary:
# vinum list
3 drives:
D d0              State: up       /dev/ad7s1e     A: 0/190782 MB (0%)
D d2              State: up       /dev/ad6s1e     A: 0/76319 MB (0%)
D d1              State: up       /dev/ad4s1e     A: 0/114473 MB (0%)

1 volumes:
V data            State: up       Plexes:       1 Size:        372 GB

1 plexes:
P data.p0       C State: up       Subdisks:     3 Size:        372 GB

3 subdisks:
S data.p0.s0      State: up       D: d0           Size:        186 GB
S data.p0.s1      State: up       D: d1           Size:        111 GB
S subdisk2        State: up       D: d2           Size:         74 GB


I'm running 5.2-RELEASE, with kernel compiled from RELEASE source to
include IPFW.  Fairly standard stuff.  Is something broken or am I doing
something wrong??

Thanks,
Michael.



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?402619CF.9030900>