Thanks. From the fs log (fs/process_dump.12751):
16:17:43 open("/dev/sdb", O_RDONLY|O_SYNC) = 4
16:17:43 lseek(4, 0, SEEK_SET) = 0
16:17:43 read(4,
"\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0"..., 512) =
512
16:17:43 read(4, "LABELONE\1\0\0\0\0\0\0\0]V\332\353 \0\0\0LVM2 001"..., 32256)
= 32256
16:17:43 brk(0x20d2000) = 0x20d2000
16:17:43 mmap(NULL, 8589926400, PROT_READ|PROT_WRITE,
MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0x7f3f857c0000
16:17:43 lseek(4, 32768, SEEK_SET) = 32768
16:17:43 read(4,
"\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0"...,
4294901760) = 2147479552
16:17:54 read(4,
"\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0"...,
2147422208) = 2147422208
16:18:05 brk(0x20fa000) = 0x20fa000
[...]
grub-probe spends 22 seconds reading 4GB from the disk. Then this
pattern repeats:
16:18:08 open("/dev/sdb", O_RDONLY|O_SYNC) = 4
16:18:08 lseek(4, 32768, SEEK_SET) = 32768
16:18:08 read(4,
"\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0"...,
4294901760) = 2147479552
16:18:19 read(4,
"\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0"...,
2147422208) = 2147422208
16:18:30 brk(0x2153000) = 0x2153000
And the same thing happens in the fs_uuid calls.
16:19:35 open("/dev/sdb", O_RDONLY|O_SYNC) = 4
16:19:35 lseek(4, 0, SEEK_SET) = 0
16:19:35 read(4,
"\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0"..., 512) =
512
16:19:35 read(4, "LABELONE\1\0\0\0\0\0\0\0]V\332\353 \0\0\0LVM2 001"..., 32256)
= 32256
16:19:35 brk(0x1707000) = 0x1707000
16:19:35 mmap(NULL, 8589926400, PROT_READ|PROT_WRITE,
MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0x7faca2289000
16:19:35 lseek(4, 32768, SEEK_SET) = 32768
16:19:35 read(4,
"\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0"...,
4294901760) = 2147479552
16:19:46 read(4,
"\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0"...,
2147422208) = 2147422208
16:19:56 brk(0x172f000) = 0x172f000
I have no idea why grub-probe thinks it needs to read 4GB of disk, but
that does explain why it's slow, and does point to a grub problem rather
than a kernel problem.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1455268
Title:
update-grub (grub-probe) during package installation on Cisco UCS B260
servers - Precise deployment fails with hwe-t kernel
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1455268/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
