Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 282548 - emerge --sync on a nfs filesystem
Summary: emerge --sync on a nfs filesystem
Status: RESOLVED INVALID
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: Current packages (show other bugs)
Hardware: All Linux
: High normal
Assignee: Gentoo Linux bug wranglers
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-08-24 10:37 UTC by Thomas Stein
Modified: 2009-08-30 17:33 UTC (History)
1 user (show)

See Also:
Package list:
Runtime testing required: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Thomas Stein 2009-08-24 10:37:58 UTC
Hello.

emerge --sync produces messages like this:

rsync: mkstemp "/usr/portage/metadata/cache/net-fs/.nfs-utils-1.1.4-r1.XKVjSz" failed: No such file or directory (2)
rsync: mkstemp "/usr/portage/metadata/cache/net-fs/.nfs-utils-1.1.5.73NLqz" failed: No such file or directory (2)
rsync: mkstemp "/usr/portage/metadata/cache/net-fs/.nfs-utils-1.1.6.IHceZy" failed: No such file or directory (2)
rsync: mkstemp "/usr/portage/metadata/cache/net-fs/.nfs-utils-1.1.6-r1.c5lHxy" failed: No such file or directory (2)
rsync: mkstemp "/usr/portage/metadata/cache/net-fs/.nfs-utils-1.2.0.YjZa6x" failed: No such file or directory (2)
rsync: mkstemp "/usr/portage/metadata/cache/net-fs/.nfs4-acl-tools-0.3.2.5JzFEx" failed: No such file or directory (2)
rsync: mkstemp "/usr/portage/metadata/cache/net-fs/.nfs4-acl-tools-0.3.3.QHRtqx" failed: No such file or directory (2)
rsync: mkstemp "/usr/portage/net-fs/nfs-utils/.nfs-utils-1.1.4-r1.ebuild.Ravu5J" failed: No such file or directory (2)
rsync: mkstemp "/usr/portage/net-fs/nfs-utils/.nfs-utils-1.1.5.ebuild.MGDxKW" failed: No such file or directory (2)
rsync: mkstemp "/usr/portage/net-fs/nfs-utils/.nfs-utils-1.1.6-r1.ebuild.ZFaDp9" failed: No such file or directory (2)
rsync: mkstemp "/usr/portage/net-fs/nfs-utils/.nfs-utils-1.1.6.ebuild.kt6Q4l" failed: No such file or directory (2)
rsync: mkstemp "/usr/portage/net-fs/nfs-utils/.nfs-utils-1.2.0.ebuild.ln6cKy" failed: No such file or directory (2)
rsync: mkstemp "/usr/portage/net-fs/nfs-utils/files/.nfs-utils-1.1.2-rpcgen-ioctl.patch.41JCpL" failed: No such file or directory (2)
rsync: mkstemp "/usr/portage/net-fs/nfs-utils/files/.nfs-utils-1.1.4-ascii-man.patch.94i64X" failed: No such file or directory (2)
rsync: mkstemp "/usr/portage/net-fs/nfs-utils/files/.nfs-utils-1.1.4-mtab-sym.patch.6DPBKa" failed: No such file or directory (2)
rsync: mkstemp "/usr/portage/net-fs/nfs-utils/files/.nfs-utils-1.1.4-no-exec.patch.BmJ7pn" failed: No such file or directory (2)
rsync: mkstemp "/usr/portage/net-fs/nfs-utils/files/.nfs.confd.WIvE5z" failed: No such file or directory (2)
rsync: mkstemp "/usr/portage/net-fs/nfs-utils/files/.nfs.initd.Tp7cLM" failed: No such file or directory (2)
rsync: mkstemp "/usr/portage/net-fs/nfs-utils/files/.nfsmount.initd.ASOvNZ" failed: No such file or directory (2)
rsync: mkstemp "/usr/portage/net-fs/nfs4-acl-tools/.nfs4-acl-tools-0.3.2.ebuild.hJ4Ged" failed: No such file or directory (2)
rsync: mkstemp "/usr/portage/net-fs/nfs4-acl-tools/.nfs4-acl-tools-0.3.3.ebuild.4nxTFq" failed: No such file or directory (2)
rsync: mkstemp "/usr/portage/sys-freebsd/freebsd-usbin/files/.nfs.confd.K8qEkW" failed: No such file or directory (2)
rsync: mkstemp "/usr/portage/sys-freebsd/freebsd-usbin/files/.nfs.initd.nfHrZr" failed: No such file or directory (2)
rsync: mkstemp "/usr/portage/sys-freebsd/freebsd-usbin/files/.nfsmount.initd.25heZX" failed: No such file or directory (2)

This happens on a nfs root file system. I think it's not allowed to create .nfs files. Is there a way to avoid this behaviour?

best regards
Thomas

Reproducible: Always
Comment 1 Justin Lecher (RETIRED) gentoo-dev 2009-08-30 17:33:00 UTC
This is not a support forum. I hit google with your problem and it seems there are solution for it and it isn't a bug. If you find out I am wrong, then please reopen the bug and I will assign the bug to the maintainer.
In this case please attach the output of emerge --info.