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

[Marc MERLIN <marc@merlins.org>]

On Thu, Jun 25, 2015 at 08:17:12PM +0000, Ruslanas Gžibovskis wrote:
> nope. started from scratch! never upgrade from old running fs. Better to
> move 1 file and extend , move another files, extend and so on then just
> convert... It's like moving from windows and only boot partition to have on
> ext2 and other system on ntfs... all my friends do the same. And by the way
> does anyone still use ext3/4? isn't it dead?  Even rhel now goes with
> default xfs...

Yes, plenty of people use ext4, it's not dead :)
It also just added built in encryption in the filesystem, which no other
filesystem has AFAIK.

Due to how btrfs works with block layouts, it shouldn't be hard to encrypt
blocks as they are written just like they can be compressed currently, but
no one has sponsored that work yet.
Because Google uses ext4 and they (we) care about encrypting data to
protect user data from things like possible hardware theft or maybe even
a datacenter being raided in some country, that's how ext4 got encryption
built in.

Marc
-- 
"A mouse is a device used to point at the xterm you want to type in" - A.S.R.
Microsoft is to operating systems ....
                                      .... what McDonalds is to gourmet cooking
Home page: http://marc.merlins.org/