On Thu, Aug 13, 2015 at 10:23:07AM +0200, Olaf Hering wrote: > > I just got the output below in syslog with a full filesystem. > Should I be worried about inconsistent filesystem now, or is that just an > overly verbose message about ENOSPC? This is a 4.1.5 kernel. You don't need to worry about an inconsistent file system, but it's an error that isn't supposed to to happen. The warning message indicates that writes issued got a success return code, but for which ran out of space, and so some number of pages got lost and couldn't be saved to disk. We keep track of how many data blocks have been committed, and we have a reserved amount of space for metadata blocks which _should_ be enough. For more details, see: http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=27dd43854227bb0e6ab70129bd21b60d396db2e7 I'm curious about your workload. How big is your file system, and how fragmented is your file system per e2freefrag? And how quickly was various programs writing to the file system at the time when you ran out of space, and what sort of files and what was the average size that was getting dumped into the file system? Oh, and how much memory did you have in your system? Thanks, - Ted -- To unsubscribe from this list: send the line "unsubscribe linux-ext4" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
