From: Roger Oberholtzer <roger@opq.se>
To: Tejun Heo <htejun@gmail.com>
Cc: linux-ide@vger.kernel.org
Subject: Re: libata question
Date: Thu, 03 Aug 2006 09:26:02 +0200 [thread overview]
Message-ID: <1154589962.25611.102.camel@acme> (raw)
In-Reply-To: <44D0BE99.8010809@gmail.com>
If I switch two disks around and do a scan, nothing changes. I need
to delete the disks and then scan to have the change noted. Is this
expected behavior?
Does this mean I must delete a disk with a command when it it removed?
This is problematic in that I do not know which disk may have been
removed!
The old /proc/scsi interface would allow you to update the idea of which
things are attached without knowing which they were and (key point)
without
messing up a device that is unchanged and mounted.
Is this possible with libata?
I know you want logs. But I really feel that if the intended use is
unclear,
I can waste lots of time here sending in logs when trying to do things
that the driver does not intend I do. Step 1 must surely be to tell the
driver's expectations/limits first.
If I remove or insert a disk, there is nothing at all added to the
kernel log. There only seems to be activity when I echo something to
a file in /sys.
If I remove disks (but run no commands on the computer) and then do a
scan, I get this in the log:
Aug 3 08:16:43 aies1 kernel: ata1.00: qc timeout (cmd 0xec)
Aug 3 08:16:43 aies1 kernel: ata1.00: failed to IDENTIFY (I/O error,
err_mask=0 x4)
Aug 3 08:16:43 aies1 kernel: ata1.00: revalidation failed (errno=-5)
Aug 3 08:16:43 aies1 kernel: ata1: failed to recover some devices,
retrying in 5 secs
Aug 3 08:16:45 aies1 kernel: ata2.00: qc timeout (cmd 0xec)
Aug 3 08:16:45 aies1 kernel: ata2.00: failed to IDENTIFY (I/O error,
err_mask=0 x4)
Aug 3 08:16:45 aies1 kernel: ata2.00: revalidation failed (errno=-5)
Aug 3 08:16:45 aies1 kernel: ata2: failed to recover some devices,
retrying in 5 secs
Aug 3 08:16:55 aies1 kernel: ata1: port is slow to respond, please be
patient
Aug 3 08:16:57 aies1 kernel: ata2: port is slow to respond, please be
patient
Aug 3 08:17:18 aies1 kernel: ata1: port failed to respond (30 secs)
Aug 3 08:17:18 aies1 kernel: ata1: soft resetting port
Aug 3 08:17:20 aies1 kernel: ata2: port failed to respond (30 secs)
Aug 3 08:17:20 aies1 kernel: ata2: soft resetting port
Aug 3 08:17:25 aies1 kernel: ata1: port is slow to respond, please be
patient
Aug 3 08:17:27 aies1 kernel: ata2: port is slow to respond, please be
patient
Aug 3 08:17:48 aies1 kernel: ata1: port failed to respond (30 secs)
Aug 3 08:17:48 aies1 kernel: ATA: abnormal status 0xD0 on port 0x30EF
Aug 3 08:17:48 aies1 kernel: ATA: abnormal status 0xD0 on port 0x30EF
Aug 3 08:17:48 aies1 kernel: ATA: abnormal status 0xD0 on port 0x30EF
Aug 3 08:17:48 aies1 kernel: ATA: abnormal status 0xD0 on port 0x30EF
--
Roger Oberholtzer
OPQ Systems AB
Ramböll Sverige AB
Kapellgränd 7
P.O. Box 4205
SE-102 65 Stockholm, Sweden
Tel: Int +46 8-615 60 20
Fax: Int +46 8-31 42 23
next prev parent reply other threads:[~2006-08-03 7:26 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-01 15:18 libata question Roger Oberholtzer
2006-08-01 15:33 ` Tejun Heo
2006-08-01 18:39 ` Roger Oberholtzer
2006-08-01 18:45 ` Tejun Heo
2006-08-01 19:03 ` Roger Oberholtzer
2006-08-01 19:06 ` Tejun Heo
2006-08-02 7:05 ` Roger Oberholtzer
2006-08-02 7:20 ` Tejun Heo
2006-08-02 8:06 ` Roger Oberholtzer
2006-08-02 14:35 ` Roger Oberholtzer
2006-08-02 15:02 ` Tejun Heo
2006-08-03 7:26 ` Roger Oberholtzer [this message]
2006-08-03 7:58 ` Tejun Heo
2006-08-03 8:49 ` Roger Oberholtzer
2006-08-03 20:08 ` Stefan Smietanowski
2006-08-02 1:22 ` 31244 PCI Card sam song
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=1154589962.25611.102.camel@acme \
--to=roger@opq.se \
--cc=htejun@gmail.com \
--cc=linux-ide@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;
as well as URLs for NNTP newsgroup(s).