* Report bug: space not released when file deleted.
@ 2011-05-23 5:42 Sid Moore
2011-05-23 11:30 ` Jeff Layton
0 siblings, 1 reply; 4+ messages in thread
From: Sid Moore @ 2011-05-23 5:42 UTC (permalink / raw)
To: linux-nfs
Hi,
On Linux NFS, I found a file deleted but its space not released in
NFSv3. It is on 2.6.32.
The steps for reproducing are listed below.
1) create a ext3 filesystem on a device, mount it to local dir
/exports/fs1_ext3/, export /exports/fs1_ext3/ with no_subtree_check to
a NFS client. this client mount this exported dir with infinite
retrans.
2) on the ext3 fs, create a large regular file (say: 600MB)
3) on NFS client, starts several processes who reading this file in 2)
in parallel
4) during step 3), kill all nfsd threads, umount this ext3 fs; then
mount this ext3 to /exports/fs1_ext3; start 8 nfsd threads.
5) after processes finished reading, delete this file. then, I found
the space occupied but this file not released.
during step 4), I think an anonymous dentry of this file was created
after fh_verify(). in step 5), a named dentry of this file also
created. So, there are two dentry on this inode. but when deleting,
only the named dentry deleted. only restart this ext3 fs or dcache
shrinked, the anonymous dentry will not be released and it referenced
the inode of this file. so its space not freed.
is my analysis correct? anyone has encountered this issue before? or,
this issue was fixed by someone? Thanks.
--
Sid
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: Report bug: space not released when file deleted.
2011-05-23 5:42 Report bug: space not released when file deleted Sid Moore
@ 2011-05-23 11:30 ` Jeff Layton
2011-05-23 14:02 ` J. Bruce Fields
0 siblings, 1 reply; 4+ messages in thread
From: Jeff Layton @ 2011-05-23 11:30 UTC (permalink / raw)
To: Sid Moore; +Cc: linux-nfs
On Mon, 23 May 2011 13:42:41 +0800
Sid Moore <learnmost@gmail.com> wrote:
> Hi,
>
> On Linux NFS, I found a file deleted but its space not released in
> NFSv3. It is on 2.6.32.
>
> The steps for reproducing are listed below.
> 1) create a ext3 filesystem on a device, mount it to local dir
> /exports/fs1_ext3/, export /exports/fs1_ext3/ with no_subtree_check to
> a NFS client. this client mount this exported dir with infinite
> retrans.
> 2) on the ext3 fs, create a large regular file (say: 600MB)
> 3) on NFS client, starts several processes who reading this file in 2)
> in parallel
> 4) during step 3), kill all nfsd threads, umount this ext3 fs; then
> mount this ext3 to /exports/fs1_ext3; start 8 nfsd threads.
> 5) after processes finished reading, delete this file. then, I found
> the space occupied but this file not released.
>
> during step 4), I think an anonymous dentry of this file was created
> after fh_verify(). in step 5), a named dentry of this file also
> created. So, there are two dentry on this inode. but when deleting,
> only the named dentry deleted. only restart this ext3 fs or dcache
> shrinked, the anonymous dentry will not be released and it referenced
> the inode of this file. so its space not freed.
>
> is my analysis correct? anyone has encountered this issue before? or,
> this issue was fixed by someone? Thanks.
>
You may want to test a more recent kernel on the server before you dig
in too deeply. I know that Bruce has fixed a number of these sorts of
problems recently.
Cheers,
--
Jeff Layton <jlayton@redhat.com>
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: Report bug: space not released when file deleted.
2011-05-23 11:30 ` Jeff Layton
@ 2011-05-23 14:02 ` J. Bruce Fields
2011-05-24 1:40 ` Sid Moore
0 siblings, 1 reply; 4+ messages in thread
From: J. Bruce Fields @ 2011-05-23 14:02 UTC (permalink / raw)
To: Jeff Layton; +Cc: Sid Moore, linux-nfs
On Mon, May 23, 2011 at 07:30:27AM -0400, Jeff Layton wrote:
> On Mon, 23 May 2011 13:42:41 +0800
> Sid Moore <learnmost@gmail.com> wrote:
>
> > Hi,
> >
> > On Linux NFS, I found a file deleted but its space not released in
> > NFSv3. It is on 2.6.32.
> >
> > The steps for reproducing are listed below.
> > 1) create a ext3 filesystem on a device, mount it to local dir
> > /exports/fs1_ext3/, export /exports/fs1_ext3/ with no_subtree_check to
> > a NFS client. this client mount this exported dir with infinite
> > retrans.
> > 2) on the ext3 fs, create a large regular file (say: 600MB)
> > 3) on NFS client, starts several processes who reading this file in 2)
> > in parallel
> > 4) during step 3), kill all nfsd threads, umount this ext3 fs; then
> > mount this ext3 to /exports/fs1_ext3; start 8 nfsd threads.
> > 5) after processes finished reading, delete this file. then, I found
> > the space occupied but this file not released.
> >
> > during step 4), I think an anonymous dentry of this file was created
> > after fh_verify(). in step 5), a named dentry of this file also
> > created. So, there are two dentry on this inode. but when deleting,
> > only the named dentry deleted. only restart this ext3 fs or dcache
> > shrinked, the anonymous dentry will not be released and it referenced
> > the inode of this file. so its space not freed.
> >
> > is my analysis correct? anyone has encountered this issue before? or,
> > this issue was fixed by someone? Thanks.
> >
>
> You may want to test a more recent kernel on the server before you dig
> in too deeply. I know that Bruce has fixed a number of these sorts of
> problems recently.
Yes, this should be fixed by d891eedbc3b1b0fade8a9ce60cc0eba1cccb59e5,
in 2.6.38.
--b.
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: Report bug: space not released when file deleted.
2011-05-23 14:02 ` J. Bruce Fields
@ 2011-05-24 1:40 ` Sid Moore
0 siblings, 0 replies; 4+ messages in thread
From: Sid Moore @ 2011-05-24 1:40 UTC (permalink / raw)
To: J. Bruce Fields; +Cc: Jeff Layton, linux-nfs
Thanks! I will check this patch.
On Mon, May 23, 2011 at 10:02 PM, J. Bruce Fields <bfields@fieldses.org=
> wrote:
> On Mon, May 23, 2011 at 07:30:27AM -0400, Jeff Layton wrote:
>> On Mon, 23 May 2011 13:42:41 +0800
>> Sid Moore <learnmost@gmail.com> wrote:
>>
>> > Hi,
>> >
>> > On Linux NFS, I found a file deleted but its space not released in
>> > NFSv3. It is on 2.6.32.
>> >
>> > The steps for reproducing are listed below.
>> > 1) create a ext3 filesystem on a device, mount it to local dir
>> > /exports/fs1_ext3/, export /exports/fs1_ext3/ with no_subtree_chec=
k to
>> > a NFS client. this client mount this exported dir with infinite
>> > retrans.
>> > 2) on the ext3 fs, create a large regular file =A0(say: 600MB)
>> > 3) on NFS client, starts several processes who reading this file i=
n 2)
>> > in parallel
>> > 4) during step 3), kill all nfsd threads, umount this ext3 fs; the=
n
>> > mount this ext3 to /exports/fs1_ext3; start 8 nfsd threads.
>> > 5) after processes finished reading, delete this file. then, I fou=
nd
>> > the space occupied but this file not released.
>> >
>> > during step 4), I think an anonymous dentry of this file was creat=
ed
>> > after fh_verify(). in step 5), a named dentry of this file also
>> > created. So, there are two dentry on this inode. but when deleting=
,
>> > only the named dentry deleted. only restart this ext3 fs or dcache
>> > shrinked, the anonymous dentry will not be released and it referen=
ced
>> > the inode of this file. so its space not freed.
>> >
>> > is my analysis correct? =A0anyone has encountered this issue befor=
e? or,
>> > this issue was fixed by someone? Thanks.
>> >
>>
>> You may want to test a more recent kernel on the server before you d=
ig
>> in too deeply. I know that Bruce has fixed a number of these sorts o=
f
>> problems recently.
>
> Yes, this should be fixed by d891eedbc3b1b0fade8a9ce60cc0eba1cccb59e5=
,
> in 2.6.38.
>
> --b.
>
^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2011-05-24 1:40 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2011-05-23 5:42 Report bug: space not released when file deleted Sid Moore
2011-05-23 11:30 ` Jeff Layton
2011-05-23 14:02 ` J. Bruce Fields
2011-05-24 1:40 ` Sid Moore
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.