File System Corruption with 2.2.18

File System Corruption with 2.2.18

[Terrence Martin]

I am having all sorts of nasty file corruption problems with 2.2.18
patched with
ide.2.2.18.1221.patch.gz
linux-2.2.18-reiserfs-3.5.29-patch.gz
raid-2.2.18-B0

The corruption is occuring on my WDC AC28400R(I also had a problem with
a 13GB WDC as well which I swapped out last night). This is the only
hard drive that is on the onboard controller which is a VIA Technologies
VT 82C586 Apollo IDE (rev 6) chipset. The drive does share the IDE bus
with a internal ATAPI Zip drive. The cable I am using to connect the WDC
is a UDMA66 40pin 80 wire cable. I realize I do not have a UDMA66
controller, or disk, but I was having problems installing with a
standard 40 pin, 40 wire cable that the 80 wire seemed to alleviate.

The other drives are my software RAID setup on 2 Promise PDC20262
controllers with 1 drive per interface for a total of 4 drives. These
drives are Quantum 13X(?) 13GB drives. I am running the default RH6.2
kernel right now for stability with no support for my promise
controllers and I am writing this from a remote site so not sure of
other distinguishing marks of the quantum HD's.

So my question is does anyone have any idea what might cause ide dma
errors to occur when I use this kernel? As I mentioned file corruption
seems to only occur on the WDC drive(s) and manisfest itself as
executables suddenly becoming unreadable binary files, strange file
permissions on new files, and X windows going completely nuts when it
tries to start. I reboot back to the stock 2.2.14 with RH and everything
seems to work fine, excepting that I cannot access my RAID device of
course. :)

I have had this problem across two mother boards(both VIA chipsets), two
CPU's, two WDC Hard drives and the cable swap. I have not swapped RAM.

Thanks for any assistance/suggestions that you might be able to render.

Regards
Terrence Martin

P.S. More specific system information follows

hdparm /dev/hda

/dev/hda:
 multcount    =  0 (off)
 I/O support  =  0 (default 16-bit)
 unmaskirq    =  0 (off)
 using_dma    =  0 (off)
 keepsettings =  0 (off)
 nowerr       =  0 (off)
 readonly     =  0 (off)
 readahead    =  8 (on)
 geometry     = 16383/16/63, sectors = 16514064, start = 0

hdparm -i /dev/hda

/dev/hda:

 Model=WDC AC28400R, FwRev=15.01J55, SerialNo=WD-WM6280172815
 Config={ HardSect NotMFM HdSw>15uSec SpinMotCtl Fixed DTR>5Mbs
FmtGapReq }
 RawCHS=16383/16/63, TrkSize=57600, SectSize=600, ECCbytes=40
 BuffType=3(DualPortCache), BuffSize=512kB, MaxMultSect=16, MultSect=off

 DblWordIO=no, OldPIO=2, DMA=yes, OldDMA=0
 CurCHS=16383/16/63, CurSects=-66060037, LBA=yes, LBAsects=16514064
 tDMA={min:120,rec:120}, DMA modes: mword0 mword1 mword2
 IORDY=on/off, tPIO={min:160,w/IORDY:120}, PIO modes: mode3 mode4
 UDMA modes: mode0 mode1 *mode2

cat /proc/pci
PCI devices found:
  Bus  0, device   0, function  0:
    Host bridge: VIA Technologies VT 82C597 Apollo VP3 (rev 4).
      Medium devsel.  Fast back-to-back capable.  Master Capable.
Latency=16.
      Prefetchable 32 bit memory at 0xe0000000 [0xe0000008].
  Bus  0, device   1, function  0:
    PCI bridge: VIA Technologies VT 82C598 Apollo MVP3 AGP (rev 0).
      Medium devsel.  Master Capable.  No bursts.  Min Gnt=12.
  Bus  0, device   7, function  0:
    ISA bridge: VIA Technologies VT 82C586 Apollo ISA (rev 71).
      Medium devsel.  Master Capable.  No bursts.
  Bus  0, device   7, function  1:
    IDE interface: VIA Technologies VT 82C586 Apollo IDE (rev 6).
      Medium devsel.  Fast back-to-back capable.  Master Capable.
Latency=64.
      I/O at 0xb400 [0xb401].
  Bus  0, device   8, function  0:
    Unknown mass storage controller: Promise Technology Unknown device
(rev 1).
      Vendor id=105a. Device id=4d38.
      Medium devsel.  IRQ 5.  Master Capable.  Latency=64.
      I/O at 0xb800 [0xb801].
      I/O at 0xbc00 [0xbc01].
      I/O at 0xc000 [0xc001].
      I/O at 0xc400 [0xc401].
      I/O at 0xc800 [0xc801].
      Non-prefetchable 32 bit memory at 0xea000000 [0xea000000].
  Bus  0, device   9, function  0:
    Unknown mass storage controller: Promise Technology Unknown device
(rev 1).
      Vendor id=105a. Device id=4d38.
      Medium devsel.  IRQ 10.  Master Capable.  Latency=64.
      I/O at 0xcc00 [0xcc01].
      I/O at 0xd000 [0xd001].
      I/O at 0xd400 [0xd401].
      I/O at 0xd800 [0xd801].
      I/O at 0xdc00 [0xdc01].
      Non-prefetchable 32 bit memory at 0xea020000 [0xea020000].
  Bus  0, device  10, function  0:
    Ethernet controller: 3Com 3C905B 100bTX (rev 36).
      Medium devsel.  IRQ 11.  Master Capable.  Latency=64.  Min
Gnt=10.Max Lat=10.
      I/O at 0xe000 [0xe001].
      Non-prefetchable 32 bit memory at 0xea040000 [0xea040000].
  Bus  1, device   0, function  0:
    VGA compatible controller: NVidia/SGS Thomson Riva 128 (rev 16).
      Medium devsel.  Fast back-to-back capable.  IRQ 5.  Master
Capable.  Latency=64.  Min Gnt=3.Max Lat=1.
      Non-prefetchable 32 bit memory at 0xe4000000 [0xe4000000].
      Prefetchable 32 bit memory at 0xe6000000 [0xe6000008].



-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/

Re: File System Corruption with 2.2.18

[Andre Hedrick]

Good Morning Vojtech!

On Wed, 17 Jan 2001, Terrence Martin wrote:

