Dmitry Monakhov wrote: > Eric Sandeen <sandeen@xxxxxxxxxx> writes: > >> Because we can badly over-reserve metadata when we >> calculate worst-case, it complicates things for quota, since >> we must reserve and then claim later, retry on EDQUOT, etc. >> Quota is also a generally smaller pool than fs free blocks, >> so this over-reservation hurts more, and more often. >> >> I'm of the opinion that it's not the worst thing to allow >> metadata to push a user slightly over quota. This simplifies >> the code and avoids the false quota rejections that result >> from worst-case speculation. > Hm.. Totally agree with issue description. And seem there is no another > solution except yours. > ASAIU alloc_nofail is called from places where it is impossible to fail > an allocation even if something goes wrong. > I ask because currently i'm working on EIO handling in alloc/free calls. > I've found that it is useless to fail claim/free procedures because > caller is unable to handle it properly. > It is impossible to fail following operation > ->writepage > ->dquot_claim_space (what to do if EIO happens?) Hm, if these start returning EIO then maybe my patch should be modified to treat EDQUOT differently than EIO ... assuming callers can handle the return at all. In other words, make NOFAIL really just mean "don't fail for EDQUOT" -Eric -- 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
