Date: Tue, 27 Jul 2004 21:17:43 +0200 From: "Daniel Eriksson" <daniel_k_eriksson@telia.com> To: "'Lukas Ertl'" <le@FreeBSD.org> Cc: freebsd-current@FreeBSD.org Subject: RE: cvs commit: src/sys/geom/vinum geom_vinum.c geom_vinum_drive.c Message-ID: <!~!UENERkVCMDkAAQACAAAAAAAAAAAAAAAAABgAAAAAAAAA0VcX9IoJqUaXPS8MjT1PdsKAAAAQAAAAASp9gKSSTUqcz9C4wBaIuAEAAAAA@telia.com> In-Reply-To: <20040725203633.M601@korben.in.tern>
next in thread | previous in thread | raw e-mail | index | archive | help
Lukas Ertl wrote: > > This made geom_vinum work on my system, at least partially.=20 > What is the > > correct way of starting geom_vinum? I tried adding=20 > geom_vinum_load=3D"YES" in > > loader.conf, but that made the machine panic during disc probing. >=20 > Where does it panic? Do you have a backtrace? No, no backtrace available because after an upgrade of the system to 2004.07.27.11.00.00 (earlier today) the panic is gone. I might have found another slight problem though, but I'm not sure if = it's a fluke or if it's repeatable. I'll let you know next time I take the = server offline. The problem was that some if the gvinum filesystems (all the striped filesystems, but not the mirrored) did not properly clear the = dirty flag on shutdown. Again, I don't know if this is a real problem. I'll = report back here if it is. /Daniel Eriksson
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?!~!UENERkVCMDkAAQACAAAAAAAAAAAAAAAAABgAAAAAAAAA0VcX9IoJqUaXPS8MjT1PdsKAAAAQAAAAASp9gKSSTUqcz9C4wBaIuAEAAAAA>