Greetings all, I apologize if my question should not have been posted to this list. I am working with code that issues vfs_writev() to a fd, which was opened using filp_open(). The pathname, which has been opened, is a DeviceMapper devnode (like /dev/dm-1), which is a linear DeviceMapper mapped to a local drive. At some point, I switch the DeviceMapper to "error" table (using "dmsetup reload" and then "dmsetup resume"). As expected, vfs_writev() starts returning -EIO. Then later, I switch the DeviceMapper back to "linear" table mapped to the same local drive. However, the vfs_writev() still returns -EIO several times, before it starts completing successfully. If do a direct IO at this point to the DM device (like dd if=/dev/urandom of=/dev/dm-1 oflag=direct), I don't hit any IO errors. I also added some prints to dm-linear code, and verified that it does not return any IO errors at this point. So it seems that the VFS layer somehow "remembers" that previously there were IO errors from that device. I started digging in the kernel code to get some clue on this, but at this point I only saw functions like make_bad_inode() and is_bad_inode(), which may be relevant somehow, but I was not able to trace where the -EIO is returned from. Can someone pls point me which code I should look at to debug this issue. I am running kernel 2.6.38-8 (stock ubuntu natty). Any clue is appreciated. Thanks, Alex. -- To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
