For what (little :-) ) it's worth, I got bit by this too. Ultimately it
boils down to the problem that once the on-disk file system is sufficiently
broken, the journal doesn't have enough information for fsck to even detect
the problem, much less fix it.
(In my case the problem most likely was cr
On Sat, 10 Aug 2013, Adrian Chadd wrote:
On 10 August 2013 19:19, AN wrote:
Hi All:
I am having a major problem on current at the moment, and I could really use
some help. I am at R253966 on amd64, my problem is the machine is panicing
with: ffs_valloc: dup alloc
I have booted into single
On 10 August 2013 19:19, AN wrote:
> Hi All:
>
> I am having a major problem on current at the moment, and I could really use
> some help. I am at R253966 on amd64, my problem is the machine is panicing
> with: ffs_valloc: dup alloc
>
> I have booted into single user mode and run fsck, it reports
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 wrote:
> On Thu, 6 Oct 2011, Jonathan Anderson wrote:
>
>> On 5 October 2011 23:50, Jonathan Anderson wrote:
>>>
>>> I was about to upgrade my build VM f
On 5 October 2011 23:50, Jonathan Anderson 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 tr
On 02Aug11 08:08, Callum Gibson wrote:
}I have an i386 -current from late Jul 18 which is running in VirtualBox
}(on 8.X amd64 host). After a VM reset I seem to have hit a SUJ-related issue.
}On boot the system produced a "panic: ffs_valloc: dup alloc". Stack trace
}below (sorry had to do this as a
On Thu, 29 Aug 2002 12:05:25 +0200,
Alexander Leidinger <[EMAIL PROTECTED]> said:
Alexander> After booting the system up xdm didn't showed up and there was no
Alexander> possibility to login on the console, so I breaked into ddb and send a
Alexander> "kill 1" to xdm. Nothing happened so I again
:
:Hi,
:
:-current from Sep 23.
:
:After a hard power off (because the system hung while switching from X
:to a virtual console) I got a panic while rebooting (background fsck
:enabled):
Disable background fsck.
-Matt
To Unsubscribe: send mai
On Fri, May 19, 2000 at 06:24:39AM +0200, Niels Chr. Bank-Pedersen wrote:
> On Fri, May 19, 2000 at 12:01:59AM +0200, Bernd Walter wrote:
> > On Thu, May 18, 2000 at 11:43:58PM +0200, Niels Chr. Bank-Pedersen wrote:
> > > On Thu, May 18, 2000 at 11:21:51PM +0200, Bernd Walter wrote:
> > > > Does v
On Fri, May 19, 2000 at 12:01:59AM +0200, Bernd Walter wrote:
> On Thu, May 18, 2000 at 11:43:58PM +0200, Niels Chr. Bank-Pedersen wrote:
> > On Thu, May 18, 2000 at 11:21:51PM +0200, Bernd Walter wrote:
> > > Does vinum list saying that one subdisk of your R5 volume is down?
> >
> > 5 subdisks:
On Thu, May 18, 2000 at 11:43:58PM +0200, Niels Chr. Bank-Pedersen wrote:
> On Thu, May 18, 2000 at 11:21:51PM +0200, Bernd Walter wrote:
> > Does vinum list saying that one subdisk of your R5 volume is down?
>
> 5 subdisks:
> S raid5.p0.s0 State: up PO:0 B Size: 4133
On Thu, May 18, 2000 at 11:21:51PM +0200, Bernd Walter wrote:
> On Thu, May 18, 2000 at 04:13:43PM +0200, Niels Chr. Bank-Pedersen wrote:
> > Hi,
> >
> > On a -current box, sources approx. 2½ days old, I'm
> > having problems using a vinum raid5 volume - usually
> > the box freezes totally when t
On Thu, May 18, 2000 at 04:13:43PM +0200, Niels Chr. Bank-Pedersen wrote:
> Hi,
>
> On a -current box, sources approx. 2½ days old, I'm
> having problems using a vinum raid5 volume - usually
> the box freezes totally when trying to use the filesystem
> (mkdir xxx; cd xxx -> crash), but last time
13 matches
Mail list logo
