xfs-masters
[Top] [All Lists]

[xfs-masters] [Bug 422] quota - incorrect space/inode usage reported

To: xfs-master@xxxxxxxxxxx
Subject: [xfs-masters] [Bug 422] quota - incorrect space/inode usage reported
From: bugzilla-daemon@xxxxxxxxxxx
Date: Tue, 13 Dec 2005 04:50:23 -0800
Reply-to: xfs-masters@xxxxxxxxxxx
Sender: xfs-masters-bounce@xxxxxxxxxxx
http://oss.sgi.com/bugzilla/show_bug.cgi?id=422


lehel@xxxxxxxxxxxxxxx changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
           Severity|major                       |critical
           Priority|P2                          |P1




------- Additional Comments From lehel@xxxxxxxxxxxxxxx  2005-12-13 04:50 CST 
-------
Well since my original report I had to get rid of the erroneous xfs filesystem, 
and I've stopped dealing with this bug.
But, to enlighten some things, this doesn't seem to be a bug (only) in the 
quota 
subsystem!

$ stat pkgcache.bin
  File: `pkgcache.bin'
  Size: 0               Blocks: 4288675848 IO Block: 4096   regular empty file
Device: 902h/2306d      Inode: 117456128   Links: 1
Access: (0644/-rw-r--r--)  Uid: (    0/    root)   Gid: (    0/    root)
Access: 2005-10-10 21:39:36.464254049 +0200
Modify: 2005-10-10 21:39:36.464254049 +0200
Change: 2005-10-10 21:39:36.464254049 +0200

This is an empty file, with a huge block count. No matter if I delete & 
recreate 
it, if the new file gets the old one's inode, it gets back this block count.
I had to create a file with a different name while the old one was there, to 
make sure it gets a new inode, and then rename it over the old one. Of course 
this was a temporary fix only, because files with wrong block counts kept 
popping up all the time. 
Now I cannot check anymore if there were users with wrong quotas who didn't own 
any files/dirs - but if there weren't, this might be the cause of all the quota 
problems.


-- 
Configure bugmail: http://oss.sgi.com/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.


<Prev in Thread] Current Thread [Next in Thread>