https://bugzilla.kernel.org/show_bug.cgi?id=15768 Summary: Incorrectly calculated free blocks result in ENOSPC from writepage Product: File System Version: 2.5 Platform: All OS/Version: Linux Tree: Mainline Status: NEW Severity: high Priority: P1 Component: ext4 AssignedTo: fs_ext4@xxxxxxxxxxxxxxxxxxxx ReportedBy: dmonakhov@xxxxxxxxxx CC: tytso@xxxxxxx Regression: No Created an attachment (id=25965) --> (https://bugzilla.kernel.org/attachment.cgi?id=25965) testcase No mount per-sb counters (freeblocks/freeinodes/dir and etc) are initialized before journal was replayed. But in fact if journal wasn't empty statistics will be probably changed after journal replay. This result in per-sb counter inconsistency which result in incorrect delalloc reservation. See testcase. This is long standing bug at least from 2.6.12 where the linus's tree starts i (was too lazy to dig in to old-git tree). But it case of ext3 this result only in incorrect numbers from statfs() The fix is simple, we just have to move counter initialisation after journal_reply. I've open this bug only as testcase storage. -- Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are watching the assignee of the bug. -- 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
