login
Search
I'm currently running open-iscsi on version 2.6.16-0 of the kernel. I've been using iSCSI to store and record video. I've been having problems with umounting an iSCSI drive after error recovery. If I disconnect the connection to my iSCSI device and let the connection timeout and remount the drive as read only I'm not able to recover the mount. As soon as I try to unmount the drive my system freezes up. I've tried all kinds of umount flags and a remount but all of these just end up blocking.
So I upgraded my kernel to 2.6.18-53 to see if this same behavior was reproducible luckily I didn't see the problem anymore. But now I'm wondering what changed between 2.6.16-0 and 2.6.18-53 to remedy this problem? I was wondering if any of you have any idea what might have changed from 16 to 18? I've looked through the change logs but I don't know the inner workings of umount all that well and what would impact this problem. I'd appreciate any help.
a changelog
http://kernelnewbies.org/Linux26Changes has human readable changelogs. but 2.6.18-53 doesn't look like a kernel.org version number so you should consult your distributor. do you have a reason preferring a very old kernel over a just old one? if the 2.6.18-53 fixes your problem, you could just run that and not worry about historic errors. and why do you want to run a -0-kernel? if your distributor applies patches, you should at least take advantage of that.
one of the things unmounting has to do is to wait until there are no more references to the file system data, and to delete said data. maybe the error handler forgot to decrement some refcounts or some data got corrupted by the error or not repaired by the handler and traversing the pointers or freeing the data uncovers this by crashing? have you tried remote console to catch the oops?
Forgot about Red Hat..
Yeah it totally slipped my mind that this was a redhat distro and that they probably patched this kernel. I really can't move to 2.6.18 either. Its too many changes and causes too many problems. It'd be preferable to patch. But I guess I need to sift through the change logs and try stuff out.