Andrew Morton <[email protected]> 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 <[email protected]>
-
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/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
