Block device's sysfs setting getting lost after suspend-resume cycle

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

 



Hi!

I just noticed that sysfs settings now seem to get lost after
a suspend/resume cycle. In my case it's queue/read_ahead_kb,
which I configure with a udev rule. This has been working fine
for years.

We start out with:
$cat /sys/block/nvme0n1/queue/read_ahead_kb
128

Set a different value:
$echo 256 > /sys/block/nvme0n1/queue/read_ahead_kb
$cat /sys/block/nvme0n1/queue/read_ahead_kb
256

<suspend & resume>

Check again:
$cat /sys/block/nvme0n1/queue/read_ahead_kb
128

I'm reasonably sure it used to retain the configured value.
The same also happens with sd (SATA) devices on a different machine,
so it seems to be a generic problem with either block or sysfs.

This is with 6.14.3-rc2. I have unfortunately no idea when this
started to happen - i only noticed it now. Will trawl through
git history but wanted to see if this rings a bell with someone.

thanks,
Holger




[Index of Archives]     [Linux RAID]     [Linux SCSI]     [Linux ATA RAID]     [IDE]     [Linux Wireless]     [Linux Kernel]     [ATH6KL]     [Linux Bluetooth]     [Linux Netdev]     [Kernel Newbies]     [Security]     [Git]     [Netfilter]     [Bugtraq]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Device Mapper]

  Powered by Linux