Re: Fwd: btrfs replace seems to corrupt the file system

On 06/27/2015 06:17 PM, Mordechay Kaganer wrote: B.H. Hello. I'm running our backup archive on btrfs. We have MD-based RAID5 array with 4 6TB disks then LVM on top of it, and btrfs volume on the LV (we don't use btrfs's own RAID features because we want RAID5 and as far as i understand the sup

Fwd: btrfs replace seems to corrupt the file system

B.H. Hello. I'm running our backup archive on btrfs. We have MD-based RAID5 array with 4 6TB disks then LVM on top of it, and btrfs volume on the LV (we don't use btrfs's own RAID features because we want RAID5 and as far as i understand the support is only partial). I wanted to move the archive

Re: [PATCH 5/5] btrfs: don't update mtime on deduped inodes

On Fri, Jun 26, 2015 at 02:01:01PM -0700, Mark Fasheh wrote: > One issue users have reported is that dedupe changes mtime on files, > resulting in tools like rsync thinking that their contents have changed when > in fact the data is exactly the same. Clone still wants an mtime change, so > we speci

Re: kernel 4.1: no space left on device

Am 27.06.2015 um 17:51 schrieb Roman Mamedov: On Sat, 27 Jun 2015 17:32:04 +0200 Stefan Priebe wrote: Hi, while having some big btrfs volumes (44TB + 37TB). I see on a regular basis the "no space left on device" message. I'm only able to "fix" this. By running btrfs balance AND unmounting an

Re: kernel 4.1: no space left on device

On Sat, 27 Jun 2015 17:32:04 +0200 Stefan Priebe wrote: > Hi, > > while having some big btrfs volumes (44TB + 37TB). > > I see on a regular basis the "no space left on device" message. I'm only > able to "fix" this. By running btrfs balance AND unmounting and > remounting the btrfs volume. >

Re: kernel 4.1: no space left on device

On 06/27/2015 10:32 AM, Stefan Priebe wrote: Hi, while having some big btrfs volumes (44TB + 37TB). I see on a regular basis the "no space left on device" message. I'm only able to "fix" this. By running btrfs balance AND unmounting and remounting the btrfs volume. Is there any way to deb

kernel 4.1: no space left on device

Hi, while having some big btrfs volumes (44TB + 37TB). I see on a regular basis the "no space left on device" message. I'm only able to "fix" this. By running btrfs balance AND unmounting and remounting the btrfs volume. Is there any way to debug / workaround this one? Greets, Stefan -- To

Re: Send/Receive Use Case

ok i’ll go home and rethink my life then ;) > On Jun 27, 2015, at 10:21 AM, Hugo Mills wrote: > > On Sat, Jun 27, 2015 at 10:04:28AM -0400, Vincent Olivier wrote: >> Hi, >> >> There are 4 things I’m not sure about re:send/receive. >> >> 1) Is it possible to first copy things on a file system u

Re: Send/Receive Use Case

On Sat, Jun 27, 2015 at 10:04:28AM -0400, Vincent Olivier wrote: > Hi, > > There are 4 things I’m not sure about re:send/receive. > > 1) Is it possible to first copy things on a file system using rsync and then > use send-receive ? And to subsequently mix rsync and send-receive ? Provided > tha

Re: Send/Receive Use Case

Hi, Le samedi 27 juin 2015 10:04:28 Vincent Olivier a écrit : > > There are 4 things I’m not sure about re:send/receive. > > 1) Is it possible to first copy things on a file system using rsync and then > use send-receive ? NO. You need to start with a BTRFS snapshot send/receive to be able to

Send/Receive Use Case

Hi, There are 4 things I’m not sure about re:send/receive. 1) Is it possible to first copy things on a file system using rsync and then use send-receive ? And to subsequently mix rsync and send-receive ? Provided that snapshots are made accordingly. 2) Is possible to “send" a snapshot diff to

Re: [PATCH 0/2] btrfs device remove alias

On 2015-06-26 15:33, David Sterba wrote: > On Fri, Jun 26, 2015 at 09:10:56AM +0800, Anand Jain wrote: >> while on this. its also good idea to create alias for >> >>btrfs replace start -> btrfs device replace. > > This was asked for back then, and briefly discussed on irc (11/2012). > The pref