Hi,
> If I use the internel pdebuild, the process fails to umount one of
> my bind mounts after the build is complete:
>
> -> unmounting /tmp/pbuilder-shared filesystem
> umount: /tmp/pbuilder-shared: not mounted
> umount: /tmp/pbuilder-shared: not mounted
> W: Retrying to unmount /tmp/pbuilder-shared
> umount: /var/cache/pbuilder/build//24872//tmp/pbuilder-shared: not mounted
>
> Could not unmount /tmp/pbuilder-shared, there might be some program
> still using files in /proc (klogd?).
> Please check and kill the process manually so that I can unmount
> /tmp/pbuilder-shared
>
> This error is only happens with chroot; try using user-mode-linux to
> avoid this message.
>
>
> This is the relevant configuration:
>
> lapse:~> grep -A3 shared ~/.pbuilderrc
> #[353]
> SHARED=/tmp/pbuilder-shared
> mkdir -p $SHARED
> chown $PBUID:$PBGID $SHARED
> BINDMOUNTS="${BINDMOUNTS:+$BINDMOUNTS }$SHARED"
>
>
> It *did* mount it:
>
> Building the build Environment
> [...]
> -> Mounting /tmp/pbuilder-shared
>
>
> The only way to solve this is by doing
>
> mount -o bind /tmp/pbuilder-shared
> /var/cache/pbuilder/build//24872//tmp/pbuilder-shared
1. Which kernel ?
I suppose this is stock ?
Kernel: Linux 2.6.17-1-686
2. what does /proc/mounts say when it's failing to umount?
3. is it reproducible all the time?
regards,
junichi
--
[EMAIL PROTECTED],netfort.gr.jp} Debian Project
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
