On Tue, Dec 16, 2008 at 02:37, Chris Mason wrote:
> On Mon, 2008-12-15 at 23:55 +0100, Kay Sievers wrote:
>> On Mon, Dec 15, 2008 at 22:03, Andreas Dilger wrote:
>> > On Dec 11, 2008 09:43 -0500, Chris Mason wrote:
>> >> The multi-device code uses a very simple brute force scan from userland
>>
On Mon, 2008-12-15 at 23:55 +0100, Kay Sievers wrote:
> On Mon, Dec 15, 2008 at 22:03, Andreas Dilger wrote:
> > On Dec 11, 2008 09:43 -0500, Chris Mason wrote:
> >> The multi-device code uses a very simple brute force scan from userland
> >> to populate the list of devices that belong to a given
On Mon, 2008-12-15 at 15:54 -0700, Joe Peterson wrote:
> Hi all, and sorry if this has been answered...
>
> Starting with kernel 2.6.28, the btrfs stable kernel module, version
> 0.16, does not compile. I maintain the Gentoo Linux ebuilds for btrfs,
> and I would very much like to retain a workin
> If multiple compression schemes are implemented how should the user go
> about choosing which one they want? Should it be done at kernel time? Or
> with the userland tools on a per file basis(maybe zlib is the default
> but a user could say I want this directory to be bzip)?
yes, why not...
doi
If multiple compression schemes are implemented how should the user go
about choosing which one they want? Should it be done at kernel time? Or
with the userland tools on a per file basis(maybe zlib is the default
but a user could say I want this directory to be bzip)?
On Mon, Dec 15, 2008 at 11:1
On Mon, Dec 15, 2008 at 22:03, Andreas Dilger wrote:
> On Dec 11, 2008 09:43 -0500, Chris Mason wrote:
>> The multi-device code uses a very simple brute force scan from userland
>> to populate the list of devices that belong to a given FS. Kay Sievers
>> has some ideas on hotplug magic to make t
Hi all, and sorry if this has been answered...
Starting with kernel 2.6.28, the btrfs stable kernel module, version
0.16, does not compile. I maintain the Gentoo Linux ebuilds for btrfs,
and I would very much like to retain a working stable btrfs as well as
unstable (which is not a problem, of co
fantastic feature!
i`m curious: can btrfs support more than one compression scheme at the same
time, i.e. is compression "pluggable" ?
lzo compression coming to my mind, as this is giving real-time compession and
may even speed up disk access.
compression ratio isn`t too bad, but speed is awes
On Dec 11, 2008 09:43 -0500, Chris Mason wrote:
> The multi-device code uses a very simple brute force scan from userland
> to populate the list of devices that belong to a given FS. Kay Sievers
> has some ideas on hotplug magic to make this less dumb. (The scan isn't
> required for single devic
On Mon, 2008-12-15 at 11:01 -0800, Sage Weil wrote:
> Hi-
>
> I've been regularly getting a lockdep warning on inode_lock vs tree->lock.
> It is quickly triggered by my code, which calls ioctl(fd, BTRFS_IOC_SYNC)
> (which just does a btrfs_sync_fs) at regular intervals.
>
> http://ceph.n
On Sun, 2008-12-14 at 00:16 +0100, devz...@web.de wrote:
> Hello !
>
> is there a way to get btrfs-unstable source without using git ?
>
> i`m trying for a while now, but it seems git doesn`t work as desired on my
> system or the problem is that i`m behind http proxy.
>
> what about some unstab
On Mon, 2008-12-15 at 11:01 -0800, Sage Weil wrote:
> Hi-
>
> I've been regularly getting a lockdep warning on inode_lock vs tree->lock.
> It is quickly triggered by my code, which calls ioctl(fd, BTRFS_IOC_SYNC)
> (which just does a btrfs_sync_fs) at regular intervals.
>
> http://ceph.n
Hi-
I've been regularly getting a lockdep warning on inode_lock vs tree->lock.
It is quickly triggered by my code, which calls ioctl(fd, BTRFS_IOC_SYNC)
(which just does a btrfs_sync_fs) at regular intervals.
http://ceph.newdream.net/dump/btrfs-lockdep-sync-ioctl.txt
The second warnin
On Thu, 2008-12-04 at 17:59 -0500, Eric Whitney wrote:
> Chris:
>
> I'm consistently getting oopses when running fsstress against both
> single and multiple device compressed btrfs filesystems using kernels
> built from the current btrfs-unstable.
>
> In this report, I'm describing an incident
14 matches
Mail list logo
