From: David Chinner <dgc@sgi.com>
To: n <xellos@bluebottle.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: limiting to UDMA/33 instead of UDMA/100 - pata_pdc202xx_old (also XFS error)?
Date: Fri, 7 Sep 2007 23:02:12 +1000 [thread overview]
Message-ID: <20070907130212.GI995458@sgi.com> (raw)
In-Reply-To: <007d01c7eaf6$74b9b350$0100a8c0@hak>
On Thu, Aug 30, 2007 at 04:11:03AM -0700, n wrote:
> hello, with kernel 2.6.22.5 using the new pata_pdc202xx_old driver it
> doesn detect the cable right on this seagate drive (i tried switching ports
> / cables ...etc)
.....
> XFS mounting filesystem sdc3
> Ending clean XFS mount for filesystem: sdc3
> XFS mounting filesystem sdc4
> Ending clean XFS mount for filesystem: sdc4
> XFS mounting filesystem sdd1
> Ending clean XFS mount for filesystem: sdd1
> XFS mounting filesystem sde1
> Ending clean XFS mount for filesystem: sde1
> XFS mounting filesystem sdf1
> Ending clean XFS mount for filesystem: sdf1
> XFS mounting filesystem sdb1
> Ending clean XFS mount for filesystem: sdb1
> ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x2
> ata1.00: (BMDMA stat 0x4)
> ata1.00: cmd ca/00:01:3f:00:00/00:00:00:00:00/e0 tag 0 cdb 0x0 data 512 out
> res 51/84:00:3f:00:00/00:00:00:00:00/e0 Emask 0x10 (ATA bus error)
> ata1: soft resetting port
> ata1.00: configured for UDMA/33
> ata1: EH complete
> ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x2
> ata1.00: (BMDMA stat 0x4)
> ata1.00: cmd ca/00:01:3f:00:00/00:00:00:00:00/e0 tag 0 cdb 0x0 data 512 out
> res 51/84:00:3f:00:00/00:00:00:00:00/e0 Emask 0x10 (ATA bus error)
> ata1: soft resetting port
> ata1.00: configured for UDMA/33
.....
> ata1.00: limiting speed to PIO4
> ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x2
> ata1.00: (BMDMA stat 0x4)
> ata1.00: cmd ca/00:00:21:9d:fc/00:00:00:00:00/e6 tag 0 cdb 0x0 data 131072
> out
> res 51/84:00:21:9d:fc/00:00:00:00:00/e6 Emask 0x10 (ATA bus error)
> ata1: soft resetting port
> ata1.00: configured for PIO4
> ata1: EH complete
> sd 0:0:0:0: [sda] 234441648 512-byte hardware sectors (120034 MB)
> xfs_force_shutdown(sda1,0x1) called from line 423 of file fs/xfs/xfs_rw.c.
> Return address = 0xc020cea8
> Filesystem "sda1": I/O Error Detected. Shutting down filesystem: sda1
> Please umount the filesystem, and rectify the problem(s)
> I/O error in filesystem ("sda1") meta-data dev sda1 block 0x6fc9be2
> ("xlog_bwrite") error 5 buf count 262144
> XFS: failed to locate log tail
> XFS: log mount/recovery failed: error 5
> XFS: log mount failed
EIO to a write to the log on recovery of the filesystem. Sounds like the
driver returned an error and XFS shut the filesysetm down to protect
it from damage.
> sd 0:0:0:0: [sda] Write Protect is off
> sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00
> sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't
> support DPO or FUA
> sd 0:0:0:0: [sda] 234441648 512-byte hardware sectors (120034 MB)
> sd 0:0:0:0: [sda] Write Protect is off
> sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00
> sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't
> support DPO or FUA
>
> after the kernel finnishes booting i can mount that drive fine (also all
> the xfs_check xfs_repair ..etc say there is no errors)
So XFS is doing the right thing and when you get the driver errors
sorted out the filesystem shoul dbe fine....
Cheers,
Dave.
--
Dave Chinner
Principal Engineer
SGI Australian Software Group
next prev parent reply other threads:[~2007-09-07 13:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-30 11:11 limiting to UDMA/33 instead of UDMA/100 - pata_pdc202xx_old (also XFS error)? n
2007-09-07 13:02 ` David Chinner [this message]
2007-09-07 23:47 ` Jeff Garzik
2007-09-08 6:41 ` n
2007-09-08 18:44 ` Alan Cox
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20070907130212.GI995458@sgi.com \
--to=dgc@sgi.com \
--cc=linux-kernel@vger.kernel.org \
--cc=xellos@bluebottle.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.