On Thu, Apr 28, 2005 at 09:59:39AM -0500, Davy Durham wrote:Well, I don't have the output of the fsck when I did the machine I did it on. And I can't do it on the production machine right now. Perhaps I can tommorrow if I can talk to the guys about cleaning it off. I'm a bit afraid to do it, reason being that if it's off on this accounting information, what files/data might I lose if I did an fsck on it (remember, the one I already did it on was empty).
Crazy huh? Well, I unmounted /home and did an fsck -f on the partition and remounted it. Then everything looked okay.
What messages were displayed by e2fsck? What version of the kernel
are you running?
No, I haven't heard of any such problems with ext2/3 filesystems.
This is the first time that someone was reported a specific problem
with the # of blocks used accounting. There is the standard "file
held open so the number of blocks used is greater than blocks reported
by du", but that won't cause df to display negative numbers.
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/