> I am having all sorts of nasty file corruption problems with 2.2.18
> patched with
> ide.2.2.18.1221.patch.gz
> linux-2.2.18-reiserfs-3.5.29-patch.gz
> raid-2.2.18-B0
> 
> The corruption is occuring on my WDC AC28400R(I also had a problem with
> a 13GB WDC as well which I swapped out last night). This is the only
> hard drive that is on the onboard controller which is a VIA Technologies
> VT 82C586 Apollo IDE (rev 6) chipset. The drive does share the IDE bus
> with a internal ATAPI Zip drive. The cable I am using to connect the WDC
> is a UDMA66 40pin 80 wire cable. I realize I do not have a UDMA66
> controller, or disk, but I was having problems installing with a
> standard 40 pin, 40 wire cable that the 80 wire seemed to alleviate.
> 
> The other drives are my software RAID setup on 2 Promise PDC20262
> controllers with 1 drive per interface for a total of 4 drives. These
> drives are Quantum 13X(?) 13GB drives. I am running the default RH6.2
> kernel right now for stability with no support for my promise
> controllers and I am writing this from a remote site so not sure of
> other distinguishing marks of the quantum HD's.
> 
> So my question is does anyone have any idea what might cause ide dma
> errors to occur when I use this kernel? As I mentioned file corruption
> seems to only occur on the WDC drive(s) and manisfest itself as
> executables suddenly becoming unreadable binary files, strange file
> permissions on new files, and X windows going completely nuts when it
> tries to start. I reboot back to the stock 2.2.14 with RH and everything
> seems to work fine, excepting that I cannot access my RAID device of
> course. :)
> 
> I have had this problem across two mother boards(both VIA chipsets), two
> CPU's, two WDC Hard drives and the cable swap. I have not swapped RAM.
> 
> Thanks for any assistance/suggestions that you might be able to render.
> 
> Regards
> Terrence Martin
> 
> P.S. More specific system information follows
> 
> hdparm /dev/hda
> 
> /dev/hda:
>  multcount    =  0 (off)
>  I/O support  =  0 (default 16-bit)
>  unmaskirq    =  0 (off)
>  using_dma    =  0 (off)
>  keepsettings =  0 (off)
>  nowerr       =  0 (off)
>  readonly     =  0 (off)
>  readahead    =  8 (on)
>  geometry     = 16383/16/63, sectors = 16514064, start = 0
> 
> hdparm -i /dev/hda
> 
> /dev/hda:
> 
>  Model=WDC AC28400R, FwRev=15.01J55, SerialNo=WD-WM6280172815
>  Config={ HardSect NotMFM HdSw>15uSec SpinMotCtl Fixed DTR>5Mbs
> FmtGapReq }
>  RawCHS=16383/16/63, TrkSize=57600, SectSize=600, ECCbytes=40
>  BuffType=3(DualPortCache), BuffSize=512kB, MaxMultSect=16, MultSect=off
> 
>  DblWordIO=no, OldPIO=2, DMA=yes, OldDMA=0
>  CurCHS=16383/16/63, CurSects=-66060037, LBA=yes, LBAsects=16514064
>  tDMA={min:120,rec:120}, DMA modes: mword0 mword1 mword2
>  IORDY=on/off, tPIO={min:160,w/IORDY:120}, PIO modes: mode3 mode4
>  UDMA modes: mode0 mode1 *mode2
> 
> cat /proc/pci
> PCI devices found:
>   Bus  0, device   0, function  0:
>     Host bridge: VIA Technologies VT 82C597 Apollo VP3 (rev 4).
>       Medium devsel.  Fast back-to-back capable.  Master Capable.
> Latency=16.
>       Prefetchable 32 bit memory at 0xe0000000 [0xe0000008].
>   Bus  0, device   1, function  0:
>     PCI bridge: VIA Technologies VT 82C598 Apollo MVP3 AGP (rev 0).
>       Medium devsel.  Master Capable.  No bursts.  Min Gnt=12.
>   Bus  0, device   7, function  0:
>     ISA bridge: VIA Technologies VT 82C586 Apollo ISA (rev 71).
>       Medium devsel.  Master Capable.  No bursts.
>   Bus  0, device   7, function  1:
>     IDE interface: VIA Technologies VT 82C586 Apollo IDE (rev 6).
>       Medium devsel.  Fast back-to-back capable.  Master Capable.
> Latency=64.
>       I/O at 0xb400 [0xb401].
>   Bus  0, device   8, function  0:
>     Unknown mass storage controller: Promise Technology Unknown device
> (rev 1).
>       Vendor id=105a. Device id=4d38.
>       Medium devsel.  IRQ 5.  Master Capable.  Latency=64.
>       I/O at 0xb800 [0xb801].
>       I/O at 0xbc00 [0xbc01].
>       I/O at 0xc000 [0xc001].
>       I/O at 0xc400 [0xc401].
>       I/O at 0xc800 [0xc801].
>       Non-prefetchable 32 bit memory at 0xea000000 [0xea000000].
>   Bus  0, device   9, function  0:
>     Unknown mass storage controller: Promise Technology Unknown device
> (rev 1).
>       Vendor id=105a. Device id=4d38.
>       Medium devsel.  IRQ 10.  Master Capable.  Latency=64.
>       I/O at 0xcc00 [0xcc01].
>       I/O at 0xd000 [0xd001].
>       I/O at 0xd400 [0xd401].
>       I/O at 0xd800 [0xd801].
>       I/O at 0xdc00 [0xdc01].
>       Non-prefetchable 32 bit memory at 0xea020000 [0xea020000].
>   Bus  0, device  10, function  0:
>     Ethernet controller: 3Com 3C905B 100bTX (rev 36).
>       Medium devsel.  IRQ 11.  Master Capable.  Latency=64.  Min
> Gnt=10.Max Lat=10.
>       I/O at 0xe000 [0xe001].
>       Non-prefetchable 32 bit memory at 0xea040000 [0xea040000].
>   Bus  1, device   0, function  0:
>     VGA compatible controller: NVidia/SGS Thomson Riva 128 (rev 16).
>       Medium devsel.  Fast back-to-back capable.  IRQ 5.  Master
> Capable.  Latency=64.  Min Gnt=3.Max Lat=1.
>       Non-prefetchable 32 bit memory at 0xe4000000 [0xe4000000].
>       Prefetchable 32 bit memory at 0xe6000000 [0xe6000008].
> 
> 
> 
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> Please read the FAQ at http://www.tux.org/lkml/
> 

Andre Hedrick
Linux ATA Development

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/

Re: File System Corruption with 2.2.18

[Vojtech Pavlik]

Hi!

Ok, just for a test, before I finish the 2.2 version of the new VIA IDE
driver, could you try with the 2.4.0 kernel if it fixes the behavior?

By the way, what motherboard is this?

Andre: Thanks for sending this to me, this is the case I was looking for
- true data corruption on 2.2 kernel. Now I hope my new driver fixes
this.

Vojtech

On Wed, Jan 17, 2001 at 10:06:38AM -0800, Andre Hedrick wrote:
> 
> Good Morning Vojtech!
> 
> On Wed, 17 Jan 2001, Terrence Martin wrote:
> 
> > I am having all sorts of nasty file corruption problems with 2.2.18
> > patched with
> > ide.2.2.18.1221.patch.gz
> > linux-2.2.18-reiserfs-3.5.29-patch.gz
> > raid-2.2.18-B0
> > 
> > The corruption is occuring on my WDC AC28400R(I also had a problem with
> > a 13GB WDC as well which I swapped out last night). This is the only
> > hard drive that is on the onboard controller which is a VIA Technologies
> > VT 82C586 Apollo IDE (rev 6) chipset. The drive does share the IDE bus
> > with a internal ATAPI Zip drive. The cable I am using to connect the WDC
> > is a UDMA66 40pin 80 wire cable. I realize I do not have a UDMA66
> > controller, or disk, but I was having problems installing with a
> > standard 40 pin, 40 wire cable that the 80 wire seemed to alleviate.
> > 
> > The other drives are my software RAID setup on 2 Promise PDC20262
> > controllers with 1 drive per interface for a total of 4 drives. These
> > drives are Quantum 13X(?) 13GB drives. I am running the default RH6.2
> > kernel right now for stability with no support for my promise
> > controllers and I am writing this from a remote site so not sure of
> > other distinguishing marks of the quantum HD's.
> > 
> > So my question is does anyone have any idea what might cause ide dma
> > errors to occur when I use this kernel? As I mentioned file corruption
> > seems to only occur on the WDC drive(s) and manisfest itself as
> > executables suddenly becoming unreadable binary files, strange file
> > permissions on new files, and X windows going completely nuts when it
> > tries to start. I reboot back to the stock 2.2.14 with RH and everything
> > seems to work fine, excepting that I cannot access my RAID device of
> > course. :)
> > 
> > I have had this problem across two mother boards(both VIA chipsets), two
> > CPU's, two WDC Hard drives and the cable swap. I have not swapped RAM.
> > 
> > Thanks for any assistance/suggestions that you might be able to render.
> > 
> > Regards
> > Terrence Martin
> > 
> > P.S. More specific system information follows
> > 
> > hdparm /dev/hda
> > 
> > /dev/hda:
> >  multcount    =  0 (off)
> >  I/O support  =  0 (default 16-bit)
> >  unmaskirq    =  0 (off)
> >  using_dma    =  0 (off)
> >  keepsettings =  0 (off)
> >  nowerr       =  0 (off)
> >  readonly     =  0 (off)
> >  readahead    =  8 (on)
> >  geometry     = 16383/16/63, sectors = 16514064, start = 0
> > 
> > hdparm -i /dev/hda
> > 
> > /dev/hda:
> > 
> >  Model=WDC AC28400R, FwRev=15.01J55, SerialNo=WD-WM6280172815
> >  Config={ HardSect NotMFM HdSw>15uSec SpinMotCtl Fixed DTR>5Mbs
> > FmtGapReq }
> >  RawCHS=16383/16/63, TrkSize=57600, SectSize=600, ECCbytes=40
> >  BuffType=3(DualPortCache), BuffSize=512kB, MaxMultSect=16, MultSect=off
> > 
> >  DblWordIO=no, OldPIO=2, DMA=yes, OldDMA=0
> >  CurCHS=16383/16/63, CurSects=-66060037, LBA=yes, LBAsects=16514064
> >  tDMA={min:120,rec:120}, DMA modes: mword0 mword1 mword2
> >  IORDY=on/off, tPIO={min:160,w/IORDY:120}, PIO modes: mode3 mode4
> >  UDMA modes: mode0 mode1 *mode2
> > 
> > cat /proc/pci
> > PCI devices found:
> >   Bus  0, device   0, function  0:
> >     Host bridge: VIA Technologies VT 82C597 Apollo VP3 (rev 4).
> >       Medium devsel.  Fast back-to-back capable.  Master Capable.
> > Latency=16.
> >       Prefetchable 32 bit memory at 0xe0000000 [0xe0000008].
> >   Bus  0, device   1, function  0:
> >     PCI bridge: VIA Technologies VT 82C598 Apollo MVP3 AGP (rev 0).
> >       Medium devsel.  Master Capable.  No bursts.  Min Gnt=12.
> >   Bus  0, device   7, function  0:
> >     ISA bridge: VIA Technologies VT 82C586 Apollo ISA (rev 71).
> >       Medium devsel.  Master Capable.  No bursts.
> >   Bus  0, device   7, function  1:
> >     IDE interface: VIA Technologies VT 82C586 Apollo IDE (rev 6).
> >       Medium devsel.  Fast back-to-back capable.  Master Capable.
> > Latency=64.
> >       I/O at 0xb400 [0xb401].
> >   Bus  0, device   8, function  0:
> >     Unknown mass storage controller: Promise Technology Unknown device
> > (rev 1).
> >       Vendor id=105a. Device id=4d38.
> >       Medium devsel.  IRQ 5.  Master Capable.  Latency=64.
> >       I/O at 0xb800 [0xb801].
> >       I/O at 0xbc00 [0xbc01].
> >       I/O at 0xc000 [0xc001].
> >       I/O at 0xc400 [0xc401].
> >       I/O at 0xc800 [0xc801].
> >       Non-prefetchable 32 bit memory at 0xea000000 [0xea000000].
> >   Bus  0, device   9, function  0:
> >     Unknown mass storage controller: Promise Technology Unknown device
> > (rev 1).
> >       Vendor id=105a. Device id=4d38.
> >       Medium devsel.  IRQ 10.  Master Capable.  Latency=64.
> >       I/O at 0xcc00 [0xcc01].
> >       I/O at 0xd000 [0xd001].
> >       I/O at 0xd400 [0xd401].
> >       I/O at 0xd800 [0xd801].
> >       I/O at 0xdc00 [0xdc01].
> >       Non-prefetchable 32 bit memory at 0xea020000 [0xea020000].
> >   Bus  0, device  10, function  0:
> >     Ethernet controller: 3Com 3C905B 100bTX (rev 36).
> >       Medium devsel.  IRQ 11.  Master Capable.  Latency=64.  Min
> > Gnt=10.Max Lat=10.
> >       I/O at 0xe000 [0xe001].
> >       Non-prefetchable 32 bit memory at 0xea040000 [0xea040000].
> >   Bus  1, device   0, function  0:
> >     VGA compatible controller: NVidia/SGS Thomson Riva 128 (rev 16).
> >       Medium devsel.  Fast back-to-back capable.  IRQ 5.  Master
> > Capable.  Latency=64.  Min Gnt=3.Max Lat=1.
> >       Non-prefetchable 32 bit memory at 0xe4000000 [0xe4000000].
> >       Prefetchable 32 bit memory at 0xe6000000 [0xe6000008].
> > 
> > 
> > 
> > -
> > To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> > the body of a message to majordomo@vger.kernel.org
> > Please read the FAQ at http://www.tux.org/lkml/
> > 
> 
> Andre Hedrick
> Linux ATA Development

