I have similar behavior with Jaunty running 2.6.28-11-server, 2.6.27-11-server, 2.6.29-02062902-generic_2.6.29-02062902_amd64 or 2.6.30-020630rc4-generic_2.6.30-020630rc4_amd64.
The problem is that after issuing "hdparm -y /dev/sdc" the disk stops and immediately spins up. I hear it. The disk is a single member of a LVM group, which group has no mounted volumes. This is a simple experiment: #hdparm -y /dev/sdc && sleep 1 && hdparm -C /dev/sdc /dev/sdc: issuing standby command /dev/sdc: drive state is: active/idle I tried to find what process caused the disk to spin up: #echo 1>/proc/sys/vm/block_dump #tail -f /var/log/kern.log | egrep -v 'on dm-2' #dm-2 is /, which is constantly accessed At this point nothing is coming from the tail. Then, from a different terminal window, I do: #hdparm -C /dev/sdc And the above tail shows: May 10 12:56:09 cave kernel: [ 2568.028494] udevd(937): dirtied inode 12292 (88) on tmpfs May 10 12:56:09 cave kernel: [ 2568.030249] udevd(937): dirtied inode 12293 (\x2fdevices\x2fpci0000:00\x2f0000:00:14.1\x2fhost5\x2ftarget5:0:0\x2f5:0:0:0\x2fblock\x2fsdc) on tmpfs May 10 12:56:09 cave kernel: [ 2568.047530] vol_id(5200): dirtied inode 1359 (sdc) on tmpfs May 10 12:56:09 cave kernel: [ 2568.069047] lvm(5204): READ block 130944 on ram0 May 10 12:56:09 cave kernel: [ 2568.069072] lvm(5204): READ block 131056 on ram0 May 10 12:56:09 cave kernel: [ 2568.069083] lvm(5204): READ block 0 on ram0 May 10 12:56:09 cave kernel: [ 2568.069092] lvm(5204): READ block 8 on ram0 .... May 10 12:56:09 cave kernel: [ 2568.178317] lvm(5204): READ block 1465148928 on sdb May 10 12:56:09 cave kernel: [ 2568.178816] lvm(5204): READ block 1465149152 on sdb May 10 12:56:09 cave kernel: [ 2568.179296] lvm(5204): READ block 0 on sdb May 10 12:56:09 cave kernel: [ 2568.179776] lvm(5204): READ block 8 on sdb May 10 12:56:09 cave kernel: [ 2568.180419] lvm(5204): READ block 0 on sdb May 10 12:56:09 cave kernel: [ 2568.180616] lvm(5204): READ block 8 on sdb May 10 12:56:09 cave kernel: [ 2568.180768] lvm(5204): READ block 72 on sdb May 10 12:56:09 cave kernel: [ 2568.180940] lvm(5204): READ block 72 on sdb May 10 12:56:09 cave kernel: [ 2568.181332] lvm(5204): READ block 390721792 on sdc May 10 12:56:09 cave kernel: [ 2568.181530] lvm(5204): READ block 390721952 on sdc May 10 12:56:09 cave kernel: [ 2568.181720] lvm(5204): READ block 0 on sdc May 10 12:56:09 cave kernel: [ 2568.181898] lvm(5204): READ block 8 on sdc May 10 12:56:09 cave kernel: [ 2568.182110] lvm(5204): READ block 0 on sdc May 10 12:56:09 cave kernel: [ 2568.182309] lvm(5204): READ block 8 on sdc May 10 12:56:09 cave kernel: [ 2568.182512] lvm(5204): READ block 8 on sdc May 10 12:56:09 cave kernel: [ 2568.182696] lvm(5204): READ block 8 on sdc May 10 12:56:09 cave kernel: [ 2568.183051] lvm(5204): READ block 390218624 on sdd1 May 10 12:56:09 cave kernel: [ 2568.184369] lvm(5204): READ block 390218768 on sdd1 May 10 12:56:09 cave kernel: [ 2568.186489] lvm(5204): READ block 0 on sdd1 May 10 12:56:09 cave kernel: [ 2568.206720] lvm(5204): READ block 8 on sdd1 May 10 12:56:09 cave kernel: [ 2568.207320] lvm(5204): READ block 0 on sdd1 May 10 12:56:09 cave kernel: [ 2568.207897] lvm(5204): READ block 8 on sdd1 May 10 12:56:09 cave kernel: [ 2568.208452] lvm(5204): READ block 13 on sdd1 May 10 12:56:09 cave kernel: [ 2568.209004] lvm(5204): READ block 13 on sdd1 May 10 12:56:09 cave kernel: [ 2568.209739] lvm(5204): READ block 497792 on sdd5 May 10 12:56:09 cave kernel: [ 2568.234196] lvm(5204): READ block 497936 on sdd5 May 10 12:56:09 cave kernel: [ 2568.236289] lvm(5204): READ block 0 on sdd5 May 10 12:56:09 cave kernel: [ 2568.236845] lvm(5204): READ block 8 on sdd5 May 10 12:56:09 cave kernel: [ 2568.237438] lvm(5204): READ block 0 on sdd5 May 10 12:56:09 cave kernel: [ 2568.238147] lvm(5204): READ block 0 on sdd1 May 10 12:56:09 cave kernel: [ 2568.238735] lvm(5204): READ block 8 on sdd1 May 10 12:56:09 cave kernel: [ 2568.239292] lvm(5204): READ block 13 on sdd1 May 10 12:56:09 cave kernel: [ 2568.239845] lvm(5204): READ block 13 on sdd1 May 10 12:56:09 cave kernel: [ 2568.240488] lvm(5204): READ block 8 on sdd1 May 10 12:56:09 cave kernel: [ 2568.241048] lvm(5204): READ block 13 on sdd1 May 10 12:56:09 cave kernel: [ 2568.242539] lvm(5204): READ block 13 on sdd1 A very similar cascade of [almost?] all disk accesses happens when I say "hdparm -C" for any drive. I have a mixture of IDE and SATA drives. Why does "hdparm -C" cause such thing? I have access to a Hardy system, having all kinds of LVM volumes and standalone partitions (all are SATA), and with the same sequence of actions, "tail -f" shows no dirtied, written or read blocks. Intrepid (at least during its early days after release) had hdparm -y working fine. Another observation is a smartd message: smartd[6360]: Device: /dev/sdc, CHECK POWER STATUS spins up disk (0x00 -> 0xff) -- hard disk will not spin down with kernel 2.6.29-11 https://bugs.launchpad.net/bugs/359513 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
