Alexander Beregalov <a.beregalov@gmail.com> writes:
BTW what sha1 of the git-commit you have used to reproduce
the bug (2.6.33-rc1 HEAD has no this BUG_ON).
This is important to me to know it, or just post the
fs/ext4/inode.c file.
Again strange, please run fsck. What about compile it from very
beginning (start from unpacking tar-ball from kernel.org)
Or may be compile it on another file-system(ext3 or
ext4 with nodelalloc option)
It is sad, but i still can not reproduce your bug.
At this time i've tested following configurations:
system : 2.6.33-rc2, x86 two cores cpu with 2GB of ram
block dev: real sata drive, loopdev over tmpfs
mkfs : 4k and 1k blocksize
mount : w/o quota, quota, journaled quota
quota : both ON and OFF states
fs-load : - fsstress with 1,4,16,32 concurrent tasks
- kernel compilation -j4, -j32
- In fact currently my mail-dir is under quota control.
Please clarify your use-case:
0) Your system speciffication: cpu_num, mem_size, page_size(i guess 8k)
block device.
1) mkfs options
2) mount options
3) quota options (if any)
4) your fs load test-case
5) How long does it takes you to reproduce the bug.
--
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html