I have freebsd 5.3 rc1 installed perfectly, i configure vinum with the handbook and all work perfect but when try run vinum with rc.conf there display the error: panic: unmount: dangling vnode cpuid: 0 uptime= 4s Cannot dump. No dump device defined Automatic reboot in 15 seconds. why happened ? I configure freebsd 4.x with this config and work perfectly :( thx to alls.
On Mon, 2004-10-25 at 05:55, Oliver Torres Delgado wrote:> I have freebsd 5.3 rc1 installed perfectly, i configure vinum with the handbook and all work perfect > but when try run vinum with rc.conf there display the error: > > panic: unmount: dangling vnode > cpuid: 0 > uptime= 4s > Cannot dump. No dump device defined > Automatic reboot in 15 seconds. > > why happened ? I configure freebsd 4.x with this config and work perfectly :(Just like me, you should have checked the mailing list archive first. Here is a nice solution: http://lists.freebsd.org/pipermail/freebsd-current/2004-August/035547.html I switched from 5.2.1 to 5.3 and had the same problem which you'ved described above. Once I've switched to gvinum, everything went back to normal. Andrew
It did, but can you tell me anywhere in the docs it says to do that? Or maybe that vinum should sense that and throw some error rather than just blindly corrupting itself. jim On Sun, 2004-11-07 at 09:38, Joe Koberg wrote:> secmgr wrote: > > > >No, I mean self corrupting raid5 sets during initialization. Discussed > >about 2-3 weeks ago. > > > > > In the following message you seemed to claim that adding 64 sectors of > slack to the > beginning of the vinum partition fixed this problem, as I suggested. Did > that fix it or not? > > > > The reason is empirically derived. When I created a 7 disk raid 5 set > > using "len 0" or all the space available, the raid set would be > > corrupt after initializing. Every time. When I reserved back that > > extra space, no corruption. > > (freebsd 4.10-p3) There was a thread on this a few days ago. > > > > jim > > > > Joe Koberg > joe at osoft dot us > >