-- 
Vojtech Pavlik
SuSE Labs
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/

Re: File System Corruption with 2.2.18

[Andre Hedrick]

I may have a new test tool but it is completely destructive the content on
the drives.  It walks the drives and fills every sector with a unique
pattern and then you can read it back and checksum the contents.

It does destroy the content on the drive, this is no worse than a random
"File System Corruption " because it absolutely destroys or corrupts the
original content for testing purposes.


On Wed, 17 Jan 2001, Vojtech Pavlik wrote:

> Hi!
> 
> Ok, just for a test, before I finish the 2.2 version of the new VIA IDE
> driver, could you try with the 2.4.0 kernel if it fixes the behavior?
> 
> By the way, what motherboard is this?
> 
> Andre: Thanks for sending this to me, this is the case I was looking for
> - true data corruption on 2.2 kernel. Now I hope my new driver fixes
> this.
> 
> Vojtech
> 
> On Wed, Jan 17, 2001 at 10:06:38AM -0800, Andre Hedrick wrote:
> > 
> > Good Morning Vojtech!
> > 
> > On Wed, 17 Jan 2001, Terrence Martin wrote:
> > 
> > > I am having all sorts of nasty file corruption problems with 2.2.18
> > > patched with
> > > ide.2.2.18.1221.patch.gz
> > > linux-2.2.18-reiserfs-3.5.29-patch.gz
> > > raid-2.2.18-B0
> > > 
> > > The corruption is occuring on my WDC AC28400R(I also had a problem with
> > > a 13GB WDC as well which I swapped out last night). This is the only
> > > hard drive that is on the onboard controller which is a VIA Technologies
> > > VT 82C586 Apollo IDE (rev 6) chipset. The drive does share the IDE bus
> > > with a internal ATAPI Zip drive. The cable I am using to connect the WDC
> > > is a UDMA66 40pin 80 wire cable. I realize I do not have a UDMA66
> > > controller, or disk, but I was having problems installing with a
> > > standard 40 pin, 40 wire cable that the 80 wire seemed to alleviate.
> > > 
> > > The other drives are my software RAID setup on 2 Promise PDC20262
> > > controllers with 1 drive per interface for a total of 4 drives. These
> > > drives are Quantum 13X(?) 13GB drives. I am running the default RH6.2
> > > kernel right now for stability with no support for my promise
> > > controllers and I am writing this from a remote site so not sure of
> > > other distinguishing marks of the quantum HD's.
> > > 
> > > So my question is does anyone have any idea what might cause ide dma
> > > errors to occur when I use this kernel? As I mentioned file corruption
> > > seems to only occur on the WDC drive(s) and manisfest itself as
> > > executables suddenly becoming unreadable binary files, strange file
> > > permissions on new files, and X windows going completely nuts when it
> > > tries to start. I reboot back to the stock 2.2.14 with RH and everything
> > > seems to work fine, excepting that I cannot access my RAID device of
> > > course. :)
> > > 
> > > I have had this problem across two mother boards(both VIA chipsets), two
> > > CPU's, two WDC Hard drives and the cable swap. I have not swapped RAM.
> > > 
> > > Thanks for any assistance/suggestions that you might be able to render.
> > > 
> > > Regards
> > > Terrence Martin
> > > 
> > > P.S. More specific system information follows
> > > 
> > > hdparm /dev/hda
> > > 
> > > /dev/hda:
> > >  multcount    =  0 (off)
> > >  I/O support  =  0 (default 16-bit)
> > >  unmaskirq    =  0 (off)
> > >  using_dma    =  0 (off)
> > >  keepsettings =  0 (off)
> > >  nowerr       =  0 (off)
> > >  readonly     =  0 (off)
> > >  readahead    =  8 (on)
> > >  geometry     = 16383/16/63, sectors = 16514064, start = 0
> > > 
> > > hdparm -i /dev/hda
> > > 
> > > /dev/hda:
> > > 
> > >  Model=WDC AC28400R, FwRev=15.01J55, SerialNo=WD-WM6280172815
> > >  Config={ HardSect NotMFM HdSw>15uSec SpinMotCtl Fixed DTR>5Mbs
> > > FmtGapReq }
> > >  RawCHS=16383/16/63, TrkSize=57600, SectSize=600, ECCbytes=40
> > >  BuffType=3(DualPortCache), BuffSize=512kB, MaxMultSect=16, MultSect=off
> > > 
> > >  DblWordIO=no, OldPIO=2, DMA=yes, OldDMA=0
> > >  CurCHS=16383/16/63, CurSects=-66060037, LBA=yes, LBAsects=16514064
> > >  tDMA={min:120,rec:120}, DMA modes: mword0 mword1 mword2
> > >  IORDY=on/off, tPIO={min:160,w/IORDY:120}, PIO modes: mode3 mode4
> > >  UDMA modes: mode0 mode1 *mode2
> > > 
> > > cat /proc/pci
> > > PCI devices found:
> > >   Bus  0, device   0, function  0:
> > >     Host bridge: VIA Technologies VT 82C597 Apollo VP3 (rev 4).
> > >       Medium devsel.  Fast back-to-back capable.  Master Capable.
> > > Latency=16.
> > >       Prefetchable 32 bit memory at 0xe0000000 [0xe0000008].
> > >   Bus  0, device   1, function  0:
> > >     PCI bridge: VIA Technologies VT 82C598 Apollo MVP3 AGP (rev 0).
> > >       Medium devsel.  Master Capable.  No bursts.  Min Gnt=12.
> > >   Bus  0, device   7, function  0:
> > >     ISA bridge: VIA Technologies VT 82C586 Apollo ISA (rev 71).
> > >       Medium devsel.  Master Capable.  No bursts.
> > >   Bus  0, device   7, function  1:
> > >     IDE interface: VIA Technologies VT 82C586 Apollo IDE (rev 6).
> > >       Medium devsel.  Fast back-to-back capable.  Master Capable.
> > > Latency=64.
> > >       I/O at 0xb400 [0xb401].
> > >   Bus  0, device   8, function  0:
> > >     Unknown mass storage controller: Promise Technology Unknown device
> > > (rev 1).
> > >       Vendor id=105a. Device id=4d38.
> > >       Medium devsel.  IRQ 5.  Master Capable.  Latency=64.
> > >       I/O at 0xb800 [0xb801].
> > >       I/O at 0xbc00 [0xbc01].
> > >       I/O at 0xc000 [0xc001].
> > >       I/O at 0xc400 [0xc401].
> > >       I/O at 0xc800 [0xc801].
> > >       Non-prefetchable 32 bit memory at 0xea000000 [0xea000000].
> > >   Bus  0, device   9, function  0:
> > >     Unknown mass storage controller: Promise Technology Unknown device
> > > (rev 1).
> > >       Vendor id=105a. Device id=4d38.
> > >       Medium devsel.  IRQ 10.  Master Capable.  Latency=64.
> > >       I/O at 0xcc00 [0xcc01].
> > >       I/O at 0xd000 [0xd001].
> > >       I/O at 0xd400 [0xd401].
> > >       I/O at 0xd800 [0xd801].
> > >       I/O at 0xdc00 [0xdc01].
> > >       Non-prefetchable 32 bit memory at 0xea020000 [0xea020000].
> > >   Bus  0, device  10, function  0:
> > >     Ethernet controller: 3Com 3C905B 100bTX (rev 36).
> > >       Medium devsel.  IRQ 11.  Master Capable.  Latency=64.  Min
> > > Gnt=10.Max Lat=10.
> > >       I/O at 0xe000 [0xe001].
> > >       Non-prefetchable 32 bit memory at 0xea040000 [0xea040000].
> > >   Bus  1, device   0, function  0:
> > >     VGA compatible controller: NVidia/SGS Thomson Riva 128 (rev 16).
> > >       Medium devsel.  Fast back-to-back capable.  IRQ 5.  Master
> > > Capable.  Latency=64.  Min Gnt=3.Max Lat=1.
> > >       Non-prefetchable 32 bit memory at 0xe4000000 [0xe4000000].
> > >       Prefetchable 32 bit memory at 0xe6000000 [0xe6000008].
> > > 
> > > 
> > > 
> > > -
> > > To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> > > the body of a message to majordomo@vger.kernel.org
> > > Please read the FAQ at http://www.tux.org/lkml/
> > > 
> > 
> > Andre Hedrick
> > Linux ATA Development
> 
> -- 
> Vojtech Pavlik
> SuSE Labs
> 

