All of lore.kernel.org
 help / color / mirror / Atom feed
From: Eric Sandeen <sandeen@redhat.com>
To: George Kola <georgekola@gmail.com>
Cc: linux-ext4@vger.kernel.org
Subject: Re: ext4 fallocate+truncate not freeing up allocated space
Date: Sat, 30 Oct 2010 10:43:55 -0500	[thread overview]
Message-ID: <4CCC3D3B.30205@redhat.com> (raw)
In-Reply-To: <AANLkTinHFBoyB=N2RN6_NARU626VnDADpCVV+NXrW4t-@mail.gmail.com>

George Kola wrote:
> Hi Erik, 
>       Thanks for replying. How to get a hold of kernel  2.6.18-225.el5 ?

It (or a later kernel) will be available to RHEL subscribers when released,
and CentOS at some time after that, on their schedule.

>  I found 2.6.18-227 at http://people.redhat.com/jwilson/el5/227.el5/x86_64/
> I tried it and the bug is fixed is 2.6.18-227.   Thanks for your help.
> 
> This may be off-topic -- how do I find the changes from 2.6.18-194.17.4
> to 2.6.18-225 (or 2.6.18-227) ? I just want to know what other changes I
> am installing in addition to the bug fix.

The kernel RPM changelog has a general description of changes, usually
with reference to bug numbers.

-Eric

> 
> Thanks,
> George 
> 
> 
> On Fri, Oct 29, 2010 at 11:39 AM, Eric Sandeen <sandeen@redhat.com
> <mailto:sandeen@redhat.com>> wrote:
> 
>     George Kola wrote:
>     > I am using RHEL (CentOS) 5.5 with kernel  2.6.18-194.17.4.el5  and
>     ext4. I
>     > posted to RHEL bugzilla and they requested me to post it here.
>     >
> 
>     ...
> 
>     > Steps to Reproduce:
>     >   Have a program
>     > 1.  Open a file on ext4 partition
> 
>     # touch testfile
> 
>     > 2. Fallocate space for that file  say 20 GB
> 
>     # /root/fallocate -l 20g testfile
>     # df -h .
>     Filesystem            Size  Used Avail Use% Mounted on
>     /dev/sdb2              30G   21G  7.7G  73% /mnt/test
>     # du -h testfile
>     21G     testfile
> 
>     > 3. Write data to the file  (but less than the allocated space) say
>     10 GB
> 
>     # dd if=/dev/zero of=testfile bs=10M count=1024 conv=notrunc
>     10737418240 bytes (11 GB) copied, 125.522 seconds, 85.5 MB/s
>     # du -h testfile
>     21G     testfile
>     # df -h .
>     Filesystem            Size  Used Avail Use% Mounted on
>     /dev/sdb2              30G   21G  7.7G  73% /mnt/test
> 
>     > 4. Close the file
>     > 5. Call truncate(file-path, size+1), truncate(file-path,size) on
>     that file
>     > to
>     > give up the space (observed that the space is given up using filefrag)
> 
>     10g size I assume? Is the below representative?
> 
>     # /root/truncate 10737418241 testfile
>     # ls -l testfile
>     -rw-r--r-- 1 root root 10737418241 Oct 29 13:48 testfile
>     # /root/truncate 10737418240 testfile
>     # ls -l testfile
>     -rw-r--r-- 1 root root 10737418240 Oct 29 13:48 testfile
> 
>     > 6. Use du and df on that ext4 partition to find that the mismatch
> 
>     # df -h .
>     Filesystem            Size  Used Avail Use% Mounted on
>     /dev/sdb2              30G   11G   18G  37% /mnt/test
> 
>     # du -h testfile
>     11G     testfile
> 
>     # uname -a
>     Linux bear-05 2.6.18-225.el5 #1 SMP Mon Sep 27 10:32:19 EDT 2010
>     x86_64 x86_64 x86_64 GNU/Linux
> 
>     Seems to work here, though there are ext4 updates in that kernel.
> 
>     -Eric
> 
>     >
>     >
>     > -George
>     >
>     >
>     >
>     > --
>     > To unsubscribe from this list: send the line "unsubscribe
>     linux-ext4" in
>     > the body of a message to majordomo@vger.kernel.org
>     <mailto:majordomo@vger.kernel.org>
>     > More majordomo info at  http://vger.kernel.org/majordomo-info.html
> 
> 


  parent reply	other threads:[~2010-10-30 15:44 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-29 18:26 ext4 fallocate+truncate not freeing up allocated space George Kola
2010-10-29 18:39 ` Eric Sandeen
2010-10-30  1:26   ` George Kola
     [not found]   ` <AANLkTinHFBoyB=N2RN6_NARU626VnDADpCVV+NXrW4t-@mail.gmail.com>
2010-10-30 15:43     ` Eric Sandeen [this message]
2010-10-29 19:10 ` Curt Wohlgemuth

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=4CCC3D3B.30205@redhat.com \
    --to=sandeen@redhat.com \
    --cc=georgekola@gmail.com \
    --cc=linux-ext4@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.