[Bug 205834] rtadvd: accessing freed struct
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=205834 Andrey V. Elsukov changed: What|Removed |Added Assignee|freebsd-bugs@FreeBSD.org|freebsd-...@freebsd.org -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 206721] FreeBSDs DHCP client(dhclient) does not support the interface-mtu option(option 26).
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=206721 Andrey V. Elsukov changed: What|Removed |Added Assignee|freebsd-bugs@FreeBSD.org|a...@freebsd.org CC||a...@freebsd.org -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 206762] -Wtautilogical-pointer-compare issues with drm(4) code
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=206762 --- Comment #4 from Jean-Sébastien Pédron --- Yes, the check looks wrong. Some time ago, I verified in later versions of Linux and it was still there. I didn't look again recently if it was fixed. I had no time to report this yet. -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 206820] [ext2fs] Panic when writing to ext3fs mounted as ext2fs
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=206820
Bug ID: 206820
Summary: [ext2fs] Panic when writing to ext3fs mounted as
ext2fs
Product: Base System
Version: 9.3-STABLE
Hardware: Any
OS: Any
Status: New
Severity: Affects Only Me
Priority: ---
Component: kern
Assignee: freebsd-bugs@FreeBSD.org
Reporter: ard...@yahoo.it
I encountered two panics on the very same operation: writing files to a ext3fs
formatted USB drive that is mounted as ext2fs.
The filesystem is created by a shell script, issuing the following commands:
# mkfs.ext3 /dev/da0s1
# tune2fs -O ^dir_index /dev/da0s1
# mount -t ext2fs /dev/da0s1 /mnt
And files are extracted from a tar archive (produced by gnu tar):
# ssh linuxhost 'cat filesystem.tar.bz2' | tar -C /mnt -xjf -'
My system is a 9-STABLE updated this morning.
# uname -a
FreeBSD myhost 9.3-STABLE FreeBSD 9.3-STABLE #144 r295117M: Mon Feb 1 09:31:54
CET 2016 root@myhost:/usr/obj/usr/src/sys/GENERIC i386
Both panics are triggered by function ext2_i2ei at
/usr/src/sys/modules/ext2fs/../../fs/ext2fs/ext2_inode_cnv.c:152
Here is an excerpt of the backtrace:
[...]
#7 0xc0f9fee7 in calltrap () at /usr/src/sys/i386/i386/exception.s:173
#8 0xd00f5759 in ext2_i2ei (ip=0xcab8f100, ei=0xe17e0f80)
at /usr/src/sys/modules/ext2fs/../../fs/ext2fs/ext2_inode_cnv.c:152
#9 0xd00f4a56 in ext2_update (vp=0xce0f38e0, waitfor=1)
at /usr/src/sys/modules/ext2fs/../../fs/ext2fs/ext2_inode.c:91
#10 0xd00fad12 in ext2_makeinode (mode=8, dvp=0xcc69f11c, vpp=0xeffeab88,
cnp=0xeffeab9c)
at /usr/src/sys/modules/ext2fs/../../fs/ext2fs/ext2_vnops.c:1586
#11 0xc0fdd612 in VOP_CREATE_APV (vop=0xd00fe3a0, a=0xeffeaae8)
at vnode_if.c:260
#12 0xc0b9d989 in vn_open_cred (ndp=0xeffeab5c, flagp=0xeffeac24,
cmode=, vn_open_flags=0, cred=0xc9ee7100,
fp=0xcafea508) at vnode_if.h:109
#13 0xc0b9de6b in vn_open (ndp=0xeffeab5c, flagp=0xeffeac24, cmode=493,
fp=0xcafea508) at /usr/src/sys/kern/vfs_vnops.c:113
#14 0xc0b99460 in kern_openat (td=0xc8420900, fd=-100,
path=0x284a61a0 ,
pathseg=UIO_USERSPACE, flags=2562, mode=493)
at /usr/src/sys/kern/vfs_syscalls.c:1128
#15 0xc0b998b5 in kern_open (td=0xc8420900,
path=0x284a61a0 ,
pathseg=UIO_USERSPACE, flags=2561, mode=493)
at /usr/src/sys/kern/vfs_syscalls.c:1079
#16 0xc0b998f0 in sys_open (td=0xc8420900, uap=0xeffeaccc)
at /usr/src/sys/kern/vfs_syscalls.c:1055
#17 0xc0fb6869 in syscall (frame=0xeffead08) at subr_syscall.c:142
#18 0xc0f9ff8c in Xint0x80_syscall ()
at /usr/src/sys/i386/i386/exception.s:279
When kgdb'ing into frame 8, the pointer to ei seems not to be valid:
(kgdb) frame 8
#8 0xd00f5759 in ext2_i2ei (ip=0xcab8f100, ei=0xe17e0f80)
at /usr/src/sys/modules/ext2fs/../../fs/ext2fs/ext2_inode_cnv.c:152
152 ei->e2di_ctime_extra = NSEC_TO_XTIME(ip->i_ctimensec);
(kgdb) print *ip
$1 = {i_vnode = 0xce0f38e0, i_ump = 0xccadc240, i_flag = 0, i_number = 122888,
i_e2fs = 0xc7798c00, i_modrev = 62488400780442, i_count = 0, i_endoff = 0,
i_diroff = 0, i_offset = 0, i_block_group = 60, i_next_alloc_block = 0,
i_next_alloc_goal = 0, i_mode = 33261, i_nlink = 1, i_uid = 0, i_gid = 0,
i_size = 0, i_blocks = 0, i_atime = 1454332232, i_mtime = 1454332232,
i_ctime = 1454332232, i_birthtime = 1454332232, i_mtimensec = 70012,
i_atimensec = 70012, i_ctimensec = 70012, i_birthnsec = 700118000,
i_gen = 1784569991, i_flags = 0, i_db = {0 }, i_ib = {0,
0, 0}, i_ext_cache = {ec_start = 0, ec_blk = 0, ec_len = 0, ec_type = 0}}
(kgdb) print *ei
Cannot access memory at address 0xe17e0f80
Some information from the previous frame:
(kgdb) frame 9
#9 0xd00f4a56 in ext2_update (vp=0xce0f38e0, waitfor=1)
at /usr/src/sys/modules/ext2fs/../../fs/ext2fs/ext2_inode.c:91
91 ext2_i2ei(ip, (struct ext2fs_dinode *)((char *)bp->b_data +
(kgdb) print bp
$2 = (struct buf *) 0xe112a8a8
(kgdb) print *bp
$3 = {b_bufobj = 0xcbe062e4, b_bcount = 1024, b_caller1 = 0x0,
b_data = 0xe17e0c00 "íA", b_error = 0, b_iocmd = 2 '\002',
b_ioflags = 2 '\002', b_iooffset = 503319552, b_resid = 0, b_iodone = 0,
b_blkno = 983046, b_offset = 503319552, b_bobufs = {tqe_next = 0x0,
tqe_prev = 0xe1231828}, b_left = 0xe12317f0, b_right = 0x0, b_vflags = 0,
b_freelist = {tqe_next = 0x0, tqe_prev = 0xe123183c}, b_qindex = 2,
b_flags = 2684354720, b_xflags = 1 '\001', b_lock = {lock_object = {
lo_name = 0xc10fe54f "bufwait", lo_flags = 108199936, lo_data = 0,
lo_witness = 0x0}, lk_lock = 3359770880, lk_exslpfail = 0, lk_timo = 0,
lk_pri = 96}, b_bufsize = 1024, b_runningbufspace = 0,
b_kvabase = 0xe17e "#", b_kvaalloc = 0x0, b_kvasize = 16384,
b_lblkno = 983046, b_vp = 0xcbe06238, b_dirtyoff = 0, b_dirtyend = 0,
b_
[Bug 206820] [ext2fs] Panic when writing to ext3fs mounted as ext2fs
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=206820 --- Comment #1 from Arrigo Marchiori --- Created attachment 166396 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=166396&action=edit /var/crash/core.txt from the first panic -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 206820] [ext2fs] Panic when writing to ext3fs mounted as ext2fs
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=206820 --- Comment #2 from Arrigo Marchiori --- Created attachment 166397 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=166397&action=edit /var/crash/core.txt from the second panic -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 206649] [PATCH] Common gestures for Cypress i2c touchpad
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=206649 Alexander Mishurov changed: What|Removed |Added Attachment #166152|0 |1 is obsolete|| --- Comment #1 from Alexander Mishurov --- Created attachment 166401 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=166401&action=edit Fix enum constant -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 206820] [ext2fs] Panic when writing to ext3fs mounted as ext2fs
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=206820
--- Comment #3 from Arrigo Marchiori ---
The panic is also reproducible when writing to a md(4) instead of a USB drive.
The stack trace is analogous.
(kgdb) bt
#0 doadump (textdump=1) at pcpu.h:250
#1 0xc0aed3ae in kern_reboot (howto=260)
at /usr/src/sys/kern/kern_shutdown.c:454
#2 0xc0aed6a5 in panic (fmt=)
at /usr/src/sys/kern/kern_shutdown.c:642
#3 0xc0d70ede in vm_fault_hold (map=0xc1b8d000, vaddr=3799322624,
fault_type=2 '\002', fault_flags=0, m_hold=0x0)
at /usr/src/sys/vm/vm_fault.c:289
#4 0xc0d7355b in vm_fault (map=0xc1b8d000, vaddr=3799322624,
fault_type=, fault_flags=0)
at /usr/src/sys/vm/vm_fault.c:229
#5 0xc0fb619f in trap_pfault (frame=0xf0a8c964, usermode=0, eva=3799322628)
at /usr/src/sys/i386/i386/trap.c:932
#6 0xc0fb744b in trap (frame=0xf0a8c964) at /usr/src/sys/i386/i386/trap.c:553
#7 0xc0f9fee7 in calltrap () at /usr/src/sys/i386/i386/exception.s:173
#8 0xcc966759 in ext2_i2ei (ip=0xc7ba8300, ei=0xe2750f80)
at /usr/src/sys/modules/ext2fs/../../fs/ext2fs/ext2_inode_cnv.c:152
#9 0xcc965a56 in ext2_update (vp=0xc99c5470, waitfor=1)
at /usr/src/sys/modules/ext2fs/../../fs/ext2fs/ext2_inode.c:91
#10 0xcc96bd12 in ext2_makeinode (mode=8, dvp=0xc99c46a8, vpp=0xf0a8cb88,
cnp=0xf0a8cb9c)
at /usr/src/sys/modules/ext2fs/../../fs/ext2fs/ext2_vnops.c:1586
#11 0xc0fdd612 in VOP_CREATE_APV (vop=0xcc96f3a0, a=0xf0a8cae8)
at vnode_if.c:260
#12 0xc0b9d989 in vn_open_cred (ndp=0xf0a8cb5c, flagp=0xf0a8cc24,
cmode=, vn_open_flags=0, cred=0xc8bcf600,
fp=0xc940bdc8) at vnode_if.h:109
#13 0xc0b9de6b in vn_open (ndp=0xf0a8cb5c, flagp=0xf0a8cc24, cmode=493,
fp=0xc940bdc8) at /usr/src/sys/kern/vfs_vnops.c:113
#14 0xc0b99460 in kern_openat (td=0xca383900, fd=-100,
path=0x284a61a0 , pathseg=UIO_USERSPACE,
flags=2562, mode=493) at /usr/src/sys/kern/vfs_syscalls.c:1128
#15 0xc0b998b5 in kern_open (td=0xca383900,
path=0x284a61a0 , pathseg=UIO_USERSPACE,
flags=2561, mode=493) at /usr/src/sys/kern/vfs_syscalls.c:1079
#16 0xc0b998f0 in sys_open (td=0xca383900, uap=0xf0a8)
at /usr/src/sys/kern/vfs_syscalls.c:1055
#17 0xc0fb6869 in syscall (frame=0xf0a8cd08) at subr_syscall.c:142
#18 0xc0f9ff8c in Xint0x80_syscall () at /usr/src/sys/i386/i386/exception.s:279
(kgdb) frame 8
#8 0xcc966759 in ext2_i2ei (ip=0xc7ba8300, ei=0xe2750f80)
at /usr/src/sys/modules/ext2fs/../../fs/ext2fs/ext2_inode_cnv.c:152
152 ei->e2di_ctime_extra = NSEC_TO_XTIME(ip->i_ctimensec);
(kgdb) print *ip
$1 = {i_vnode = 0xc99c5470, i_ump = 0xc7b92380, i_flag = 0, i_number = 49160,
i_e2fs = 0xc7858c00, i_modrev = 18475684767084, i_count = 0, i_endoff = 0,
i_diroff = 0, i_offset = 0, i_block_group = 24, i_next_alloc_block = 0,
i_next_alloc_goal = 0, i_mode = 33261, i_nlink = 1, i_uid = 0, i_gid = 0,
i_size = 0, i_blocks = 0, i_atime = 1454338085, i_mtime = 1454338085,
i_ctime = 1454338085, i_birthtime = 1454338085, i_mtimensec = 52281,
i_atimensec = 52281, i_ctimensec = 52281, i_birthnsec = 522809000,
i_gen = 679956546, i_flags = 0, i_db = {0 }, i_ib = {0, 0,
0}, i_ext_cache = {ec_start = 0, ec_blk = 0, ec_len = 0, ec_type = 0}}
(kgdb) print *ei
Cannot access memory at address 0xe2750f80
(kgdb) frame 9
#9 0xcc965a56 in ext2_update (vp=0xc99c5470, waitfor=1)
at /usr/src/sys/modules/ext2fs/../../fs/ext2fs/ext2_inode.c:91
91 ext2_i2ei(ip, (struct ext2fs_dinode *)((char *)bp->b_data +
(kgdb) print *vp
$2 = {v_type = VREG, v_tag = 0xcc96e830 "ext2fs", v_op = 0xcc96f3a0,
v_data = 0xc7ba8300, v_mount = 0xc7dc77ec, v_nmntvnodes = {tqe_next = 0x0,
tqe_prev = 0xc99c56bc}, v_un = {vu_mount = 0x0, vu_socket = 0x0,
vu_cdev = 0x0, vu_fifoinfo = 0x0}, v_hashlist = {le_next = 0x0,
le_prev = 0xc793f988}, v_hash = 49160, v_cache_src = {lh_first = 0x0},
v_cache_dst = {tqh_first = 0x0, tqh_last = 0xc99c54a0}, v_cache_dd = 0x0,
v_cstart = 0, v_lasta = 0, v_lastw = 0, v_clen = 0, v_lock = {lock_object = {
lo_name = 0xcc96e830 "ext2fs", lo_flags = 108199944, lo_data = 0,
lo_witness = 0x0}, lk_lock = 3392682240, lk_exslpfail = 0, lk_timo = 51,
lk_pri = 96}, v_interlock = {lock_object = {
lo_name = 0xc11003e9 "vnode interlock", lo_flags = 16973824,
lo_data = 0, lo_witness = 0x0}, mtx_lock = 4}, v_vnlock = 0xc99c54c8,
v_holdcnt = 1, v_usecount = 1, v_iflag = 512, v_vflag = 0, v_writecount = 0,
v_actfreelist = {tqe_next = 0xc99c56a8, tqe_prev = 0xc7dc782c}, v_bufobj = {
bo_mtx = {lock_object = {lo_name = 0xc11003f9 "bufobj interlock",
lo_flags = 16973824, lo_data = 0, lo_witness = 0x0}, mtx_lock = 4},
bo_clean = {bv_hd = {tqh_first = 0x0, tqh_last = 0xc99c5530},
bv_root = 0x0, bv_cnt = 0}, bo_dirty = {bv_hd = {tqh_first = 0x0,
tqh_last = 0xc99c5540}, bv_root = 0x0, bv_cnt = 0}, bo_numoutput = 0,
bo_flag = 0, bo_ops = 0xc1371e80, bo_bsize = 1024, bo_ob
[Bug 206820] [ext2fs] Panic when writing to ext3fs mounted as ext2fs
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=206820 --- Comment #4 from Arrigo Marchiori --- Running e2fsck on the md(4)-backed file, after reboot: # e2fsck /dev/md0s1 e2fsck 1.42.13 (17-May-2015) /dev/md0s1 was not cleanly unmounted, check forced. Pass 1: Checking inodes, blocks, and sizes Inode 30721, i_size is 24, should be 1024. Fix? yes Inode 49154 is in use, but has dtime set. Fix? yes Inode 110593, i_size is 24, should be 1024. Fix? yes Inode 126977, i_size is 24, should be 1024. Fix? yes Pass 2: Checking directory structure Pass 3: Checking directory connectivity Pass 4: Checking reference counts Pass 5: Checking group summary information Block bitmap differences: +123139 +(196867--196880) +197137 +(197426--197445) +197702 +(197876--197888) +442627 +508163 Fix? yes Free blocks count wrong for group #15 (7934, counted=7933). Fix? yes Free blocks count wrong for group #24 (7934, counted=7885). Fix? yes Free blocks count wrong for group #54 (7934, counted=7933). Fix? yes Free blocks count wrong for group #62 (7934, counted=7933). Fix? yes Free blocks count wrong (497201, counted=497149). Fix? yes Inode bitmap differences: +30721 +(49153--49159) +110593 +126977 Fix? yes Free inodes count wrong for group #15 (2048, counted=2047). Fix? yes Directories count wrong for group #15 (0, counted=1). Fix? yes Free inodes count wrong for group #24 (2048, counted=2041). Fix? yes Directories count wrong for group #24 (0, counted=1). Fix? yes Free inodes count wrong for group #54 (2048, counted=2047). Fix? yes Directories count wrong for group #54 (0, counted=1). Fix? yes Free inodes count wrong for group #62 (2048, counted=2047). Fix? yes Directories count wrong for group #62 (0, counted=1). Fix? yes Free inodes count wrong (131061, counted=131051). Fix? yes /dev/md0s1: * FILE SYSTEM WAS MODIFIED * /dev/md0s1: 21/131072 files (9.5% non-contiguous), 27135/524284 blocks -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 206820] [ext2fs] Panic when writing to ext3fs mounted as ext2fs
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=206820 --- Comment #5 from Arrigo Marchiori --- FWIW, the problem is _not_ reproducible on my 10-RELEASE x86-64 machine: # uname -a FreeBSD myhost 10.1-RELEASE-p26 FreeBSD 10.1-RELEASE-p26 #0: Wed Jan 13 20:59:29 UTC 2016 r...@amd64-builder.daemonology.net:/usr/obj/usr/src/sys/GENERIC amd64 -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 206820] [ext2fs] Panic when writing to ext3fs mounted as ext2fs
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=206820 Mark Linimon changed: What|Removed |Added Assignee|freebsd-bugs@FreeBSD.org|freebsd...@freebsd.org -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 206829] /usr/share/dtrace/toolkit/hotcpu perl
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=206829 Bug ID: 206829 Summary: /usr/share/dtrace/toolkit/hotcpu perl Product: Base System Version: 10.2-RELEASE Hardware: Any OS: Any Status: New Severity: Affects Many People Priority: --- Component: misc Assignee: freebsd-bugs@FreeBSD.org Reporter: aduit...@gmail.com The /usr/share/dtrace/toolkit/hotcpu script has '/usr/bin/perl' as its interpreter. Of course, Perl is no longer in the Base System, so this should probably be changed to something like '/usr/bin/env perl'. -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 205359] Add support for Advantech PCI-1602 rev B board and PCI-1603
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=205359 --- Comment #3 from j...@transactionware.com --- (In reply to Marius Strobl from comment #2) Thanks for the update Marius. I will import into our tree and test. -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 206829] /usr/share/dtrace/toolkit/hotcpu perl
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=206829 NGie Cooper changed: What|Removed |Added CC||ma...@freebsd.org, ||n...@freebsd.org --- Comment #1 from NGie Cooper --- There isn't a hotcpu dtrace script in the tree. Granted, there are a number of DTrace scripts in cddl/... that still reference /usr/bin/perl, but this wasn't one of them (and Mark fixed a few on head). % find . -name \*hotcpu\* % git log -n 1 commit 023162425ee9a240c7424fcbb8e0a96f6bebfaf5 Author: glebius Date: Thu Jan 14 22:48:13 2016 + Fix typo. Approved by:so Notes: svn path=/releng/10.2/; revision=294052 -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 206836] Random Lockups of partition /var
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=206836 Bug ID: 206836 Summary: Random Lockups of partition /var Product: Base System Version: 10.2-RELEASE Hardware: amd64 OS: Any Status: New Severity: Affects Some People Priority: --- Component: kern Assignee: freebsd-bugs@FreeBSD.org Reporter: schm...@ze.tum.de CC: freebsd-am...@freebsd.org CC: freebsd-am...@freebsd.org I have 64 Servers Running on Supermicro blades. Most of them running 10.1-release. We are in the process of updating them to 10.2-release. On all updated systems the /var partition locks after 20 to 50 days. Services on the system start to fail. Login Block. On Preopen Connections I can access all other partitions just fine. Just accessing anything on /var blocks the whole process without return. There are no massages on the console. We have to force power off to restart the system. All partitions where SU+Journaling. I've deactivated journaling on all partitions but the lockups are still coming. On all systems are different services. (MySQL, Jenkins, Apache). The same Hardware was working and still is working on 10.1-Release an earlier releases just fine. Hostname dd.mm. hh:mm Actions taken --- amnesix 7. 9.2015 10:30 Reboot miraculix 29. 9.2015 03:00 Reboot amnesix18.10.2015 05:00 Reboot amnesix29.11.2015 16:00 Reboot. Disabled journaling olympia12.12.2015 11:00 Reboot. Disabled journaling devzope17.12.2015 04:00 Reboot. Disabled journaling miraculix 22.12.2015 01:20 Reboot. Disabled journaling olympia30.12.2015 19:00 Reboot amnesix 9. 1.2016 02:00 Reboot. fsck -f on all partitions delphi 28. 1.2016 05:40 Reboot. Disabled journaling. fsck -f devzope30. 1.2016 04:50 Reboot. fsck -f devzope 1. 2.2016 01:45 Reboot. fsck -f miraculix 2. 2.2016 06:30 Reboot. fsck -f The symptoms are always the same. After the Power down and reboot the Raid is resyncing but the system is working just fine until the next lookup. I've attached the dmesg.boot of one of the servers. They are all identical. -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 206836] Random Lockups of partition /var
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=206836 schm...@ze.tum.de changed: What|Removed |Added CC||schm...@ze.tum.de --- Comment #1 from schm...@ze.tum.de --- Created attachment 166418 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=166418&action=edit dmesg.boot of one of the servers -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
