From: "Jeffrey W. Baker" <jwbaker@acm.org>
To: Petr Vandrovec <VANDROVE@vc.cvut.cz>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Different geometry settings for identical drives
Date: 30 May 2003 16:38:09 -0700 [thread overview]
Message-ID: <1054337888.24145.6.camel@heat> (raw)
In-Reply-To: <306584240A9@vcnet.vc.cvut.cz>
On Fri, 2003-05-30 at 16:20, Petr Vandrovec wrote:
> On 30 May 03 at 15:46, Jeffrey Baker wrote:
>
> > hda: host protected area => 1
> > hda: setmax LBA 234441648, native 234375000
> > hda: 234375000 sectors (120000 MB) w/8192KiB Cache, CHS=232514/16/63, UDMA(100)
> > hdc: attached ide-disk driver.
> > hdc: host protected area => 1
> > hdc: setmax LBA 234441648, native 234375000
> > hdc: 234375000 sectors (120000 MB) w/8192KiB Cache, CHS=232514/16/63, UDMA(100)
> > hdd: attached ide-cdrom driver.
> > hdd: ATAPI 24X CD-ROM drive, 128kB Cache, UDMA(33)
> >
> > The result is that hda works fine but hdc doesn't. When I try to mke2fs
> > on the latter I see:
> >
> > hdc: dma_intr: status=0x51 { DriveReady SeekComplete Error }
> > hdc: dma_intr: error=0x10 { SectorIdNotFound }, LBAsect=234441583, sector=232343808
> >
> > You can see that LBAsect (234441583) is higher than the "native" sectors
> > quoted by the kernel (234375000, difference 66583 sectors). Why are
> > these two disks being addressed differently?
>
> As far as I can tell, it has nothing to do with disk geometry.
>
> Someone just cut couple of sectors at the end from disk, you compiled
> your kernel without CONFIG_IDEDISK_STROKE, but still kernel for some
> reason reports block size as if idedisk_set_max_address() was invoked.
>
> I do not see how this could happen with 2.4.21-rc3... Can you recheck
> that you are using 2.4.21-rc3 without any additional patches?
I'm running 2.4.21-rc3 with the latest patch from ftp.x86-64.org:
prime:/usr/src# uname -r
2.4.21-rc3
The x86-64.org patch doesn't touch much outside of arch/x86_64. You are
right that CONFIG_IDE_STROKE is off:
prime:/usr/src/linux# grep IDE .config | sort | tac
CONFIG_IDEDMA_PCI_AUTO=y
CONFIG_IDEDMA_AUTO=y
CONFIG_IDE=y
CONFIG_BLK_DEV_IDE_MODES=y
CONFIG_BLK_DEV_IDEPCI=y
CONFIG_BLK_DEV_IDEFLOPPY=y
CONFIG_BLK_DEV_IDEDMA_PCI=y
CONFIG_BLK_DEV_IDEDMA=y
CONFIG_BLK_DEV_IDEDISK=y
CONFIG_BLK_DEV_IDECD=y
CONFIG_BLK_DEV_IDE=y
# IDE, ATA and ATAPI Block devices
# CONFIG_VIDEO_SELECT is not set
# CONFIG_VIDEO_DEV is not set
# CONFIG_PARIDE is not set
# CONFIG_IDE_TASK_IOCTL is not set
# CONFIG_IDE_CHIPSETS is not set
# CONFIG_IDEPCI_SHARE_IRQ is not set
# CONFIG_IDEDMA_PCI_WIP is not set
# CONFIG_IDEDMA_ONLYDISK is not set
# CONFIG_IDEDMA_IVB is not set
# CONFIG_IDEDISK_STROKE is not set
# CONFIG_IDEDISK_MULTI_MODE is not set
# CONFIG_BLK_DEV_IDETAPE is not set
# CONFIG_BLK_DEV_IDESCSI is not set
# CONFIG_BLK_DEV_IDEDMA_FORCED is not set
# CONFIG_BLK_DEV_IDECS is not set
# CONFIG_BLK_DEV_HD_IDE is not set
# CONFIG_AMD74XX_OVERRIDE is not set
# ATA/IDE/MFM/RLL support
-jwb
next prev parent reply other threads:[~2003-05-30 23:24 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-30 23:20 Different geometry settings for identical drives Petr Vandrovec
2003-05-30 23:38 ` Jeffrey W. Baker [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-05-31 0:19 Petr Vandrovec
2003-06-02 18:13 ` Jeffrey W. Baker
2003-05-30 22:46 Jeffrey Baker
2003-05-30 23:50 ` Andries Brouwer
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=1054337888.24145.6.camel@heat \
--to=jwbaker@acm.org \
--cc=VANDROVE@vc.cvut.cz \
--cc=linux-kernel@vger.kernel.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox