Xavier Gnata posted on Sat, 17 Oct 2015 18:36:32 +0200 as excerpted:
> Hi,
>
> On a desktop equipped with an ssd with one 100GB virtual image used
> frequently, what do you recommend?
> 1) nothing special, it is all fine as long as you have a recent kernel
> (which I do)
> 2) Disabling
Btrfs has changed to delete subvolume/snapshot asynchronously, which means that
after umount itself, if we've already deleted 'ext2_saved', rollback can still
be completed.
So this adds a check for ROOT_BACKREF before checking ROOT_ITEM since
ROOT_BACKREF is immediately not in the btree after
Just following up - the replace operation completed successfully and then the
source device (/dev/sdb) was removed, with all chunks moved on the target
(/dev/sdj). Putting it down to RAID level complexities I guess.
[root@array ~]# btrfs replace status -1 /export/archive/
Started on 15.Oct
On Sat, Oct 17, 2015 at 08:44:35AM +1100, Dave Chinner wrote:
>
> > When we're doing writes, it'll check the preallocated extents for extra
> > refs and force COW if any exist. So writes into a preallocated region
> > can enospc.
>
> This really seems like an btrfs interpretation/implementation
Hi,
On a desktop equipped with an ssd with one 100GB virtual image used
frequently, what do you recommend?
1) nothing special, it is all fine as long as you have a recent kernel
(which I do)
2) Disabling copy-on-write for just the VM image directory.
3) autodefrag as a mount option.
4)
