lkml.org 
[lkml]   [1998]   [Jan]   [6]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
From
Date
SubjectRe: Jaz drive and EXT2FS - HELP! - (long)
I have an Adaptech 2940 SCSI controller and experienced the same
problem. Disable TAGGED_QUEUEING works for me.

Hoang



Don't know what happened here, however, if I were you, I'll
try recompile the kernel iwth TAGGED_QUEUEING, PAGE_ENABLE
disabled. These are some advanced features, suppose to speed
up the SCSI I/O, but I think something wrong with the Jaz
interface or whatever reason, whenever I tried to copy a large
directory, it'd screw up the directory entries. So use the
most basic setup if you got a Jaz drive.


On Tue, 6 Jan 1998, Steve Logue wrote:

> Hello,
>
> Can anyone give me some ideas on where and what to check to help
> diagnose a filesystem/SCSI/Jaz drive prob? I have been haveing my
> filesystem crash on my Jaz cartridge for no apperant reason. Each
time
> I get messages listed at the end of this message. I have gone through
> my whole system looking for anything that might be the culprit. I
have
> an Adaptec 2940 UW with the latest BIOS, and am using the latest
stable
> kernel. It is on IRQ 15, but I have all IDE turned off in my system
> BIOS. The internal 68-pin cable is terminated by my harddrive, and
the
> internal 50-pin cable is terminated with the passive termination block
> that comes from Iomega. Termination of the card is set to the LOW
byte
> off, and HIGH byte on (not-automatic). I have limited the bus speed
to
> 10 Mb to the Jaz drive, and CDROM, and 40 Mb to the card, and my hard
> drive. SCAM in enable, but Extended Translation is off. The
following
> are the settings that I entered when I compiled my kernel: I have run
> badblocks -vw /dev/sdb1 1044464 many times, and have never seen an
> error. I have also low level formatted this specific cartridge just
to
> be sure. Lastly, I do not have any problems with this specific
> drive/cartridge under heavy usage in Win95, or FreeBSD.
>
> -STEVEl
>
>
> CONFIG_SCSI_AIC7XXX=y
> CONFIG_AIC7XXX_TAGGED_QUEUEING=y
> CONFIG_OVERRIDE_CMDS=y
> CONFIG_AIC7XXX_CMDS_PER_LUN=64
> CONFIG_AIC7XXX_PAGE_ENABLE=y
> CONFIG_AIC7XXX_PROC_STATS=y
> CONFIG_AIC7XXX_RESET_DELAY=5
>
>
> Here is the dmesg output that is relative:
>
>
> aic7xxx: <Adaptec AHA-294X Ultra SCSI host adapter> at PCI 10
> aic7xxx: BIOS enabled, IO Port 0xe400, IO Mem 0xe7000000, IRQ 15,
> Revision C
> aic7xxx: Wide Channel, SCSI ID 7, 16/255 SCBs, QFull 16, QMask 0x1f
> scsi0 : Adaptec AHA274x/284x/294x (EISA/VLB/PCI-Fast SCSI) 4.1.1/3.2.1
> scsi : 1 host.
> scsi0: Scanning channel A for devices.
> Vendor: SEAGATE Model: ST32155W Rev: 0596
> Type: Direct-Access ANSI SCSI revision: 02
> Detected scsi disk sda at scsi0, channel 0, id 0, lun 0
> Vendor: PLEXTOR Model: CD-ROM PX-4XCE Rev: 1.01
> Type: CD-ROM ANSI SCSI revision: 02
> Detected scsi CD-ROM sr0 at scsi0, channel 0, id 3, lun 0
> Vendor: iomega Model: jaz 1GB Rev: J.83
> Type: Direct-Access ANSI SCSI revision: 02
> Detected scsi removable disk sdb at scsi0, channel 0, id 4, lun 0
> scsi : detected 1 SCSI cdrom 2 SCSI disks total.
> SCSI device sda: hdwr sector= 512 bytes. Sectors= 4197405 [2049 MB]
[2.0
> GB]
> SCSI device sdb: hdwr sector= 512 bytes. Sectors= 2091050 [1021 MB]
[1.0
> GB]
> sdb: Write Protect is off
>
>
> Here is the /proc filesystem statistics:
>
>
> Adaptec AIC7xxx driver version: 4.1.1/3.2.1
> Compile Options:
> AIC7XXX_RESET_DELAY : 5
> AIC7XXX_CMDS_PER_LUN : 64
> AIC7XXX_TAGGED_QUEUEING: Enabled
> AIC7XXX_PAGE_ENABLE : Enabled
> AIC7XXX_PROC_STATS : Enabled
>
> Adapter Configuration:
> SCSI Adapter: Adaptec AHA-294X Ultra SCSI host adapter
> (AIC-788x chipset)
> Host Bus: Wide
> Base IO: 0xe400
> Base IO Memory: 0xe7000000
> IRQ: 15
> SCBs: Used 87, HW 16, Page 255
> Interrupts: 182831
> Serial EEPROM: True
> Extended Translation: Disabled
> SCSI Bus Reset: Enabled
> Ultra SCSI: Enabled
> Disconnect Enable Flags: 0xffff
>
> Statistics:
> CHAN#A (TGT 0 LUN 0):
> nxfers 177021 (93604 read;83417 written)
> blks(512) rd=1410456; blks(512) wr=719134
> < 512 512-1K 1-2K 2-4K 4-8K 8-16K 16-32K 32-64K 64-128K
> >128K
> Reads: 1 0 40673 7118 18951 17474 3751 3146
> 2490 0
> Writes: 0 0 51747 19549 7095 2154 953 428
> 1491 0
>
> CHAN#A (TGT 3 LUN 0):
> nxfers 5 (5 read;0 written)
> blks(512) rd=9; blks(512) wr=0
> < 512 512-1K 1-2K 2-4K 4-8K 8-16K 16-32K 32-64K 64-128K
> >128K
> Reads: 2 1 0 2 0 0 0 0
> 0 0
> Writes: 0 0 0 0 0 0 0 0
> 0 0
>
> CHAN#A (TGT 4 LUN 0):
> nxfers 5641 (2179 read;3462 written)
> blks(512) rd=101235; blks(512) wr=417958
> < 512 512-1K 1-2K 2-4K 4-8K 8-16K 16-32K 32-64K 64-128K
> >128K
> Reads: 1 1 1203 0 3 134 8 785
> 44 0
> Writes: 0 0 849 468 278 128 23 40
> 1676 0
>
>
> Lastly, these are a sample of the errors that I am getting. I have
> gotten many of them, and have only put an example of everyking here
for
> reading. I have the filesystem mounted with the option:
> "check=strict".
>
>
> messages:Jan 6 00:28:53 bock kernel: EXT2-fs warning (device 08:11):
> ext2_free_inode: bit already cleared for inode 140761
>
> messages.2:Dec 21 22:48:41 logues kernel: EXT2-fs error (device
08:11):
> ext2_readdir: bad entry in directory #16385: rec_len % 4 != 0 -
> offset=0, inode=1701996900, rec_len=29795, name_len=29295
>
> messages.2:Dec 21 22:49:33 logues kernel: EXT2-fs error (device
08:11):
> ext2_find_entry: bad entry in directory #16385: rec_len % 4 != 0 -
> offset=1024, inode=1701996900, rec_len=29795, name_len=29295
>
> messages.2:Dec 23 17:17:03 logues kernel: EXT2-fs error (device
08:11):
> ext2_free_blocks: Freeing blocks not in datazone - block = 1283566791,
> count = 1
>
> messages.2:Dec 26 17:40:47 logues kernel: EXT2-fs warning (device
> 08:11): ext2_rmdir: empty directory has nlink!=2 (3)
>
>
Max Chern, Unix Software Engineer | Voice: 818-296-5014
EarthLink Network, Inc. | Fax: 818-296-5113
maxchern@earthlink.net | 3100 New York Dr., Ste 201
http://www.earthlink.net/ | Pasadena, CA 91107

\
 
 \ /
  Last update: 2005-03-22 13:41    [from the cache]
©2003-2014 Jasper Spaans. Advertise on this site