Tsai Li Ming wrote:
Scott Silva wrote:
on 4-2-2009 2:00 PM Anne Wilson spake the following:
On Thursday 02 April 2009 21:40:59 R P Herrold wrote:
On Wed, 1 Apr 2009, Paul Heinlein wrote:
I don't know if it's a bug or a feature, but the filesystem-2.4.0-2.el5.centos rpm won't upgrade cleanly if /home is an NFS filesystem.
I confirm this is present in 5.3 where /home is an NFS mount, and that I missed it in testing. A workaround is:
- Boot into single user node.
- run: /sbin/service network start
- run: yum -y update filesystem
If your system emitted the warning, but did not 'bail', it is safe to retieve the rpm locally, and to run:
# rpm -Uvh filesystem*rpm --force
as there are no scripts in play:
[herrold@centos-5 ~]$ sudo rpm -q --scripts filesystem [herrold@centos-5 ~]$
The cause is the NFS root_squash being in effect when a NFS overmount is on a mountpoint, it seems. /home happens to express it
It seems Paul and I are the last two users of NFS mounted /home left.
I have /home exported and ran the upgrade from this laptop over the network, where that directory is mounted and displayed in a folderview under KDE4. I had no problems whatsoever. Is this the sort of situation you mean?
Anne
The way I read it was their /home was mounted on NFS, not just exported.
I had a problem with /mnt or /media too with a mounted ISO. Had to umount the ISO before filesystem rpm can be updated. This happened when I yum update to RHEL 5.3 recently.
My guess is a scriptlet is failing - quite possibly because an SELinux chcon command fails in those conditions. They probably need to change the chcon portion of the scriptlet to add a ||: after the command so it doesn't bomb out.
Someone should take a look at the spec file, add the ||: after the chcon (or whatever it might be) and if it allow the package to update, file a bug report upstream so it gets fixed in rhel svn.