Re: libata question

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



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

-
: send the line "unsubscribe linux-ide" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html

[Index of Archives]     [Linux Filesystems]     [Linux SCSI]     [Linux RAID]     [Git]     [Kernel Newbies]     [Linux Newbie]     [Security]     [Netfilter]     [Bugtraq]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Samba]     [Device Mapper]

  Powered by Linux