Date: Sun, 08 Jan 2006 18:30:32 -0700 From: Tyler <tyler@tylercentral.com> To: freebsd-geom@freebsd.org Subject: g_vfs_done error 5 Message-ID: <000101c614bc$4843fc20$6400a8c0@TylerMain>
next in thread | raw e-mail | index | archive | help
Hi All,
I don't think this error is strictly Geom related, but I thought I'd ask
here anyway. I've seen a lot of posts regarding this error, but no
solutions.
I've run 2x 40GB drives in RAID 1 using Geom_Mirror and all has been well
for about a year. I added a PCI ATA133 RAID controller today and it doesn't
work well with my mirror. It is a very generic controller with a Silicon
image chipset. FreeBSD see's it, I partitioned and formatted it, but if I
copy large amounts of data to it, the system panics and crashes. This is a
headless server, so the error's spew on the console and I can't get a copy
of them, but here's the gist.
g_vfs_done():ar0s1d[WRITE(offset=189802479616, length=16384)]error = 5
Repeated over 200 times.
The error at the panic is:
Panic: initiate_write_inodeblock_ufs2: already started.
I didn't see any memory errors or anything else that would indicate limited
resources. Here's my setup. Please let me know if this is a known issue,
and if there is a solution.
ad0: 38172MB <MAXTOR 6L040L2 A93.0500> at ata0-master UDMA100
acd0: DVDROM <Pioneer DVD-ROM ATAPIModel DVD-105S 0111/E1.11> at ata0-slave
UDMA33
ad2: 38172MB <MAXTOR 6L040J2 AR1.0400> at ata1-master UDMA100
ad6: 58644MB <Maxtor 6Y060L0 YAR41BW0> at ata3-master UDMA133
ad7: 43979MB <IBM DTLA-307045 TX6OA60A> at ata3-slave UDMA100
ar0: 87955MB <Silicon Image Medley RAID0 (stripe 64 KB)> status: READY
ar0: disk0 READY using ad6 at ata3-master
ar0: disk1 READY using ad7 at ata3-slave
GEOM_MIRROR: Device gm0 created (id=2553880986).
GEOM_MIRROR: Device gm0: provider ad0 detected.
GEOM_MIRROR: Device gm0: provider ad2 detected.
GEOM_MIRROR: Device gm0: provider ad2 activated.
GEOM_MIRROR: Device gm0: provider ad0 activated.
GEOM_MIRROR: Device gm0: provider mirror/gm0 launched.
Trying to mount root from ufs:/dev/mirror/gm0s1a
> uname -a
FreeBSD Server1 6.0-RELEASE-p1 FreeBSD 6.0-RELEASE-p1 #2: Tue Jan 3
22:17:56 MST 2006 root@Server1:/usr/obj/usr/src/sys/TYLER-FBSD6 i386
(06:27 PM)(/var/log)# fdisk /dev/mirror/gm0
******* Working on device /dev/mirror/gm0 *******
parameters extracted from in-core disklabel are:
cylinders=4866 heads=255 sectors/track=63 (16065 blks/cyl)
Figures below won't work with BIOS for partitions not in cyl 1
parameters to be used for BIOS calculations are:
cylinders=4866 heads=255 sectors/track=63 (16065 blks/cyl)
Media sector size is 512
Warning: BIOS sector numbering starts with sector 1
Information from DOS bootblock is:
The data for partition 1 is:
sysid 165 (0xa5),(FreeBSD/NetBSD/386BSD)
start 63, size 78172227 (38170 Meg), flag 80 (active)
beg: cyl 0/ head 1/ sector 1;
end: cyl 769/ head 254/ sector 63
The data for partition 2 is:
<UNUSED>
The data for partition 3 is:
<UNUSED>
The data for partition 4 is:
<UNUSED>
(06:27 PM)(/var/log)# fdisk /dev/ar0
******* Working on device /dev/ar0 *******
parameters extracted from in-core disklabel are:
cylinders=11212 heads=255 sectors/track=63 (16065 blks/cyl)
Figures below won't work with BIOS for partitions not in cyl 1
parameters to be used for BIOS calculations are:
cylinders=11212 heads=255 sectors/track=63 (16065 blks/cyl)
Media sector size is 512
Warning: BIOS sector numbering starts with sector 1
Information from DOS bootblock is:
The data for partition 1 is:
sysid 165 (0xa5),(FreeBSD/NetBSD/386BSD)
start 63, size 180120717 (87949 Meg), flag 80 (active)
beg: cyl 0/ head 1/ sector 1;
end: cyl 1023/ head 254/ sector 63
The data for partition 2 is:
<UNUSED>
The data for partition 3 is:
<UNUSED>
The data for partition 4 is:
<UNUSED>
Tyler
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?000101c614bc$4843fc20$6400a8c0>