On Mon, September 03, 2012 at 18:31 (+0200), Suman C wrote:
I am trying to integrate the quota patch from August 10th by Jan
Schmidt and getting conflicts when I git apply.
I've rebased it on top of Chris' current master, you can pull from
git://git.jan-o-sch.net/btrfs-progs qgroup
if
Hi list,
OpenSVC = 120904.1516 now contains a replication driver for the btrfs
send/receive mecanism. This new driver adds up to the zfs, rsync, dds,
netapp, datacore and drbd existing drivers.
It is no more mature than btrfs send/receive itself, so don't use in
production clusters for now.
On Tue, Sep 04, 2012 at 08:23:20AM -0600, Christophe Varoqui wrote:
Hi list,
OpenSVC = 120904.1516 now contains a replication driver for the btrfs
send/receive mecanism. This new driver adds up to the zfs, rsync, dds,
netapp, datacore and drbd existing drivers.
It is no more mature than
On Tue, Sep 04, 2012 at 03:23:13AM -0600, Jan Schmidt wrote:
On Mon, September 03, 2012 at 18:31 (+0200), Suman C wrote:
I am trying to integrate the quota patch from August 10th by Jan
Schmidt and getting conflicts when I git apply.
I've rebased it on top of Chris' current master, you can
This message is more explicit than ERROR: could not resolve root_id,
the message that will be shown immediately before `btrfs send` bails.
Also skip invalid high OIDs.
Signed-off-by: Gabriel de Perthuis g2p.code+bt...@gmail.com
---
send-utils.c | 6 ++
1 file changed, 6 insertions(+)
diff
On Tue, Sep 04, 2012 at 06:07:50PM +0200, Petr Tichý wrote:
I have a 130 GB btrfs with rsnapshot-like backups mounted with
compressoin=zlib and now I'm getting ENOSPC, while df shows only
some 60 % used. I'm running Linux version 3.2.0-3-amd64 (Debian
3.2.23-1). Is my btrfs really full? Will a
Here are the stacks encountered during the opensvc btrfs send/receive
development.
The system is a debian squeeze amd64 in a kvm over debian squeeze amd64.
The disks handed to btrfs are logical volumes passed to the kvm as vdb
and vdc. The vm kernel is 3.6rc3 and btrfs-progs are at git commit
Hi,
On 09/02/2012 03:03 AM, Shentino wrote:
This whole subject was also about using sed to corrupt-o-magic a
file's data on disk.
Is this an acceptable method for testing?
I am not sure that doing sed /dev/sdX /dev/sdX ... is the right
thing to do, because it rewrites the full disk. This
On Tue, Sep 04, 2012 at 11:26:34AM -0600, Christophe Varoqui wrote:
Here are the stacks encountered during the opensvc btrfs send/receive
development.
The system is a debian squeeze amd64 in a kvm over debian squeeze amd64.
The disks handed to btrfs are logical volumes passed to the kvm as
On Tue, Sep 4, 2012 at 11:15 AM, Goffredo Baroncelli kreij...@libero.it wrote:
Hi,
On 09/02/2012 03:03 AM, Shentino wrote:
This whole subject was also about using sed to corrupt-o-magic a
file's data on disk.
Is this an acceptable method for testing?
I am not sure that doing sed
On Tue, September 04, 2012 at 18:40 (+0200), Gabriel de Perthuis wrote:
This message is more explicit than ERROR: could not resolve root_id,
the message that will be shown immediately before `btrfs send` bails.
Also skip invalid high OIDs.
Signed-off-by: Gabriel de Perthuis
On 09/05/2012 03:59 AM, Shentino wrote:
I am not sure that doing sed/dev/sdX/dev/sdX ... is the right thing to
do, because it rewrites the full disk. This means that:
- it takes a lot of time
- you don't have any control about which part of the disk you change: what
happens if sed
12 matches
Mail list logo
