From: Ted Ts'o <tytso@mit.edu>
To: Eric Sandeen <sandeen@redhat.com>
Cc: ext4 development <linux-ext4@vger.kernel.org>
Subject: Re: Bigalloc ENOSPC woes
Date: Mon, 30 Jan 2012 17:31:11 -0500 [thread overview]
Message-ID: <20120130223111.GA20940@thunk.org> (raw)
In-Reply-To: <4F270949.30800@redhat.com>
On Mon, Jan 30, 2012 at 03:19:05PM -0600, Eric Sandeen wrote:
> I got nervous when I tried this on an -O bigalloc -C 65536 fs:
>
> # echo foo > blah; du -hc blah; sync; du -hc blah
> 4.0K blah
> 4.0K total
> 64K blah
> 64K total
>
> Seems that du should never report less than the cluster size, should it?
Yes, that seems like a bug.
> And that made me wonder about ENOSPC handling - are we tracing
> delalloc allocations correctly?
>
> From running xfstest 204 on a similarly-created fs, it really seems
> that we are not....
>
> Ted, are you aware of those issues in bigalloc?
No, this is news to me. I'll have to take a closer look at this;
thanks for bring this up.
- Ted
next prev parent reply other threads:[~2012-01-30 22:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-30 21:19 Bigalloc ENOSPC woes Eric Sandeen
2012-01-30 22:31 ` Ted Ts'o [this message]
2012-01-31 16:03 ` Tao Ma
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=20120130223111.GA20940@thunk.org \
--to=tytso@mit.edu \
--cc=linux-ext4@vger.kernel.org \
--cc=sandeen@redhat.com \
/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.