similar to: quota problems with ext3/249-ac9

I've updated today the version of ext3 on my laptop (from 0.9.3 to 0.9.4) and I am unable to boot anymore (hand copy below): VFS: Diskquotas version dquot_6.5.0 initialized Journalling Block Device driver loaded Invalid operand: 0000 CPU: 0 EIP: 0010:[<c01256bf>] ... ... ... Kernel panic: attempted to kill init. Since this is my / fs, I am unable to boot anymore (and of course

I am writing a package, which contains several functions and variables. The variables are for internal use by functions. Functions are ment to be callable by a user. However, the function cannot access these variables. The package contains only R code, and was created using package.skeleton package.skeleton(name="ac9", list=c(ls(pattern="(AB2)|(ac9)"),

On 23/09/2019 15:18, Marco Gaiarin via samba wrote: > Mandi! Rowland penny via samba > In chel di` si favelave... > >> I repeat (louder this time): NO ONE NEEDS THE 'WINBIND ENUM' LINES IN >> SMB.CONF > While it is true that i can live happily without 'winbind enum', it is > not completely true that 'no one needs' that. > > For example,

I am writing a package. Please, study the sequence of my actions below, and comment, what's incorrect. The package contains pure R code. 1. At the one level up from the package directory, from the system command prompt: R CMD build --binary ac9 This produces the file ac9_0.1.zip (The package name is ac9, and the package's DESCRIPTION file says its version is 0.1) 2. Then I run Rgui in

Patches against 2.4.10-pre4 and 2.4.9-ac9 are at http://www.uow.edu.au/~andrewm/linux/ext3/ It's a fairly large change. The most significant parts are * the inclusion of Stephen's error-handling work, which is designed to remount the fs read-only in the presence of software and hardware errors, rather than forcing a panic. * Stephen's fix for the journal_revoke assertion

Hi, I have exactly the same problem that you experienced in Nov, 2013. I am using ext4 with journaled quota and the quota usage is only updating when I run quotacheck manually. Have you found a solution? Regards, Alex > I have set up user quotas on an ext4 filesystem. It does not appear that > the quota system is being updated, except when I manually run quotacheck. > > More detail:

Has anyone had any success with the interactivity.patch on the ext3 website? I'm going to try to use it because I've had a lot of lockups in past day under heavy load with 2.4.9-ac9, and I can't figure out if it's because of ext3 or VM or my crappy VIA IDE controller.

Hi. I recently migrated two machines from ext2 to ext3. Kernels (nearly identical) are 2.4.9-ac9 + preemptivity-patch + wrr-patch. The Installations are based on Mandrake 7.2 + 8.0. Also I have e2fstools-1.23 newly compiled on them. Both machines have two ext3 partitions (root + multimedia-data). On one machine I see a .journal file on both partitions, on the other machine (Mandrake-8.0)

Hi all, Being new on this list I do not really know if this is the correct list to post. After searching the archives I am pretty sure the answer is not yet here (or I can't search, which can be true) My problem is as follows We are currently testing a Linux/Samba server to host the home shares for about 1000 students at our school (the test is conducted with just 10 of them). With ca

I have set up user quotas on an ext4 filesystem. It does not appear that the quota system is being updated, except when I manually run quotacheck. More detail: I run "warnquota -s" from a script in /etc/cron.daily. I noticed that no one had received an "over quota" message in a long time. Using "repquota -as", it indeed looked as though everyone was under their

Hi... I have a Dell Latitute with an ATA/ATAPI-5 T13 1321D and it would seem that my disk access is extremely slow. I have the latest updated kernel from RedHat 8.0 kernel 2.4.18-27.8.0. Somehow I think it is related to the UDMA stuff (shows my level of understanding). I have run hdparm and although I think I should at least udma level 5, I have at most udma2 listed. Is this a kernel

Hello, I am having some trouble getting quota's to work. When I try to set the quota for a user, it does not show up when I run repquota. I am doing this on a Redhat (RHEL5) machine (I assume it is the same on Centos). I think I am missing a step, but this is what I am doing: (1) I add usrquota to the /etc/fstab file, then reboot LABEL=/home /home ext3 defaults,usrquota 1 2 (2) Verify

Hi all, I am working with a pc cluster, running redhat el 4, on opteron cpus. we have several bigger RAID systems locally attached to the fileservers; now I would like to create a big striped filesystem with around 15TB. ext3 unfortunatelly only supports filesystem size up to 8TB, do you have an idea if / when this border will be increased ? I already found some discussions on LKML about it ?

On 23/09/2019 13:42, Trenta sis via samba wrote: > Thanks, ntlm auth is temporary until we have solved some issues > getent is needed by filesystem acl > If you think you need the 'winbind enum' lines so that 'getent' works, then think again ;-) If you do not have the 'winbind enum 'lines 'getent passwd username' will still work. 'getent passwd'

---------- Forwarded Message ---------- Subject: ext3 for 2.4 Date: Thu, 17 May 2001 21:20:38 +1000 From: Andrew Morton <andrewm@uow.edu.au> To: ext2-devel@lists.sourceforge.net, "Peter J. Braam" <braam@mountainviewdata.com>, Andreas Dilger <adilger@turbolinux.com>, "Stephen C. Tweedie" <sct@redhat.com> Cc: linux-fsdevel@vger.kernel.org Summary:

Hi, I have an existing (Open)LDAP which I'm using with dovecot and I would like to implement quotas. I have global quotas working, but I would like per user quotas similar to what is described in the wiki (http://wiki2.dovecot.org/Quota/Configuration#LDAP) My problem is that there is no obvious attribute in the schemas shipped in the RHEL/Centos 6 to hold the quota string. Is it possible to

Looks working. [root at mail ~]# ls -lh / total 72K -rw------- 1 root root 8.0K Mar 13 09:56 aquota.group -rw------- 1 root root 7.0K Mar 13 09:56 aquota.user .... [root at mail ~]# repquota -a *** Report for user quotas on device /dev/vda1 Block grace time: 7days; Inode grace time: 7days Block limits File limits User used soft hard

For the future search: > Anyway, i've lost some time for: > https://sourceforge.net/p/linuxquota/bugs/135/ Author reply, problem fixed in 4.04 (that debian buster have); specifically, author say: Well, there's a better solution for this. If you have quota-tools >= 4.04 and if you run at least on kernel 4.6, there is support for Q_GETNEXTQUOTA quotactl and thus quota

happens. It also appears that somewhere in steps 1 and 2 above Word sends a request to turn off the read,write,and execute bits for the owner of the file. When you look at this filesystem after the attempted save the original file does indeed have these bits cleared (i.e. the user has no read,write,or execute permissions on the file), and that I think is why the error is being generated.

Hi all, is any one aware quotas not working in 5,5? I'm using XFS as a file system. My fstab has the appropriate usrquota,grpquota but when I try to run; quotacheck -cug /foo I get; quotacheck: Can't find filesystem to check or filesystem not mounted with quota option. I already have a large amount of data in the mount. Do quotas get implemented on only empty filesystems and