Andre Hedrick
Linux ATA Development

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/

Re: File System Corruption with 2.2.18

[Vojtech Pavlik]

Hi!

Cute. Can it be run on say a swap partition?

Vojtech

On Wed, Jan 17, 2001 at 10:40:13AM -0800, Andre Hedrick wrote:

> I may have a new test tool but it is completely destructive the content on
> the drives.  It walks the drives and fills every sector with a unique
> pattern and then you can read it back and checksum the contents.
> 
> It does destroy the content on the drive, this is no worse than a random
> "File System Corruption " because it absolutely destroys or corrupts the
> original content for testing purposes.
> 
> 
> On Wed, 17 Jan 2001, Vojtech Pavlik wrote:
> 
> > Hi!
> > 
> > Ok, just for a test, before I finish the 2.2 version of the new VIA IDE
> > driver, could you try with the 2.4.0 kernel if it fixes the behavior?
> > 
> > By the way, what motherboard is this?
> > 
> > Andre: Thanks for sending this to me, this is the case I was looking for
> > - true data corruption on 2.2 kernel. Now I hope my new driver fixes
> > this.
> > 
> > Vojtech
> > 
> > On Wed, Jan 17, 2001 at 10:06:38AM -0800, Andre Hedrick wrote:
> > > 
> > > Good Morning Vojtech!
> > > 
> > > On Wed, 17 Jan 2001, Terrence Martin wrote:
> > > 
> > > > I am having all sorts of nasty file corruption problems with 2.2.18
> > > > patched with
> > > > ide.2.2.18.1221.patch.gz
> > > > linux-2.2.18-reiserfs-3.5.29-patch.gz
> > > > raid-2.2.18-B0
> > > > 
> > > > The corruption is occuring on my WDC AC28400R(I also had a problem with
> > > > a 13GB WDC as well which I swapped out last night). This is the only
> > > > hard drive that is on the onboard controller which is a VIA Technologies
> > > > VT 82C586 Apollo IDE (rev 6) chipset. The drive does share the IDE bus
> > > > with a internal ATAPI Zip drive. The cable I am using to connect the WDC
> > > > is a UDMA66 40pin 80 wire cable. I realize I do not have a UDMA66
> > > > controller, or disk, but I was having problems installing with a
> > > > standard 40 pin, 40 wire cable that the 80 wire seemed to alleviate.
> > > > 
> > > > The other drives are my software RAID setup on 2 Promise PDC20262
> > > > controllers with 1 drive per interface for a total of 4 drives. These
> > > > drives are Quantum 13X(?) 13GB drives. I am running the default RH6.2
> > > > kernel right now for stability with no support for my promise
> > > > controllers and I am writing this from a remote site so not sure of
> > > > other distinguishing marks of the quantum HD's.
> > > > 
> > > > So my question is does anyone have any idea what might cause ide dma
> > > > errors to occur when I use this kernel? As I mentioned file corruption
> > > > seems to only occur on the WDC drive(s) and manisfest itself as
> > > > executables suddenly becoming unreadable binary files, strange file
> > > > permissions on new files, and X windows going completely nuts when it
> > > > tries to start. I reboot back to the stock 2.2.14 with RH and everything
> > > > seems to work fine, excepting that I cannot access my RAID device of
> > > > course. :)
> > > > 
> > > > I have had this problem across two mother boards(both VIA chipsets), two
> > > > CPU's, two WDC Hard drives and the cable swap. I have not swapped RAM.
> > > > 
> > > > Thanks for any assistance/suggestions that you might be able to render.
> > > > 
> > > > Regards
> > > > Terrence Martin
> > > > 
> > > > P.S. More specific system information follows
> > > > 
> > > > hdparm /dev/hda
> > > > 
> > > > /dev/hda:
> > > >  multcount    =  0 (off)
> > > >  I/O support  =  0 (default 16-bit)
> > > >  unmaskirq    =  0 (off)
> > > >  using_dma    =  0 (off)
> > > >  keepsettings =  0 (off)
> > > >  nowerr       =  0 (off)
> > > >  readonly     =  0 (off)
> > > >  readahead    =  8 (on)
> > > >  geometry     = 16383/16/63, sectors = 16514064, start = 0
> > > > 
> > > > hdparm -i /dev/hda
> > > > 
> > > > /dev/hda:
> > > > 
> > > >  Model=WDC AC28400R, FwRev=15.01J55, SerialNo=WD-WM6280172815
> > > >  Config={ HardSect NotMFM HdSw>15uSec SpinMotCtl Fixed DTR>5Mbs
> > > > FmtGapReq }
> > > >  RawCHS=16383/16/63, TrkSize=57600, SectSize=600, ECCbytes=40
> > > >  BuffType=3(DualPortCache), BuffSize=512kB, MaxMultSect=16, MultSect=off
> > > > 
> > > >  DblWordIO=no, OldPIO=2, DMA=yes, OldDMA=0
> > > >  CurCHS=16383/16/63, CurSects=-66060037, LBA=yes, LBAsects=16514064
> > > >  tDMA={min:120,rec:120}, DMA modes: mword0 mword1 mword2
> > > >  IORDY=on/off, tPIO={min:160,w/IORDY:120}, PIO modes: mode3 mode4
> > > >  UDMA modes: mode0 mode1 *mode2
> > > > 
> > > > cat /proc/pci
> > > > PCI devices found:
> > > >   Bus  0, device   0, function  0:
> > > >     Host bridge: VIA Technologies VT 82C597 Apollo VP3 (rev 4).
> > > >       Medium devsel.  Fast back-to-back capable.  Master Capable.
> > > > Latency=16.
> > > >       Prefetchable 32 bit memory at 0xe0000000 [0xe0000008].
> > > >   Bus  0, device   1, function  0:
> > > >     PCI bridge: VIA Technologies VT 82C598 Apollo MVP3 AGP (rev 0).
> > > >       Medium devsel.  Master Capable.  No bursts.  Min Gnt=12.
> > > >   Bus  0, device   7, function  0:
> > > >     ISA bridge: VIA Technologies VT 82C586 Apollo ISA (rev 71).
> > > >       Medium devsel.  Master Capable.  No bursts.
> > > >   Bus  0, device   7, function  1:
> > > >     IDE interface: VIA Technologies VT 82C586 Apollo IDE (rev 6).
> > > >       Medium devsel.  Fast back-to-back capable.  Master Capable.
> > > > Latency=64.
> > > >       I/O at 0xb400 [0xb401].
> > > >   Bus  0, device   8, function  0:
> > > >     Unknown mass storage controller: Promise Technology Unknown device
> > > > (rev 1).
> > > >       Vendor id=105a. Device id=4d38.
> > > >       Medium devsel.  IRQ 5.  Master Capable.  Latency=64.
> > > >       I/O at 0xb800 [0xb801].
> > > >       I/O at 0xbc00 [0xbc01].
> > > >       I/O at 0xc000 [0xc001].
> > > >       I/O at 0xc400 [0xc401].
> > > >       I/O at 0xc800 [0xc801].
> > > >       Non-prefetchable 32 bit memory at 0xea000000 [0xea000000].
> > > >   Bus  0, device   9, function  0:
> > > >     Unknown mass storage controller: Promise Technology Unknown device
> > > > (rev 1).
> > > >       Vendor id=105a. Device id=4d38.
> > > >       Medium devsel.  IRQ 10.  Master Capable.  Latency=64.
> > > >       I/O at 0xcc00 [0xcc01].
> > > >       I/O at 0xd000 [0xd001].
> > > >       I/O at 0xd400 [0xd401].
> > > >       I/O at 0xd800 [0xd801].
> > > >       I/O at 0xdc00 [0xdc01].
> > > >       Non-prefetchable 32 bit memory at 0xea020000 [0xea020000].
> > > >   Bus  0, device  10, function  0:
> > > >     Ethernet controller: 3Com 3C905B 100bTX (rev 36).
> > > >       Medium devsel.  IRQ 11.  Master Capable.  Latency=64.  Min
> > > > Gnt=10.Max Lat=10.
> > > >       I/O at 0xe000 [0xe001].
> > > >       Non-prefetchable 32 bit memory at 0xea040000 [0xea040000].
> > > >   Bus  1, device   0, function  0:
> > > >     VGA compatible controller: NVidia/SGS Thomson Riva 128 (rev 16).
> > > >       Medium devsel.  Fast back-to-back capable.  IRQ 5.  Master
> > > > Capable.  Latency=64.  Min Gnt=3.Max Lat=1.
> > > >       Non-prefetchable 32 bit memory at 0xe4000000 [0xe4000000].
> > > >       Prefetchable 32 bit memory at 0xe6000000 [0xe6000008].
> > > > 
> > > > 
> > > > 
> > > > -
> > > > To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> > > > the body of a message to majordomo@vger.kernel.org
> > > > Please read the FAQ at http://www.tux.org/lkml/
> > > > 
> > > 
> > > Andre Hedrick
> > > Linux ATA Development
> > 
> > -- 
> > Vojtech Pavlik
> > SuSE Labs
> > 
> 
> Andre Hedrick
> Linux ATA Development

