Re: btrfs ways to travel back in time

> atime). Also, this might break some configurations not expecting the > set-default method I have never seen this before. Can you extend on this or provide a link so i can read more about such limitation? > > > 2. reboot > > b) always mount into snapshot > > 1. mount -o suvol=/.current $disk #

btrfs ways to travel back in time

I can think of few ways to revert changes with btrfs, but I wonder what are the trade-offs between each method and perhaps there is already research done on this? ways to restore a snapshot ( post kernel 3.* ): a) via set-default 1. btrfs subvolume set-default / $id 2. reboot b) always mount

btrfs-progs: btrfs convert v2

Hi Qu, thanks for your work on btrfs convert. Does your btrfs convert work ( namely https://www.spinics.net/lists/linux-btrfs/msg49719.html patches ) change any caveats described here -> https://btrfs.wiki.kernel.org/index.php/Conversion_from_Ext3#Before_first_use i.e. does larger than 1 gb

upgrading kernel 3.13 to 3.16

Hi all, Are there any known issues upgrading btrfs running ubuntu kernel 3.13 to 3.16 ? System was once converted from ext4 using btrfs-convert ( btrfs-progs 3.17 ). The commit that worries me is following: * Btrfs: incompatible format change to remove hole extents (+373/-56) (

Re: Ideas for btrfs-convert fix(or rework)

[ resending as it didnt get through. ] I got different opinion. btrfs-convert is something that brought me to btrfs. While there are other bugs to fix, someone dedicating time to fix btrfs-convert is of high interest to me. Sending right message to community, might make some rolling distros to

Re: Btrfs progs release 4.1

sorry for side question - but does this mean that btrfs-convert issues others were having on kernel 4.0+ on this mailing list is now addressed ? On Wed, Sep 9, 2015 at 4:24 AM, Qu Wenruo wrote: > > > Qu Wenruo wrote on 2015/09/09 09:34 +0800: >> >> Hi David, >> >> Sorry

Re: btrfs partition converted from ext4 becomes read-only minutes after booting: WARNING: CPU: 2 PID: 2777 at ../fs/btrfs/super.c:260 __btrfs_abort_transaction+0x4b/0x120

Slightly off topic does these bugs exist in systems that converted from ext4 to btrfs using kernel 3.13 and then upgraded to kernel 4.1 ? On Thu, Jul 9, 2015 at 4:09 AM, Chris Murphy li...@colorremedies.com wrote: On Thu, Jun 25, 2015 at 8:08 PM, Qu Wenruo quwen...@cn.fujitsu.com wrote: A

Re: btrfs partition converted from ext4 becomes read-only minutes after booting: WARNING: CPU: 2 PID: 2777 at ../fs/btrfs/super.c:260 __btrfs_abort_transaction+0x4b/0x120

That's unfortunate. Many users, including me, started using btrfs by converting from ext4. I hope this gets fixed. Vytas On Thu, Jun 25, 2015 at 5:16 AM, Marc MERLIN m...@merlins.org wrote: On Thu, Jun 18, 2015 at 02:05:04PM +0300, Robert Munteanu wrote: On Wed, Jun 17, 2015 at 8:46 PM, Marc

Re: [newb] move /home to subvolume

as far as I know, you can't do this, you need to temporary move /home somewhere else, create /home subvolume and copy everything back. - Vytas On Mon, Jun 1, 2015 at 1:36 PM, Neal Becker ndbeck...@gmail.com wrote: I have everything under /: sudo btrfs subvolume list / ID 257 gen 65795 top

rolling back to ext4 doesn't work if rebalanced

Is it possible to automate btrfs-convert so that it would defrag and balance the disk without loosing ability to roll back to ext4 partition ? i.e: btrfs-convert /dev/sda3 # I can still rollback using btrfs-convert -r /dev/sda3 btrfs filesystem defrag -r / # I can still rollback using