Gvirstor "newfs" problem - help needed

[Ivan Voras]

Arne Wörner wrote:
> Hi!
> 
> --- Ivan Voras <ivoras at fer.hr> wrote:
>> cg 0: bad magic number
>>
> I know that message from my tests with graid5...
> It was clearly caused by a bug in graid5, but I cannot remember when or why it
> happened...
> I would guess, it happened because of some cache or request-sorting
> mismanagement (the write didnt take place but the read was executed; or the
> second write took place before the first write)... Is that possible in
> gvirstor? Does newfs create such a request-pattern (overlapping write requests
> <-- would be a little bit astonishing)?
> 
> But I can definitely say, that it was a bug in graid5...

Thanks for replying! gvirstor doesn't reorder IO and i doesn't have a
cache, so it's not that. I agree that it's almost certainly a bug in
gvirstor.

The only "slightly unusual" thing newfs does is that it first writes a
"big" block, then reads a smaller block from within the written big
block and doesn't like what it gets. But this scenario is well tested by
my test cases and I don't see why it fails for newfs.


-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 250 bytes
Desc: OpenPGP digital signature
Url : http://lists.freebsd.org/pipermail/freebsd-geom/attachments/20070813/9896bb47/signature.pgp