Petre Rodan put forth on 12/23/2010 3:16 PM: > but my original mail had a different target really. I have to recognize that I don't know much about the inner-workings of a filesystem, but I find it odd that once there is no input from the outside, a process keeps writing to the drive indefinitely. in my very narrow thinking the fact that these writes dissapear after a remount would prove their redundance. Ahh, quite right. Sorry Petre. This might shed some light on your issue. Old background thread: http://oss.sgi.com/archives/xfs/2003-09/msg00674.html Current documentation on this turnable knob: http://www.mjmwired.net/kernel/Documentation/filesystems/xfs.txt fs.xfs.xfssyncd_centisecs (Min: 100 Default: 3000 Max: 720000) The interval at which the xfssyncd thread flushes metadata out to disk. This thread will flush log activity out, and do some processing on unlinked inodes. Maybe related or also worth mentioning: fs.xfs.age_buffer_centisecs (Min: 100 Default: 1500 Max: 720000) The age at which xfsbufd flushes dirty metadata buffers to disk. As of 2.6.36, it looks like you can stretch this out to a more reasonable (for your application) 12 minutes if you like. I'm not sure if the max value is different than 2.6.32.2 as I don't have a box or VM available with 2.6.32.2. Try bumping these values to 720000 and see if that allows your disk to sleep for 12 mins. -- Stan _______________________________________________ xfs mailing list xfs@xxxxxxxxxxx http://oss.sgi.com/mailman/listinfo/xfs
