Hi Neil, first of all, thanks for replying.
Neil Brown wrote: > On Wednesday February 20, [EMAIL PROTECTED] wrote: >> 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: >> >> >> 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. > > You could always build your own nfs-utils and configure with > --without-uuid. > > Not an ideal solution... What would be the downside of that solution? I suppose NFS would keep on working even if I disabled that switch, but you gave the impression there was some (major) drawback. Cheers, --Timo - 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
