On Thu, Nov 19, 2009 at 19:24, Kay Sievers <kay.sievers@xxxxxxxx> wrote: > On Thu, Nov 19, 2009 at 19:03, Christoph Stritt <phoenix@xxxxxxxxx> wrote: >> Kay Sievers wrote: >>> On Thu, Nov 19, 2009 at 15:51, Kay Sievers <kay.sievers@xxxxxxxx> wrote: >>>> On Thu, Nov 19, 2009 at 15:29, Christoph Stritt <phoenix@xxxxxxxxx> 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;h=66094a4a7fc1d303e80785d586800eae9841502b >>>> >>>> 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). > > Ok, something to look into. Thanks a lot for the tests! For now, I've added a check if the device is an optical drive, which should prevent this from happening. Thanks, Kay -- To unsubscribe from this list: send the line "unsubscribe linux-hotplug" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
