On 07/11/2012 08:31 PM, Steve Langasek wrote:
> Hi Muharem,
>
> On Wed, Jul 11, 2012 at 12:30:31PM -0000, Muharem Hrnjadovic wrote:
>> $ sudo apt-get install --reinstall nfs-common
>> Reading package lists... Done
>> Building dependency tree
>> Reading state information... Done
>> The following packages were automatically installed and are no longer required:
>> xfonts-encodings linux-headers-3.0.0-22 libapt-inst1.3 xfonts-utils
>> libxfont1 libept1 libvtk5.6 libvpx0 linux-headers-3.0.0-22-server
>> libapt-pkg4.11 x-ttcidfont-conf libfontenc1 libjpeg62 libnl3 defoma
>> libllvm2.9
>> Use 'apt-get autoremove' to remove them.
>> 0 upgraded, 0 newly installed, 1 reinstalled, 0 to remove and 0 not upgraded.
>> 2 not fully installed or removed.
>> After this operation, 0 B of additional disk space will be used.
>> Setting up nfs-common (1:1.2.5-3ubuntu3) ...
>> rmdir: failed to remove `/var/lib/nfs/rpc_pipefs'
>> dpkg: error processing nfs-common (--configure):
>> subprocess installed post-installation script returned error exit status 1
>> dpkg: dependency problems prevent configuration of nfs-kernel-server:
>> nfs-kernel-server depends on nfs-common (= 1:1.2.5-3ubuntu3); however:
>> Package nfs-common is not configured yet.
>> dpkg: error processing nfs-kernel-server (--configure):
>> dependency problems - leaving unconfigured
>> No apport report written because the error message indicates it's a follow-up error from a previous failure.
>> Errors were encountered while processing:
>> nfs-common
>> nfs-kernel-server
>> E: Sub-process /usr/bin/dpkg returned an error code (1)
>
> The latest version of nfs-common in precise does:
>
> rmdir --ignore-fail-on-non-empty /var/lib/nfs/rpc_pipefs
>
> So the question is, why is rmdir failing? Is this directory a mount point?
> If so, why was stopping idmapd and gssd not sufficient to trigger
> unmounting?
Hello Steve,
that directory was not a mount point. Unfortunately I did not have the
time to look at its content. I did a
On 07/11/2012 08:31 PM, Steve Langasek wrote: 3.0.0-22 libapt-inst1.3 xfonts-utils 3.0.0-22- server nfs/rpc_ pipefs' fail-on- non-empty /var/lib/ nfs/rpc_ pipefs
> Hi Muharem,
>
> On Wed, Jul 11, 2012 at 12:30:31PM -0000, Muharem Hrnjadovic wrote:
>> $ sudo apt-get install --reinstall nfs-common
>> Reading package lists... Done
>> Building dependency tree
>> Reading state information... Done
>> The following packages were automatically installed and are no longer required:
>> xfonts-encodings linux-headers-
>> libxfont1 libept1 libvtk5.6 libvpx0 linux-headers-
>> libapt-pkg4.11 x-ttcidfont-conf libfontenc1 libjpeg62 libnl3 defoma
>> libllvm2.9
>> Use 'apt-get autoremove' to remove them.
>> 0 upgraded, 0 newly installed, 1 reinstalled, 0 to remove and 0 not upgraded.
>> 2 not fully installed or removed.
>> After this operation, 0 B of additional disk space will be used.
>> Setting up nfs-common (1:1.2.5-3ubuntu3) ...
>> rmdir: failed to remove `/var/lib/
>> dpkg: error processing nfs-common (--configure):
>> subprocess installed post-installation script returned error exit status 1
>> dpkg: dependency problems prevent configuration of nfs-kernel-server:
>> nfs-kernel-server depends on nfs-common (= 1:1.2.5-3ubuntu3); however:
>> Package nfs-common is not configured yet.
>> dpkg: error processing nfs-kernel-server (--configure):
>> dependency problems - leaving unconfigured
>> No apport report written because the error message indicates it's a follow-up error from a previous failure.
>> Errors were encountered while processing:
>> nfs-common
>> nfs-kernel-server
>> E: Sub-process /usr/bin/dpkg returned an error code (1)
>
> The latest version of nfs-common in precise does:
>
> rmdir --ignore-
>
> So the question is, why is rmdir failing? Is this directory a mount point?
> If so, why was stopping idmapd and gssd not sufficient to trigger
> unmounting?
Hello Steve,
that directory was not a mount point. Unfortunately I did not have the
time to look at its content. I did a
apt-get remove --purge nfs-common
followed by
apt-get install nfs-common nfs-kernel-server
and that fixed the issue.