Comment 21 for bug 221009

I spoke too soon; it's still issuing storms of fsync() calls. However, perhaps due to other unrelated config changes in the server including a move to a better storage subsystem and changes in the I/O scheduler policy, I'm no longer seeing the I/O stalls.

This bug is certainly not fixed, though.

craig@tillium:~$ strace -p 16603 -e fsync -tT
Process 16603 attached - interrupt to quit
12:42:54 fsync(43) = 0 <0.041079>
12:42:54 fsync(25) = 0 <0.006983>
12:42:55 fsync(43) = 0 <0.002066>
12:42:55 fsync(25) = 0 <0.001079>
12:42:55 fsync(43) = 0 <0.001818>
12:42:55 fsync(25) = 0 <0.000879>
12:42:58 fsync(43) = 0 <0.016294>
12:42:58 fsync(25) = 0 <0.003590>
12:43:02 --- SIGCHLD (Child exited) @ 0 (0) ---
12:43:04 fsync(43) = 0 <0.010158>
12:43:04 fsync(25) = 0 <0.004260>
12:43:04 fsync(43) = 0 <0.001897>
12:43:04 fsync(25) = 0 <0.000345>
12:43:04 fsync(43) = 0 <0.001617>
12:43:04 fsync(25) = 0 <0.000607>
12:43:17 fsync(43) = 0 <0.041240>
12:43:17 fsync(25) = 0 <0.005839>
12:43:18 fsync(43) = 0 <0.020532>
12:43:18 fsync(25) = 0 <0.001234>
12:43:21 fsync(43) = 0 <0.040277>
12:43:21 fsync(25) = 0 <0.004756>
12:43:21 fsync(43) = 0 <0.007197>
12:43:21 fsync(25) = 0 <0.000355>
12:43:21 fsync(43) = 0 <0.001899>
12:43:21 fsync(25) = 0 <0.001048>
12:43:21 fsync(43) = 0 <0.002305>
12:43:21 fsync(25) = 0 <0.000700>
12:43:21 fsync(43) = 0 <0.001840>
12:43:21 fsync(25) = 0 <0.000829>
12:43:21 fsync(43) = 0 <0.001911>
12:43:21 fsync(25) = 0 <0.000352>
12:43:21 fsync(43) = 0 <0.002159>
12:43:21 fsync(25) = 0 <0.000654>
12:43:25 fsync(43) = 0 <0.051897>
12:43:25 fsync(25) = 0 <0.005379>

$ dpkg -l firefox-3.0
ii firefox-3.0 3.0+nobinonly-0ubuntu0.8.04.1