Jonathan Nieder wrote:
Thanks for the update, and no problem. What filesystem options does
your test system use (as shown in /proc/mounts or by dumpe2fs -h
<bdev>)? How do you set up quotas on it?
Both the test system (that doesn't show errors) and the live system
(that does) have identical mount options:
ext4 rw,noatime,errors=remount-ro,acl,barrier=1,data=ordered,usrquota
The initial quotas were enabled with "quotaon -a", then by setting a
100GB / 1 million file quota for each user on the system other than
root, using "setquota".
Don't know why I couldn't reproduce it. Perhaps something to do with the
live server's (heavy and varied) disk write patterns.
Looking closer, straightforward testing of that one patch would
probably not reveal much anyway --- any subtle effects wouldn't
necessarily be triggered often. Pointers that might help someone
review the code:
Hmmm. These changes to eliminate an erroneous -- but harmless -- warning
gives me the heebie-jeebies! In your shoes, I'd mark this as "won't fix"
and let it get fixed in the next real kernel version change....
--
Robert L Mathews, Tiger Technologies, http://www.tigertech.net/
--
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/4f4c024b.2090...@tigertech.com
