Date: Tue, 13 Apr 2010 17:12:55 -0400 (EDT) From: Charles Sprickman <spork@bway.net> To: freebsd-fs@freebsd.org Subject: g_vfs_done() errors on Dell/LSI RAID array Message-ID: <alpine.OSX.2.00.1004131700490.98088@hotlap.local>
next in thread | raw e-mail | index | archive | help
Hello, Not sure if this is the right place or if this is a geom issue, or a raid controller issue... Please point me in the right direction. Last night I saw the following in my daily output: +g_vfs_done():mfid0s1g[READ(offset=2456998070156636160, length=16384)]error = 5 +g_vfs_done():mfid0s1g[READ(offset=2456998070156636160, length=16384)]error = 5 +g_vfs_done():mfid0s1g[READ(offset=2456998070156636160, length=16384)]error = 5 I'm a bit confused, as some googling indicated that this has something to do with a mis-labelled disk, but that offset seems really huge, unless I'm comparing two different units. bsdlabel shows me this for that drive/array: # /dev/mfid0s1: 8 partitions: # size offset fstype [fsize bsize bps/cpg] a: 8388608 0 4.2BSD 2048 16384 28528 b: 12582912 8388608 swap c: 2928135357 0 unused 0 0 # "raw" part, don't edit d: 16777216 20971520 4.2BSD 2048 16384 28528 e: 16777216 37748736 4.2BSD 2048 16384 28528 f: 67108864 54525952 4.2BSD 2048 16384 28528 g: 2806500541 121634816 4.2BSD 2048 16384 28520 Adding the size plus offset, the end of my disk should be at 2928135357. The offset in the error is 2456998070156636160. Error 5 is apparently an "I/O Error". This is a Dell 2970 running amd64, 7.2-RELEASE. The RAID card is Dell's rebadged LSI: mfi0: <Dell PERC 6> port 0xec00-0xecff mem 0xe9f80000-0xe9fbffff,0xe9fc0000-0xe9ffffff irq 37 at device 0.0 on pci7 mfi0: Megaraid SAS driver Ver 3.00 mfi0: 3049 (boot + 3s/0x0020/info) - Firmware version 1.22.02-0612 mfi0: 3050 (boot + 23s/0x0008/info) - Battery Present mfi0: 3051 (boot + 23s/0x0020/info) - Controller hardware revision ID (0x0) mfi0: 3052 (boot + 23s/0x0020/info) - Package version 6.2.0-0013 There's some talk in this thread about whether this is either a driver issue, a geom issue, a filesystem issue, some weird bug that people only see on 64-bit AMD procs, etc.: http://old.nabble.com/g_vfs_done():da3s1a-READ(offset%3D81064794762854400,-length%3D8192)-error-%3D-5-td13199158.html Any help tracking down what this is trying to tell me would be appreciated. thanks, Charles ___ Charles Sprickman NetEng/SysAdmin Bway.net - New York's Best Internet - www.bway.net spork@bway.net - 212.655.9344
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?alpine.OSX.2.00.1004131700490.98088>