Date: Tue, 29 Jan 2013 18:44:46 +0200 From: Alexander Motin <mav@FreeBSD.org> To: Jeremy Chadwick <jdc@koitsu.org> Cc: freebsd-fs@freebsd.org, avg@freebsd.org Subject: Re: disk "flipped" - a known problem? Message-ID: <5107FC7E.8070108@FreeBSD.org> In-Reply-To: <20130125211232.GA3037@icarus.home.lan> References: <20130121221617.GA23909@icarus.home.lan> <50FED818.7070704@FreeBSD.org> <20130125083619.GA51096@icarus.home.lan> <20130125211232.GA3037@icarus.home.lan>
next in thread | previous in thread | raw e-mail | index | archive | help
On 25.01.2013 23:12, Jeremy Chadwick wrote: > Now about cam_periph_alloc -- I wanted to provide proof that I have seen > this message before / proving Andriy isn't crazy. :-) This is from > when I was messing about with this bad disk the day I received it: > > Jan 18 19:54:57 icarus kernel: ada5 at ahcich5 bus 0 scbus5 target 0 lun 0 > Jan 18 19:54:57 icarus kernel: ada5: <WDC WD1500ADFD-00NLR4 21.07QR4> ATA-7 SATA 1.x device > Jan 18 19:54:57 icarus kernel: ada5: 150.000MB/s transfers (SATA 1.x, UDMA6, PIO 8192bytes) > Jan 18 19:54:57 icarus kernel: ada5: Command Queueing enabled > Jan 18 19:54:57 icarus kernel: ada5: 143089MB (293046768 512 byte sectors: 16H 63S/T 16383C) > Jan 18 19:54:57 icarus kernel: ada5: Previously was known as ad14 > Jan 18 19:54:57 icarus kernel: cam_periph_alloc: attempt to re-allocate valid device pass5 rejected flags 0x18 refcount 1 > Jan 18 19:54:57 icarus kernel: passasync: Unable to attach new device due to status 0x6: CCB request was invalid > Jan 18 19:54:57 icarus kernel: GEOM_RAID: NVIDIA-6: Array NVIDIA-6 created. > Jan 18 19:55:27 icarus kernel: GEOM_RAID: NVIDIA-6: Force array start due to timeout. > Jan 18 19:55:27 icarus kernel: GEOM_RAID: NVIDIA-6: Disk ada5 state changed from NONE to ACTIVE. > Jan 18 19:55:27 icarus kernel: GEOM_RAID: NVIDIA-6: Subdisk RAID 0+1 279.47G:3-ada5 state changed from NONE to REBUILD. > Jan 18 19:55:27 icarus kernel: GEOM_RAID: NVIDIA-6: Array started. > Jan 18 19:55:27 icarus kernel: GEOM_RAID: NVIDIA-6: Volume RAID 0+1 279.47G state changed from STARTING to BROKEN. > Jan 18 19:55:39 icarus kernel: GEOM_RAID: NVIDIA-6: Volume RAID 0+1 279.47G state changed from BROKEN to STOPPED. > Jan 18 19:55:49 icarus kernel: GEOM_RAID: NVIDIA-6: Array NVIDIA-6 destroyed. > > So why didn't I see this message today? On January 20th I rebuild > world/kernel after removing GEOM_RAID from my kernel config. The reason > I removed GEOM_RAID is that, as you can see, that bad disk** was > previously in a system (not my own) with an nVidia SATA chipset with > their RAID option ROM enabled (my system is Intel, hence "array timeout" > since there's no nVidia option ROM, I believe). Array timeout means that within defined timeout GEOM RAID failed to detect all of array components. GEOM RAID doesn't depend on option ROM presence to access the data. Array was finally marked as BROKEN because it was one disk of RAID0+1's four. > I got sick and tired of having to "fight" with the kernel. The last two > messages were a result of me doing "graid stop ada5". And of course "dd > if=/dev/zero of=/dev/ada5 bs=64k" will cause GEOM to re-taste, causing > the RAID metadata to get re-read, "NVIDIA-7" created, rinse lather > repeat. But there's already a thread on this: > > http://lists.freebsd.org/pipermail/freebsd-fs/2013-January/016292.html > > Just easier for me to remove the option, that's all. I would personally prefer to erase unwanted stale metadata with `graid delete NVIDIA-7`. It erases only one sector where metadata stored and doesn't corrupt any other data on the disk. -- Alexander Motin
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?5107FC7E.8070108>