Just an update
> > --- Scott Long <[EMAIL PROTECTED]> wrote:
> > > I can geneate 30,000 I/O's per second for hours on end on several
> > > types of storage hardware on FreeBSD SMP, and have no
> > problems. Since
> > > you're seeing this problem both when connected to a 3ware
> > controller
> >
Just a wild shot here: I have seen a similar message recently when I
played with my disks. I re-arranged some partitions (and filesystems)
within a slice and it so happened (and I almost know why) that there was
some discrepancy between on-disk and in-memory label of that slice. I
ran newfs on one
> > One basic question to ask: where does the value for offset= in
> > g_vfs_done() come from ?
> >>From the time the error shows up in syslog I believe, the error only
> > happens, when a file get's appended.
>
> I wonder if (wild guess follows) there's a 32/64 bit
> conversion problem somewher
On 15/10/2007, d_elbracht <[EMAIL PROTECTED]> wrote:
> One basic question to ask: where does the value for offset= in g_vfs_done()
> come from ?
Either from the file system or from bugs in the code. I don't remember
seeing similar reports before so the probability of there being bugs
in the code
> > One basic question to ask: where does the value for offset= in
> > g_vfs_done() come from ?
>
> Either from the file system or from bugs in the code. I don't
> remember seeing similar reports before so the probability of
> there being bugs in the code is fairly small.
>
> This is all on ra
ng this error:
> > g_vfs_done():da3s1a[READ(offset=81064794762854400,
> length=8192)]error
> > = 5 on a 12 GB Hyperdrive
> >
> > the offset changes sometimes, but it is always
> 81064794x and
> > well out the 12GB range.
>
> Yes.
>
> > According t
Jan Mikkelsen wrote:
Scott Long wrote:
Ivan Voras wrote:
Either that or file system errors. Does fsck run ok or does
it say
anything unusual?
No, filesystem corruption has nothing to do with g_vfs_done
messages.
Well, perhaps not directly but I think filesystem corruption can
indirectly c
Scott Long wrote:
> Ivan Voras wrote:
> > Either that or file system errors. Does fsck run ok or does
> it say
> > anything unusual?
> >
>
> No, filesystem corruption has nothing to do with g_vfs_done
> messages.
Well, perhaps not directly but I think filesystem corruption can
indirectly cause g_
ffset=81064794762854400, length=8192)]error = 5
on a 12 GB Hyperdrive
the offset changes sometimes, but it is always 81064794x and well
out the 12GB range.
Yes.
According to systat -vm, da3 does tps > 500 (yes, that's a lot)
That's not a lot :) That's actually low for a m
vfs_done():da3s1a[READ(offset=81064794762854400, length=8192)]error = 5
> on a 12 GB Hyperdrive
>
> the offset changes sometimes, but it is always 81064794x and well
> out the 12GB range.
Yes.
> According to systat -vm, da3 does tps > 500 (yes, that's a lot)
That's not a
_done():da3s1a[READ(offset=81064794762854400, length=8192)]error = 5
on a 12 GB Hyperdrive
I trashed a perfectly disk drive before learning that there is a serious
bug
in g_vfs. Apparently it is one of those things which shows up in some
configurations and not others. Although I am told they are u
> --- Scott Long <[EMAIL PROTECTED]> wrote:
> > I can geneate 30,000 I/O's per second for hours on end on several
> > types of storage hardware on FreeBSD SMP, and have no
> problems. Since
> > you're seeing this problem both when connected to a 3ware
> controller
> > and when connected to a
ffset=81064794762854400, length=8192)]error = 5
on a 12 GB Hyperdrive
I trashed a perfectly disk drive before learning that there is a serious bug
in g_vfs. Apparently it is one of those things which shows up in some
configurations and not others. Although I am told they are unable to
isolate the pr
ng this error:
> > g_vfs_done():da3s1a[READ(offset=81064794762854400,
> length=8192)]error
> > = 5 on a 12 GB Hyperdrive
> >
> > the offset changes sometimes, but it is always
> 81064794x and
> > well out the 12GB range.
> >
> > We did have the Hyper
d_elbracht wrote:
we are trying to diagnose errors seen on 6.2, SMP, amd64, cvsup'ed of
2007-10-09
Mainboard is a Tyan Thunder h2000M (S3992-E) with 16 GB RAM and 2 x Opteron
2216, da3 is on a 3ware 9550-12
we are seeing this error:
g_vfs_done():da3s1a[READ(offset=81064794762854400, l
we are trying to diagnose errors seen on 6.2, SMP, amd64, cvsup'ed of
2007-10-09
Mainboard is a Tyan Thunder h2000M (S3992-E) with 16 GB RAM and 2 x Opteron
2216, da3 is on a 3ware 9550-12
we are seeing this error:
g_vfs_done():da3s1a[READ(offset=81064794762854400, length=8192)]error = 5
on
16 matches
Mail list logo
