Hi all
> I have a server where the `dmesg` is full of:
>
> Filesystem "hda4": xlog_state_do_callback: looping 10
> Filesystem "hda4": xlog_state_do_callback: looping 20
> Filesystem "hda4": xlog_state_do_callback: looping 10
> Filesystem "hda4": xlog_state_do_callback: looping 10
> Filesystem "hda4": xlog_state_do_callback: looping 10
> Filesystem "hda4": xlog_state_do_callback: looping 20
> [...]
>
> The hda4 partition contains the /var tree.
[...]
I have been seeing the same messages in the following config:
HP zx8620 16way
processor : 7
vendor : GenuineIntel
arch : IA-64
family : Itanium 2
model : 1
revision : 5
archrev : 0
features : branchlong
cpu number : 0
cpu regs : 4
cpu MHz : 1500.000000
itc MHz : 1500.000000
BogoMIPS : 2239.75
We are currently benchmarking Linux scalablity, so to avoid
disk latency issues on filesystem benchmarks we have been
generating each filesystem of interest on ramdisk then
running osdl-re-aim-7 with disk only tests. With xfs I start
seeing the looping messages at about 50 clients, ( using a 2M
FILESIZE and 128M DISKDIR in the reaim.config ) with a 8way
configuration. (This is just for your records)
What effect can this have on the filesystem transactions,
does it slow writes down due to the out of order logs. We
are currently using the O_SYNC flag on open.
Thanks
Darren
--------------------------------------------------
Darren Williams <dsw AT gelato.unsw.edu.au>
Gelato@UNSW <www.gelato.unsw.edu.au>
--------------------------------------------------
|