-- 
Vojtech Pavlik
SuSE Labs
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/

Re: File System Corruption with 2.2.18

[Terrence Martin]

Vojtech Pavlik wrote:

> Hi!
>
> Ok, just for a test, before I finish the 2.2 version of the new VIA IDE
> driver, could you try with the 2.4.0 kernel if it fixes the behavior?
>

Hmm ok I will give it a try...this will have to wait for a few hours as I am at
work. btw, how easy is it to install 2.4.0 on a stock RH6.2 install? hehe :)

>
> By the way, what motherboard is this?
>

It is an FIC PA 2013 (1MB Cache Version) with a K6-3 400, it has a relatively
recent BIOS patch as well, perhaps 6 months ago.

The other motherboard (also had corruption problems) was a California Graphics
Photon 100HC with a K6-2 300.

>
> Andre: Thanks for sending this to me, this is the case I was looking for
> - true data corruption on 2.2 kernel. Now I hope my new driver fixes
> this.

So do I...:)

Cheers,

Terrence



>
>
> Vojtech
>
> On Wed, Jan 17, 2001 at 10:06:38AM -0800, Andre Hedrick wrote:
> >
> > Good Morning Vojtech!
> >
> > On Wed, 17 Jan 2001, Terrence Martin wrote:
> >
> > > I am having all sorts of nasty file corruption problems with 2.2.18
> > > patched with
> > > ide.2.2.18.1221.patch.gz
> > > linux-2.2.18-reiserfs-3.5.29-patch.gz
> > > raid-2.2.18-B0
> > >
> > > The corruption is occuring on my WDC AC28400R(I also had a problem with
> > > a 13GB WDC as well which I swapped out last night). This is the only
> > > hard drive that is on the onboard controller which is a VIA Technologies
> > > VT 82C586 Apollo IDE (rev 6) chipset. The drive does share the IDE bus
> > > with a internal ATAPI Zip drive. The cable I am using to connect the WDC
> > > is a UDMA66 40pin 80 wire cable. I realize I do not have a UDMA66
> > > controller, or disk, but I was having problems installing with a
> > > standard 40 pin, 40 wire cable that the 80 wire seemed to alleviate.
> > >
> > > The other drives are my software RAID setup on 2 Promise PDC20262
> > > controllers with 1 drive per interface for a total of 4 drives. These
> > > drives are Quantum 13X(?) 13GB drives. I am running the default RH6.2
> > > kernel right now for stability with no support for my promise
> > > controllers and I am writing this from a remote site so not sure of
> > > other distinguishing marks of the quantum HD's.
> > >
> > > So my question is does anyone have any idea what might cause ide dma
> > > errors to occur when I use this kernel? As I mentioned file corruption
> > > seems to only occur on the WDC drive(s) and manisfest itself as
> > > executables suddenly becoming unreadable binary files, strange file
> > > permissions on new files, and X windows going completely nuts when it
> > > tries to start. I reboot back to the stock 2.2.14 with RH and everything
> > > seems to work fine, excepting that I cannot access my RAID device of
> > > course. :)
> > >
> > > I have had this problem across two mother boards(both VIA chipsets), two
> > > CPU's, two WDC Hard drives and the cable swap. I have not swapped RAM.
> > >
> > > Thanks for any assistance/suggestions that you might be able to render.
> > >
> > > Regards
> > > Terrence Martin
> > >
> > > P.S. More specific system information follows
> > >
> > > hdparm /dev/hda
> > >
> > > /dev/hda:
> > >  multcount    =  0 (off)
> > >  I/O support  =  0 (default 16-bit)
> > >  unmaskirq    =  0 (off)
> > >  using_dma    =  0 (off)
> > >  keepsettings =  0 (off)
> > >  nowerr       =  0 (off)
> > >  readonly     =  0 (off)
> > >  readahead    =  8 (on)
> > >  geometry     = 16383/16/63, sectors = 16514064, start = 0
> > >
> > > hdparm -i /dev/hda
> > >
> > > /dev/hda:
> > >
> > >  Model=WDC AC28400R, FwRev=15.01J55, SerialNo=WD-WM6280172815
> > >  Config={ HardSect NotMFM HdSw>15uSec SpinMotCtl Fixed DTR>5Mbs
> > > FmtGapReq }
> > >  RawCHS=16383/16/63, TrkSize=57600, SectSize=600, ECCbytes=40
> > >  BuffType=3(DualPortCache), BuffSize=512kB, MaxMultSect=16, MultSect=off
> > >
> > >  DblWordIO=no, OldPIO=2, DMA=yes, OldDMA=0
> > >  CurCHS=16383/16/63, CurSects=-66060037, LBA=yes, LBAsects=16514064
> > >  tDMA={min:120,rec:120}, DMA modes: mword0 mword1 mword2
> > >  IORDY=on/off, tPIO={min:160,w/IORDY:120}, PIO modes: mode3 mode4
> > >  UDMA modes: mode0 mode1 *mode2
> > >
> > > cat /proc/pci
> > > PCI devices found:
> > >   Bus  0, device   0, function  0:
> > >     Host bridge: VIA Technologies VT 82C597 Apollo VP3 (rev 4).
> > >       Medium devsel.  Fast back-to-back capable.  Master Capable.
> > > Latency=16.
> > >       Prefetchable 32 bit memory at 0xe0000000 [0xe0000008].
> > >   Bus  0, device   1, function  0:
> > >     PCI bridge: VIA Technologies VT 82C598 Apollo MVP3 AGP (rev 0).
> > >       Medium devsel.  Master Capable.  No bursts.  Min Gnt=12.
> > >   Bus  0, device   7, function  0:
> > >     ISA bridge: VIA Technologies VT 82C586 Apollo ISA (rev 71).
> > >       Medium devsel.  Master Capable.  No bursts.
> > >   Bus  0, device   7, function  1:
> > >     IDE interface: VIA Technologies VT 82C586 Apollo IDE (rev 6).
> > >       Medium devsel.  Fast back-to-back capable.  Master Capable.
> > > Latency=64.
> > >       I/O at 0xb400 [0xb401].
> > >   Bus  0, device   8, function  0:
> > >     Unknown mass storage controller: Promise Technology Unknown device
> > > (rev 1).
> > >       Vendor id=105a. Device id=4d38.
> > >       Medium devsel.  IRQ 5.  Master Capable.  Latency=64.
> > >       I/O at 0xb800 [0xb801].
> > >       I/O at 0xbc00 [0xbc01].
> > >       I/O at 0xc000 [0xc001].
> > >       I/O at 0xc400 [0xc401].
> > >       I/O at 0xc800 [0xc801].
> > >       Non-prefetchable 32 bit memory at 0xea000000 [0xea000000].
> > >   Bus  0, device   9, function  0:
> > >     Unknown mass storage controller: Promise Technology Unknown device
> > > (rev 1).
> > >       Vendor id=105a. Device id=4d38.
> > >       Medium devsel.  IRQ 10.  Master Capable.  Latency=64.
> > >       I/O at 0xcc00 [0xcc01].
> > >       I/O at 0xd000 [0xd001].
> > >       I/O at 0xd400 [0xd401].
> > >       I/O at 0xd800 [0xd801].
> > >       I/O at 0xdc00 [0xdc01].
> > >       Non-prefetchable 32 bit memory at 0xea020000 [0xea020000].
> > >   Bus  0, device  10, function  0:
> > >     Ethernet controller: 3Com 3C905B 100bTX (rev 36).
> > >       Medium devsel.  IRQ 11.  Master Capable.  Latency=64.  Min
> > > Gnt=10.Max Lat=10.
> > >       I/O at 0xe000 [0xe001].
> > >       Non-prefetchable 32 bit memory at 0xea040000 [0xea040000].
> > >   Bus  1, device   0, function  0:
> > >     VGA compatible controller: NVidia/SGS Thomson Riva 128 (rev 16).
> > >       Medium devsel.  Fast back-to-back capable.  IRQ 5.  Master
> > > Capable.  Latency=64.  Min Gnt=3.Max Lat=1.
> > >       Non-prefetchable 32 bit memory at 0xe4000000 [0xe4000000].
> > >       Prefetchable 32 bit memory at 0xe6000000 [0xe6000008].
> > >
> > >
> > >
> > > -
> > > To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> > > the body of a message to majordomo@vger.kernel.org
> > > Please read the FAQ at http://www.tux.org/lkml/
> > >
> >
> > Andre Hedrick
> > Linux ATA Development
>
> --
> Vojtech Pavlik
> SuSE Labs
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> Please read the FAQ at http://www.tux.org/lkml/

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/

