Date: Mon, 13 Aug 2007 14:12:50 +0200 From: Ivan Voras <ivoras@fer.hr> To: freebsd-geom@freebsd.org Subject: Re: Gvirstor "newfs" problem - help needed Message-ID: <f9phs4$ov8$1@sea.gmane.org> In-Reply-To: <31903.4141.qm@web30306.mail.mud.yahoo.com> References: <f9oaqg$ggm$1@sea.gmane.org> <31903.4141.qm@web30306.mail.mud.yahoo.com>
next in thread | previous in thread | raw e-mail | index | archive | help
[-- Attachment #1 --] Arne Wörner wrote: > Hi! > > --- Ivan Voras <ivoras@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. [-- Attachment #2 --] -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.5 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFGwErCldnAQVacBcgRAlOzAKCsGfuSOGWvvOqpqaNuaj6P015mnQCgrK5d s/xLmtfrk0mFc2XKWS280bY= =6nYt -----END PGP SIGNATURE-----
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?f9phs4$ov8$1>