Re: Occasional crashes, Bug or dying disk?

[Jonathan T. Looney]

On 2/2/16, 5:53 PM, "owner-freebsd-curr...@freebsd.org on behalf of
Christian Walther"  wrote:

>Hello list,
>
>since updating the current installation on my trusty Thinkpad T43 I
>keep getting occasional crashes like the following:
>
>#1  0xc0c23a03 in kern_reboot (howto=260)
>at /usr/src/sys/kern/kern_shutdown.c:364
>#2  0xc0c23f3d in vpanic (fmt=, ap=out>)
>at /usr/src/sys/kern/kern_shutdown.c:757
>#3  0xc0c23f5b in panic (fmt=0xc1590fad "ffs_blkfree_cg: freeing free
>frag")
>at /usr/src/sys/kern/kern_shutdown.c:688
>[...]
>I wonder if this might be a bug in FFS or a related subsystem, or my
>hard disk dying. smartctl lists several READ DMA und WRITE DMA related
>errors.

I (and several others) spent time trying to track down "the bug" causing
panics like this on a particular set of hardware. I finally wrote a
program that wrote and read byte patterns from the disk (using O_DIRECT).
I found that what the program read back didn't match what it wrote. In
circumstances like that, you can't expect any filesystem to work reliably.

Given the long pedigree of the UFS/FFS code, I think it is much more
likely to be a hardware problem than a problem with the UFS/FFS code.

Jonathan


___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Occasional crashes, Bug or dying disk?

[Christian Walther]

Hello list,

since updating the current installation on my trusty Thinkpad T43 I
keep getting occasional crashes like the following:

#1  0xc0c23a03 in kern_reboot (howto=260)
at /usr/src/sys/kern/kern_shutdown.c:364
#2  0xc0c23f3d in vpanic (fmt=, ap=)
at /usr/src/sys/kern/kern_shutdown.c:757
#3  0xc0c23f5b in panic (fmt=0xc1590fad "ffs_blkfree_cg: freeing free frag")
at /usr/src/sys/kern/kern_shutdown.c:688
#4  0xc0eb467a in ffs_blkfree_cg (ump=0xc7e11000, fs=0xc7e120d4,
devvp=, bno=32075253, size=,
inum=, dephd=)
at /usr/src/sys/ufs/ffs/ffs_alloc.c:2237
#5  0xc0eb0b27 in ffs_blkfree (ump=0x0, fs=0x0, devvp=0xc7abdc34,
bno=32075253, size=4096, vtype=,
dephd=) at /usr/src/sys/ufs/ffs/ffs_alloc.c:2343
#6  0xc0edea9a in freework_freeblock (freework=)
at /usr/src/sys/ufs/ffs/ffs_softdep.c:7749
#7  0xc0ed1f85 in handle_workitem_freeblocks (freeblks=0xc76a5d00, flags=512)
at /usr/src/sys/ufs/ffs/ffs_softdep.c:7803
#8  0xc0eda341 in process_worklist_item (mp=)
at /usr/src/sys/ufs/ffs/ffs_softdep.c:1799
#9  0xc0ec5d5f in softdep_process_worklist (mp=0xc7d8fd20, full=0)
at /usr/src/sys/ufs/ffs/ffs_softdep.c:1593
#10 0xc0eca3ee in softdep_flush (addr=0xc7d8fd20)
at /usr/src/sys/ufs/ffs/ffs_softdep.c:1395
#11 0xc0be7c9e in fork_exit (callout=0xc0eca310 )
at /usr/src/sys/kern/kern_fork.c:1010
#12 0xc1162d50 in fork_trampoline () at /usr/src/sys/i386/i386/exception.s:287

I wonder if this might be a bug in FFS or a related subsystem, or my
hard disk dying. smartctl lists several READ DMA und WRITE DMA related
errors.
Appears to be related to Bug 132960, which might celebrate it's 10th
birthday soon. ;)


Any ideas?


Best wishes,
Christian Walther
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"