Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 25 Apr 2013 09:06:49 -0500
From:      Guy Helmer <guy.helmer@gmail.com>
To:        FreeBSD Stable <freebsd-stable@freebsd.org>
Subject:   FreeBSD 9: fdisk -It crashes kernel
Message-ID:  <80F41679-9C3A-4E61-8AAD-403410344C32@gmail.com>

next in thread | raw e-mail | index | archive | help
Encountered a surprise when my disk resizing rc.d script caused FreeBSD =
9.1-STABLE to crash. I used "fdisk -It ada0" to determine what the =
available size of the disk (which happened to be the root disk), and on =
FreeBSD 9.1 the kernel comes crashing down:

+ fdisk -It ada0
+ /rescue/sed -En 's,.*start ([0-9]+).*size ([0-9]+).*,\1 + \2,p'
vnode_pager_getpages: I/O read error
vm_fault: pager read error, pid 65 (fdisk)
pid 65 (fdisk), uid 0: exited on signal 11
eval: arithmetic expression: expecting primary: ""
Entropy harvesting: point_to_pointeval: date: Device not configured
eval: df: Device not configured
eval: dmesg: Device not configured
cat: /bin/ls: Device not configured
 kickstart.
eval: cannot open /etc/fstab: Device not configured
eval: cannot open /etc/fstab: Device not configured
eval: swapon: Device not configured
Warning! No /etc/fstab: skipping disk checks
fstab: /etc/fstab:0: Device not configured

Fatal trap 12: page fault while in kernel mode
cpuid =3D 1; apic id =3D 01
fault virtual address   =3D 0x0
fault code                     =3D supervisor read, page not present
instruction pointer      =3D 0x20:0xc0825fc4
stack pointer               =3D 0x28:0xc5a088c8
frame pointer              =3D 0x28:0xc5a08914
code segment            =3D base 0x0, limit 0xfffff, type 0x1b
                                     =3D DLP 0, pres 1, def32 1, gran 1
processor eflags       =3D interrupt enabled, resume, IOPL =3D 0
current process         =3D 91 (mount)
[ thread pid 91 tid 100056 ]
Stopped at  g_access+0x24: mlvl 0(%ebx),%eax
db> where
Tracing pid 91 tid 100056 td 0xc84c42f0
g_access(c8481d34,0,1,1,0,=85) at g_access+0x24/frame 0xc5a08914
ffs_mount(c8481d34,c0d78380,2,c5a08c00,c829ae6c,=85) af =
ffs_mount+0xf74/frame 0xc5a08a34
vfs_donmount(c84c42f0,10000,0,c84cf200,c84cf200,=85) at =
vfs_donmount+0x1423/frame 0xc5a08c24
sys_nmount(c84c42f0,c5a08ccc,c5a08cc4,1010006,c5a08d08,=85) at =
sys_nmount+0x7f/frame 0xc5a08c48
syscall(c5a08d08) at syscall+0x443/frame 0xc508cfc
Xint0x80_syscall() at Xint0x80_syscall+0x21/frame 0xc5a08cfc
--- syscall (378, FreeBSD ELF32, sys_nmount), eip =3D 0x480d5feb, esp =3D =
0xbfbfce1c, ebp =3D 0xbfbfd378 ---



I'll fix my script to not do this, but it seems odd that fdisk -It can =
make the disk "go away".

Guy=



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?80F41679-9C3A-4E61-8AAD-403410344C32>