LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
* xfs used disk space bug in 2.6.38-rc1 (commit 6e857567dbbfe14dd6cc3f7414671b047b1ff5c7)
@ 2011-01-20 22:01 Alex Romosan
2011-01-21 2:25 ` Alex Romosan
2011-01-21 3:42 ` Dave Chinner
0 siblings, 2 replies; 4+ messages in thread
From: Alex Romosan @ 2011-01-20 22:01 UTC (permalink / raw)
To: linux-kernel; +Cc: xfs
my home directory is using xfs and i noticed that when i try to compile
a program or do any kind of disk access (like git pull, etc) the amount
of space used jumps by tens of gigabytes causing the disk to seemingly
become full (eventually). on reboot the used disk space goes back to the
correct value. i did a 'git bisect start -- fs/xfs' and i tracked it
down to commit 6e857567dbbfe14dd6cc3f7414671b047b1ff5c7. if i revert
this patch then disk usage doesn't increase unexpectedly (i have 270GB
free and the disk became full by simply trying to compile wine). i can
try patches if somebody comes up with one.
--alex--
--
| I believe the moment is at hand when, by a paranoiac and active |
| advance of the mind, it will be possible (simultaneously with |
| automatism and other passive states) to systematize confusion |
| and thus to help to discredit completely the world of reality. |
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: xfs used disk space bug in 2.6.38-rc1 (commit 6e857567dbbfe14dd6cc3f7414671b047b1ff5c7)
2011-01-20 22:01 xfs used disk space bug in 2.6.38-rc1 (commit 6e857567dbbfe14dd6cc3f7414671b047b1ff5c7) Alex Romosan
@ 2011-01-21 2:25 ` Alex Romosan
2011-01-21 3:42 ` Dave Chinner
1 sibling, 0 replies; 4+ messages in thread
From: Alex Romosan @ 2011-01-21 2:25 UTC (permalink / raw)
To: linux-kernel; +Cc: xfs
Alex Romosan <romosan@sycorax.lbl.gov> writes:
> my home directory is using xfs and i noticed that when i try to compile
> a program or do any kind of disk access (like git pull, etc) the amount
> of space used jumps by tens of gigabytes causing the disk to seemingly
> become full (eventually). on reboot the used disk space goes back to the
> correct value. i did a 'git bisect start -- fs/xfs' and i tracked it
> down to commit 6e857567dbbfe14dd6cc3f7414671b047b1ff5c7. if i revert
> this patch then disk usage doesn't increase unexpectedly (i have 270GB
> free and the disk became full by simply trying to compile wine). i can
> try patches if somebody comes up with one.
actually, even with that patch reverted the disk usage still creeps up
eventually so something else is not quite right.
--alex--
--
| I believe the moment is at hand when, by a paranoiac and active |
| advance of the mind, it will be possible (simultaneously with |
| automatism and other passive states) to systematize confusion |
| and thus to help to discredit completely the world of reality. |
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: xfs used disk space bug in 2.6.38-rc1 (commit 6e857567dbbfe14dd6cc3f7414671b047b1ff5c7)
2011-01-20 22:01 xfs used disk space bug in 2.6.38-rc1 (commit 6e857567dbbfe14dd6cc3f7414671b047b1ff5c7) Alex Romosan
2011-01-21 2:25 ` Alex Romosan
@ 2011-01-21 3:42 ` Dave Chinner
2011-01-21 16:05 ` Alex Romosan
1 sibling, 1 reply; 4+ messages in thread
From: Dave Chinner @ 2011-01-21 3:42 UTC (permalink / raw)
To: Alex Romosan; +Cc: linux-kernel, xfs
On Thu, Jan 20, 2011 at 02:01:45PM -0800, Alex Romosan wrote:
> my home directory is using xfs and i noticed that when i try to compile
> a program or do any kind of disk access (like git pull, etc) the amount
> of space used jumps by tens of gigabytes causing the disk to seemingly
> become full (eventually). on reboot the used disk space goes back to the
> correct value. i did a 'git bisect start -- fs/xfs' and i tracked it
> down to commit 6e857567dbbfe14dd6cc3f7414671b047b1ff5c7. if i revert
When you quote a commit, can you please include the name of the
commit. e.g:
6e85756 ("xfs: don't truncate prealloc from frequently accessed inodes")
> this patch then disk usage doesn't increase unexpectedly (i have 270GB
> free and the disk became full by simply trying to compile wine). i can
> try patches if somebody comes up with one.
I don't think you tracked the problem down to the correct commit.
The previous commit:
055388a xfs: dynamic speculative EOF preallocation
Is the one with the known bug that causes excessive preallocation
when files are zero sized. The candidate fix is here:
http://oss.sgi.com/archives/xfs/2011-01/msg00281.html
Can you see if that solves your problem?
Cheers,
Dave.
--
Dave Chinner
david@fromorbit.com
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: xfs used disk space bug in 2.6.38-rc1 (commit 6e857567dbbfe14dd6cc3f7414671b047b1ff5c7)
2011-01-21 3:42 ` Dave Chinner
@ 2011-01-21 16:05 ` Alex Romosan
0 siblings, 0 replies; 4+ messages in thread
From: Alex Romosan @ 2011-01-21 16:05 UTC (permalink / raw)
To: Dave Chinner; +Cc: linux-kernel, xfs
Dave Chinner <david@fromorbit.com> writes:
> When you quote a commit, can you please include the name of the
> commit. e.g:
>
> 6e85756 ("xfs: don't truncate prealloc from frequently accessed inodes")
>
sorry.
> Is the one with the known bug that causes excessive preallocation
> when files are zero sized. The candidate fix is here:
>
> http://oss.sgi.com/archives/xfs/2011-01/msg00281.html
>
> Can you see if that solves your problem?
i've tried it and disk usage is back to normal. thanks.
--alex--
--
| I believe the moment is at hand when, by a paranoiac and active |
| advance of the mind, it will be possible (simultaneously with |
| automatism and other passive states) to systematize confusion |
| and thus to help to discredit completely the world of reality. |
^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2011-01-21 16:05 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2011-01-20 22:01 xfs used disk space bug in 2.6.38-rc1 (commit 6e857567dbbfe14dd6cc3f7414671b047b1ff5c7) Alex Romosan
2011-01-21 2:25 ` Alex Romosan
2011-01-21 3:42 ` Dave Chinner
2011-01-21 16:05 ` Alex Romosan
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).