Weird mount problem

mmealman ulist at gs1.ubuntuforums.org
Tue Feb 22 15:40:33 UTC 2005


Bob Nielsen Wrote: 
> On Sun, Feb 20, 2005 at 11:22:24PM -0500, Ron Peterson wrote:
> > On Sun, Feb 20, 2005 at 12:17:59PM -0800, Bob Nielsen wrote:
> > > On Sun, Feb 20, 2005 at 01:18:43PM -0500, Ron Peterson wrote:
> > > > On Sun, Feb 20, 2005 at 08:24:04AM -0800, Bob Nielsen wrote:
> > > > > On Sun, Feb 20, 2005 at 07:51:38AM +0000, Sean Miller wrote:
> > > > > > rpowersau at gmail.com wrote:
> > > > > > 
> > > > > > >Why hdb2? Have you tried hdb0, hdb1, ...?
> > > > > > > 
> > > > > > >
> > > > > > One thing you haven't told us is the mount command you are
> trying to use...
> > > > > 
> > > > > mount -t ext3 /dev/hdb2 /mnt
> > > > > 
> > > > > > 
> > > > > > If it's mount /dev/hda2 /mnt it is not going to work, because
> /mnt is 
> > > > > > not a mountpoint; it is a directory too high.
> > > > > 
> > > > > Actually it is a mount point, since there were no directories
> or files 
> > > > > below that point.
> > > > 
> > > > Anyplace is a mount point, the mount will just hide anything
> beneath it.
> > > > 
> > > > > There is a Win 98SE (fat32) partition at /dev/hdb1 and I get
> the same 
> > > > > error when trying to mount it:
> > > > > 
> > > > > $ sudo mount -t vfat /dev/hdb1 /mnt
> > > > > mount: /dev/hdb1 already mounted or /mnt busy
> > > > 
> > > > Make sure you're not cd'd into the directory somewhere..
> > > > 
> > > > Have you tried using fuser or lsof to see what processes may be
> using
> > > > the directory?  e.g.
> > > > 
> > > > fuser /mnt
> > > > lsof +D /mnt
> > > 
> > > Neither of these commands report any results.   I am not a newbie
> (using 
> > > Linux for >10 years), but I have never seen anything like this
> before.
> > 
> > Weird.  Just on a lark ... are you doing any NFS?  If you run 'df'
> does
> > it return?  I've seen hung NFS mounts make things go wonky before..
> > 
> 
> No NFS and df works.  I did some more tests and found that it only
> happens when I use the patched 2.6.8 kernel for Win4Lin, not with a
> warty kernel.  Even more confusing....
> 
> 

I'm having this same issue and it seems so are other people:

http://tinyurl.com/7x2vr
http://tinyurl.com/3krwh

In the second thread something is mentioned about an exit 0 causing the
disks to lock, but when I commented out exit 0 from my libdevmapper init
script it didn't help.


-- 
mmealman




More information about the ubuntu-users mailing list