Date: Fri, 14 Oct 2011 11:32:39 +0100 From: Jonathan Anderson <jonathan@FreeBSD.org> To: Benjamin Kaduk <kaduk@mit.edu> Cc: freebsd-current@freebsd.org Subject: Re: PANIC: "ffs_valloc: dup alloc" on boot Message-ID: <CAMGEAwDrhL0xN-ba%2BUkxYo7yGCu-ndr=h9RB9LzYewz8JWRo3A@mail.gmail.com> In-Reply-To: <alpine.GSO.1.10.1110061058050.882@multics.mit.edu> References: <CAMGEAwBECZHcoAcP_D-v-RivaiHJh18OkQu-61WJJQ68%2BxXWGQ@mail.gmail.com> <CAMGEAwAwdu8H50_aD367CM%2BKKuzYemEWMAubXTmfXBeYmvJRLw@mail.gmail.com> <alpine.GSO.1.10.1110061058050.882@multics.mit.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
That's ok, a more aggressive fsck-from-a-rescue-disk strategy managed to clean things up. J Anderson On 6 October 2011 15:58, Benjamin Kaduk <kaduk@mit.edu> wrote: > On Thu, 6 Oct 2011, Jonathan Anderson wrote: > >> On 5 October 2011 23:50, Jonathan Anderson <jonathan@freebsd.org> wrote: >>> >>> I was about to upgrade my build VM from BETA2 to BETA3, but I can't >>> seem to boot BETA2 any more: I get a "ffs_valloc: dup alloc" panic on >>> boot, every time. fsck runs and says, "ok, I've cleaned things up for >>> you", but then later on, when trying to update motd, FFS dies. >> >> Here are two screenshots: fsck succeeding and the relevant backtrace. > > Mailman seems to have stripped them. > > -Ben Kaduk > -- Jonathan Anderson jonathan@FreeBSD.org http://freebsd.org/~jonathan/
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAMGEAwDrhL0xN-ba%2BUkxYo7yGCu-ndr=h9RB9LzYewz8JWRo3A>