Messages in this thread |  | | | Date | Fri, 15 Mar 2002 18:23:56 -0500 | | From | Theodore Tso <> | | Subject | Re: mke2fs (and mkreiserfs) core dumps |
| |
On Wed, Mar 13, 2002 at 02:54:20PM -0700, Andreas Dilger wrote: > > If you don't have any "ulimit" calls in the login, it should also be OK. > It's just that some vendor startup scripts set a ulimit for non-root > users. Trying to set it back to "unlimited" doesn't work. >
Also check your PAM configuration files, since pam_limits can also be causing the problem. (Namely, any attempt to set the filesize to be "unlimited" cause it to be capped at 2GB.) There's also the question whether or not filesize limits should really apply to device files, since the original point of filesize limits were as a simple-minded quota control mechanism, and there seems to be little point to causing attempts to access block deivces to fail --- under what circumstances would this *ever* be considered a useful thing?
Anyway, as of e2fsprogs 1.27, since I got tired of handling user questions about this, e2fsprogs will attempt to unlimit filesize unconditionally, if it has the superuser privileges to do so. Because of the fact that in effect, the kernel ABI changed between 2.2 and 2.4 (the value of "Unlimited" change), in e2fsprogs I had to hard-code the value of unlimited, so that it would do the right thing regardless of which header files were used to compile e2fsprogs. (Oh, joy, oh rapture.)
- Ted
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
|  |