> Possibly share_images is mounted read-only or if it's a share on another
> machine, it's not allowed to write.
I think that's the problem - The share is a Windows read-only share, but I had 'rw' in the /etc/fstab line for it. The lesson here is be careful when you cut and paste. :-)
I'll reboot the linux system to kill the connection (easier than getting permission's changed on the Windows box) and now that I've fixed the fstab file the problem shouldn't recur. This also explains why severla other (read-only) shares were acting a bit erratically.
- Doug
>
> -----Original Message-----
> From: Douglas Stalker [mailto:[EMAIL PROTECTED]
>
> > > [EMAIL PROTECTED] pristic01]# umount share_images
> > > umount: share_images: can't write superblock
> > >
>
>
> > umount -l ?
>
> This shows the same problem. even combining -l with -f fails to unmount the
> share.
-- SLUG - Sydney Linux User's Group - http://slug.org.au/ More Info: http://lists.slug.org.au/listinfo/slug
