RE: Mount locks on bad ISO image?
I'm running 2.4.2 so it's probably just the broken loop device. Thanks, Aaron -Original Message- From: Guest section DW [mailto:[EMAIL PROTECTED]] Sent: March 29, 2001 15:13 To: Aaron Lunansky; [EMAIL PROTECTED] Subject: Re: Mount locks on bad ISO image? On Thu, Mar 29, 2001 at 02:16:03PM -0500, Aaron Lunansky wrote: > I tried mounting a file as an ISO image (turns out it was corrupted) - after > running mount file.iso /cdrom -o loop > mount hung and did not respond.. I could not ^Z it into the background, or > kill, or kill -9 it... > > I'm certain that I have ISO and loopback support compiled into my kernel. > > Anyone know what might be going on? Answer 1: in 2.4.2 the loop device does not work (but things are better in the -ac patches). Answer 2: the kernel tends to believe filesystem data, and a corrupted filesystem can seriously confuse the kernel. If you make sure that the problem does not lie in loop (you can mount other images without problems), then I wouldnt mind seeing your image (or rather, the first MB or two of it) to see whether the isofs code must be improved. (In that case, put some smallish fragment up for ftp and mail the URL to [EMAIL PROTECTED] Don't mail cd images.) Andries - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: Mount locks on bad ISO image?
On Thu, Mar 29, 2001 at 02:16:03PM -0500, Aaron Lunansky wrote: > I tried mounting a file as an ISO image (turns out it was corrupted) - after > running mount file.iso /cdrom -o loop > mount hung and did not respond.. I could not ^Z it into the background, or > kill, or kill -9 it... > > I'm certain that I have ISO and loopback support compiled into my kernel. > > Anyone know what might be going on? Answer 1: in 2.4.2 the loop device does not work (but things are better in the -ac patches). Answer 2: the kernel tends to believe filesystem data, and a corrupted filesystem can seriously confuse the kernel. If you make sure that the problem does not lie in loop (you can mount other images without problems), then I wouldnt mind seeing your image (or rather, the first MB or two of it) to see whether the isofs code must be improved. (In that case, put some smallish fragment up for ftp and mail the URL to [EMAIL PROTECTED] Don't mail cd images.) Andries - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Mount locks on bad ISO image?
I tried mounting a file as an ISO image (turns out it was corrupted) - after running mount file.iso /cdrom -o loop mount hung and did not respond.. I could not ^Z it into the background, or kill, or kill -9 it... I'm certain that I have ISO and loopback support compiled into my kernel. Anyone know what might be going on? Regards, Aaron - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/