All of lore.kernel.org
 help / color / mirror / Atom feed
From: Wichert Akkerman <wichert@wiggy.net>
To: Andries Brouwer <aebr@win.tue.nl>
Cc: linux-kernel@vger.kernel.org
Subject: Re: negative diskspace usage
Date: Sun, 23 Jan 2005 23:56:28 +0100	[thread overview]
Message-ID: <20050123225628.GA27675@wiggy.net> (raw)
In-Reply-To: <20050122212328.GC11170@pclin040.win.tue.nl>

Previously Andries Brouwer wrote:
> I assume this was produced by statfs or statfs64 or so.

statfs64 indeed.

> Are you still able to examine the situation?

No, but I do have some more information. A e2fsck run on that filesystem
was just as interesting:

/dev/md4: clean, 16/132480 files, -15514/264960 blocks

Forcing an e2fsck revelated a few groups with incorrect block counts:

Free blocks count wrong for group #2 (34308, counted=32306).
Free blocks count wrong for group #6 (45805, counted=32306).
Free blocks count wrong for group #8 (14741, counted=2354).
Free blocks count wrong (280474, counted=252586).

After fixing those everything returned to normal. I did run dumpe2fs
on the filesystem, if that is interesting I can retrieve and post that.

Wichert.

-- 
Wichert Akkerman <wichert@wiggy.net>    It is simple to make things.
http://www.wiggy.net/                   It is hard to make things simple.

  reply	other threads:[~2005-01-23 22:56 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-01-21 14:11 negative diskspace usage Wichert Akkerman
2005-01-22 21:23 ` Andries Brouwer
2005-01-23 22:56   ` Wichert Akkerman [this message]
2005-01-23 23:26     ` Andries Brouwer
2005-01-24  9:07       ` Wichert Akkerman
  -- strict thread matches above, loose matches on Subject: below --
2005-01-22  8:37 ndiamond
2005-01-22 10:09 ` Wichert Akkerman
2005-01-22 20:41   ` Norbert van Nobelen
2005-05-03 11:31 Dave Gilbert (Home)

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20050123225628.GA27675@wiggy.net \
    --to=wichert@wiggy.net \
    --cc=aebr@win.tue.nl \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.