On 09.08.24 22:13, Christian Heusel wrote:
On 24/08/09 08:42PM, Christian Heusel wrote:
On 24/08/09 08:34AM, Damien Le Moal wrote:
On 2024/08/07 15:10, Niklas Cassel wrote:
On Wed, Aug 07, 2024 at 11:26:46AM -0700, Damien Le Moal wrote:
On 2024/08/07 10:23, Christian Heusel wrote:
on my NAS I am encountering the following issue since v6.6.44 (LTS), when executing the hdparm command for my WD-WCC7K4NLX884 drives to get the active or standby state:
[...] Yes, indeed. I do not want to revert any of these recent patches, because as you rightly summarize here, these fix something that has been broken for a long time. We were just lucky that we did not see more application failures until now, or rather unlucky that we did not as that would have revealed these problems earlier.
It seems like this does not only break hdparm but also hddtemp, which does not use hdparm as dep as far as I can tell:
As someone on the same thread has pointed out, this also seems to affect udiskd:
For the record, three more people reported similar symptoms in the past few days:
https://lore.kernel.org/all/e620f887-a674-f007-c17b-dc16f9a0a588@web.de/ https://bugzilla.kernel.org/show_bug.cgi?id=219144
Ciao, Thorsten
P.S.: I for the tracking for now assume those are indeed the same problem:
#regzbot dup: https://lore.kernel.org/all/e620f887-a674-f007-c17b-dc16f9a0a588@web.de/ #regzbot dup: https://bugzilla.kernel.org/show_bug.cgi?id=219144