Bug 6002
Summary: | quota + 2.6.15.1 | ||
---|---|---|---|
Product: | File System | Reporter: | Nerijus Kislauskas (nerijus.kislauskas) |
Component: | Other | Assignee: | Jan Kara (jack) |
Status: | CLOSED CODE_FIX | ||
Severity: | high | CC: | akpm |
Priority: | P2 | ||
Hardware: | i386 | ||
OS: | Linux | ||
Kernel Version: | Linux version 2.6.15.1 | Subsystem: | |
Regression: | --- | Bisected commit-id: | |
Attachments: | Patch fixing BUG in invalidate_dquots() |
Description
Nerijus Kislauskas
2006-02-03 03:27:25 UTC
Hmm, that's strange. It looks as if someone still uses quota while invalidate_dquots() is running. What were you running to test the quota? Was something running while you did quotaoff? It was strange to us that when quotacheck finished job, it couldn't rename quota.user.new to quota.user. Output was something like that: bedugnis:~# quotacheck -a quotacheck: Cannot rename new quotafile /disks/disk1/quota.user.new to name /disks/disk1/quota.user: Operation not permited Also the same with quota.group. If quotas is turned off, then it is ok, and quotacheck could easily rename needed files (both user and quota). Segmentation fault come right after "quotaoff -g /disks/disk1" command. We share this partition over NFS (nfsd) to other 2 systems, so disk activity is high. I've tested this situation on my desktop (Debian unstable and it's 2.6.15.1 precompiled kernel). Testings were passed (quotacheck renamed quota.user and quota.group easily, but 1 user was there). Our system has aproximately 25000 - 30000 mail users, and we had to go back to 2.4.31 kernel. Does these numbers could be a reason for file accessing and renaming problems? (a lot of mail is delivered to this mashine). Also we need to check for quotas very often. OK, I think I've found the problem (at least after applying the patch I was not able to reproduce the problem any longer). I'll post here a patch in a while - could you please test it also in your environment? Created attachment 7380 [details]
Patch fixing BUG in invalidate_dquots()
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I'm sorry, but I'm unable to test your patch. This server now is a production server, others too. I will stay on a 2.4 kernel (if it would be necessary to move to 2.6) , so there is no environment to test it now. Anyway, thanks for patch. I'm glad to help you. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFD+ZZWVaDswePJAMURAmW5AJ420UpGld9Iu18k1ZdsRPY0vkToDgCeM6tC CB04Xd8yh7NeVDD8e2A+gKk= =xrXM -----END PGP SIGNATURE----- OK, I've submitted patch for inclusion in kernel. |