Messages in this thread | | | Subject | Quota lockups | Date | Mon, 12 Oct 1998 09:46:51 -0500 | From | Jonathan Corbet <> |
| |
> I did quite a bit of stress testing for the quota code and wasn't able to > trigger any stuck processes. Could you put together a script to reproduce the > problem?
I posted some time ago the sure way to lock up the quota code: have an empty 'quota.user' file. Then do something that causes somebody to allocate space on the device. The file system gets locked once to make the quota change, then again because the first block of the quota file needs to be allocated, which requires another quota modification. *Lock*.
Running "quotacheck" before enabling quotas fixes the problem; unfortunately Red Hat's startup script does it wrong (with the fs unmounted) so the new quota.user gets written in the wrong place.
The most straightforward fix would be to force the existence of the first block of the quota file before allowing quotas to be turned on. But this has the look of the sort of band-aid fix that Linus doesn't like, for good reason...
jon
Jonathan Corbet, Eklektix, Inc. corbet@eklektix.com
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu Please read the FAQ at http://www.tux.org/lkml/
| |