Current-Users archive
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]
Re: panic: ffs_valloc: dup alloc
On Mon, 19 Jan 2009 12:22:02 +0000
David Holland <dholland-current%netbsd.org@localhost> wrote:
> On Sun, Jan 18, 2009 at 04:07:05PM -0500, Steven M. Bellovin wrote:
> > While I'm not seeing exactly that problem, I do see problems that
> > result in duplicate blocks after a crash. I think it's timing- and
> > disk-layout dependent, but I do think there's a serious file system
> > problem in -current. I'm seriously contemplating wiping my disk
> > and installing a system from a couple of months ago.
>
> Do you have any ideas how one might set about replicating it? (What
> mount options, partition size, etc. are you using?)
>
I posted the other day -- if I build devel/apr, even running
single-user (but only with SMP enabled), it always crashes the system,
generally with duplicate inodes under apr/work.
Here's the disk label:
# disklabel wd0
# /dev/rwd0d:
type: unknown
disk: ST9160823AS
label:
flags:
bytes/sector: 512
sectors/track: 63
tracks/cylinder: 16
sectors/cylinder: 1008
cylinders: 310101
total sectors: 312581808
rpm: 3600
interleave: 1
trackskew: 0
cylinderskew: 0
headswitch: 0 # microseconds
track-to-track seek: 0 # microseconds
drivedata: 0
16 partitions:
# size offset fstype [fsize bsize cpg/sgs]
a: 196402752 107775360 4.2BSD 2048 16384 0 # (Cyl. 106920 - 301763)
b: 8397648 304178112 swap # (Cyl. 301764 - 310094)
c: 204800400 107775360 unused 0 0 # (Cyl. 106920 - 310094)
d: 312581808 0 unused 0 0 # (Cyl. 0 - 310100)
e: 12894208 2048 unknown # (Cyl. 2*- 12793*)
f: 94878000 12897360 NTFS # (Cyl. 12795 - 106919)o
and mount:
# mount
/dev/wd0a on / type ffs (local)
mfs:149 on /tmp type mfs (synchronous, local)
kernfs on /kern type kernfs (local)
ptyfs on /dev/pts type ptyfs (local)
procfs on /proc type procfs (local)
In other words, nothing weird.
--Steve Bellovin, http://www.cs.columbia.edu/~smb
Home |
Main Index |
Thread Index |
Old Index