Re: File System Corruption with 2.2.18

[Vojtech Pavlik]

On Wed, Jan 17, 2001 at 11:53:36AM -0700, Terrence Martin wrote:
> Vojtech Pavlik wrote:
> 
> > Hi!
> >
> > Ok, just for a test, before I finish the 2.2 version of the new VIA IDE
> > driver, could you try with the 2.4.0 kernel if it fixes the behavior?
> >
> 
> Hmm ok I will give it a try...this will have to wait for a few hours as I am at
> work. btw, how easy is it to install 2.4.0 on a stock RH6.2 install? hehe :)

RH 6.2? Uh. Well, you'll have to upgrade a couple packages I fear, if
you want 2.4 as your default kernel. For just a testing run it should
'just work'. Well, maybe you'll need a newer gcc to compile it - I don't
remember which version RH 6.2 uses.

> > By the way, what motherboard is this?
> 
> It is an FIC PA 2013 (1MB Cache Version) with a K6-3 400, it has a relatively
> recent BIOS patch as well, perhaps 6 months ago.
> 
> The other motherboard (also had corruption problems) was a California Graphics
> Photon 100HC with a K6-2 300.

Ok, thanks.

> >
> > Andre: Thanks for sending this to me, this is the case I was looking for
> > - true data corruption on 2.2 kernel. Now I hope my new driver fixes
> > this.
> 
> So do I...:)
> 
> Cheers,
> 
> Terrence
> 
> 
> 
> >
> >
> > Vojtech
> >
> > On Wed, Jan 17, 2001 at 10:06:38AM -0800, Andre Hedrick wrote:
> > >
> > > Good Morning Vojtech!
> > >
> > > On Wed, 17 Jan 2001, Terrence Martin wrote:
> > >
> > > > I am having all sorts of nasty file corruption problems with 2.2.18
> > > > patched with
> > > > ide.2.2.18.1221.patch.gz
> > > > linux-2.2.18-reiserfs-3.5.29-patch.gz
> > > > raid-2.2.18-B0
> > > >
> > > > The corruption is occuring on my WDC AC28400R(I also had a problem with
> > > > a 13GB WDC as well which I swapped out last night). This is the only
> > > > hard drive that is on the onboard controller which is a VIA Technologies
> > > > VT 82C586 Apollo IDE (rev 6) chipset. The drive does share the IDE bus
> > > > with a internal ATAPI Zip drive. The cable I am using to connect the WDC
> > > > is a UDMA66 40pin 80 wire cable. I realize I do not have a UDMA66
> > > > controller, or disk, but I was having problems installing with a
> > > > standard 40 pin, 40 wire cable that the 80 wire seemed to alleviate.
> > > >
> > > > The other drives are my software RAID setup on 2 Promise PDC20262
> > > > controllers with 1 drive per interface for a total of 4 drives. These
> > > > drives are Quantum 13X(?) 13GB drives. I am running the default RH6.2
> > > > kernel right now for stability with no support for my promise
> > > > controllers and I am writing this from a remote site so not sure of
> > > > other distinguishing marks of the quantum HD's.
> > > >
> > > > So my question is does anyone have any idea what might cause ide dma
> > > > errors to occur when I use this kernel? As I mentioned file corruption
> > > > seems to only occur on the WDC drive(s) and manisfest itself as
> > > > executables suddenly becoming unreadable binary files, strange file
> > > > permissions on new files, and X windows going completely nuts when it
> > > > tries to start. I reboot back to the stock 2.2.14 with RH and everything
> > > > seems to work fine, excepting that I cannot access my RAID device of
> > > > course. :)
> > > >
> > > > I have had this problem across two mother boards(both VIA chipsets), two
> > > > CPU's, two WDC Hard drives and the cable swap. I have not swapped RAM.
> > > >
> > > > Thanks for any assistance/suggestions that you might be able to render.
> > > >
> > > > Regards
> > > > Terrence Martin
> > > >
> > > > P.S. More specific system information follows
> > > >
> > > > hdparm /dev/hda
> > > >
> > > > /dev/hda:
> > > >  multcount    =  0 (off)
> > > >  I/O support  =  0 (default 16-bit)
> > > >  unmaskirq    =  0 (off)
> > > >  using_dma    =  0 (off)
> > > >  keepsettings =  0 (off)
> > > >  nowerr       =  0 (off)
> > > >  readonly     =  0 (off)
> > > >  readahead    =  8 (on)
> > > >  geometry     = 16383/16/63, sectors = 16514064, start = 0
> > > >
> > > > hdparm -i /dev/hda
> > > >
> > > > /dev/hda:
> > > >
> > > >  Model=WDC AC28400R, FwRev=15.01J55, SerialNo=WD-WM6280172815
> > > >  Config={ HardSect NotMFM HdSw>15uSec SpinMotCtl Fixed DTR>5Mbs
> > > > FmtGapReq }
> > > >  RawCHS=16383/16/63, TrkSize=57600, SectSize=600, ECCbytes=40
> > > >  BuffType=3(DualPortCache), BuffSize=512kB, MaxMultSect=16, MultSect=off
> > > >
> > > >  DblWordIO=no, OldPIO=2, DMA=yes, OldDMA=0
> > > >  CurCHS=16383/16/63, CurSects=-66060037, LBA=yes, LBAsects=16514064
> > > >  tDMA={min:120,rec:120}, DMA modes: mword0 mword1 mword2
> > > >  IORDY=on/off, tPIO={min:160,w/IORDY:120}, PIO modes: mode3 mode4
> > > >  UDMA modes: mode0 mode1 *mode2
> > > >
> > > > cat /proc/pci
> > > > PCI devices found:
> > > >   Bus  0, device   0, function  0:
> > > >     Host bridge: VIA Technologies VT 82C597 Apollo VP3 (rev 4).
> > > >       Medium devsel.  Fast back-to-back capable.  Master Capable.
> > > > Latency=16.
> > > >       Prefetchable 32 bit memory at 0xe0000000 [0xe0000008].
> > > >   Bus  0, device   1, function  0:
> > > >     PCI bridge: VIA Technologies VT 82C598 Apollo MVP3 AGP (rev 0).
> > > >       Medium devsel.  Master Capable.  No bursts.  Min Gnt=12.
> > > >   Bus  0, device   7, function  0:
> > > >     ISA bridge: VIA Technologies VT 82C586 Apollo ISA (rev 71).
> > > >       Medium devsel.  Master Capable.  No bursts.
> > > >   Bus  0, device   7, function  1:
> > > >     IDE interface: VIA Technologies VT 82C586 Apollo IDE (rev 6).
> > > >       Medium devsel.  Fast back-to-back capable.  Master Capable.
> > > > Latency=64.
> > > >       I/O at 0xb400 [0xb401].
> > > >   Bus  0, device   8, function  0:
> > > >     Unknown mass storage controller: Promise Technology Unknown device
> > > > (rev 1).
> > > >       Vendor id=105a. Device id=4d38.
> > > >       Medium devsel.  IRQ 5.  Master Capable.  Latency=64.
> > > >       I/O at 0xb800 [0xb801].
> > > >       I/O at 0xbc00 [0xbc01].
> > > >       I/O at 0xc000 [0xc001].
> > > >       I/O at 0xc400 [0xc401].
> > > >       I/O at 0xc800 [0xc801].
> > > >       Non-prefetchable 32 bit memory at 0xea000000 [0xea000000].
> > > >   Bus  0, device   9, function  0:
> > > >     Unknown mass storage controller: Promise Technology Unknown device
> > > > (rev 1).
> > > >       Vendor id=105a. Device id=4d38.
> > > >       Medium devsel.  IRQ 10.  Master Capable.  Latency=64.
> > > >       I/O at 0xcc00 [0xcc01].
> > > >       I/O at 0xd000 [0xd001].
> > > >       I/O at 0xd400 [0xd401].
> > > >       I/O at 0xd800 [0xd801].
> > > >       I/O at 0xdc00 [0xdc01].
> > > >       Non-prefetchable 32 bit memory at 0xea020000 [0xea020000].
> > > >   Bus  0, device  10, function  0:
> > > >     Ethernet controller: 3Com 3C905B 100bTX (rev 36).
> > > >       Medium devsel.  IRQ 11.  Master Capable.  Latency=64.  Min
> > > > Gnt=10.Max Lat=10.
> > > >       I/O at 0xe000 [0xe001].
> > > >       Non-prefetchable 32 bit memory at 0xea040000 [0xea040000].
> > > >   Bus  1, device   0, function  0:
> > > >     VGA compatible controller: NVidia/SGS Thomson Riva 128 (rev 16).
> > > >       Medium devsel.  Fast back-to-back capable.  IRQ 5.  Master
> > > > Capable.  Latency=64.  Min Gnt=3.Max Lat=1.
> > > >       Non-prefetchable 32 bit memory at 0xe4000000 [0xe4000000].
> > > >       Prefetchable 32 bit memory at 0xe6000000 [0xe6000008].
> > > >
> > > >
> > > >
> > > > -
> > > > To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> > > > the body of a message to majordomo@vger.kernel.org
> > > > Please read the FAQ at http://www.tux.org/lkml/
> > > >
> > >
> > > Andre Hedrick
> > > Linux ATA Development
> >
> > --
> > Vojtech Pavlik
> > SuSE Labs
> > -
> > To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> > the body of a message to majordomo@vger.kernel.org
> > Please read the FAQ at http://www.tux.org/lkml/

