From: Andreas Dilger <adilger@turbolabs.com>
To: linux-lvm@sistina.com
Subject: Re: [linux-lvm] More strangeness
Date: Tue, 9 Oct 2001 21:56:12 -0600 [thread overview]
Message-ID: <20011009215612.K6348@turbolinux.com> (raw)
In-Reply-To: <000901c1513c$0b59d9d0$836788cf@industry>
On Oct 09, 2001 23:31 -0400, Jason A. Lixfeld wrote:
> Oct 9 22:26:36 hit0day kernel: hdg: read_intr: error=0x10 {
> SectorIdNotFound }, LBAsect=239992834, sector=2
> Oct 9 22:26:36 hit0day kernel: hdg: read_intr: status=0x59 { DriveReady
> SeekComplete DataRequest Error }
> Oct 9 22:26:36 hit0day kernel: hdg: read_intr: error=0x10 {
> SectorIdNotFound }, LBAsect=239992834, sector=2
> Oct 9 22:26:36 hit0day kernel: hdg: read_intr: status=0x59 { DriveReady
> SeekComplete DataRequest Error }
> Oct 9 22:26:36 hit0day kernel: hdg: read_intr: error=0x10 {
> SectorIdNotFound }, LBAsect=239992834, sector=2
> Oct 9 22:26:36 hit0day sshd: Starting sshd:
> Oct 9 22:26:36 hit0day kernel: hdg: read_intr: status=0x59 { DriveReady
> SeekComplete DataRequest Error }
> Oct 9 22:26:36 hit0day kernel: hdg: read_intr: error=0x10 {
> SectorIdNotFound }, LBAsect=239992834, sector=2
> Oct 9 22:26:36 hit0day kernel: ide3: reset: success
> <various hard drive errors for ALL drives (/dev/hde /dev/hdg AND
> /dev/hdi) in LVM test continue for a couple of pages>
There is another user with similar problems with SCSI disks. With LVM
on, it causes disk errors, but with LVM off (or raw disk access) all
is well. It must be something in the low-level LVM kernel code which
is going wrong.
The above looks like LVM doing wrong math - LBAsect=239992834 is
119996417 kiB = 117184 MiB which is larger than hdg (61GB or so).
Do you have similar problems with ext2 and/or reiserfs?
Could you try using an older version of the LVM kernel code to see if
the problem exists there as well? Running ext3 on 2.4.10 is a bit on
the risky side, since there is no "official" patch for it.
You could try enabling LVM DEBUG_MAP (don't log to an LVM device!!!)
to see what it is doing when it gets these errors. You could also
try enabling the JBD buffer debugging to get additional info.
Cheers, Andreas
--
Andreas Dilger \ "If a man ate a pound of pasta and a pound of antipasto,
\ would they cancel out, leaving him still hungry?"
http://www-mddsp.enel.ucalgary.ca/People/adilger/ -- Dogbert
next prev parent reply other threads:[~2001-10-10 3:56 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-10 3:31 [linux-lvm] More strangeness Jason A. Lixfeld
2001-10-10 3:56 ` Andreas Dilger [this message]
2001-10-10 10:18 ` Jason A. Lixfeld
2001-10-10 15:24 ` Andreas Dilger
-- strict thread matches above, loose matches on Subject: below --
2001-10-10 12:37 Jean-Eric Cuendet
2001-10-10 16:38 jlixfeld
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=20011009215612.K6348@turbolinux.com \
--to=adilger@turbolabs.com \
--cc=linux-lvm@sistina.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).