On 24. January 2011 - 13:13, Hugo Mills wrote:
Date: Mon, 24 Jan 2011 13:13:41 +
From: Hugo Mills hugo-l...@carfax.org.uk
To: Felix Blanke felixbla...@gmail.com
Cc: kreij...@inwind.it, Hugo Mills hugo-l...@carfax.org.uk,
linux-btrfs@vger.kernel.org
Subject: Re: Bug in mkfs.btrfs?!
On Mon, Jan 24, 2011 at 02:29:36PM +, Hugo Mills wrote:
If, instead, the initial losetup call tracked the symlinks back to
the original device node (i.e. something like /dev/sdb3, or
/dev/mapper/ruthven-btest in my example), then the name that's
stored in the kernel would be shorter,
On Mon, Jan 24, 2011 at 02:53:05PM +0100, Felix Blanke wrote:
On 24. January 2011 - 13:13, Hugo Mills wrote:
On Mon, Jan 24, 2011 at 02:01:04PM +0100, Felix Blanke wrote:
Hi,
you were talking about the LOOP_GET_STATUS function. I'm not quite sure
where does it
came
On Mon, Jan 24, 2011 at 02:29:36PM +, Hugo Mills wrote:
If, instead, the initial losetup call tracked the symlinks back to
the original device node (i.e. something like /dev/sdb3, or
/dev/mapper/ruthven-btest in my example), then the name that's
stored in the kernel would be
util-linux-2.18-r1 and still no symlink following.
I'll ask for that at the kernel mailing list in the next days. If your (Hugo)
util-linux doesn't include any kind of patches that behaviour is really strange.
Felix
On 24. January 2011 - 15:44, Felix Blanke wrote:
Date: Mon, 24 Jan 2011
On Sat, Jan 22, 2011 at 5:45 AM, Hugo Mills hugo-l...@carfax.org.uk wrote:
On Fri, Jan 21, 2011 at 11:28:19AM -0800, Freddie Cash wrote:
So, is Btrfs pooled storage or not? Do you throw 24 disks into a
single Btrfs filesystem, and then split that up into separate
sub-volumes as needed?
Defragmentation is not working when a directory is supplied as the
argument. When a file name is supplied as the argument,
defragmentation works well.
This can be demonstrated as follows:
# mount /dev/sdb2 /mnt/btrfs
# cd /mnt/btrfs/
# cp /usr/src/linux/fs/btrfs/zlib.c .(any suitable file
On Monday, January 24, 2011 19:11:07 Mitch Harder wrote:
Defragmentation is not working when a directory is supplied as the
argument. When a file name is supplied as the argument,
defragmentation works well.
This can be demonstrated as follows:
# mount /dev/sdb2 /mnt/btrfs
# cd
Hi,
it is getting interesting :)
If I'm using the debian util-linux (with the patches) I'm getting an error while
executing losetup:
ioctl: LOOP_SET_STATUS: Invalid argument
Now the interesting part: The strace of the debian util-linux shows:
readlink(/dev, 0x7fffcea2a0a0, 4096) = -1
If gentoo is configured for using loop-aes, a patch is applied:
http://loop-aes.sourceforge.net/updates/util-linux-ng-2.17.1-20100308.diff.bz2
Debian doesn't seem to apply that patch, therefore I'm getting that ioctl error
and
can't loop my encrypted devices.
Now everything does make sense :)
We were failing xfstests 224 by either hanging or failing to remove files.
These patches fix it so that we can now pass 224. The first patch is obvious,
and the 2nd one is as well, but the 3rd one could use a good hard look. Thanks,
Josef
--
To unsubscribe from this list: send the line
When we do btrfs_block_rsv_release, if global_block_rsv is not full we will
release all the extra bytes to global_block_rsv, even if it's only a little
short of the amount of space that we need to reserve. This causes us to starve
ourselves of reservable space during the transaction which will
When running xfstests 224 I kept getting ENOSPC when trying to remove the files,
and this is because we were returning ret from check_path_shared while it was
uninitalized, which isn't right. Fix this to return 0 properly, and now
xfstests 224 doesn't freak out when it tries to clean itself up.
Hello,
I recently migrated my system to btrfs on two drives (spinning)
configured as raid1. When writing to this filesystem, the system shows
some weird behaviour: it starts off with writing to both drives
simultaneously for a few seconds, but after that it starts writing to
the drives one
On 25/01/11 08:39, Helmut Hullen wrote:
Regard the difference between df and btrfs filesystem df.
I suspect this is fixed in 2.6.38 with the following commit.
BE WARNED: there are some fairly hairy changes to the pathname
lookup code to replace the BKL with RCU (not specific to btrfs)
and so
The error check of btrfs_join_transaction()/btrfs_join_transaction_nolock()
is added, and the mistake of the error check in several places is
corrected.
For more stable Btrfs, I think that we should reduce BUG_ON().
But, I think that long time is necessary for this.
So, I propose this patch as a
Hi,
I am using 2.6.36.3 kernel with btrfs, 512MB memory and a very slow
disk, no special options for mounting btrfs except noatime. Now I
found it very slow. When I rm a 5GB movie, it took 20 secs.
--
竹密岂妨流水过
山高哪阻野云飞
--
To unsubscribe from this list: send the line unsubscribe linux-btrfs in
the
Hallo, Chris,
Du meintest am 25.01.11:
Regard the difference between df and btrfs filesystem df.
I suspect this is fixed in 2.6.38 with the following commit.
[...]
Looks good - I'll take a try.
Viele Gruesse!
Helmut
--
To unsubscribe from this list: send the line unsubscribe linux-btrfs in
18 matches
Mail list logo
