On Wednesday February 20, [EMAIL PROTECTED] wrote: > Hi all, > > I have two disks in my server, one of them (hda) being used for backups > solely. To reduce noise level and power consumption, I have been trying > to keep it running in standby mode (as opposed to active) most of the time. > > Although there should be nothing accessing the disk except my custom > backup cron job initiating at 5am daily, something was constantly > bringing it back into active state after a rough 20-25 minutes. With the > help of blktrace, I monitored every single I/O access to the disk and > found a single process only that would cause the wake-up: > > > $ sudo blkparse -i hda.blktrace.0 > Input file hda.blktrace.0 added > [...] > 3,0 0 6 88.950000000 6806 Q R 447 + 8 [rpc.mountd] > [...] > > > So for some reason, rpc.mountd issues this disk request in regular > intervals although nothing on the disk is being NFS-exported according > to /etc/exports.
This is doubtlessly something related to libblkid. We use libblkid to get a unique UID for each filesystem and use that as an identified in the filehandle. We only ever ask it for the UID of specific devices that have been exported. However it is quite possible that it touches other devices as well... I'm using libblkid in a way that it wasn't originally designed to be used. It was (as far as I can tell) designed to find a device given a UUID or similar. In that case you would expect it to touch every device. I'm doing the reverse and it probably isn't doing things the ideal way. I guess someone should figure out how libblkid works and make it work better for us...... You could always build your own nfs-utils and configure with --without-uuid. Not an ideal solution... NeilBrown - To unsubscribe from this list: send the line "unsubscribe linux-nfs" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
