On Tuesday, 12 December 2006 00:54, Neil Brown wrote: > On Tuesday December 12, [EMAIL PROTECTED] wrote: > > On Monday, 11 December 2006 23:52, Neil Brown wrote: > > > On Monday December 11, [EMAIL PROTECTED] wrote: > > > > Hi, > > > > > > > > On Monday, 11 December 2006 09:58, Andrew Morton wrote: > > > > > > > > > > Temporarily at > > > > > > > > > > http://userweb.kernel.org/~akpm/2.6.19-mm1/ > > > > > > > > > > Will appear later at > > > > > > > > > > > > > > > ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.19/2.6.19-mm1/ > > > > > > > > It caused all of the md RAID1s on my test box to drop one of their > > > > partitions, > > > > apparently at random. > > > > > > That's clever.... > > > > > > Do you have any kernel logs of this happening? My guess would be the > > > underlying device driver is returned more errors than before, but we > > > need the logs to be sure. > > > > I've only found lots of messages like this: > > > > md: super_written gets error=-5, uptodate=0 > > So when md writes to write out the superblock, to gets EIO... Odd that > you aren't getting errors for normal writes. > > What devices are the md/raid1 built on?
Sata drives, on sata_uli.
> >
> > I'll try to reproduce it tomorrow and collect some more information.
>
> Thanks. More information is definitely better than less, so send over
> anything you can find.
Okay, seems to be readily reproducible, dmesg output from the failing kernel
attached.
Greetings,
Rafael
--
If you don't have the time to read,
you don't have the time or the tools to write.
- Stephen King
dmesg.log.gz
Description: GNU Zip compressed data
