Stefan Leiner schrieb in 0,9K (33 Zeilen):

was bedeutet das:

Mar 23 15:40:36 Amd Kernel: set_blocksize: b_count 1, dev ide0(3,1), block 287966! Mar 23 15:40:36 Amd Kernel: set_blocksize: b_count 1, dev ide0(3,1), block 379!

weissel@tiger:~ > cd /usr/src/linux weissel@tiger:/usr/src/linux > find -type f | xargs grep "set_blocksize: b_count" Binary file ./fs/buffer.o matches Binary file ./fs/fs.o matches Binary file ./vmlinux matches weissel@tiger:/usr/src/linux > find -type f | xargs grep "set_blocksize:" ./fs/buffer.c: printk(KERN_WARNING "set_blocksize: dev %s buffer_dirty %lu size %lu\n", kdevname(dev), bh->b_blocknr, bh->b_size); ./fs/buffer.c: "set_blocksize: " Binary file ./fs/buffer.o matches Binary file ./fs/fs.o matches Binary file ./vmlinux matches weissel@tiger:/usr/src/linux > less fs/buffer.c Anscheinend wird da nur etwas Kernelmagie mit Blockgroessen getrieben. (Angabe der Kernelversion waere sinnvoll gewesen!) -Wolfgang --------------------------------------------------------------------- To unsubscribe, e-mail: suse-linux-unsubscribe@suse.com For additional commands, e-mail: suse-linux-help@suse.com