second "mount" hangs

[Michael Rothwell]

Here ya go (SysRQ-t):

Nov 18 13:49:54 gromit kernel: mount         D C0D62000     0 18486  
1131                     (NOTLB)
Nov 18 13:49:54 gromit kernel: Call Trace: [__down_read+88/120]
[get_super+73/100] [sync_inodes+21/76] [fsync_dev+23/48]
[invalidate_device+23/88] 
Nov 18 13:49:54 gromit kernel: Call Trace: [<c028ca8c>] [<c013253d>]
[<c013f659>] [<c012f5ef>] [<c013fc77>] 
Nov 18 13:49:54 gromit kernel:    [<d48ea72e>] [blkdev_put+99/144]
[get_sb_bdev+360/672] [<d497ab80>] [set_devname+39/84]
[do_kern_mount+170/296] 
Nov 18 13:49:54 gromit kernel:    [<d48ea72e>] [<c0133cfb>] [<c0132ae8>]
[<d497ab80>] [<c0141307>] [<c013309a>] 
Nov 18 13:49:54 gromit kernel:    [<d497ab80>] [do_add_mount+28/208]
[do_mount+270/296] [copy_mount_options+80/156] [sys_mount+124/192]
[system_call+51/56] 
Nov 18 13:49:54 gromit kernel:    [<d497ab80>] [<c0142098>] [<c01422f6>]
[<c014219c>] [<c014238c>] [<c0106beb>] 


On Sun, 2001-11-18 at 13:33, David Woodhouse wrote:
> 
> 
> rothwell at holly-springs.nc.us said:
> > I mounted a JFFS2 filesystem stored on a 16MB partition on a zip disk,
> > using mtdblock and blktmd. I accidentally typed "mount /mnt/flash"
> > rather than "umount /mnt/flash", and "mount" is now hung. Unkillable. /
> > mnt/flash is still mounted and usable, but not unmountable. It seems I
> > will have to reboot to umount the filesystem. I can't even eject the
> > zip disk. 
> 
> ISTR someone reported this to me recently. I don't recall them ever 
> responding with the results of SysRq-T when I asked though. What are the 
> relevant processes waiting for?
> 
> 
> --
> dwmw2
> 
> 
> 
> ______________________________________________________
> Linux MTD discussion mailing list
> http://lists.infradead.org/mailman/listinfo/linux-mtd/