![]() | ||||||||||
Messages in this thread |
Andrew Morton <akpm@osdl.org> writes: > If filemap_fdatawrite() returns an error, this might be due to some I/O > problem: dead disk, unplugged cable, etc. Given the generally crappy > quality of the kernel's handling of such exceptions, there's a good chance > that the filemap_fdatawait() will get stuck in D state forever. > > I don't know how useful that really is - probably not very. Plus, yes, we > should wait on writeout after a -ENOSPC. > > So hum, not sure. My gut feeling is that anything which we can do to help > the kernel limp along after an I/O error is a good thing, hence the > don't-wait-after-EIO feature should remain. I see, thanks for explaining it. Please don't apply patch, I need to consider it obviously. -- OGAWA Hirofumi <hirofumi@mail.parknet.co.jp> - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/ | |||||||||
| Last update: 2005-10-24 01:59 [from the cache] ©2003-2008 | ||||||||||