-- 
Vojtech Pavlik
SuSE Labs
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/

Re: File System Corruption with 2.2.18

[Andre Hedrick]

On Wed, 17 Jan 2001, Vojtech Pavlik wrote:

> Hi!
> 
> Cute. Can it be run on say a swap partition?

maybe but why?


Andre Hedrick
Linux ATA Development

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/

Re: File System Corruption with 2.2.18

[Tim Fletcher]

> > Hi!
> >
> > Cute. Can it be run on say a swap partition?
>
> maybe but why?

Because it stores no data, hence the wiping out of it is no problem?

-- 
   Tim Fletcher - Network manager   .~.
                                    /V\      L   I   N   U   X
     nightshade@solanum.net        // \\  >Don't fear the penguin<
tim@parrswood.manchester.sch.uk   /(   )\
 irc: Night-Shade on quakenet      ^^-^^

The only function of economic forecasting is to make astrology look
respectable.
                -- John Kenneth Galbraith

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/

Re: File System Corruption with 2.2.18

[Andre Hedrick]

On Wed, 17 Jan 2001, Tim Fletcher wrote:

> > > Hi!
> > >
> > > Cute. Can it be run on say a swap partition?
> >
> > maybe but why?
> 
> Because it stores no data, hence the wiping out of it is no problem?

Well that is useless test them because you can not test things completely.

Andre Hedrick
Linux ATA Development

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/

Re: File System Corruption with 2.2.18

[Tim Fletcher]

> > > maybe but why?
> >
> > Because it stores no data, hence the wiping out of it is no problem?
>
> Well that is useless test them because you can not test things completely.

I ment that if the partiton has no persient data on it then the test can
be run (the test wipes all data on the partition out during the test,
right?) with no loss of data on the machine. The partition is still on the
same disk so the test data is valid?

I am thinking that the test is somewhat like badblocks -w or have I got
the wrong end of the stick?

-- 
   Tim Fletcher - Network manager   .~.
                                    /V\      L   I   N   U   X
     nightshade@solanum.net        // \\  >Don't fear the penguin<
tim@parrswood.manchester.sch.uk   /(   )\
 irc: Night-Shade on quakenet      ^^-^^

"I love the way Microsoft follows standards.  In much the
same manner that fish follow migrating caribou."
                                            Paul Tomblin

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/

Re: File System Corruption with 2.2.18

[Andre Hedrick]

