![]() | |||||||||||
Messages in this thread |
>All warnings boil down to a single cause: when these file systems are >mounted -o sync or dirsync, dirty blocks are still written out >asynchronously. It appears to me that these mount options don't have any >effect on these file systems. Is this the intended behavior? At least my HDD LED flashes regularly when I add -o sync... (Using `mount / -o remount,sync`) It may happen that FISC reads the disk before the write command even finished. With all the HD head movement optimization in the kernel (block layer, boiling down to TCQ/NCQ), this sounds possible. Jan Engelhardt -- - 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-03-22 14:10 [from the cache] ©2003-2008 | |||||||||||