Date: Wed, 07 Jan 2004 08:49:56 +0100 From: Mathieu Arnold <mat@FreeBSD.org> To: Greg 'groggy' Lehey <grog@FreeBSD.org> Cc: current@freebsd.org Subject: Re: growfs problem [was Re: Adding a drive in vinum] Message-ID: <168088234.1073465396@pouet.in.mat.cc> In-Reply-To: <20040107030000.GK7617@wantadilla.lemis.com> References: <116314781.1073413622@pouet.in.mat.cc> <119377812.1073416685@pouet.in.mat.cc> <20040107030000.GK7617@wantadilla.lemis.com>
next in thread | previous in thread | raw e-mail | index | archive | help
--==========A7F7B85765BF18B87A9F==========
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline
+-Le 07/01/2004 13:30 +1030, Greg 'groggy' Lehey =E9crivait :
| On Tuesday, 6 January 2004 at 19:18:06 +0100, Mathieu Arnold wrote:
|> Ok, I could not wait, so I did :
|> a create with :
|> drive vinumdrive1 device /dev/ad3e
|> sd name data.p0.s1 drive vinumdrive1 len 0
|>=20
|> then :
|> attach data.p0.s1 data.p0
|>=20
|> That worked well, I had a 115GB volume, I now have a 301GB one, I'm
|> happy :)
|>=20
|> Now, growfs, so, I launch it :
|>=20
|> ...
|> new file systemsize is: 78997019 frags
|> growfs: wtfs: write error: 631976157: Inappropriate ioctl for device
|=20
| Can you check the state of the volume and its plexes and subdisks? If
| they're all OK,, can you run this with ktrace? I'd be interested to
| see what the ioctl is.
Damn, I would have sworn all subdisks were up, but, the new one was
"stale". I'm now running growfs again (and praying a bit too).
It has just borked with :
new file systemsize is: 78997019 frags
Warning: 4312 sector(s) cannot be allocated.
growfs: 308580.0MB (631971840 sectors) block size 32768, fragment size 4096
using 417 cylinder groups of 740.00MB, 23680 blks, 47360 inodes.
with soft updates
super-block backups (for fsck -b #) at:
(...)
619847872, 621363392,growfs: wtfs: write error: 622884032: Inappropriate
ioctl for device
because of I guess :
ad3: TIMEOUT - WRITE_DMA retrying (2 retries left)
ata1: resetting devices ..
done
ad3: FAILURE - already active DMA on this device
ad3: setting up DMA failed
vinum: data.p0.s1 is stale by force
vinum: data.p0 is corrupt
fatal :data.p0.s1 write error, block 380115538 for 32768 bytes
data.p0.s1: user buffer block 621369728 for 32768 bytes
I've redone it twice, and twice it did it at the same place.
Should I guess that my disk has a problem ?
for info, here are my vinum list and printconfig
3 drives:
D vinumdrive0 State: up /dev/ad2e A: 0/117800 MB (0%)
D vinumdrive1 State: up /dev/ad3e A: 0/190782 MB (0%)
1 volumes:
V data State: up Plexes: 1 Size: 301 GB
1 plexes:
P data.p0 C State: up Subdisks: 2 Size: 301 GB
2 subdisks:
S data.p0.s0 State: up D: vinumdrive0 Size: 115 GB
S data.p0.s1 State: up D: vinumdrive1 Size: 186 GB
drive vinumdrive0 device /dev/ad2e
drive vinumdrive1 device /dev/ad3e
volume data
plex name data.p0 org concat vol data
sd name data.p0.s0 drive vinumdrive0 plex data.p0 len 241254455s
driveoffset 265s plexoffset 0s
sd name data.p0.s1 drive vinumdrive1 plex data.p0 len 390721703s
driveoffset 265s plexoffset 241254455s
One strange thing lies in the 3 drived up there where there are only 2. I'm
wondering why there is written 3.
--=20
Mathieu Arnold
--==========A7F7B85765BF18B87A9F==========
Content-Type: application/pgp-signature
Content-Transfer-Encoding: 7bit
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.2 (MingW32)
iD8DBQE/+7omqYYpzGz/vmcRAjEpAJ94I4dPV07QT+HEMDhlztK9kNXG3gCfS/vS
wu0OAMTbUhnoqgnoPAKiSC4=
=+7qn
-----END PGP SIGNATURE-----
--==========A7F7B85765BF18B87A9F==========--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?168088234.1073465396>