On Thu, Jul 03, 2003 at 04:40:34PM +0200, Lars Braeuer wrote:
hi herbert,
Herbert Poetzl wrote:
Well, at first I setup standard quota stuff in my hostsystem (no vserver context quota), just to see how everything works etc. I'm able to set user quota's with edquota. The user quota's are saved. Example:
- edquota -u quota_user
- setting block soft limit 100000 and hard limit 200000
- exiting edquota
- editing the same user again with "edquota -u quota_user"
- the soft and hard limits I set are still present
Now I'm trying the same thing (still in the hostsystem) after applying all the necessary patches:
kernel: patch-2.4.21ctx17, linux-2.4.21-ctx17-vquota-0.10.diff
quota-tools: quota-tools-3.08-ctx17-v0.35.diff
vserver-0.22: vserver-0.22-cap_quotactl.diff
okay, here is the checklist:
- kernel rebuilt and installed and booted? (check with cat /proc/version)
yes, Linux version 2.4.21ctx-17quota
- quota files removed/rebuilt? ( rm, quotacheck -vaugxm )
yes.
- quota turned on? ( quotaon -vaugx )
yes.
my best guess would be, that quota wasn't activated
if this remains true, after you positively checked the list above, please send me a transcript of your
actions accompanied by results of
* download of patches * cd /usr/src/linux-2.4.21 * patch -p1 <../patch-2.4.21ctx-17 * patch -p1 <../linux-2.4.21-ctx17-vquota-0.10.diff * cd ../ * download quota-tools * cd quota-tools * patch -p1 <../quota-tools-3.08-ctx17-v0.35.diff * cd ../ * download vserver-0.22 * cd vserver-0.22 * patch -p1 <../vserver-0.22-cap_quotactl.diff * active "Block Devices > Virtual Root Device Support" in kernel conf * install kernel image * reboot
what about
- building the kernel?
- building the quota tools?
- installing the quota tools?
I simply assume you did ...
yes. sorry for not mentioning it.
cat /proc/version
Linux version 2.4.21ctx-17quota ([EMAIL PROTECTED]) (gcc version 2.95.4 20011002 (Debian prerelease)) #1 Thu Jul 3 14:54:40 CEST 2003
cat /proc/mounts
rootfs / rootfs rw 0 0 /dev/root / ext2 rw 0 0 proc /proc proc rw 0 0 devpts /dev/pts devpts rw 0 0 /dev/hda1 /boot ext2 rw 0 0 /dev/hda5 /usr ext2 rw 0 0 /dev/hdb1 /windows/C vfat rw,nosuid,nodev,noexec 0 0 /dev/hdb5 /windows/D vfat rw,nosuid,nodev,noexec 0 0 /dev/hda6 /windows/E vfat rw,nosuid,nodev,noexec 0 0
hmm, you are sure, you're not pulling my leg?
accroding to your /proc/mounts /dev/hda2 is either your root filesystem (with quota disabled) or not mounted at all ...
well. it's mounted and usrquota is turned on. here's my /etc/mtab
/dev/hda2 / ext2 rw,usrquota,errors=remount-ro 0 0 proc /proc proc rw 0 0 devpts /dev/pts devpts rw,gid=5,mode=620 0 0 /dev/hda1 /boot ext2 rw 0 0 /dev/hda5 /usr ext2 rw 0 0 /dev/hdb1 /windows/C vfat rw,noexec,nosuid,nodev,uid=1000,gid=1000,umask=0002 0 0 /dev/hdb5 /windows/D vfat rw,noexec,nosuid,nodev,uid=1000,gid=1000,umask=0002 0 0 /dev/hda6 /windows/E vfat rw,noexec,nosuid,nodev,uid=1000,gid=1000,umask=0002 0 0
on a different system I installed the 2.4.20ctx-17 kernel + quota/vquota patches and basic quota in the hostsystem seems to work fine. I think I'll just stick with this for the moment.
maybe it's something about the kernel version.
