From: lsorense@csclub.uwaterloo.ca (Lennart Sorensen)
To: "Theodore Ts'o" <tytso@mit.edu>,
Davy Durham <pubaddr2@davyandbeth.com>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: ext3 issue..
Date: Thu, 28 Apr 2005 16:55:36 -0400 [thread overview]
Message-ID: <20050428205536.GA2297@csclub.uwaterloo.ca> (raw)
In-Reply-To: <20050428200908.GB6669@thunk.org>
On Thu, Apr 28, 2005 at 04:09:08PM -0400, Theodore Ts'o wrote:
> 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.
I think I have seen this once or twice in the past. A reboot always
made it go away and it didn't seem to come back. fsck never showed
anything so I assumed it was just the kernel having lost its mind about
the state of the FS.
I think I was using 2.4.18 or so at the time I last saw it. It is quite
a while ago but it was ext3 as well as far as I recall.
I originally thought my df and company was messed up (since I think I
have seen a case on sparc where the libc/df were out of sync causing
weird output).
I never thought much about it since it didn't seem to be reproduceable
since it never repeated itself.
Len Sorensen
next prev parent reply other threads:[~2005-04-28 20:55 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-28 14:59 Davy Durham
2005-04-28 20:09 ` Theodore Ts'o
2005-04-28 20:55 ` Lennart Sorensen [this message]
2005-04-29 11:55 ` folkert
2005-05-03 20:38 ` Theodore Ts'o
2005-04-29 2:35 ` Davy Durham
2005-04-29 13:19 ` Lennart Sorensen
2005-05-02 1:27 ` Davy Durham
2005-05-03 12:38 ` Davy Durham
2005-05-03 12:53 ` Christopher Chan
2005-05-03 22:17 ` Darren Williams
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=20050428205536.GA2297@csclub.uwaterloo.ca \
--to=lsorense@csclub.uwaterloo.ca \
--cc=linux-kernel@vger.kernel.org \
--cc=pubaddr2@davyandbeth.com \
--cc=tytso@mit.edu \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®