NetBSD-Bugs archive
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]
Re: kern/39400: tacking FFS snapshot triggers "lock error" panic
The following reply was made to PR kern/39400; it has been noted by GNATS.
From: Manuel Bouyer <bouyer%antioche.eu.org@localhost>
To: gnats-bugs%NetBSD.org@localhost
Cc:
Subject: Re: kern/39400: tacking FFS snapshot triggers "lock error" panic
Date: Sun, 24 Aug 2008 16:50:08 +0200
On Sun, Aug 24, 2008 at 02:25:00PM +0000, Manuel Bouyer wrote:
> >Number: 39400
> >Category: kern
> >Synopsis: tacking FFS snapshot triggers "lock error" panic
> >Confidential: no
> >Severity: serious
> >Priority: high
> >Responsible: kern-bug-people
> >State: open
> >Class: sw-bug
> >Submitter-Id: net
> >Arrival-Date: Sun Aug 24 14:25:00 +0000 2008
> >Originator: Manuel Bouyer
> >Release: NetBSD 4.99.72
> >Organization:
> >Environment:
> System: NetBSD 4.99.72 NetBSD 4.99.72 (XEN3_DOMU) #98: Sun Aug 24 15:29:54
> CEST 2008
> bouyer@rock:/dsk/l1/misc/bouyer/tmp/amd64/obj/dsk/l1/misc/bouyer/current/src/sys/arch/amd64/compile/XEN3_DOMU
> amd64
> Architecture: amd64
> Machine: amd64
> >Description:
> taking an internal shapshot twice of the same filesystem
> triggers a lock error panic:
It also seems that tacking a snapshot only once, and then rebooting
cause the kernel to hang trying to unmount the filesystem on which the
snapshot was tacken:
dump -a -f /dev/null -X /
reboot
will hang trying to umount /
--
Manuel Bouyer <bouyer%antioche.eu.org@localhost>
NetBSD: 26 ans d'experience feront toujours la difference
--
Home |
Main Index |
Thread Index |
Old Index