All of lore.kernel.org
 help / color / mirror / Atom feed
From: Christoph Stritt <phoenix@jobob.com>
To: linux-hotplug@vger.kernel.org
Subject: Re: udev 147 (ata_id) blanks RW media
Date: Thu, 19 Nov 2009 18:03:34 +0000	[thread overview]
Message-ID: <4B058876.9000604@jobob.com> (raw)
In-Reply-To: <4B054940.9050307@jobob.com>

Kay Sievers wrote:
> On Thu, Nov 19, 2009 at 15:51, Kay Sievers <kay.sievers@vrfy.org> wrote:
>> On Thu, Nov 19, 2009 at 15:29, Christoph Stritt <phoenix@jobob.com> wrote:
>>> Marco d'Itri wrote:
>>>
>>>>> im forwarding this bug since it is udev ata_id that is causing it:
>>>> Again: please try to reproduce the issue after booting with
>>>> init=/bin/bash and running ata_id from the command line with no udevd
>>>> process running.
>>>>
>>> sorry for not mentioning it, but that IS how i tested it.
>>> Well, with init=/bin/sh.
>>>
>>> With my old boot disk, kernel 2.6.24.4, it happens aswell.
>> Hmm, I have a:
>>  INQUIRY: [TSSTcorp][CDDVDW SE-S084B ][TS01]
>> here, and it seems not to not kill any RW media.
>>
>> It's maybe caused by the recently added ATA queries:
>>  http://git.kernel.org/?p=linux/hotplug/udev.git;a=commitdiff;hf094a4a7fc1d303e80785d586800eae9841502b
>>
>> Any chance to try if the same happens with the current libata drivers
>> (sr0) instead of the now deprecated IDE drivers (hdb)?
> 
> It would be still interesting to know, if the same happens with the
> new drivers. But it would not happen by default, because we do not run
> ata_id on optical drives with the libata drivers.

I changed my Kernel to libata+ata_piix (intel ich6). Only change is that it
doesn't get erased on boot, as you stated.
# ./ata_id /dev/sr0 blanks the disk as it did with the older ata drivers (hdb).


  parent reply	other threads:[~2009-11-19 18:03 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-19 13:33 udev 147 (ata_id) blanks RW media Christoph Stritt
2009-11-19 13:55 ` Marco d'Itri
2009-11-19 14:29 ` Christoph Stritt
2009-11-19 14:48 ` Christoph Stritt
2009-11-19 14:51 ` Kay Sievers
2009-11-19 15:08 ` Kay Sievers
2009-11-19 18:03 ` Christoph Stritt [this message]
2009-11-19 18:24 ` Kay Sievers
2009-11-20  2:11 ` Kay Sievers
2009-11-20 10:07 ` Christoph Stritt
2009-11-20 13:56 ` Lennart Poettering

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=4B058876.9000604@jobob.com \
    --to=phoenix@jobob.com \
    --cc=linux-hotplug@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 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.