jehan procaccia wrote:
...
[root@gizeh ~]
$ getent passwd |grep 42658
karipha:x:42658:426:Karipha
BOUMER:/mci/mast2008/karipha:/usr/local/bin/bash
[root@gizeh ~]
$ quota -s karipha
Disk quotas for user karipha (uid 42658):
Filesystem blocks quota limit grace files quota limit
grace
/dev/mapper/VolGroup02S2IA-LVVG02Users07
603M* 489M 538M 39:07 6622 50000 55000
$ find /disk07 -inum 3542694
/disk07/mast2008/karipha/.recently-used.xbel
Other inodes incriminated showed the same result -> over-quota . So if
user data finally cannot be written, after all ... quota wouldn't allow
it anyway .
The unfortunate thing in your situation though is that the user
-thought- it did get written, just FYI.
When quota is working properly, the denial is obvious up front.
-Eric
Hope this helps you understand what's going on.
- Ted
Yes, thanks for that detailed answer.
regards , jehan .
--
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
