Since the addition of the latest round of ENOSPC fixes, I wanted to
provide some feedback on problems I was having compiling OpenOffice on
a btrfs partition.
I had posted a while back that I would encounter ENOSPC bugs before
filling up the disk when compiling OpenOffice.
I have retested with
I believe you mean 2.6.30-rc2
On Mon, Apr 20, 2009 at 3:32 PM, Chris Mason chris.ma...@oracle.com wrote:
Hello everyone,
I've updated the unstable tree to 2.6.29-rc2 and pushed out some of the
pending fixes. This has my current fixes for fsync latency, which make
btrfs behave much better
, Mitch Harder (aka DontPanic) wrote:
I've been creating a local git repository of full btrfs-unstable sources.
I'll create a new branch off the master branch, and apply the patch
supplied in the Feb. 11 message to the M/L.
I then create a kernel module based on the results in /fs/btrfs
I have also been getting similar warnings filling up my logs.
However, in my case, I have been experimenting with back-porting btrfs
to a 2.6.28 kernel. So I've been waiting for the back-porting efforts
to get a little further along.
But I thought I'd respond in case this information helps.
I've generated another allocation error with the debugging patch installed.
In order to get a better idea of disk usage around the period of the
allocation errors, I made up a bash script to dump 'df -T
/var/tmp/portage' every 3 seconds to the terminal (where my btrfs
drive is mounted at
Some Follow-Up:
Just to ease my mind, I ran 7 iterations of a destructive badblocks
test on the partition I've been using without error ('badblocks -sw -t
random -p 7 /dev/sdc2').
On Mon, Nov 17, 2008 at 10:08 PM, Mitch Harder (aka DontPanic)
[EMAIL PROTECTED] wrote:
I've generated another
I tested this patch by compiling OpenOffice on a 3.5 GB partition
using compression.
I am still getting an allocation error at the very end of the build
process when trying to delete the work files once the compilation
completed and installed successfully.
The FETCH_HEAD that I applied the patch
