Messages in this thread | | | Date | Thu, 07 Apr 2005 12:00:30 +0900 | From | Hifumi Hisashi <> | Subject | Re: Linux 2.4.30-rc3 md/ext3 problems (ext3 gurus : please check) |
| |
Hi,
At 23:20 05/04/06, Stephen C. Tweedie wrote: >Yes. But it is conventional to interpret a short write as being a >failure. Returning less bytes than were requested in the write >indicates that the rest failed. It just doesn't give the exact nature >of the failure (EIO vs ENOSPC etc.) For regular files, a short write is >never permitted unless there are errors of some description.
When commit_write() FULLY succeed (requested bytes == returned bytes) but generic_osync_inode() return error due to I/O failure, current do_generic_file_write() cannot return error. I encountered above situation a lot under an I/O trouble condition .
In ver 2.6.11, the return value of generic_osync_inode() is returned directry to user when I/O failure occur.
thanks.
- 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/
| |