> Craig Schlenter wrote:
> > I get the messages in the subject when trying to unmount a iso9660 cdrom.
> > I also get them when trying to unmount a loop mounted iso9660 filesystem
> > (been playing with a cdwriter).
>
> Craig,
> I tried playing with a CDROM and didn't get any busy inodes, so maybe
> the cdwriter is forgetting to release an inode.
>
> I made some changes to invalidate_inodes so that it can be called prior
> to the unmounting, as it's really not safe to proceed with unmounting
> with inodes still in use. The attached patch will check for this and
> print out a list of the busy inodes -- by name if they have a name,
> otherwise by number.
>
> Could you please try to reproduce the problem and see what inodes are
> busy? Then hopefully the cdwriter (or kernel) can be fixed ...
OK, after applying the patch (making it 2.1.50 + the sr.c invalidate
inodes + your patch) I get:
[root@flashy /root]# umount /mnt
umount: /dev/scd0: device is busy
/var/log/messages is tagged on to the end of this message
The CDROM has symlinks on it btw. (See Linus' pre-2.1.51 message).
On 2.1.51-pre1 the unmount works fine!! Excellent!
Thank you!
Cheers,
--Craig
Aug 17 17:19:25 flashy kernel: Busy Inodes for Device 0b:00:
Aug 17 17:19:25 flashy kernel: inode 4056346: count=65535 state=0
Aug 17 17:19:25 flashy kernel: inode 4056196: count=65535 state=0
Aug 17 17:19:25 flashy kernel: inode 4056038: count=65535 state=0
Aug 17 17:19:25 flashy kernel: inode 4055886: count=65535 state=0
Aug 17 17:19:25 flashy kernel: inode 4055746: count=65535 state=0
Aug 17 17:19:25 flashy kernel: inode 4055604: count=65535 state=0
Aug 17 17:19:25 flashy kernel: inode 4055464: count=65535 state=0
Aug 17 17:19:25 flashy kernel: inode 4055328: count=65535 state=0
Aug 17 17:19:25 flashy kernel: inode 4055184: count=65535 state=0
Aug 17 17:19:25 flashy kernel: inode 4055040: count=65535 state=0
Aug 17 17:19:25 flashy kernel: inode 4054770: count=65535 state=0
Aug 17 17:19:25 flashy kernel: inode 4054626: count=65535 state=0
Aug 17 17:19:25 flashy kernel: inode 4054476: count=65535 state=0
Aug 17 17:19:25 flashy kernel: inode 4054324: count=65535 state=0
Aug 17 17:19:25 flashy kernel: inode 4054180: count=65535 state=0
Aug 17 17:19:25 flashy kernel: inode 4054020: count=65535 state=0
Aug 17 17:19:25 flashy kernel: inode 4053870: count=65535 state=0
Aug 17 17:19:25 flashy kernel: inode 4053726: count=65535 state=0
Aug 17 17:19:25 flashy kernel: inode 4053582: count=65535 state=0
Aug 17 17:19:25 flashy kernel: inode 4053430: count=65535 state=0
Aug 17 17:19:25 flashy kernel: inode 4053280: count=65535 state=0
Aug 17 17:19:25 flashy kernel: inode 4053136: count=65535 state=0
Aug 17 17:19:25 flashy kernel: inode 4052992: count=65535 state=0
Aug 17 17:19:25 flashy kernel: inode 4052806: count=65535 state=0
Aug 17 17:19:25 flashy kernel: inode 4052664: count=65535 state=0
Aug 17 17:19:25 flashy kernel: inode 4052520: count=65535 state=0
Aug 17 17:19:25 flashy kernel: inode 4052370: count=65535 state=0
Aug 17 17:19:25 flashy kernel: inode 4052214: count=65535 state=0
Aug 17 17:19:25 flashy kernel: inode 4052064: count=65535 state=0
Aug 17 17:19:25 flashy kernel: inode 4051906: count=65535 state=0
Aug 17 17:19:25 flashy kernel: inode 4051764: count=65535 state=0
Aug 17 17:19:25 flashy kernel: inode 4051604: count=65535 state=0
Aug 17 17:19:25 flashy kernel: inode 4051460: count=65535 state=0
Aug 17 17:19:25 flashy kernel: inode 4051298: count=65535 state=0
Aug 17 17:19:25 flashy kernel: inode 4051148: count=65535 state=0
Aug 17 17:19:25 flashy kernel: inode 3815548: count=65535 state=0
Aug 17 17:19:25 flashy kernel: inode 89190: count=65535 state=0
Aug 17 17:19:25 flashy kernel: inode 78462: count=65535 state=0