All of lore.kernel.org
 help / color / mirror / Atom feed
From: "news.gmane.org" <francois.valenduc@tvcablenet.be>
To: Theodore Tso <tytso@mit.edu>
Cc: linux-ext4@vger.kernel.org
Subject: Re: Wrong calculation of space remaining on a 32 bit system.
Date: Sun, 02 Nov 2008 22:46:25 +0100	[thread overview]
Message-ID: <490E1FB1.8020100@tvcablenet.be> (raw)
In-Reply-To: <20081102204352.GJ8134@mit.edu>

Theodore Tso a écrit :
> On Sun, Nov 02, 2008 at 03:40:25PM +0100, François Valenduc wrote:
>> I have already filed a bug report (see
>> http://bugzilla.kernel.org/show_bug.cgi?id=11840) but unfortunately,
>> nobody seems to care about it.
> 
> Hi,
> 
> 	Sorry no one responded, but while the Bugzilla system is great
> for tracking bugs, it's not a good place to call attention to a bug.
> In fact, I'm not sure that fs_ext4@kernel-bugs.osdl.org forwards
> anywhere sane (I'm checking up on that, though).  In general it's a
> good idea by sending e-mail to either linux-kernel@vger.kernel.org or
> (preferred) linux-ext4@vger.kernel.org.
> 
> 	From your description, the ext4 filesystem thought there was
> some kind of on-disk corruption or other problem with your filesystem,
> and remounted it read-only.  That's consistent with your report of the
> messages in the syslog of:
> 
> ext4_da_writepages: jbd2_start: 1024 pages, ino 40898; err -30
> 
> There should have been something in your logs *before* all of the err
> -30 complaints, however.  Was this your root filesystem, or do you
> have this saved in logfile in /var/log?  If so, can you search back
> for something that occurs before all of the ext4_da_writepages error
> messages?
> 
> 							- Ted

Thanks for your reply.
In fact, the errors I mentionned don't occur anymore. But the problem of
  the diskspace remains. I never managed until now to use more than one
third of a partition on a 32 bit system. After that, I always get a
message saying that the partition is full, which can't be true.

François
--
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

  reply	other threads:[~2008-11-02 21:46 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-02 14:40 Wrong calculation of space remaining on a 32 bit system François Valenduc
2008-11-02 20:43 ` Theodore Tso
2008-11-02 21:46   ` news.gmane.org [this message]
2008-11-02 21:54     ` Graham Murray
2008-11-02 22:24       ` François Valenduc
2008-11-02 23:01         ` Theodore Tso
2008-11-03 18:28           ` François Valenduc
2008-11-03 20:24             ` Theodore Tso
2008-11-03 21:23               ` François Valenduc
2008-11-03 21:46                 ` Theodore Tso

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=490E1FB1.8020100@tvcablenet.be \
    --to=francois.valenduc@tvcablenet.be \
    --cc=linux-ext4@vger.kernel.org \
    --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 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.