ATA errors corrupt other I/O & set / readonly

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

 



Two weeks ago on recommendation of downstream bug owner I filed https://bugzilla.kernel.org/show_bug.cgi?id=43128 expecting to see some kind of non-delayed reaction from someone either in the bug or here, and am quite disappointed that nothing has yet happened. Is the bug's owner sick, on holiday, or at a convention?

I originally resisted filing because I believe that actual problem is the device's and not kernel or drivers. Yet, that it is possible for any such device failure to cause system corruption doesn't seem right either. So, can someone please comment on the likelihood that this bug can or will be fixed? I would like someone to respond here or in the bug before proceeding to try again to convince the manufacturer its product is defective and get a refund instead of yet another replacement of a defective product with another defective product.

Once I return it for refund I will no longer be able to follow up on the bugs I filed, yet I need a working device that doesn't require I figure out a correct cmdline workaround for every one of the several systems it ever needs to be connected to.

Please, what should I do?
--
"The wise are known for their understanding, and pleasant
words are persuasive." Proverbs 16:21 (New Living Translation)

 Team OS/2 ** Reg. Linux User #211409 ** a11y rocks!

Felix Miata  ***  http://fm.no-ip.com/
--
To unsubscribe from this list: 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