Date: Fri, 08 Feb 2008 20:22:13 -0800 From: Julian Elischer <julian@elischer.org> To: Joe Peterson <joe@skyrush.com> Cc: freebsd-fs@freebsd.org, freebsd-stable@freebsd.org Subject: Re: Analysis of disk file block with ZFS checksum error Message-ID: <47AD2A75.8010908@elischer.org> In-Reply-To: <47AD1979.8020704@skyrush.com> References: <47ACD7D4.5050905@skyrush.com> <D6B0BBFB-D6DB-4DE1-9094-8EA69710A10C@apple.com> <47ACDE82.1050100@skyrush.com> <20080208173517.rdtobnxqg4g004c4@www.wolves.k12.mo.us> <47ACF0AE.3040802@skyrush.com> <47ACF338.3020802@elischer.org> <47AD1979.8020704@skyrush.com>
index | next in thread | previous in thread | raw e-mail
Joe Peterson wrote: > Julian Elischer wrote: >> it could be an old file.. >> what kind of disks? > > It's a Seagate ST3500630A parallel ATA drive. > >> I had a scenario where 3ware controllers were just failing to write to >> a drive in the array, so old data showed through. > > I have an Intel ICH4 controller - nothing unusual. > >> the filesystem and the partitions and the raids all were on different >> alignments so teh only part of the system that had a boundary that >> aligned with the bad data was the physical stripes laid down by the >> controller. It was 64k stripes and 64k data missing, exactly on >> stripe boundaries. Due to the fact that FreeBSD had partitioned the >> drive staring at 63 blocks in, nothing else aligned with the problem. > > Hmm, well this is a straight-forward disk situation - never used RAID on > this drive. Give what is happening, I wonder the changes of it being > HW, OS, or a filesystem issue. > > -Joe still, see whether the 64k lines up with the drive or with the filesystem (if the filesystem is not on an exact 64k boundary of the drive).home | help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?47AD2A75.8010908>