[-- Attachment #1: Type: text/plain, Size: 1329 bytes --]

On Thu, 18 Jan 2001, Tim Fletcher wrote:

> > Well that is useless test them because you can not test things completely.
> 
> I ment that if the partiton has no persient data on it then the test can
> be run (the test wipes all data on the partition out during the test,
> right?) with no loss of data on the machine. The partition is still on the
> same disk so the test data is valid?
> 
> I am thinking that the test is somewhat like badblocks -w or have I got
> the wrong end of the stick?

Sorry there is no stick to get the end of....
This is a pure diagnostic tool the determine OS/CHIPSET/DEVICE failures.
You generate a pattern buffer and write it to the disk and step the buffer
1 byte per sector and go head to tail.  Then you read it back head to tail
and compare what should be there with what is there.  Failures == FS
corruption is likely under highest loads, period.  Then you attempt 
to extract any patterns or periodic events to determine if it is driver or
device or other portions of the OS.

I am tired of people pointing the finger at me claim my work is the cause
of FS corruption.

This is a pattern walk and it will give some performance issue.
It does not care about the OS, it is doing the direct access that some
would call bit-bangging in the old days.

Cheers,

Andre Hedrick
Linux ATA Development

[-- Attachment #2: Type: text/plain, Size: 4328 bytes --]

Device: QUANTUM FIREBALLP LM20.4 Serial Number: 184222256110
0000: 7f51 6686 cbbf bd2d bf2b 1053 e683 1428 .Qf....-.+.S...(
0010: d813 2126 2bf5 1e4c ea8b 7453 bf38 40fa ..!&+..L..tS.8@.
0020: 7424 743d b839 fce1 feaf cb75 9f0f 68b5 t$t=.9.....u..h.
0030: 58e4 22ed 098f 6bec 4036 383d 2aab 7726 X."...k.@68=*.w&
0040: e625 41c6 1e06 a69b 1d9e 8863 e727 0143 .%A........c.'.C
0050: f625 f3b6 7017 50bd c125 90ba 6e77 1198 .%..p.P..%..nw..
0060: 2e0f 3300 4ea4 ff5f 033e d0b2 46df 6094 ..3.N.._.>..F.`.
0070: 5651 3bec 565e 65d0 af0b e4bc 85ec 8465 VQ;.V^e........e
0080: 727d 3219 862d 7d1f 473e 3cf2 ce9b 51ad r}2..-}.G><...Q.
0090: db57 3494 f0d5 52de 7120 7e52 3792 320d .W4...R.q ~R7.2.
00a0: e672 aebf 8161 7d21 6a73 1cbd 0c07 2a2c .r...a}!js....*,
00b0: 9337 6ba4 f5a3 3467 04ef e7f6 65f0 02b8 .7k...4g....e...
00c0: 3e90 a76f b48b 6ef9 2242 37c0 e218 e0b0 >..o..n."B7.....
00d0: c508 8615 ed06 1953 fb20 f5ea 668d 93c1 .......S. ..f...
00e0: 2426 a245 9e8b 356d 8f32 922e 0bb7 e4f2 $&.E..5m.2......
00f0: 09d2 324b b198 532c 0104 99f7 7bb3 98bc ..2K..S,....{...
0100: c9a6 5d99 4ff4 407f 439a c74e 096a e76f ..].O.@.C..N.j.o
0110: dd67 433a 01f3 9ce3 4728 16ed f1a4 e383 .gC:....G(......
0120: f1f6 3505 637b 86ce c648 fbb1 a36b 62de ..5.c{...H...kb.
0130: c4e2 09b3 598f aa14 0624 8eb1 7b02 6a8a ....Y....$..{.j.
0140: 5a70 cc17 b73d 518e 069e 5459 2938 22b8 Zp...=Q...TY)8".
0150: 57ab 57bc 0176 1b88 0e7d 5986 ca51 43a8 W.W..v...}Y..QC.
0160: ffb4 7959 ea67 728c 5387 1260 0dd0 7d5f ..yY.gr.S..`..}_
0170: f121 0e7f 4d9d 2349 0170 8d88 9bed 5ca5 .!..M.#I.p....\.
0180: 20a3 2c32 d57c 403f d468 b62f e828 3925  .,2.|@?.h./.(9%
0190: 2513 112b 0eb2 a720 ed44 23e1 4fe1 8454 %..+... .D#.O..T
01a0: d11a 4b4a 1c8f ebb6 ce9c b41f 8bc6 245d ..KJ..........$]
01b0: 429b 3a89 b2f6 72e5 fbb3 73d0 2ef5 26a2 B.:...r...s...&.
01c0: d8c2 a641 d28f 03c1 2669 497b 8073 5624 ...A....&iI{.sV$
01d0: 0744 4638 392f 216f 0c07 0ec3 ea37 825c .DF89/!o.....7.\
01e0: b976 2617 6f5f 5f6c 3052 ef93 2327 f040 .v&.o__l0R..#'.@
01f0: 31d3 326d 91db 08b7 3f87 6a3a c781 46bf 1.2m....?.j:..F.
0200: 57fe 6174 1846 c347 2b52 3e55 6e19 74fe W.at.F.G+R>Un.t.
0210: 1446 bf11 aab8 4135 f3dc e2be cf6d 3fd3 .F....A5.....m?.
0220: cb36 5500 d241 c66f 1ea1 99cb 2684 a3a6 .6U..A.o....&...
0230: ae71 241f 74df 77a5 5aee b3ab 1d47 c243 .q$.t.w.Z....G.C
0240: c5a3 f609 04d5 0d3a 3a8f 492b 287b 9466 .......::.I+({.f
0250: 3c88 e6f9 97b3 3e59 8330 4ac1 bce4 57aa <.....>Y.0J...W.
0260: 8708 c106 8766 9142 c1dc 9e1a 6015 b468 .....f.B....`..h
0270: 9ce2 8b0f fba1 f422 566a 179c 0106 8912 ......."Vj......
0280: 15ec 20a3 a20d 1f82 d491 7f99 9138 e3c2 .. ..........8..
0290: 39e1 8610 cc1d 51c4 19a0 8e64 e268 aad4 9.....Q....d.h..
02a0: 502e 1ebf 93b6 6e66 bcaa ba75 a45d 2720 P.....nf...u.]' 
02b0: ff9e ddd5 5ef7 cec3 fba7 a8f4 a8a8 21a5 ....^.........!.
02c0: b472 597f 424d 8f15 45b3 c897 5793 6349 .rY.BM..E...W.cI
02d0: f74c 51b5 26c9 fd6f c2c9 2d8f fc34 011e .LQ.&..o..-..4..
02e0: a802 ba48 7cfd 69ac 93c4 7e50 f397 c4a0 ...H|.i...~P....
02f0: e503 8d27 d865 d51a 3a52 ae9c e987 3bbb ...'.e..:R....;.
0300: 072d 6f5f 50c9 736a a6c3 3f63 fc46 6392 .-o_P.sj..?c.Fc.
0310: 44d0 ceb8 f886 83a1 412b 1934 f621 37ca D.......A+.4.!7.
0320: 4bfa 8f69 c0af c6d1 d384 035c f266 7564 K..i.......\.fud
0330: 41c9 62e5 b965 4418 f453 25fd 46d8 4e2f A.b..eD..S%.F.N/
0340: 335a 9b84 5023 952e eda8 a216 5bb6 f583 3Z..P#......[...
0350: 5962 9e23 bb34 13ef 4090 f5a7 4c53 8be7 Yb.#.4..@...LS..
0360: a744 a014 55ac 62d8 0baa c4c1 830b 46ae .D..U.b.......F.
0370: fe0a d501 cd58 89ab 9f3f 7e62 6de2 7a66 .....X...?~bm.zf
0380: d650 d194 f18d d9ed 3745 6408 a1e1 5162 .P......7Ed...Qb
0390: 660b 73df 8fa8 9aad ecdb f0cd 02c1 2f4b f.s.........../K
03a0: 87b2 dbe4 f502 58ca cb8f ef9d c9e5 e8bd ......X.........
03b0: 7684 5338 98ab cf96 c66f 5914 4eef 3ef0 v.S8.....oY.N.>.
03c0: d07c f8b0 ac7a c67c 63a3 8230 f8ed 66e9 .|...z.|c..0..f.
03d0: c9da f346 fa7d 2e13 6a8d 7eeb 8367 08c8 ...F.}..j.~..g..
03e0: 521d b2bc ff75 703a 7932 119b 4f5d 357d R....up:y2..O]5}
03f0: 9fda 6f47 4bb6 f2fe d45a bbca 57d1 70b6 ..oGK....Z..W.p.

Total Diameter Sequential DMA Pattern Write Test  = 19.17 MB/Sec (681.57 Seconds)

Total Diameter Sequential DMA Pattern Read Test  = 12.57 MB/Sec (1039.89 Seconds)

Re: File System Corruption with 2.2.18

[Ville Herva]

On Wed, Jan 17, 2001 at 05:14:02PM -0800, you [Andre Hedrick] claimed:
> On Thu, 18 Jan 2001, Tim Fletcher wrote:
> 
> > > Well that is useless test them because you can not test things completely.
> > 
> > I ment that if the partiton has no persient data on it then the test can
> > be run (the test wipes all data on the partition out during the test,
> > right?) with no loss of data on the machine. The partition is still on the
> > same disk so the test data is valid?
> > 
> > I am thinking that the test is somewhat like badblocks -w or have I got
> > the wrong end of the stick?
> 
> Sorry there is no stick to get the end of....
> This is a pure diagnostic tool the determine OS/CHIPSET/DEVICE failures.
> You generate a pattern buffer and write it to the disk and step the buffer
> 1 byte per sector and go head to tail.  Then you read it back head to tail
> and compare what should be there with what is there.  Failures == FS
> corruption is likely under highest loads, period.  Then you attempt 
> to extract any patterns or periodic events to determine if it is driver or
> device or other portions of the OS.
> 
> I am tired of people pointing the finger at me claim my work is the cause
> of FS corruption.
> 
> This is a pattern walk and it will give some performance issue.
> It does not care about the OS, it is doing the direct access that some
> would call bit-bangging in the old days.

But it works on all ATA disks? Does it work for SCSI as well?

I think it would be cool if you'd make it available (on linux-ide.org?),
so that people install servers (and anybody who _cares_) could test their
hardware/driver combination before starting using the box.

Now we have memtest86, cpuburn (what more). It would be nice to have a
good (if not complete) test set to run on each new linux box. It's not
nice to use the box for a month and then go "f..., this box has faulty
memory!" or ..."faulty disk!". Yes, that's what's happened to all of us.

It's much nicer to get a warranty replacement, when you don't have any
data on the disk.


-- v --

v@iki.fi
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/

Re: File System Corruption with 2.2.18

[Andre Hedrick]

> But it works on all ATA disks? Does it work for SCSI as well?

The KIOBUFS version may, but not the taskfile version.

> I think it would be cool if you'd make it available (on linux-ide.org?),
> so that people install servers (and anybody who _cares_) could test their
> hardware/driver combination before starting using the box.

who is going to ship install images with this kernel code added and the
most dangerous feature ever create eanble?

> Now we have memtest86, cpuburn (what more). It would be nice to have a
> good (if not complete) test set to run on each new linux box. It's not
> nice to use the box for a month and then go "f..., this box has faulty
> memory!" or ..."faulty disk!". Yes, that's what's happened to all of us.
> 
> It's much nicer to get a warranty replacement, when you don't have any
> data on the disk.

It can do that without a file system also.... ;-)

Andre Hedrick
Linux ATA Development

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/

Re: File System Corruption with 2.2.18

[Ville Herva]

On Thu, Jan 18, 2001 at 12:45:13AM -0800, you [Andre Hedrick] claimed:
> 
> > But it works on all ATA disks? Does it work for SCSI as well?
> 
> The KIOBUFS version may, but not the taskfile version.

Ok.
 
> > I think it would be cool if you'd make it available (on linux-ide.org?),
> > so that people install servers (and anybody who _cares_) could test their
> > hardware/driver combination before starting using the box.
> 
> who is going to ship install images with this kernel code added and the
> most dangerous feature ever create eanble?

I don't think any vendor has to ship it. The memtest86 suite is available
as a floppy image, the harddisk tester could be as well. (Of course with a
LARGE alert saying "THIS *DESTROYS* ALL YOUR HARDDISK CONTENTS, please
unplug everyting you don't want tested to be sure".

> > Now we have memtest86, cpuburn (what more). It would be nice to have a
> > good (if not complete) test set to run on each new linux box. It's not
> > nice to use the box for a month and then go "f..., this box has faulty
> > memory!" or ..."faulty disk!". Yes, that's what's happened to all of us.
> > 
> > It's much nicer to get a warranty replacement, when you don't have any
> > data on the disk.
> 
> It can do that without a file system also.... ;-)

Yes.


-- v --

v@iki.fi
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/

Re: File System Corruption with 2.2.18

[Terrence Martin]

Just to follow up, on Vojtech's advice I installed kernel 2.4.0 instead(I
also moved to 7.0 RH to accomplish this) and everything seems to be working
fine(I did not apply your new patches Vojtech, as yet they have not proved
necessary). I have not done any exhaustive testing, however the failure rate
has gone from boot kernel, wait 10 mins, write to disk fail, to no failures
at this point after installing many many RH7.0 updates etc...

Thanks for the assistance, and good work on the 2.4.0 kernel I am
impressed..:)

Cheers,

Terrence Martin



-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/